> CommCell Console > Backup and Restore Agents > Virtualization > Virtual Server Agent > VM-Centric Operations for Virtual Server Agent

Migration of Virtualization Clients to the Latest Version of Indexing

You can use the VSA V1 to V2 Migration workflow to migrate virtualization clients, subclients, backup sets, and tenant virtualization clients from Indexing Version 1 to the latest version of indexing.

Important Considerations

  • Starting with Commvault Platform Release 2024E (11.36), Indexing Version 1 for the Virtual Server Agent (VSA) will be end of life and will no longer be supported for new VSA features (new functionality will use VM‑centric indexing instead). Existing migration workflows that rely on Indexing Version 1 will continue to operate as before.

  • After the Indexing V1 to Indexing V2 migration completes, the first backup job that you run on the migrated client must be a full backup.

  • Once the Indexing V1 to Indexing V2 migration of a hypervisor client completes, Commvault generates a job for the VSA hypervisor client under Indexing V2 with actual data on VMs. The storage policy will only have jobs for individual child VMs. This will allow Commvault to calculate peak usage at the VM level instead of at the hypervisor client level.

    For only the month in which the migration is completed, Front-End Terabytes (FET) are calculated for both Indexing V1 and Indexing V2 VMs. After that, capacity usage will be calculated only for the Indexing V2 VMs.

    To view usage at the hypervisor client level, add the Virtualization Client column in the Current Capacity Usage > Subclient Peak Usage report.

  • When you perform the migration to the latest version of indexing, you must select virtualization clients from one company at a time.

  • You cannot schedule this workflow to run at a user-defined time. The job will fail.

  • If 2FA multi factor authentication is enabled, the VSA V1 to V2 Migration workflow fails. To avoid this problem, before migrating, disable 2FA multi factor authentication, and then run the workflow. After the migration completes, re-enable 2FA multi factor authentication.

  • If horizontally scaled deduplication is used within the storage pool, migrating to the latest version of indexing can cause data blocks to be rebaselined on storage.

  • After the migration completes, de-configure the VSA Indexing V1 client and do not re-enable it. De-configuring the client allows data aging to occur based on the days based retention option as described in Advanced - Data Aging and Deconfigured Clients.

When to Use the VSA V1 to V2 Migration Workflow

Indexing V2 is enabled by default when you create a new virtualization client in a new Commvault installation. However, if you have existing virtualization clients in your CommCell environment that were installed before Service Pack 15, and you are upgrading them to a more recent feature release, then you can use the VSA V1 to V2 Migration workflow to migrate the virtualization clients to Indexing V2. However, you must manually download the workflow from the Commvault Store because it not installed by default.

For Indexing V2, you must have admin privilege when executing the workflow. For more information, see the following:

Supported Virtualization Clients

You can use the VSA V1 to V2 Migration workflow for the following virtualization clients:

  • Amazon EC2

  • Azure

  • Azure Stack Hub

  • Citrix Hypervisor (XenServer)

  • Hyper-V

  • Huawei FusionCompute

  • Nutanix AHV

  • Openstack

  • Oracle VM

  • Red Hat Virtualization

  • VMware

  • VMware Cloud Director

Workflow Process

The workflow performs the following actions:

  • For clients with multiple agents, migrates only the VSA instance.

  • Creates a new Indexing V2 client and updates the VSA Indexing V1 virtualization clients and subclients, adding a _V1 suffix to them. Note that new VSA client names and subclient names will be the same as the original names.

  • Clones all backup sets and subclients under the VSA Indexing V1 client and migrates them to the latest version of indexing.

  • Copies all properties configured on the VSA, the backup set, and the subclient.

  • After the migration completes, disables backup activity on the Indexing V1 client at the VSA level.

  • Sends an email to the administrator (and any others who are specified in the workflow) that indicates whether the workflow completed successfully or failed.

  • After the migration completes, the first backup job that you run on the migrated client must be a full backup.

What Is Not Migrated

The following items are not included in the migration process:

  • Clients that have multiple virtual server instances (V9-style clients).

  • For clients with multiple agents, only the VSA instance is migrated.

×

Loading...