Applying DRpolicy to an ApplicationSet-based application

Before you begin

Ensure that both managed clusters referenced in the DRPolicy are reachable. If not, the application will not be DR protected untill both clusters are online.

Procedure

  1. On the Hub cluster, navigate to All Clusters > Applications.
  2. Click the Actions menu at the end of application to view the list of available actions.
  3. Click Manage disaster recovery.
  4. Click Enroll application.
  5. Select Policy name and click Next.
  6. Select an Application resource and then use PVC label selector to select PCV label for the selected resource.
    Note: You can select more than one PVC label for the selected application resources.
  7. After adding all the application resources, click Next.
  8. In the Enroll managed application modal, review the policy configuration details and click Assign. The newly assigned Data policy details are displayed on the Manage disaster recovery modal.
  9. Verify that you can view the assigned policy details on the Applications page.
    1. On the Applications page, navigate to the DR Status column and view the status.

      The status can be any of the following:

      • Protecting: Shown during initial DR setup before data synchronization begins
      • Healthy: All volumes and Kubernetes resources are syncing normally
      • Warning: Volumes or Kubernetes resources are syncing slower than usual
      • Critical: Volumes or Kubernetes resources are not syncing
      • Protection Error: An error occurred during application protection setup

      You can click the status to view the last synced time for application volumes and the DR policy assigned.

      Note: It may take a few minutes for the DR Status to move from Protecting to Healthy after disaster recovery is enabled. The DR status will show Protecting during initial setup, then automatically transition to health-based statuses (Healthy/Warning/Critical) once data synchronization begins.
    2. Failover and relocate status can be viewed in the DR Status column when initiated. These statuses can be clicked to view more details about the action.

      DR Status shows either Protecting, Healthy, Warning, or Critical when failover or relocate is not taking place. During failover or relocate operations, the status will show the operation-specific status (FailingOver, Relocating, and so on).

  10. In the user interface, verify the volume consistency groups:
    1. In the Overview tab, at the end of the protected application row from the action menu (⋮), select Manage disaster recovery.
    2. In the modal, verify Volume group replication is Enabled.
    3. In the same modal, select View volume groups.
    4. Verify the volume consistency groups have the correct volumes and a Synced status.
  11. Optional: For Rados block device (RBD), verify volumereplication, volumereplicationgroup, and volumegroupreplication on the primary cluster.

    For volumereplication:

    oc get volumereplication -A

    Example output:

    NAMESPACE        NAME                                      AGE    VOLUMEREPLICATIONCLASS                  SOURCEKIND               SOURCENAME                                                    DESIREDSTATE   CURRENTSTATE
busybox-sample   vr-bc4a166e-13bc-45cd-99f0-8bd516f7ffcc   112s   rbd-volumereplicationclass-1625360775   VolumeGroupReplication   vgr-07a0050bee1f25720f5cae8d5daa6230-busybox-placement-drpc   primary        Primary

    For volumereplicationgroup:

    oc get volumereplicationgroup -A

    Example output:

    NAMESPACE        NAME                     DESIREDSTATE   CURRENTSTATE
busybox-sample   busybox-placement-drpc   primary        Primary

    For volumegroupreplication:

    oc get volumegroupreplication -A

    Example output:

    NAMESPACE        NAME                                                          VOLUMEGROUPREPLICATIONCLASS                             VOLUMEGROUPREPLICATIONCONTENT                     DESIREDSTATE   CURRENTSTATE   AGE
busybox-sample   vgr-07a0050bee1f25720f5cae8d5daa6230-busybox-placement-drpc   rbd-volumegroupreplicationclass-1625360775-1602718344   vgrcontent-bc4a166e-13bc-45cd-99f0-8bd516f7ffcc   primary        Primary        114s
  12. Optional: For CephFS, verify ReplicationGroupSource and ReplicationSource on the Primary cluster.

    For ReplicationGroupSource:

    oc get ReplicationGroupSource -A

    Example output:

    NAMESPACE        NAME                                              LAST SYNC              DURATION          NEXT SYNC              SOURCE                                                                                                         LAST SYNC START
busybox-cephfs   busybox-cephfs-bbd241b65b6589782fddaa82636e358d   2026-03-18T11:20:14Z   1m16.462467415s   2026-03-18T11:25:00Z   {"matchLabels":{"ramendr.openshift.io/consistency-group":"busybox-cephfs-bbd241b65b6589782fddaa82636e358d"}}

    For ReplicationSource:

    oc get ReplicationSource -A

    Example output:

    NAMESPACE        NAME          SOURCE           LAST SYNC              DURATION        NEXT SYNC
busybox-cephfs   busybox-pvc   vs-busybox-pvc   2026-03-18T11:20:14Z   16.450725976s
  13. Optional: For CephFS, verify ReplicationGroupDestination and ReplicationDestination on the Secondary cluster.

    For ReplicationGroupDestination:

    oc get ReplicationGroupDestination -A

    Example output:

    NAMESPACE        NAME                                              LAST SYNC              DURATION        LAST SYNC START
busybox-cephfs   busybox-cephfs-b1f2b5bac27b3d8805437424895d212c   2026-03-18T11:20:15Z   47.700328282s   2026-03-18T11:20:15Z

    For ReplicationDestination:

    oc get ReplicationDestination -A

    Example output:

    NAMESPACE        NAME          LAST SYNC              DURATION        NEXT SYNC
busybox-cephfs   busybox-pvc   2026-03-18T11:20:15Z   47.401909636s