That would be fine as long as the protection group contains only the one volume. Then create the recovery plan with this protection group and you can safely fail it over without impacting any other volumes.
Yes that is what I will have, 1 volume with 1 VM. Thank you. As far as cleanup goes, I will shut down the VM, remove it from inventory, unmounts the datastore, remove from the hosts, and then re-enable replication primary -> DR.
1 person found this helpful
Which version of SRM? I assume you are using one of the latest versions?
If so, once the Planned Failover of the Recovery Plan has been executed, you should run the Reprotect workflow. This will configure replication and protection in the reverse direction. You can then fail back to the original site, where you can run the Reprotect again and everything will be back to how you started.
This would be a useful thing to test as you will probably want to this in the case of full-scale disaster recovery or Planned Migration.
Otherwise, you will have to remove the recovery plan and protection groups before you delete the VM. SRM will be tracking the VM due to its protection status and if it suddently just disappears, it can cause issues in the SRM DB.
6.1.1 of SRM which I believe has the reprotect.