DR - Failback Scenario
-
Hi,
We are exploring DR scenarios currently. We have multiple XO Pools on different Geo locations. So far we've been doing Continuous Replicas from Pool A to Pool B.
We have had few isolated incidents where we had to turn on the replica, but we've not had the need to failback to the original machine (sync changes back).In an event of failure of the Pool A (data center A), we can quickly turn on all replicas as they'll be replicated in Pool B - Great ! However, we don't see any automated way for the failback process (going from Pool B to Pool A, after Pool A is recovered)
So far we are thinking to have additional Continuous Replication jobs, going from Pool B to Pool A, in case we failover to Pool B. Though that would mean that we'll have to delete the VMs in Pool A, and do a full replica, which will take a long time, as well as bandwidth.
Is there any right / approved way of setting up the continuous replicas for disaster recovery with a failback option which doesn't need to do a full replica ?
Hristo
-
Hi,
Indeed, there's no existing way to reverse a CR after an incident on the "source site". That's because it's a complicated topics, depending on many variables.
See https://github.com/vatesfr/xen-orchestra/issues/2154
If you have a subscription for your XCP-ng+XO infrastructure, we might reconsider this to create something tailored to your need, please open a support ticket in that case.
closed Ability to reverse a CR/DR job #2154
-
Hi olivierlambert,
Thank you for the quick reply.It is indeed complicated process and we're trying to work around it. We do have only XO premium subscription.
We haven't considered licensing the hypervisors yet.I guess we'll have to look at manual replica jobs to failback for now.
Hristo
-
Keep us posted, we can offer more when you have the whole stack under subscription (and we'll have new offers in the next months in that way)
-
That's great, we'll be watching the space.
