Hi. I know the standard workflow of a failover/failback:
- Failover to Recovery Site
- Reprotect (reverse replication to original Protected Site)
- Failback (to original Protected Site)
- Reprotect (reverse replication to get environment to original state)
Now, during the first reprotect. SRM reverses replication. That means any changes that have taken place at the recovery site will be written to the original Protected Site storage. My question is, is there a way to perform a real failover (not test failover) and failback without bringing back changed data? Customer will be performing a bunch of testing while failed over, BUT they don't want to bring back those changes for fear that original production data could be compromised.
I'm not sure how this would be accomplished. Once again, test failover is not an option here.
Ultimately, we'd need to have SRM back to it's original state (ready for a Protected to Recovery site failover) after the failover is complete.
thanks