Asynchronous Disaster Recovery
In an asynchronous disaster recovery setup, you can replicate your applications and their data between two Kubernetes or OpenShift clusters. A separate Portworx Enterprise cluster runs on each Kubernetes or OpenShift cluster.
The following diagram shows an asynchronous DR setup involving two clusters that are geographically apart:
- Application data and supported Kubernetes resources are asynchronously replicated from a source to a destination cluster, which means there is a delay between data changes occurring on the source cluster and their replication to the destination cluster.
- Incremental changes from Kubernetes or OpenShift applications and Portworx data are continuously sent to the destination cluster.
- If the source cluster becomes unavailable, you can activate the applications in the destination cluster.
Perform the following steps to set up asynchronous DR:
📄 Prerequisites
Prerequisites for Async DR migration.
📄 Prepare your Portworx cluster
Prepare your Portworx cluster 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.
📄 Failback an application
Learn how to failback an application from the backup Kubernetes cluster to the original one.