Ensure that the following requirements are met:
-
The VSA proxy that is used for browse and restore operations must have the MediaAgent package installed.
-
The MediaAgent that is used for browse and restore operations must have the Virtual Server Agent package installed.
If different storage policies are used for subclients under a virtualization client that uses the latest version of indexing, different MediaAgents might be used to read and write data to different storage libraries. In that case, all of the MediaAgents that are used for backup or restore jobs must be able to communicate with each other.
-
If a storage policy is specified for a client group that includes a VM, and a different storage policy is specified for the subclient that contains that VM, the index for the VM and the data for the VM might be stored in different locations, causing backups to fail during the archive index phase. As a workaround, disable the storage policy association for the client group so that backups can continue.
-
For Hyper-V, the latest version of indexing is supported for Hyper-V VMs running Windows Server 2012 R2 or a more recent version.
Enabling VM-Centric Operations
For Commvault deployments in SP14 or earlier, new VMware virtualization clients use Indexing Version 1. For Service Pack 14 and more recent service packs, support for VM-centric operations is available for streaming and IntelliSnap backup operations performed using the Virtual Server Agent (VSA) with VMware.
For a new Commvault deployment, the latest version of indexing is enabled by default, and new virtualization clients automatically use the latest version of indexing to support VM-centric operations. For an existing Commvault deployment from SP14 or earlier, you must enable the latest version of indexing
For any new Commvault deployment after SP 28, the latest version of indexing is enabled by default for any newly created hypervisor, and new virtualization clients automatically use the latest version of indexing to support VM-centric operations, unless V1 is explicitly chosen. Other existing Indexing Version 1 Virtualization Clients can remain.
To determine whether you should enable the latest version of indexing for VM-centric operations, contact your account representative to review your requirements with Commvault Support and Development, to ensure that you can switch to VM-centric operations without having a negative impact on current operational processes. Commvault Support can also facilitate the upgrade process to ensure continued access to existing backups and a smooth transition to VM-centric operations.
Upgrades
For virtualization clients that are configured for VM-centric operations using the latest version of indexing (VSA V2), you should upgrade all MediaAgents and access nodes (VSA proxies) to Feature Release 20 (11.20).
After you upgrade the CommServe system to 11.20 (Feature Release 20), upgrade all VSA proxies to 11.20.
If all VSA proxy machines are at an earlier release, enhancements for 11.20 are not used. If some proxies are updated to 11.20 and others are at an earlier release, only the 11.20 proxies are used for operations, which might result in slower performance.
If a virtual server instance or a subclient uses a VSA proxy that has not been upgraded to 11.20, you receive an error message when you run a backup, asking you to upgrade the proxy.