Source:SEP sesam DataMover: Difference between revisions

From SEPsesam
Line 44: Line 44:


=== Prerequisites ===
=== Prerequisites ===
* Operating system MS Windows or Linux
{{:Hardware_requirements/en}}
* 2 GB main memory
* A installed SEP sesam component (Sesam server, RDS or client).  A regular path backup has to work.
* A installed SEP sesam component (Sesam server, RDS or client).  A regular path backup has to work.


=== Function ===
=== 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).
When Citrix XenServer are organized in pools, the Sesam DataMover (SDM-CX) has to 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 [[http://wiki.sepsoftware.com/wiki/index.php/Citrix_XEN_Server_en here]]
More detailed information about the functionality, you can get [[http://wiki.sepsoftware.com/wiki/index.php/Citrix_XEN_Server_en here]]


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

Revision as of 12:42, 10 May 2017

Template:Copyright SEP AG en


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). This role tells the Sesam server that the original client can only be reached by sending the request to the DataMover. 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 NetApp (SDM-NA)


SEP sesam DataMover for VMware vSphere (SDM-VV)

Prerequisites

  • Supported operating systems:
    • MS Windows Server 2008/2012 [R2] 64-bit
    • Linux (from SEP sesam v. 4.4 or higher): SLES 11 64-bit SP1 and SP2, SLES 10 64-bit SP4, RHEL 5.9 64-bit, RHEL 6.2 64-bit, RHEL 6.3 64-bit, RHEL 6.4 64-bit. For details, check VMware home page for supported operating systems.
  • 4 GB main memory
  • 50 GB hard disk
  • Any of the following SEP sesam components must be installed: SEP sesam Server, RDS or client.
  • A regular path backup has to work.
  • VMware VDDK must be installed on the data mover. For details, see VMware Requirements & Restrictions.

Recommendation

Based on a VMware VDDK restriction, the SEP sesam DataMover (SDM-VV) should run on a physical machine and not on a VM. If the SDM-VV operates on a VM, it is not possible to backup a virtual machine that runs on the same ESXi hypervisor and is stored on the same VMware data store as the SEP sesam DataMover.

Function

To request the VMware farm information, the SEP sesam Server usually connects to the central vCenter server. All control tasks are handled there:

  • From which objects have the VM?
  • On which ESXi hypervisor is the VM running?
  • Creating and removing 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 Sesam DataMover from the corresponding ESXi server and transported to the media server (SEP sesam Server or RDS).

If the 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).

For more details, see VMware Requirements & Restrictions.

SEP sesam DataMover for Citrix XenServer (SDM-CX)

Prerequisites

Hardware requirements/en

  • 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) has to 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]


SEP sesam DataMover for NetApp (SDM-NA)

Prerequisites

  • SEP Sesam Server with version at least 4.2.1.x
  • The SEP Sesam server must be installed on a Linux system
  • The NetApp system must be reachable over its Web API (http://www.netapp.com/us/products/management-software/) and remote management must be possible via HTTP FilerView (Netapp FilerView: http://filer/na_admin/)
  • The backup server must have proper rights to mount the volumes to be backed up locally
  • Password and Username of the NetApp system

Function

The SDM-NA makes it possible to access the NetApp Storage API to read and control volumes and snapshots. More details see [here]