Migrate Media Agent

To migrate a MediaAgent with a disk library to a new Windows system while setting up high availability, the recommended approach is to use the Replace MediaAgent application: https://documentation.commvault.com/2023e/expert/migrating_to_new_mediaagent_using_replace_mediaagent_app.html

It automates the migration of disk libraries, DDBs, index cache, and configurations. Just install the same MediaAgent packages on the new system, launch the tool, select the source and target MAs, and proceed with migrating the mount paths and DDBs. If you're using tape, you’ll need to reconfigure those libraries manually. After migration, it’s a good idea to test backups and restores to confirm everything’s working fine.

If the automated method isn't viable, manual migration is also possible—copy over the index cache and DDB folders, use synchronous copy via storage policies to replicate data, and then switch the new MA to primary.

For high availability, Commvault recommends active-active configurations using GridStor instead of cold standby. You can configure multiple MediaAgents with access to the same library and set up Data Paths properly so both nodes are used for load balancing and automatic failover. Once migration is complete, the old MediaAgent can be reinstalled and added back to the GridStor group to keep it active in the setup.

https://documentation.commvault.com/2023e/expert/configuring_data_paths_for_storage_policy_copy.html

Hope it helps!