Adding new replicated items results in different MARS agent versions installed

Darius Leonavičius hi,

private endpoints can be tricky little devils when it comes to updates ) first, make sure ur asr appliance is truly up to date. sometimes the 'latest' update needs a second look https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication

aha, and about those outdated agents... since u can't update via portal, u gotta push them manually. download the latest mars agent directly from microsoft here https://aka.ms/azurebackup_agent then install it on each server that's misbehaving. yes, it's a bit of manual work, but c'est la vie ))

the replication groups might be causing this version salad. verify if all servers in the same group get consistent versions. if not, recreate the group. details here https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-common-questions

sometimes the cache storage account gets moody. make sure its firewall rules allow traffic from all servers. private endpoints love to block things silently ))

keep an eye on the system clock! time sync issues can make agents install wrong versions. windows time service should be happy on all servers.

merci for bringing this to q&a ) hope this sorts out ur agent drama.

Alex

and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer

https://ctrlaltdel.blog/