Upgrade to the latest version of Portworx Enterprise for continued support. Documentation for the latest version of Portworx Enterprise can be found here.
Synchronous DR for Kubernetes
Portworx supports synchronous (Metro) DR when installed as a single stretch cluster across multiple Kubernetes clusters. The Kubernetes clusters need to span across a metropolitan area network with a maximum latency of 10 ms. This document explains how to install a stretch Portworx cluster and achieve synchronous DR. It will demonstrate how to failover and failback applications between two Kubernetes clusters.
Perform the following steps to set up Metro DR:
NOTE:
- The sections of this document require specifying a
<namespace>, you should update this to the namespace where Portworx is installed in your environment. - A maximum replication factor of
2is supported in a Metro-DR deployment. Usingrepl: 3might cause downtime because of a loss of volume quorum.
-
Prerequisites arrow_forward_iosPrerequisites for synchronous DR migration
-
Prepare your Portworx cluster arrow_forward_iosFind out how to install a single stretch Portworx cluster across multiple Kubernetes clusters.
-
Generate and apply cluster pair arrow_forward_iosFind out how to pair your clusters
-
Synchronize your clusters or schedule migrations arrow_forward_iosFind out how to synchronize your clusters by scheduling periodic migrations between them.
-
Configure a reverse migration schedule arrow_forward_iosFind out how to reverse synchronize your clusters.
-
Failover an application arrow_forward_iosFind out how to failover an application from one Kubernetes cluster to another.
-
Failback an application arrow_forward_iosFind out how to failback an application from the backup Kubernetes cluster to the original one.