Source:SEP sesam DataMover
Overview
SEP sesam data mover is a functional role that provides access to a third-party software API or redirects the data stream to a SEP sesam Server/Remote Device Server (RDS). 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 with either a SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client. Which SEP sesam component is possible to combine depends on a third-party software.
General requirements
The following are the hardware requirements for the SEP sesam Server, RDS or SEP sesam Client. They are similar for both servers, SEP sesam Server and RDS, except for the required space on the file system for the SEP sesam database, which is not necessary for RDS.
- The hardware requirements for the SEP sesam components represent the common requirements. Additional amount of RAM/CPU may be required for bigger Si3 data stores. For details, see Si3 Deduplication Hardware Requirements.
- (Windows only) Make sure that you are using CPUs with supported AVX versions (AVX, AVX2, or AVX-512) and FMA3 (Fused Multiply-Add 3-operand Form) or FMA4 (Fused Multiply-Add 4-operand Form) to prevent the Sesam Transfer Protocol Server (STPD) from automatically disabling the HTTPS port. This happens when the CPU instructions are missing due to unsupported AVX. Consequently, the TLS key and certificate cannot be created. For a list of supported AVX versions, see Advanced Vector Extensions.
Requirements | SEP sesam Server Standard edition | SEP sesam Advanced Server edition | SEP sesam Premium Server edition | SEP sesam Enterprise Server | SEP sesam Client |
---|---|---|---|---|---|
Memory (without Si3 deduplication) | 8 GB RAM | Minimum 16 GB RAM | 32 GB RAM | Minimum 64 GB RAM | 2 GB (recommended 4 GB) |
Memory (with Si3 deduplication) | Minimum 32 GB RAM | Minimum 32 GB RAM | 64 GB RAM | Minimum 128 GB RAM | Minimum 8 GB |
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 | 200 GB | 300 GB | 500 GB | 500 GB | 4 GB (for all client data) |
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)
- SEP sesam data mover for Citrix XenServer (SDM-CX)
- SEP sesam data mover for Micro Focus (previously Novell) services (SDM-NS)
- SEP sesam data mover for NetApp (SDM-NA)
- SEP sesam data mover for Nutanix (SDM-NTX)
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).
- 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 operating 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 SEP sesam 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.
Note | |
|
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 Micro Focus (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 Micro Focus SMS components (SMDR, TSAs) are required, while eDirectory or other Micro Focus (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.
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.
SEP sesam data mover for Nutanix (SDM-NTX)
A SEP sesam data mover is required to perform a SEP sesam backup and restore in a Nutanix AHV environment. A data mover role for Nutanix AHV can be combined either with a SEP sesam Linux Server or Linux Client (for SEP sesam Windows Server), or in the case of using HotAdd transport mode, the data mover must be a SEP sesam Client installed on Nutanix. Each of them can serve as SEP sesam data mover to transfer (send or receive) data between SEP sesam Server and Nutanix AHV.
Note that your data mover must match the version of your SEP sesam Server. This means that you need to update the data mover to the same version as your SEP sesam Server every time you update the server.
To ensure efficient data protection and restorability of your data, configure your Nutanix data mover with a fully qualified domain name (FQDN). This step should be performed before adding your Nutanix AHV as a client to the SEP sesam environment.
To verify that your data mover is configured correctly, follow these steps:
- From the Main selection -> Components -> Clients, double-click your data mover for Nutanix.
- Check the Interfaces field: make sure that a fully qualified domain name (FQDN) is specified for your client. If the FQDN is not yet specified, enter it on a new line, e.g, dm_ntx_comp.de, and click OK to apply the changes.
- Ensure that the FQDN is resolvable by using sm_setup tool from the command line. For syntax details, see Using sm_setup check_resolution. The returned addresses and hostnames must match. If the reverse resolve returns a different name than the name specified on the command line, there will be problems with backing up the client.
- A regular path backup has to work. For details on typical backup configuration, see Standard Backup Procedure.
For details, see Nutanix AHV Backup.