What is a SEP sesam DataMover

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2019. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Grolar. 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

The following are the hardware requirements for the SEP sesam Server or RDS. They are similar for both, except in that the space for the SEP sesam database required on the file system is not necessary for RDS.

The hardware requirements for the SEP sesam Server or RDS represent the common requirements. Additional amount of RAM/CPU may be required for bigger Si3 data stores. For details, see Si3 Deduplication Hardware Requirements.

Requirements SEP sesam Server Standard edition SEP sesam Advanced Server edition SEP sesam Premium Server edition SEP sesam Enterprise Server
Memory (without Si3 deduplication) 8 GB RAM Minimum 16 GB RAM 32 GB RAM Minimum 64 GB RAM
Memory (with Si3 deduplication) Minimum 16 GB RAM Minimum 32 GB RAM 64 GB RAM Minimum 128 GB RAM
Core (without Si3 deduplication) 1x CPU with 4 cores (≥ 2,4 GHz) 1x CPU with 8 cores (≥ 2,4 GHz) Minimum 1x CPU with 8 cores (≥ 2,4 GHz) Minimum 2x CPUs with 4 cores (≥ 2,4 GHz)
Core (with Si3 deduplication) 1x CPU with 6 cores (≥ 2,6 GHz) 2x CPUs with 8 cores (≥ 2,6 GHz) 2x CPUs with minimum 8 cores (≥ 2,6 GHz) Minimum 2x CPUs with 8 cores (≥ 2,6 GHz)
Minimum hard disk space for SEP sesam metadata 100 GB 300 GB 500 GB 500 GB
No. of backup clients Up to 15 Recommended up to 50 Recommended up to 150 Recommended for more than 150

Data mover types

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

A data mover for VMware vSphere is required to run a SEP sesam backup and restore in a vSphere environment with vStorage API. SEP sesam data mover is a functional role allowing access to a third-party software API. 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 for VMware vSphere can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client. Any of these can serve as a SEP sesam data mover to transfer (send or receive) data between SEP sesam Server and VMware vSphere Farm. Note that your data mover has to match the version of your SEP sesam Server. This means that you have to update the data mover to the same version as your SEP sesam Server each time you update the server.

Data mover system requirements

Supported operating systems:

  • First, check the VDDK Compatibility Matrix and select the VDDK version suitable for your environment. Before you deploy a SEP sesam data mover, determine the matching VDDK version and the supported data mover operating system. As a rule of thumb, Windows v. ≥ Windows 2016/WIN 10 (64-bit) and Linux v. ≥ SLES 12/RHEL 7 can be used as a data mover in most cases. For information which operating systems are supported by the VMware for the specific VDDK, check the respective VMware VDDK release notes. Note that the VMware policy concerning backward and forward compatibility is for VDDK to support N-2 and N+1 releases (the two previous major versions and the next minor version).
  • Information sign.png Note
    • Even though installing the SEP sesam data mover on unsupported operating system might work, SEP sesam cannot provide any support for such configuration.
    • When upgrading a data mover to a newer version, always check that the operationg system is supported as VMware might have dropped support from one VDDK release to the next release.
  • Fast network interface (1 Gbit max. = 390 GB/h; 10 GBit max. = ~ 2,x TB/h)
  • CPU = Min. 4 cores
  • RAM = Min. 8 GB
  • 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; VDDK is installed automatically during the SEP sesam installation on Windows. On Linux, you have to install the required VDDK version manually. For details, see Installing VDDK on Linux.

Configure VMware datamover.jpg

For details, see VMware Requirements & Restrictions.

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

A SEP sesam data mover (SDM-CX) is required to run a SEP sesam backup and restore in a Citrix XenServer environment. Normally nothing has to be done to make the SEP sesam Server itself work as a data mover without any customization. The only reason to change the data mover would be that the data stream received from the XenServer should not be processed by the SEP sesam Server but by an RDS. A data mover role for Citrix XenServer can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client. Any of these can serve as a SEP sesam data mover (SDM-CX) to transfer (send or receive) data between SEP sesam Server and Citrix XenServer. When Citrix XenServers are organized in pools, the SEP sesam data mover (SDM-CX) has to communicate directly with the pool master. When the backup starts, the pool master tells the SDM-CX on which Citrix XenServer the VM is located and forces a communication switch to the appropriate Citrix XenServer (mapping).

  • Any of the following SEP sesam components must be installed: SEP sesam Server, RDS or client.
  • A regular path backup has to work. For details on typical backup configuration, see Standard Backup Procedure.

For details, see Citrix XenServer Requirements and Configuration.

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

Prerequisites

  • Operating system Novell OES2 Linux or Novell OES11, OES 2015 or OES 2018. Note that installing SLES 11 as data mover is only supported on OES11 and OES 2015, because Novell supports SMS components on SLES 11 only with OES11 installed. For OES 2018 only SLES 12 is supported by Micro Focus (previously Novell). SEP AG cannot guarantee that the Novell SMS components will work properly on a data mover based on any other Linux systems. Check the SEP sesam OS and Database Support Matrix for the list of supported Micro Focus (Novell) OES versions.
  • The Novell SMS components (SMDR, TSAs) are required, while eDirectory or other Novell service is not needed.
  • 8 GB main memory
  • Any of the following SEP sesam components must be installed: SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client.
  • A regular path backup has to work.
  • The SEP sesam Novell client has to be installed.

Configure oes-linux datamover.PNG

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

SEP sesam data mover for NetApp (SDM-NA)

With the SEP sesam data mover for NetApp is possible to access the NetApp Storage API to read and control volumes and snapshots.

Prerequisites

  • For the backup type Snapshot over NFS: The SEP sesam Server/RDS must be installed on a Linux system.
  • For the backup type NDMP/snapvault: The SEP sesam Server/RDS can be a regular Windows or Linux system.
  • The NetApp system must be reachable over its Web API and remote management must be possible by Netapp FilerView.
  • The backup server must have proper rights to mount the volumes to be backed up locally.
  • Password and username of the NetApp system.

For details, see NetApp documentation.