Post HyperScale Migration: What You Need Know

After migrating a HyperScale 1.5 Appliance storage pool to a Commvault HyperScale X storage pool, observe / perform the following tasks.

Storage Policy Changes

You will view the following changes associated with Storage Policy and Storage Policy copies, depending on the type of migration that was selected.

The original Storage Policy will be renamed with the prefix HSReplace_<original_storage_policy_name>. For example, if the original storage policy name was MyHyperScaleSP, it will be renamed as HSReplace_MyHyperScaleSP.
A new storage policy with the original name will be created with the new Commvault HyperScale X storage pool as the storage target.
All CommCell entities, like subclients, schedules, plans, etc. will be re-associated with the new storage policy.
A secondary copy on the original Storage Policy will be created with the new Commvault HyperScale X storage pool as the storage target. The retention setting will be the same as the primary. This secondary copy will be used as the target for Auxiliary Copy operation, which is automatically started when you migrate the data.

A new secondary copy on the original Storage Policy will be created with the new Commvault HyperScale X storage pool as the storage target. The retention setting will be the same as the original primary copy.
All currently running jobs will be killed and the copy will be promoted as the primary copy with the same name as the original primary copy.
The original Storage Policy Copy will be renamed with the prefix HSReplace_<original_storage_policy_Copy name>. For example, if the original storage policy name was Primary, it will be renamed as HSReplace_Primary. The End Time in the Storage Policy Copy Properties - Copy Policy tab, will be set to the creation date and time of the new copy.

The new Storage Policy / Storage Policy Copies are cloned from the original and all retention related settings and client associations and source copy settings will be replicated on the new copies. However, all other property settings will be set using the smart defaults. If you have some customized settings, you may want to compare the old and new Storage Policy / Storage Policy Copies properties and establish the necessary settings.
If data aging was disabled on the source, the new copy will be created with data aging enabled.

Entities that were flagged in the HyperScale Pre-Migration Report under the Message column may need to be addressed after the migration.