Skip to main content
commvault.com commvault.com
Question

Replacing old media agent: Move Mount path, or create new storage copy

  • February 26, 2025
  • 2 replies
  • 33 views
T
Bit
Forum|alt.badge.img

Hello;

We are getting a new media agent, along with a new storage library, and I want to replace the old media agent and storage library. Once I have the new stuff setup I am debating how to replace the old media agent

 

  1. Under every storage policy and plan, create a new copy that writes to the library.  Copy all jobs to that new copy, then retire the old media agent
  2. Move the DDB and move the old library mount paths to the new storage library. (https://documentation.commvault.com/2023e/expert/moving_mount_path_to_new_location.html)

 

Just wondering if anyone else has replaced the media agent.  Which method did you go with?

Erase4ndReuseMedia
Byte
Forum|alt.badge.img+13

My preference is to create new Storage Policy Copies, rather than trying to move around Deduplication Databases and Mount Paths. 

Having said that, if the existing MediaAgent and Library can remain in place for the duration of the required retention, I would instead look at creating whole new Storage Policies, which allows you to migrate Clients in a staggered approach.

Or you could combine the above two methods.

A
Vaulter
Forum|alt.badge.img+8

​@TakkyAdmin , It also depends on the size of the DDB / Mountpath that would required to be moved to the new MA. Moving as such would take time. 

Also, does it require to retire the old MA immediately? 

If not then may be bringing the new infrastructure online along with new copy gradually could also help. Once the new copy has all the jobs, it could be promoted to become primary and the old copy / MA could be retired.

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings