Performing a Failback

Scenarios

After a failover, services are running at the disaster recovery site. You can fail back to your production site with a failback.

Failback is a high-risk operation. After a failback, services are started at the production site. At this time, you must ensure that disaster recovery site services are stopped. Otherwise, services may be conflicted or interrupted and data may be damaged because both sites are providing services.

Failback is not supported for replica pairs whose Type is set to IDC-to-cloud and Scenario set to V2C.

Prerequisites

• Initial synchronization is completed for the protected instance, and the status of the protected instance is Synchronization finished or Failback failed.
• Protected instance services are running at the disaster recovery site.
• All services on the disaster recovery site server are stopped, and all data has been flushed to disks.

Procedure

1. Log in to the management console.
2. Click Service List and choose Storage > Storage Disaster Recovery Service.

   The Storage Disaster Recovery Service page is displayed.

3. Choose Asynchronous Replication. In the right pane, locate the replica pair housing the protected instance you want to perform a failback and click the number in the Protected Instances column.

   The Protection Groups tab page is displayed.

4. In the navigation tree, choose the target protection group.

   The protection group details page is displayed.

5. In the Protected Instances area, locate the target protected instance and choose More > Execute Failback in the Operation column.

   

6. On the displayed page, click Submit.

   

7. The protected instance status changes to Executing failback. Wait until the operation is complete.

   

8. After the protected instance status changes to Failback completed, the operation is successful.