The Virtual Server Agent (VSA) for Commvault includes the latest certified VDDK version and earlier versions that can be used for backups, including backups for ESX versions that are no longer supported by VMware.
-
VDDK 7.0: Will be loaded for vCenters running vSphere 7.0 or later.
-
VDDK 6.7.3: Will be loaded for vCenters running vSphere 6.7 Update 3 or later.
-
VDDK 6.0.2: Will be loaded by default for vCenters that do not require VDDK 6.5 or later. This VDDK can be used for ESXi versions prior to ESXi 5.5 that are supported by Commvault.
The VSA package includes VDDKs in the following folder structure:
\Base\Vmware\VDDK\VDDK700\bin
\Base\Vmware\VDDK\VDDK673\bin
\Base\Vmware\VDDK\VDDK602\binThe VDDK is not loaded until the VDDK is needed for a backup or restore operation. Once a VSA proxy has loaded a more recent VDDK version, it cannot revert to using an older version.
Use separate VSA proxies to support different VDDK versions
A single physical or virtual machine can only support one active VDDK version, and different VSA proxies must be configured to support different VDDK versions. If VSA proxies are deployed as virtual machines, the VSA proxy VMs supporting different VDDK versions must be hosted on different ESX servers.
In environments that include vSphere 6.5 or 6.7, as well as ESX hosts that are not supported by vSphere 6.5 or 6.7, configure separate VSA subclients and assign different VSA proxies to each of the subclients:
-
Configure one subclient and VSA proxy to support older hosts with proxies using VDDK 6.0.2.
-
Configure a separate subclient and VSA proxy to support vSphere 6.5, 6.7, or 7.0.
The version of the VDDK that is loaded automatically matches the highest level of vSphere in the deployment. For example, if the deployment includes vSphere 6.5 and vSphere 6.7 Update 3, VDDK 6.7.3 is loaded automatically.