VM-Centric Operations in Command Center (VSA V2)

The Command Center uses a VM-centric approach for all hypervisors, but some hypervisors use Indexing Version 2 to enable more efficient backup and recovery for virtual machines. This change is not visible to Command Center users, but might affect some back-end processing.

Hypervisor Support for Indexing Version 2


Supports V2 indexing?

Enabled by default?

Alibaba Cloud

Yes (Command Center only)

Enabled by default when you create a new virtualization client for Red Hat OpenShift.





Azure Stack


Citrix Xen




Google Cloud Platform


Huawei FusionCompute




Nutanix AHV




Oracle Cloud Classic


Oracle Cloud Infrastructure

Yes (Command Center only)

Enabled by default when you create a new virtualization client for Red Hat OpenShift.

Oracle VM


Red Hat OpenShift

SP17 and later (Command Center only)

Enabled by default when you create a new virtualization client for Red Hat OpenShift.

Red Hat Virtualization


vCloud Director


(Command Center and CommCell Console)

Enabled by default for a new Commvault deployment when you create a new virtualization client for vCloud Director.



(Command Center and CommCell Console)

Enabled by default for a new Commvault deployment when you create a new virtualization client for VMware.

Known Issues

For detailed information about VM-centric operations using the CommCell Console, see VM-Centric Operations for Virtual Server Agent with VMware.

The following operations are not supported with Indexing Version 2 for the Virtual Server Agent:

  • File and folder information is not collected during backups.

  • File indexing for virtual machines is not supported.

  • To restore guest files and folders from a VM-centric backup, use the disk library for one of the copies (primary or secondary) and perform a live browse from the disk library. Guest file restores from tape are not supported with VM-centric backups, because file details are not collected in VM-centric backups, and live browse operations are not supported from tape copies. As a workaround if no disk library is available, you can restore a full VM or a virtual machine disk from a tape copy.

  • Specifying encryption settings using VM-level settings.

    You can specify encryption settings through the storage policy.

  • End users can use Command Center to perform VM-centric operations. Web Console does not support VM-centric operations.

  • For a VM instance client, the Browse and Restore Options dialog box shows options for Virtual Machine files and Attach Disks to Existing VM, but those types of restores can be performed only from a backup set under the virtualization client.

  • If a virtual machine is deleted from the vCenter, the VM client remains in the CommCell Console. To avoid errors for the deleted VM, delete the VM client manually and remove the corresponding VM from all subclients where it is included as content.


    VM clients are de-configured only after the period specified in the Number of days to keep deleted VMs setting for Media Management/Data Aging (defaults to 30 days). Ensure that backup copy jobs complete before the VM client is de-configured.

  • If you restore files from a virtual machine that has a File System Agent installed, the Virtual Server Agent backup might not have the most recent backup data. To ensure that you are restoring from the most recent backup, initiate the restore from the job history for the virtual machine.

  • You cannot use the virtual machine archiving feature for VM-centric virtualization clients.

  • Job-based browse from a VSA subclient will fail if the most recent job is a synthetic full backup job for the VM.

  • Secondary copy operations from a snapshot replica are not supported with Indexing Version 2. The following types of replication from IntelliSnap backups are not supported with Indexing Version 2:

    • Offline replication using NetApp SnapVault and SnapMirror configurations

    • Replication using NetApp with OnCommand Unified Manager (OCUM)

    • Inline replication

  • If virtual machines are backed up using a storage policy with spool copy settings (no retention), you must run data aging after creating a backup copy. If you do not run a data aging job after creating a backup copy, browse and restore operations fail when they try to access the default copy of backup data.

  • If you configure a secondary copy on a storage policy and select only the virtualization client or subclient on the Associations tab of the Storage Policy Copy properties dialog box, the virtual machines that are under the virtualization client or subclient are not shown as selected. The secondary copy that is created does include the jobs for the parent (virtualization client or subclient) and the jobs for each VM. This is only a display issue.

  • If you configure a secondary copy for a subclient and perform a backup, the secondary copy includes the backup job for the subclient and each of the VMs in the subclient content. If a VM subsequently moves to a different subclient, backup jobs for the VM continue to be associated with the original subclient and secondary copy, and are not available from the new subclient. You can still recover data from any backup job by initiating a restore from the job history for the VM client.

  • If a VM has a Version 10 Commvault agent installed, a backup of the VM fails if the parent virtualization client uses Indexing Version 2.

  • If a VM is backed up using multiple subclients under the same backup set, and the subclients use different storage policies, this configuration could result in incorrect handling of extents for synthetic full backups and restores, premature data aging, and failed restores. This situation can occur when VMs are assigned to subclient content based on automatic discovery rules: for example, when a VM moves to a different datastore and subclient contents use rules to select VMs based on the VM datastore.

  • On storage policies that are used for VMware backups with Indexing Version 2, the Incremental Storage Policy option is not supported. If that option is selected in the storage policy associated with a subclient or VM group that uses Indexing Version 2, incremental and differential backups for some VMs fail during the archive indexing stage. For more information, see KB Article VMW0043.

  • For virtualization clients that are configured for VM-centric operations, after performing a synthetic full backup, you cannot perform another synthetic full backup until you have run at least one incremental backup.