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 Indexing Version 2.
Important Considerations
-
When you perform the migration to Indexing V2, 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 Indexing V2 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 Version 11 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 VSA V2, you must have admin privilege when executing the workflow. For information, see Workflow Security.
Supported virtualization clients
You can use the VSA V1 to V2 Migration workflow for the following virtualization clients:
-
Amazon EC2
-
Azure
-
Azure Stack Hub
-
Hyper-V
-
Nutanix AHV
-
Openstack
-
VMware (and vCloud)
Workflow Process
The workflow performs the following actions:
-
For clients with multiple agents, migrates only the VSA instance.
-
Updates the VSA Indexing V1 virtualization clients and subclients, adding a _V1 suffix to them. (New VSA Indexing V2 client name 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 an VSA Indexing V2.
-
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 is 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.