Metro-DR solution for Fusion Data Foundation

Understand the Metro Disaster Recovery (Metro-DR) steps and commands necessary to be able to failover an application from one OpenShift Container Platform cluster to another and then failback the same application to the original primary cluster. In this case, the OpenShift Container Platform clusters are created or imported by using Red Hat Advanced Cluster Management (RHACM) with distance limitations between the OpenShift Container Platform clusters of less than 10 ms RTT latency.

The persistent storage for applications is provided by an external IBM Storage Ceph cluster that is stretched between the two locations with the OpenShift Container Platform instances that are connected to this storage cluster. An arbiter node with a storage monitor service is required at a third location, which is a different location than where OpenShift Container Platform instances are deployed to establish quorum for the IBM Storage Ceph cluster in the case of a site outage. This third location can be in the range of ~100 ms RTT from the storage cluster that is connected to the OpenShift Container Platform instances.

This is a general overview of the Metro-DR steps that are required to configure and execute OpenShift application disaster recovery capabilities by using Fusion Data Foundation and RHACM across two distinct OpenShift Container Platform clusters separated by distance. In addition to these two managed clusters, a third OpenShift Container Platform cluster is required that is the RHACM hub cluster.