This article is contunuation of the previouse one: VCF Fleet with Site High Availability (Across Zones)
Now let’s move from high availability within a region to disaster recovery across regions.
On this slide we have:
-
Region 1, which acts as the primary site, and
-
Region 2, which acts as the disaster recovery site.
Each region has its own VCF instance. Between them we configure replication for the relevant workloads and, where appropriate, management components.
The focus here is different from the stretched cluster:
-
A stretched cluster is about continuous availability and shared capacity across two zones, usually in the same region, with IP portability.
-
A DR design is about recovering from a regional disaster. One side is active, the other is primarily there for failover and recovery.
With DR across regions we:
-
Provide robust disaster recovery mechanisms to ensure business continuity if an entire region is lost.
-
Include strategies for failover and failback between Region 1 and Region 2.
-
Plan the appropriate capacity and number of availability zones in the DR region so it can take over the required workloads.
You can essentially think in terms of reflection:
-
In one scenario, Region A is active and Region B is the DR target.
-
In another, you can reverse that relationship or even run active‑active patterns, depending on business needs.
