When the production servers and disks in the primary AZ become faulty due to force majeure and a failover has been performed, enable the DR servers and disks to provide services. After the fault in the faulty AZ has been restored, users can make API calls to reprotect a replication consistency group, that is, to enable the restored resources in the faulty AZ to function as DR servers and DR disks.
For details, see Reprotecting a Replication Consistency Group in the Elastic Volume Service API Reference.
For details, see Querying Details About a Replication Consistency Group in the Elastic Volume Service API Reference.
After the request has been delivered, the replication status of the replication consistency group changes to copying. Once the replication status changes to active, the data synchronization is complete.
The time required for the data synchronization within a replication consistency group varies depending on the number of EVS replication pairs in the group, EVS disk capacity, and amount of differential data generated after a primary AZ fault occurred. Normally, the data synchronization of a reprotection takes a relative long period of time. Please wait patiently.