Portworx Documentation has moved to https://docs.portworx.com
Portworx Enterprise version 2.13 has reached end of life and end of extended maintenance. Refer to the release support policy doc here.
Upgrade to the latest version of Portworx Enterprise for continued support. Documentation for the latest version of Portworx Enterprise can be found here.
Upgrade to the latest version of Portworx Enterprise for continued support. Documentation for the latest version of Portworx Enterprise can be found here.
Asynchronous Disaster Recovery (DR)
With asynchronous DR, you can replicate Kubernetes applications and their data between two Kubernetes clusters. Here, a separate Portworx Enterprise cluster runs under each Kubernetes cluster.
- The source Kubernetes cluster asynchronously backs up apps, configuration and data to the destination Kubernetes cluster.
- Incremental changes from Kubernetes applications and Portworx data are continuously sent to the destination cluster.
- In case the source cluster becomes unavailable, you can activate the applications in the destination cluster.
You can find a list of supported Kubernetes resources in the Supported Kubernetes article.
Follow the instructions in the following sections in order to set up an asynchronous DR for your cluster.
NOTE: The following sections require specifying a
<namespace>
. In your environment, update this to the namespace where Portworx is installed. Typically, Portworx is installed in either the kube-system
or portworx
namespace.
-
Prerequisites Prerequisites for Async DR migration.
-
Prepare your environment Prepare your source and destination clusters for asynchronous DR.
-
Generate and apply a cluster pair spec How to pair your clusters.
-
Schedule a migration How to set up asynchronous schedules.
-
Failover an application How to failover an application from one Kubernetes cluster to another.
Last edited: Tuesday, May 16, 2023
Questions? Visit the Portworx forum.