Source:SEP sesam DataMover

From SEPsesam
Revision as of 10:36, 21 August 2012 by Hg (talk | contribs)

(C)SEP AG

Copyright 1999-2012 by SEP AG. All Rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.


Definition

A SEP sesam DataMover is a functional role, which allows an access to a 3rd party software API. This DataMover role can be combined with a SEP sesam component (Sesam server, RDS or client). Which Sesam component is possible for combination depends on 3rd party software. Hereinafter the existing Sesam DataMovers are described.


DataMover Types

  • SEP sesam DataMover for VMware vSphere (SDM-VV)
  • SEP sesam DataMover for Citrix XenServer (SDM-CX)
  • SEP sesam DataMover for Novell Services (SDM-NS)


SEP sesam DataMover for VMware vSphere (SDM-VV)

Prerequisites

  • Operating system MS Windows Server 2003/2008 [R2]
  • In the upcoming SEP sesam version 4.2 a SDM-VV on Linux will be supported !!
  • 4GB main memory
  • 50 GB harddisk
  • A SEP sesam component (Sesam server, RDS or client) must be installed. A regular path backup has to work.
  • Installation of the VMware VDDK version 5.0

Recommendation

Based on a VMware VDDK restriction, the SDM-VV should run on a physical machine not on a VM. When the SDM-VV operates on a VM, it is not possible to backup a VM, which runs on the same ESXi hypervisor and is stored on the same VMware Datastore like the Sesam DataMover (SDM-VV).

Function

To request of the VMware farm inforamtion, the SEP sesam server connects usually to the central vCenter server. All control tasks will be handled there:

  • From which objects have the VM ?
  • On which ESXi hypervisor the VM is running ?
  • Create and remove of VM snapshots

When all preparatory activities for backup or restore are completed with the vCenter server, the actual VM data will be picked up by the VMware VDDK the Sesam DataMover from the corresponding ESXi server and transport to the media server (Sesam server or RDS).

If the Sesam DataMover (SDM-VV) has access to the same SAN LUNs that sees the ESXi hypervisor, and the SDM-VV works on a SEP Sesam SAN Remote Device Server (SAN-RDS) component, then on the SDM-VV, the data of the VM can be transported directly from the central storage to the storage device (LAN-free).

More detailed information about the functionality, you can get [here]


SEP sesam DataMover for Citrix XenServer (SDM-CX)

Prerequisites

  • Operating system MS Windows or Linux
  • 2 GB main memory
  • A installed SEP sesam component (Sesam server, RDS or client). A regular path backup has to work.

Function

When Citrix XenServer are organized in pools, the Sesam DataMover (SDM-CX) should always communicate directly with the pool master. At the backup starts, the pool master tells the SDM-CX on which Citrix XenServer the VM is located and force a communication switch to the appropriate Citrix XenServer (mapping).

More detailed information about the functionality, you can get [here]


* SEP sesam DataMover for Novell Services (SDM-NS)

Prerequisites

  • Operating system Novell OES2 Linux or Novell OES11. No eDirectory or another Novell Service hast to be installed on that machine. Only the Novell SMS components (SMDR, TSAs) will be required.
  • 2 GB main memory
  • An installed SEP sesam component (Sesam server, RDS or client). A regular path backup has to work.
  • The Sesam Novell client haas to be installed

Function

More detailed information about the functionality, you can get [here]