We are setting up srm for the first time and ran into a problem. We have a dc running at the recovery site online and on a 10.110.12 network. This dc replicates to the remainder of the dc at the customer sites. All the vms that are included in the srm test will start with a 10.110.10 ip address in the primary site and failover. I have the recovery plan setup to change this ip to match the dc at the recovery location which would be 10.110.12 ip space. All the primary vms will failover and poibt to the recovery dc as there dns in the srm config.
When running a test for the first time yesterday, everything worked for the most part in the plan and the vms failed over but.....
Then the customer reported dns issues. We found out that the recovery vms came up online talked to the dc in the Dr location and then went out and replicated to the other dcs in the organization. Resulting in changing the ips to the new recovery side everywhere in dns. Changed from 10.110.10 then to the new ones that came online 10.110.12.
Srm was cleaned up and then the customer manually corrected the ips back to the correct ips. Major issues...
My question is who has done this srm testing with a live dc at the recovery location before? Does anyone have a workaround to PREVENT the replication?
-Turn off the recovery side dc before the test?
-Remove the dns entry in all of the vms failing over in the test?
Please let me know your thoughts.
thanks
J