Our current deployment has 4 physical MediaAgents on prem to backup to a flash array, we have an Aux Copy from the flash array to Azure which has 4 MediaAgents in Azure. The current Aux Copy job shows Source MediaAgent as the 4 OnPremMAs and the destination as the 4 AzureMAs.
We have recently deployed an on prem S3 with an additional 4 physical MediaAgents and have added it as a Synchronous Copy similar to the Azure Aux Copy. The on prem S3 Aux Copy job shows one physical MediaAgent as the source and destination MediaAgent.
One of the “new” MediaAgents was actually part of the line for the OnPremMAs at one point but was replace by newer hardware. This one MediaAgent is the one that is showing as the Source and Destination MediaAgent. This OldMA shows up on the Mount Paths for the flash array with Read/Write Access.
The S3 has been configured with 4 Mount Paths, one for each new physical MediaAgents and each has been shared with each of the new physicals with Read/Write Access.
I was expecting the on prem S3 Aux Copy to show 4 OnPremMAs as the Source MediaAgents and the 4 NewMAs as the destination but I only see the one OldMA seems to be part of both groups. I am looking for clarification and suggestions for cleaning this up.
Thank you