Skip to main content
commvault.com commvault.com
Question

Consolidating Mount Paths during Media Agent HW Refresh

  • June 8, 2026
  • 2 replies
  • 29 views
A
Novice
Forum|alt.badge.img

Hi all, I’m planning on replacing our MA server, and I just needed a sanity check on the Replace Media Agent App and Move Mount Point processes. The old MA has a Disk Library with 7 mounth paths, most of which are iSCSI LUNs from a couple different arrays. The new MA will have much more direct attached storage, so I’m plannin on just 2 mount points. 

If I run the Replace Meda Agent App process, and let it run the Move Mount Point process, am I able to consolidate the old mount paths down to 2 during this process, and specify the destination of each of the source MP’s? 

 

I assumed that I can because the Move Mount Path function in the Commcell console offers me the option to move it to an existing device, however the documentation says:

  • The move mount path operation overwrites the destination mount path. Therefore, ensure that the destination mount path is an empty folder. 

Can anyone offer any clafification?

Thanks!

2 replies

W
Vaulter
Forum|alt.badge.img+10
  • WasimVaulter
  • Vaulter
  • June 9, 2026

Hi ​@Adam Gabriel,

 

The requirement is as follows: The existing MediaAgent has 7 mount paths(from different disk) configured. The customer is currently using the Replica MediaAgent App, and their objective is to migrate all 7 mount paths from the old MediaAgent to a new MediaAgent, while consolidating them into only 2 mount paths on the destination.

However, this type of consolidation during the migration process is not feasible.

As an alternative approach, we recommend migrating the 7 mount paths from the old MediaAgent to the new MediaAgent in a one-to-one manner, thereby maintaining all 7 mount paths on their respective disks.

Post-migration, the “Prevent data block references for new backups” option can be enabled on 5 of the mount paths. These mount paths can then be retired and deleted once all associated jobs and data have aged out. It is important to note that this process will take a considerable amount of time, as it is dependent on the configured retention period.

As an additional option, prior to using the Replica MediaAgent App, a new disk library can be created on the target MediaAgent with 2 mount paths and a DDB. Subsequently, Auxiliary Copy operations can be performed to move data from the existing library (with 7 mount paths) to the newly created library (with 2 mount paths). Once the data migration is complete, the jobs in the old library can be deleted, and the old library can be decommissioned.

 

Regards,

Wasim
 

A
Novice
Forum|alt.badge.img

If the consolidation of paths isn’t possible during the Replace Media Agent App workflow, then surely the better alternative is to just migrate the media agent using the manual operations steps here, rather than waiting multiple months for the data to age out, no? 

 

I’m also still caught up on the conflicting documentation, though. In one place I read: 

You can move a mount path to an existing device on the same library. The destination device can be a local path or a network path. When you move a mount path to an existing device, the software consolidates the mount path with the destination device and the device represents a single mount path.

And in another, I read:

The move mount path operation overwrites the destination mount path. Therefore, ensure that the destination mount path is an empty folder. 

 

Perhaps it’s best that I open a support ticket.

Readiverse Academy Certifications

description of image
Terms & ConditionsAccessibility statement