Source:SEP sesam DataMover: Difference between revisions

From SEPsesam
No edit summary
(Corrected Novell to Micro Focus.)
(34 intermediate revisions by 3 users not shown)
Line 1: Line 1:
(C)SEP AG
<translate><!--T:1-->
<div class="noprint"><languages />
{{Copyright SEP AG en}}


Copyright 1999-2012 by SEP AG. All Rights reserved.
<!--T:2-->
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/SEP_sesam_Documentation#previous|Documentation archive]]}}</div>


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.


== Overview == <!--T:3--></translate>
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>
<translate><!--T:4-->
Additional resources</translate></b></center>


== Definition ==
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
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.
| rowspan="2" style="padding:0px 10px 0px;" |<translate>
<!--T:5-->
[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_sesam_Components|SEP sesam Components]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>
<!--T:6-->
See also: [[Special:MyLanguage/SEP_sesam_Components|SEP sesam Components]]</translate>
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | <translate>
<!--T:7-->
[[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>
<!--T:8-->
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.</translate>
|}


== DataMover Types ==
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
* SEP sesam DataMover for VMware vSphere (SDM-VV)
| rowspan="2" style="padding:0px 10px 0px;" | <translate>
* SEP sesam DataMover for Citrix XenServer (SDM-CX)
<!--T:9-->
* SEP sesam DataMover for Novell Services (SDM-NS)
[[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>
<!--T:10-->
Problems? See the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].</translate>
|}</div>
<translate><!--T:11-->
SEP sesam [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover]] is a functional role allowing access to a third-party software API or to redirect data stream to a SEP sesam server/remote device server. It tells the SEP sesam Server that the original client can only be reached by sending the request to the data mover. A data mover role can be combined either with a [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]], [[Special:MyLanguage/SEP_sesam_Glossary#RDS|SEP sesam Remote Device Server]] or a [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]]. Which SEP sesam component is possible for combination depends on a third-party software.


== General requirements == <!--T:12--></translate>
<translate><!--T:13-->
{{:Hardware requirements/en}}</translate>


== SEP sesam DataMover for VMware vSphere (SDM-VV) ==
<translate>== Data mover types == <!--T:14--></translate>
* <translate><!--T:15-->
[[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#VMware|SEP sesam data mover for VMware vSphere (SDM-VV)]]</translate>
* <translate><!--T:16-->
[[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#Citrix|SEP sesam data mover for Citrix XenServer (SDM-CX)]]</translate>
* <translate><!--T:17-->
[[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#Novell|SEP sesam data mover for Micro Focus (previously Novell) services (SDM-NS)]]</translate>
* <translate><!--T:18-->
[[Special:MyLanguage/What_is_a_SEP_sesam_DataMover#NetApp|SEP sesam data mover for NetApp (SDM-NA)]]


=== Voraussetzungen ===
== {{anchor|VMware}}SEP sesam data mover for VMware vSphere (SDM-VV) == <!--T:19--></translate>
* Operating system MS Windows Server 2003/2008 [R2]
<translate><!--T:20-->
* In the upcoming SEP sesam version 4.2 a SDM-VV on Linux will be supported !!
{{:Template:Data mover VMware vSphere/en}}
* 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 ===
<!--T:21-->
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).
For details, see [[Special:MyLanguage/4_4_3:VMware_Requirements_&_Restrictions|VMware Requirements & Restrictions]].


=== Function ===
== {{anchor|Citrix}}SEP sesam data mover for Citrix XenServer (SDM-CX) == <!--T:22--></translate>
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:
<translate><!--T:23-->
* From which objects have the VM ?
{{:Template:Data mover Citrix XenServer/en}}
* 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).
<!--T:24-->
For details, see [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration|Citrix XenServer Requirements and Configuration]].


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).
== {{anchor|Novell}}SEP sesam data mover for Micro Focus (Novell) services (SDM-NS) == <!--T:25--></translate>
<translate><!--T:26-->
{{:Template:Data mover Novell/en}}


<!--T:27-->
For details on SDM-NS functionality, see [[Special:MyLanguage/Backup_principles_using_SEP_sesam_in_a_Micro_Focus_OES_environment|Micro Focus documentation]].


== SEP sesam DataMover for Citrix XenServer (SDM-CX) ==
== {{anchor|NetApp}}SEP sesam data mover for NetApp (SDM-NA) == <!--T:28--></translate>
<translate><!--T:29-->
{{:Template:Data mover NetApp/en}}


=== Voraussetzungen ===
<!--T:30-->
* Operating system MS Windows or Linux
For details, see [[Special:MyLanguage/Netapp_en#Prerequisites|NetApp documentation]].
* 2 GB main memory
* A installed SEP sesam component (Sesam server, RDS or client). A regular path backup has to work.


=== Funktion ===
<div class="noprint">
Sind mehrere Citrix XenServer in einem Pool organisiert, dann sollte der DataMover immer direkt mit dem Pool-Master kommunizieren. Der Pool-Master teilt dem DataMover beim Start des Backup mit, auf welchem Citrix XenServer die VM aktuell läuft und stößt automatisch ein einen KOmmunilationwechsel zum entsprechenden Citrix XenServer an (Mapping).
==See also== <!--T:31-->
 
[[Special:MyLanguage/SEP_sesam_Components|SEP sesam Components]]</div></translate>
 
== * SEP sesam DataMover für Novell Services (SDM-NS) ==
 
=== Voraussetzungen ===
* Betriebssystem Novell OES2 Linux oder Novell OES11. Es muss kein eDirectory oder ein anderer Novell Dienst auf dieser Maschine installiert sein. Nur die Novell SMS-Komponenten (SMDR, TSAs) werden benötigt.
* 2 GB Hauptspeicher
* Eine Sesam Komponente (Client, RDS oder Sesam Server) muss installiert sein. Ein Pfad-Backup muss möglich sein.
* Sesam Novell Client muss installiert sein
 
=== Funktion ===
Detailiertere Information über die Funktion erhalten Sie [[http://wiki.sepsoftware.com/wiki/index.php/Sicherungsprinzip_mit_SEP_sesam_in_einer_Novell_OES_Umgebung hier]]

Revision as of 13:53, 16 June 2020

Other languages:

Template:Copyright SEP AG en

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check Documentation archive.


Overview

SEP sesam data mover is a functional role allowing access to a third-party software API or to redirect data stream to a SEP sesam server/remote device server. It tells the SEP sesam Server that the original client can only be reached by sending the request to the data mover. A data mover role can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client. Which SEP sesam component is possible for combination depends on a third-party software.

General requirements

Hardware requirements/en

Data mover types

SEP sesam data mover for VMware vSphere (SDM-VV)

Template:Data mover VMware vSphere/en

For details, see VMware Requirements & Restrictions.

SEP sesam data mover for Citrix XenServer (SDM-CX)

Template:Data mover Citrix XenServer/en

For details, see Citrix XenServer Requirements and Configuration.

SEP sesam data mover for Micro Focus (Novell) services (SDM-NS)

Template:Data mover Novell/en

For details on SDM-NS functionality, see Micro Focus documentation.

SEP sesam data mover for NetApp (SDM-NA)

Template:Data mover NetApp/en

For details, see NetApp documentation.