an old thread to bring up but after much research the only one which matches my own experiences. using SRM 5.5.1 and vsphere replication 5.5.1
we have 2 vCenter servers. each has a primary VR appliance but also 2 branch based VR's in other countries acting as a local DR source managed by the same vCenter instances
When setting up vsphere replication for a VM we can override the auto-assign and pick the appropriate VR to carry out the replication
an SRM fail-over works as expected. However the SRM re-protect is where issues start. it seems the re-protect auto assigns the VR to use and the logic behind auto assign is to use the VR with the least replications! Therefore it picks our branch based VR on a slow link causing long/impossible re-protect times. It also tries to do a full sync which doesn't seem right at all.
has anyone else experienced these quirks and or worked around them?
my only workaround might be to power off the branch VR's during a re-protect so it forcefully goes to the right place but this isn't a fantastic solution!