Trying to get a disaster recovery plan in place to protect against a major disaster such as server room fire...
We have a couple of clusters geographically separated which I have set up as remote-sites. Site A and B lets call them.
I've set up a PD w/ consistency group with the VMs to protect and periodically snapshot from site A to B. Now in the case of a fire/destroyed cluster at site A... obviously step one is rebuilding a cluster at that site with the appropriate configs, but then...
With a brand new cluster in place, what is the standard process to retreive the snapshots from site B back to the new site A ?
So far, I've activated the backup on site B (as if it was an unplanned outage and left it off). and recreated the remote-site link on the newly built out site A. I am thinking I now create a new PD to shuffle the VMs/consistency group back to Site A and then activate there and I am done ?
I know this works as I've done it now. But is this the 'preferred method'?
I'd appreciate any thoughts from the gurus out there ;)
Best answer by JonView original
If you had 2 clusters, A and B, and you migrated a PD from A to B, and cluster A still existed, then by definition the PD would "be there" with some seed data, allowing you to re-replicate and fail back much easier.
In the case where cluster A "went away", then you can't really pre-build anything.
That said, If I missed the mark on understanding this, feel free to restate and I'll take a second swing.