Skip to main content
Version: 3.6

Synchronous Disaster Recovery

This topic explains how to install a stretched Portworx cluster and achieve synchronous disaster recovery (DR). It demonstrates how to failover and failback applications between two clusters.

To deploy a synchronous DR (also known as Metro DR) setup, you must install a single stretched Portworx cluster across two clusters. A single Portworx cluster spans an on-premises environment with a maximum round-trip latency of 10 ms.

The following diagram shows a synchronous DR setup involving two clusters in the same metropolitan area network:

Detailed Sync setup

Supported platforms​

The following table shows the platforms and storage configurations supported for synchronous DR:

PlatformvSphere cloud driveFlashArray cloud driveLocal drivesKubeVirt VMs
VMware vSphere Kubernetes Service✓---
Vanilla Kubernetes✓✓✓-
Rancher Kubernetes Engine 2✓✓--
OpenShift Container Platform✓✓✓✓
SUSE Virtualization¹-✓-✓

¹ SUSE Virtualization requires Stork 26.2.0 or later and Portworx Enterprise 3.5.2 or later.

important
  • Cluster-wide operators are not migrated as part of a DR migration if they are not installed in the same namespace as the applications you want to migrate (for example, in OpenShift, the operator installation defaults to the openshift-operators namespace). As a result, after migration, you will not be able to scale up or down your applications on the destination cluster using storkctl.
  • In a Synchronous DR setup:
    • The maximum supported replication factor is 2.
    • Portworx does not support sharedv4 service volumes in the cluster.
  • For KubeVirt VMs, synchronous DR is supported only with Portworx Enterprise raw block volumes. Sharedv4 service volumes are not supported.

Setting up synchronous DR​

Perform the following steps to set up synchronous DR:

Last updated on