Happy to have helped, though I think credit goes to you!

In mount paths, if I delete the share to the original MA, and refresh.  It changes the displayed name to the first one in the share list.

Ok, unmarked.  I’ll get some MM folks to chime in.  We may have to open a support case, though we can try solving from here first 

@DavidB , do you want to reinvestigate this one?  I can unmark the answer.  It does sound like a display issue.

Not sure I have a problem, or just a display issue.

After doing the following

In the mount path, share the new MA

Set the new data path default

move the DDB

If I go the Library, it still shows the “mount path” as being on the original MA.  The original test I did seemed to update this to reflect the new default data path MA.  But others I have done the same with do not.

Migrate Cloud Library

If you have a cloud library, then share the new MediaAgent with the cloud library.

1. From the CommCell Browser, expand Storage Resources > Libraries > cloud_library.
2. Right-click mount_path and then click Properties.
3. On the Sharing tab, select the device and then click Share.
4. In the Sharing Mount Path dialog box, select the MediaAgent, and then click OK.

   The new MediaAgent is now shared with the Cloud Library.

Set the New MediaAgent as a Data Path

Once the library (disk/cloud/tape) is migrated successfully, you must make the new MediaAgent the default data path for all the Storage Policies that were associated with the old MediaAgent.

1. From the CommCell Browser, expand Policies > Storage Policies > storage_policy.
2. Right-click the appropriate storage policy copy, and then click Properties.
3. Click the Data Path tab, and then click Add.
4. In the Copy Data Path Candidates dialog box, select the new MediaAgent, and then click OK.
5. Select the new MediaAgent, and then click Set Default.
6. Click OK.

Set up a test system to try this out.  Shared the library, moved the DDB.  What I have left is a storage policy that still points to the original MA.  I know I can create a different policy and select the new MA.  But I’m wondering what that does to previous backups.  If I retire the original MA, do I loose access to them?  Retention is set to 120 days, and I could probably keep it around for that.  But am concerned. And would the next backup automatically convert to a full?  Thought it would.  But did not do so in my test.

That’s part one.  What I also want to do ultimately is to retire the origin MA.  So I’m assuming there is something else I need to do so that the second MA takes the place of the origin one completely, and I don’t have to move the backups to a different library. (The cloud library is a secondary copy).