Hi @Jean-Paul

That approach works. Don't forget to move index DBs over to the new MA server too. 

Alternatively, depending on your retention, you don't have to move all the data, you could allow it to age naturally and just configure / promote a new (empty) storage policy copy. Then wait for the retention to be met before decommissioning the old MA server,

HTH

Niall

Thank you for you answer.

what about this approach:

https://documentation.commvault.com/v11/essential/43645_performing_mediaagent_recovery.html

That approach works too but if you follow that approach you cant have the old MA and the new MA installed and online in the Commserve together as you would be “reusing” the MAs name/ip address. I would prefer to have both old and new MA servers online together and then be able to manage the migration but it is personal preference. 

I guess it comes down to what the associated Hardware is and then specifically if it is local disk, SAN disk or CIFS for the Disk Library rand then what the volume of data there is too]. 

Niall

@Jean-Paul Take a look at this link for a MediaAgent hardware refresh:
https://documentation.commvault.com/2022e/expert/11069_mediaagent_hardware_refresh_overview.html

If you are just needing to move from one MediaAgent to another this should do the trick.

Thank you Niall,

can you give me more details about “move index DBs over the new MA”

The Dash copy does not copy all include Index and DDB?

Moving Index Cache: https://documentation.commvault.com/2022e/expert/93146_moving_index_directory_for_index_server.html

Moving DDB: https://documentation.commvault.com/2022e/expert/11078_move_ddb_to_new_mediaagent.html