Copyright © SEP AG 1999-2023. 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.
Supported VDDK versions
SEP sesam requires the VMware Virtual Disk Development Kit (VDDK) to be installed on SEP sesam data mover (SDM-VV). A data mover role for VMware vSphere can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or SEP sesam Client.
The following table shows the recommended VDDK version in combination with SEP sesam.
- On Windows, the VDDK is installed by default, but depending on your environment a different VDDK version may be required. In this case, install the required VDDK version manually.
- For Linux, you have to install the required VDDK version manually. For details, see Installing VDDK on Linux.
As the VMware version information can be changed by VMware, SEP recommends to check the VMware Product Interoperability Matrix.
VMware version Note a
|Supported VDDK Note b||SEP sesam Release Versions||Limitations|
|vSphere 7.0||VDDK 7.0.2 (manual update required) Note d||5.0.0 Jaglion||Check VMware Release Notes for compatibility and issues.|
|vSphere 7.0||VDDK 6.5.2 (see limitations!)||4.4.3 Beefalo V2 (see limitations!)||vSphere 7.0 with VDDK 6.5.2 is not officially supported by VMware. However, some customers are backing up vSphere 7.0 with Beefalo version 2, which contains VDDK 6.5.2. Although this version of VDDK is not officially supported for vSphere 7.0, it appears to work. Note that any issues related to the use of this officially unsupported version are the responsibility of the user and not SEP sesam or VMware.|
|vSphere 6.7 (supported proxy OS)||VDDK 6.5.2 (manual update required)
VDDK 6.0.3 (manual update required)
|4.4.3 Grolar and Beefalo||Check VMware Release Notes for compatibility and issues.|
|vSphere 6.5 (supported proxy OS)||VDDK 6.5.2 (manual update required)
VDDK 6.0.3 (included in SEP sesam Windows client ≥ 22.214.171.124)
VDDK 6.0.2 (included in SEP sesam Windows client ≤ 126.96.36.199)
|4.4.3 Tigon and Tigon V2 (188.8.131.52-.48)
|vSphere 6.0||VDDK 6.0.2||≤ 184.108.40.206|
|vSphere 5.5||VDDK 5.5 – 5.5.5||4.4.2|
|vSphere 5.1||VDDK 5.1||≤ 4.4.1|
|vSphere 5.0||VDDK 5.0||≤ 4.4.1|
- Windows Server 2008 R2
- Windows Server 2012 and 2012 R2
- Windows Server 2016
- Windows 10
- Red Hat Enterprise Linux; RHEL 6.7, 6.8, 7.2 and 7.3
- SUSE Linux Enterprise Server; SLES 11 SP4 and SLES 12 SP1
- Windows Server 2019
- Windows Server 2016, including versions 1709 and 1803
- Windows Server 2012 and 2012 R2
- Red Hat Enterprise Linux RHEL 7.7 and 8.0
- CentOS 7.7
- SUSE Linux Enterprise Server SLES 12 SP5 and 15 SP1
As of VMware vSphere 5, backup with SEP sesam is only supported with a licensed ESXi hypervisor. Backup of ESXi 5.5 hypervisors is supported as of SEP sesam version 220.127.116.11.
The VMware policy concerning backward and forward compatibility is for VDDK to support N-2 and N+1 releases. For example, VDDK 6.0 and all of its update releases support vSphere 5.1, 5.5, and 6.5 (except new features).
VDDK 6.5.2 was tested by VMware with the following operating systems to perform proxy backup:
VDDK 7.0.2 supports the following operating systems: