Hi all!
I'm planning to build geographically dispersed cluster with online (synchronous) storage replication. So I will have two sites, site-A and site-B and two storage systems stor-A (on site-A) and stor-B (on site-B). I also have two cluster nodes clus-A (on site-A) and clus-B (on site-B). I'm planning to use traditional quorum (vanilla) instead of mns. In normal case site-A is always running services and site-B is standby.
My question here is:
If site-A totally fails (fire, earthquake etc.), how can I bring services up on site-B? When using storage replication, also the quorum-disk is replicated and the replica of quorum on stor-B says that clus-A is the active node. Can I somehow force clus-B to be the active node?
I'm planning to build geographically dispersed cluster with online (synchronous) storage replication. So I will have two sites, site-A and site-B and two storage systems stor-A (on site-A) and stor-B (on site-B). I also have two cluster nodes clus-A (on site-A) and clus-B (on site-B). I'm planning to use traditional quorum (vanilla) instead of mns. In normal case site-A is always running services and site-B is standby.
My question here is:
If site-A totally fails (fire, earthquake etc.), how can I bring services up on site-B? When using storage replication, also the quorum-disk is replicated and the replica of quorum on stor-B says that clus-A is the active node. Can I somehow force clus-B to be the active node?
