Hello @drPhil
You can move the data outside of CV if you want but it is never recommended as Commvault does not have control and this means we cannot guarantee the data will be healthy.
Just make sure you stop the CV services on both MA’s before you start the operation.
In the mount path properties you will just update the location to have access from the new MA and how it will get there. It is important to make sure you list the exact location to the path and if the data CV try's to look for is there we wont have issues.
The CVMA and CVD log on the MA when you start the services is a good location to look if there are any issues.
Kind regards
Albert Williams
Hi Albert,
could you please describe a little bit deeper how to update the location to the new MA? In the Mount Path properties, only thing that I can edit is Sharing tab. I assume, that the disks from the array are already mapped/attached to the MA server operating system. Indeed, I want to say to Commvault, that there should be the same path only on the new MA, because it is just about mapping disk from storage array.
Hello @drPhil
Navigate to Storage Resources » Library’s.
Once you are looking at all of your mount paths you can go to the properties and then sharing tab.
This tab outlines how each server will access the same set of data. If you shut down the services on the MA, move the data, update this location in the CS GUI to the new location and then start the services again CV will work like nothing has changed.
I will say again, this is not recommended due to any issue with the data movement is out of CV hands. Do this at your own descension.
We used to have documentation around performing the steps with a robocopy on Documentation but it has been removed due to some problems that were caused with the robocopy its self that we have no control of.
Kind regards
Albert Williams
Thank you @Albert Williams for your help!
Moving mount paths (presented as local disks from the storage array) from one Media Agent to another is possible with careful planning. Before starting, it's crucial to stop all jobs and services on both Media Agents. Below, I would like to provide a high-level overview of our procedure and steps.
- First, unmap the disks from the old Media Agent in the server's operating system, and stop presenting those disks from the storage array to the old Media Agent server.
- Next, present the same disks/paths to the new Media Agent server.
- Once the new Media Agent recognizes the attached disks from the storage array, you can add these paths under Storage Resources » Library » Sharing tab. Here, add the new paths and remove the old ones.
Ensure that the mount paths retain exactly the same names to avoid issues after migration.