Metro-DR deployment workflow

This section provides an overview of the steps required to configure and deploy Metro-DR capabilities using the latest versions of IBM Fusion Data Foundation, IBM Storage Ceph and Red Hat Advanced Cluster Management for Kubernetes (RHACM) version 2.9 or later, across two distinct OpenShift Container Platform clusters. In addition to two managed clusters, a third OpenShift Container Platform cluster will be required to deploy the Advanced Cluster Management.

To configure your infrastructure, perform the following steps:

1. Ensure requirements across the Hub, Primary and Secondary Openshift Container Platform clusters that are part of the DR solution are met.
   See Requirements for enabling Metro-DR.
2. Ensure you meet the requirements for deploying IBM Storage Ceph stretch cluster with arbiter.
   See Requirements for deploying IBM Storage Ceph stretch cluster with arbiter.
3. Deploy and configure IBM Storage Ceph stretch mode.
   For instructions on enabling Ceph cluster on two different data centers using stretched mode functionality, see Deploying IBM Storage Ceph.
4. Install Fusion Data Foundation operator and create a storage system on Primary and Secondary-managed clusters.
   See Installing Fusion Data Foundation on managed clusters.
5. Install the ODF Multicluster Orchestrator on the Hub cluster.
   See Installing Fusion Data Foundation Multicluster Orchestrator operator.
6. Configure SSL access between the Hub, Primary and Secondary clusters.
   See Configuring SSL access across clusters.
7. Create a DRPolicy resource for use with applications requiring DR protection across the Primary and Secondary clusters.
   See Creating Disaster Recovery Policy on Hub cluster.

   Note: The Metro-DR solution can only have one DRpolicy.
8. Testing your disaster recovery solution with:
   1. Subscription-based application:
      • Create sample applications. See Creating sample application.
      • Test failover and relocate operations using the sample application between managed clusters. See Subscription-based application failover and relocating subscription-based application.
   2. ApplicationSet-based application:
      • Create sample applications. See Creating ApplicationSet-based applications.
      • Test failover and relocate operations using the sample application between managed clusters. See ApplicationSet-based application failover and relocating ApplicationSet-based application.
   3. Discovered applications
      • Ensure all requirements mentioned in Prerequisites is addressed. See Prerequisites for disaster recovery protection of discovered applications.
      • Create a sample discovered application. See Creating a sample discovered application
      • Enroll the discovered application. See Enrolling a sample discovered application for disaster recovery protection
      • Test failover and relocate. See Failover disaster recovery protected discovered application and Relocate disaster recovery protected discovered application.