HyperScale nodes can be migrated to a new CommCell without losing the data stored in the nodes. The migrated nodes can then be used to backup new data from the destination CommCell and data existing in the nodes can be restored if needed.
Before You Begin
To obtain the ConfigCCMHyperScaleStoragePool QScript needed to complete the migration process, contact Commvault Customer Support.
Procedure
-
From the source CommCell, export the metadata associated with the nodes that you plan to migrate. For more information, see Exporting the Metadata from the Source CommCell Environment
During the export, make sure that the MediaAgents available in the nodes that you plan to migrate are selected from the tree displayed under the Select Associations option, in the Export Options dialog box.
-
In the destination CommCell, import the metadata. For more information, see Importing the Metadata to the Destination CommCell Environment.
The imported client computers appear under a new client computer group with the name source_commserve_environment_clients. The client group created in the destination CommCell environment. The storage policies and the libraries for the migrated client computers are created with the name CCM_entity.
-
Change the client identifier of the migrated MediaAgents associated with the nodes to match the original client identifiers in the source CommCell. For instructions to view the client identifier, see Locating the Client Name.
-
Register the MediaAgent computer with the destination CommServe computer. For instructions, see Registering the Migrated Client Computers.
-
Modify the mount path associated with migrated nodes to set the following options:
-
Set the MediaAgent access type to Read/Write.
-
Enable the Preferred option.
For more information, see Modifying a Mount Path.
-
-
Share the migrated mount path with the other nodes with the Read/Write and Preferred options. (As CommCell migration brings the mount path from only one node, it is important to share the mount paths with the other nodes.) For more information, see Sharing a Mount Path.
-
Add new shared mount paths on the migrated HyperScale nodes using the Expert Storage Configuration dialog box.
For assistance to create multiple mount paths under a device location, contact Commvault Customer Support.
-
Create a new Global Deduplication Policy (GDSP) with the same name as the original disk storage pool and the same HyperScale nodes before migration. For more information, see Creating a Storage Policy with Global Deduplication.
Add the same number of partitions as the original policy, before migration.
For example, if there are 3 nodes, add 6 partitions spread 2 across the 3 nodes, under the
/ws/ddbfolder. -
Run the ConfigCCMHyperScaleStoragePool QScript to automatically identify all the migrated storage pools and the corresponding new GDSP and set the necessary flags accordingly. (The only prerequisite needed for this operation is the new GDSP created in step 7, using same HyperScale nodes.