Skip to main content

Disaster Recovery Quickstart

This path validates the disaster recovery chain: create sync policies, a basic DR configuration, and a DR instance, wait for Protected, then run an instance failover.

The screenshots in this tutorial come from a real walkthrough:

ItemExample
Instancedocs-walkthrough-20260511
DR configurationdc01
Protected namespacedr-pvc-src-170
Initial primary clusterip170-test-001
Initial secondary clustercluster-ip171-1774332463

Prerequisites​

  • Source and target clusters are registered and Ready.
  • Storage repository is Ready and reachable from both clusters.
  • A demo namespace such as dr-pvc-src-170 exists on the source cluster.
  • Target cluster has required StorageClasses, IngressClasses, image pull secrets, and CRDs.

Create Policies​

Policy management

Create policy

Sync policy type

Create Basic Configuration​

DR basic configuration

Create DR basic configuration

Create DR Instance​

Empty DR instance list

Create DR instance basic form

Select a business namespace and keep workload mode as replica. The screenshot selects test-nginx-2; in the walkthrough environment you can select dr-pvc-src-170. When creating a DR instance, the namespace dropdown only shows namespaces that contain a running Deployment or StatefulSet application. Namespaces that only contain bare Pods, DaemonSets, Jobs, or CronJobs are not selectable protected scopes.

Select protected namespace

Use advanced options for StorageClass mapping, DataSync/ResourceSync policy overrides, Resource Policies, resource custom modifications, and bulk modifications/deletions. This is a scrollable form; continue down to the Resource Policies area when you need fine-grained resource scope control.

Create DR instance advanced options

Create DR instance Resource Policies

Wait until the instance becomes Protected. DataSync should have synchronized data and ResourceSync should have prepared standby resources on the target cluster.

Protected DR instance list

Open the detail page by clicking the instance name.

DR instance detail

Use the sync tab to inspect DataSync and ResourceSync.

Resource and data sync status

Run Failover​

Trigger failover from the instance action. The operator runs precheck, pause schedules, source scale-down, final sync, target scale-up, replica check, role switch, and schedule resume.

Protected instance operation topology

The confirmation popover exposes source scale-down, final sync, and pod-ready validation options.

Failover confirmation

During execution, the instance enters failover-in-progress state.

Failover running

After a successful quick failover, the instance becomes Active; the current UI shows this as unprotected.

Active after failover

Run reverse protection to return to Protected in the new direction.

Protected after reprotect

Verify​

kubectl -n disaster-system get disasterinstance docs-walkthrough-20260511 -o yaml
kubectl -n disaster-system get disasteroperation -l testudo.softcdata.com/instance=docs-walkthrough-20260511
kubectl --context <target-cluster> -n dr-pvc-src-170 get deploy,sts,svc,pvc