I am in the initial stages of testing a 1:N SRM 5.5 setup. I have vcenterA (production) and vcenterB (DR). I also have two remote clusters, clusterA (production, hosted on vcenterA) and clusterB (DR, hosted on vcenterB). I have a primary appliance deployed on the prod and DR vcenters, as well as an appliance at each remote site. (The connection is much faster directly between the remote sites then trying to route it through one of the vcenter locations)
The initial fail-over works flawlessly, but my issue is on the reprotection. When it configures the Storage & Protection in the reverse direction, it automatically assumes I want to use the primary VR appliance for that vcenter, and not the one at the remote site (which is added as an additional appliance under the vcenter, if I am setting up the initial replication I can easily specify the remote appliance, it is just the reprotect where there is an issue). Is there any config setting where I can set specific protection groups / recovery plans to reprotect on a specific VR appliance as opposed to the auto-assign? The "Move to" option is grayed out..
I have tested just removing the replication and recreating it on each server during the reprotect, which has worked in my test environment, but I would not want to do that in an actual DR situation as I feel like that amount of manual intervention adds a significant amount of risk...