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!

Sorry, but the second link works not for me……
https://documentation.commvault.com/2023e/expert/configuring_data_paths_for_storage_policy_copy.html

Hi Dennis, 

use this instead
 https://documentation.commvault.com/2024e/expert/copy_properties_data_path_configuration.html

Hi,
some questions about the migration :-)

What is the best step to migrate the tape library from the “old” MediaAgent to the new one.
Is ReFS or NTFS better for the Luns where the moint point are located?
When mount points migration is started, the backups continue to run ?

Regards
Dennis
 

Hi Dennis, 

Migrating tape library: https://documentation.commvault.com/11.20/migrate_tape_library.html

ReFS (Resilient File System) is generally preferred for deduplication databases (DDBs) and mount paths on newer Windows versions (especially for scale and performance).

NTFS is still acceptable and well-supported.

For your final question:

• If you’re using the Replace MediaAgent tool, 

  • Mount paths are updated one by one.

  • During the switch, Commvault prevents jobs from using paths in transition.

  • Backups will continue to run using other available mount paths not being actively migrated.

• If you have only one mount path, you may observe a temporary pause or job delay while the path is being migrated.

Tip: Stagger the migration or do it during low-activity hours to avoid impact.

Hi,
a question about GRID Store.
We have a SAN Luns attached to our MediaAgent (Windows).
But I can't assign the same LUN’s to the second Windows Media Agent when the first Media Agent uses this LUN’s.
Or would I have to work with cluster services?

Regards
Dennis

​@Dennis To set up high availability for SAN-attached LUNs across two Windows MediaAgents without using clustering, you can go ahead with Commvault’s GridStor (Alternate Data Paths). Just present the same LUN to both MediaAgents using Fibre Channel or iSCSI. On MediaAgent 1, access the LUN locally (say D:\), and on MediaAgent 2, access it via a UNC path (like \\MediaAgent1\D$).

Make sure to set static mount paths to avoid any conflicts, and enable Index Cache Sharing so that failover is smooth. In case MediaAgent 1 goes down, MediaAgent 2 can take over without any manual effort. Hope this helps.