Failover applications from site 1 to site 2

Application failover is the capability of automatically switching over to the secondary site when the primary site becomes unavailable.

Before you begin

Consider the following points before you failover applications:

If backup policies are applied to the applications on site 1, they continue to run until those polices are removed from the failover application.
The applications must be enabled for disaster recovery.
Scale down of an application before initiating planned failover.
Before unplanned failover of applications to surviving site, do Metro-DR Data Fencing. For the procedure, see Metro-DR data fencing.

The planned failover must be done from the site where you want the applications to be failed over.

Note: If you plan to failover virtual machines, also see Disaster recovery for virtual machines.

In the Replicated applications page, click Actions > Failover.
The Failover remote applications window gets displayed. It also indicates the number of applications available for failover. This Failover does a failover for all remote applications.
In the Failover remote applications window, select the applications and click Failover.
It creates the Persistent Volumes (PVs) that belong to the applications in the local site. In addition, it creates namespace and application CR on the cluster from where you initiated the failover. After relocation is complete to remote cluster, a success message is displayed on the screen.
In the Replicated applications page, check the status of the Primary cluster.

Initially, the status of the Primary cluster for the application is Failing over. After successful completion of the failover, the primary cluster of the given application must be changed to secondary site or partner cluster. After completion, it displays
icon next to the name of the Primary cluster, and a Failover complete notification is displayed. The IBM Fusion HCI prepares the cluster for deployment of the relocated applications.
Scale up the applications.