Skip to main content
commvault.com commvault.com
Answer

Data movement on splitting Commcell

  • August 1, 2025
  • 3 replies
  • 57 views
C
Forum|alt.badge.img+3

Hello All,

My company has two lines of business and a single CommCell for both. Each line of business has its own virtualization environment with VMware and NAS data, all based on NetApp, with different storage policies for each line and kind. There is only one Media Agent and one DAS disk library on that Media Agent used for all policies, plus a third AirGap library. We use IntelliSnap for both VMware and CIFS. After the NetApp snapshot (for both NAS and VMs), we perform a backup copy for VM and NDMP for CIFS, sending all data to the same DAS disk library with a single mount path, plus Aux copy to AirGap.

Now, we want to split that CommCell to separate the lines of business, and we have a new disk library and a new Media Agent ready for the line of business that will be moved to the new CommCell.

I’ve reviewed the documentation on CommCell Splitting and CommCell Migration, and I believe Splitting would be the right approach. However, I don't fully understand when and how the backup data is transferred from the current CommCell’s library to the new one for the clients being migrated to the new CommCell.

Also, since data stored in AirGap cannot be migrated, what happens to the backup data that resides in the AirGap library when the clients are deleted?

 

 

Thank for the help.

 

Regards,

Best answer by Pradeep

Hi ​@CarlosPerez ,

PFB Plan of Action : Migrating Clients and Data to New CommServe

To migrate clients from the existing CommServe to the new CommServe, we can leverage the CCM method.

For migrating the associated backup data currently residing in the Air-Gap library, follow the steps outlined below:

  1. Deploy New Media Agent and Library on Existing CS
     Set up the new Media Agent and attach the new library to the existing CommServe.

  2. Configure Auxiliary Copy
     Create an auxiliary copy using the new library under the relevant Storage Policy where the client data currently resides.

  3. Perform Auxiliary Copy Operation
     Run the aux copy to replicate the data from the existing AGP library to the new library.

  4. Promote New Library on the Migrated CommServe
     Once the migration is complete, promote the new library copy as the Primary copy on the new CommServe.

  5. Decommission Old Media Agent and Library
     After successful validation, disable or delete the old Media Agent and AGP library to complete the transition.


https://documentation.commvault.com/11.40/expert/use_cases_and_operations_for_commcell_migration.html

3 replies

P
Vaulter
Forum|alt.badge.img+12
  • PradeepVaulter
  • Vaulter
  • Answer
  • August 2, 2025

Hi ​@CarlosPerez ,

PFB Plan of Action : Migrating Clients and Data to New CommServe

To migrate clients from the existing CommServe to the new CommServe, we can leverage the CCM method.

For migrating the associated backup data currently residing in the Air-Gap library, follow the steps outlined below:

  1. Deploy New Media Agent and Library on Existing CS
     Set up the new Media Agent and attach the new library to the existing CommServe.

  2. Configure Auxiliary Copy
     Create an auxiliary copy using the new library under the relevant Storage Policy where the client data currently resides.

  3. Perform Auxiliary Copy Operation
     Run the aux copy to replicate the data from the existing AGP library to the new library.

  4. Promote New Library on the Migrated CommServe
     Once the migration is complete, promote the new library copy as the Primary copy on the new CommServe.

  5. Decommission Old Media Agent and Library
     After successful validation, disable or delete the old Media Agent and AGP library to complete the transition.


https://documentation.commvault.com/11.40/expert/use_cases_and_operations_for_commcell_migration.html

C
Forum|alt.badge.img+3
  • CarlosPerez
  • Author
  • August 7, 2025

Thank you Pradeep, I have reviewed the documentation; I believe these would be the steps, but I have some questions.


1- Create an auxiliary copy for each storage policy from which I want to migrate data, using the existing MediaAgent and configuring a new CIFS library and a new Metallic AirGap library. These libraries will be the final destination libraries I will use once the migration is complete.
Can the Metallic AirGap copy be configured as the source of an auxiliary copy? Will the migrated library be set to read-only like when using Splitting? What will happen to it in the original CommCell?

2- Data export: Since I will be using a new MediaAgent at the destination, should I select “Do not export MediaAgents”?

3- Data import: In 'Destination MediaAgent', I select the MA that is part of the new CommCell. What will happen with the DDBs of the copies in the new libraries? If they are not needed for restore operations, should I delete them at the end?

4- Once I finish, I create new storage policies for the new backups.

5- I register the migrated clients.

In this process, if I leave 'Try to contact source CommServe' and 'Deconfigure the migrated clients on source and remove datapath' checked, the option says:
“Select this option to deconfigure all the migrated client computers and to delete the data paths (the mount paths) that are associated with the MediaAgent client computers.”
Will it delete only the datapaths from the storage policies, or also the mount paths of the DAS library?
Will it delete the data associated with the migrated clients from the libraries, including the AirGap?
Do I need to block access from the original CommCell to the new libraries beforehand?

 

Regards

P
Vaulter
Forum|alt.badge.img+12
  • PradeepVaulter
  • Vaulter
  • August 9, 2025

Hi ​@CarlosPerez 

As per the latest info from the documentation. it will be removing the mount path from MA. However, I would request to log support case to review and validate the existing setup before we proceed further.

C
Terms & ConditionsCookie settingsAccessibility statement