After HyperMetro data centers recover from a fault, services will be migrated back to them.
Prerequisites
- Application-based protection policies and recovery plans have been configured.
- For protected groups that use asynchronous remote replication, the DR center has at least one copy of intact service data.
Context
Services are migrated from HyperMetro data centers to the DR center due to a recoverable fault such as an unexpected power failure. After the HyperMetro data centers recover from the fault, you must synchronize data generated during the DR from the DR center to the HyperMetro data centers and migrate services back to the HyperMetro data centers.
Procedure
- In HyperMetro (SAN) and asynchronous replication (SAN) scenarios, you can use UltraVR to migrate back services as follows:
- Check the environment before starting the reprotection.
- Log in to a service host in an HyperMetro data center and stop services.
For FusionCompute VMs: Log in to FusionCompute, delete protected VMs, and disassociate datastores used by the VMs with the VMs.
- Suspend site A to suspend HyperMetro pairs of storage arrays at the active end in the HyperMetro data centers.
Figure 1 shows the state of data replication between storage arrays before the planned migration.
- Log in to a service host in an HyperMetro data center and stop services.
- Perform reprotection to protect services migrated to the remote DR center.
After the planned migration is complete, the application system is working at the remote DR site and protected groups become Invalid. You must perform reprotection to recover the replication status and synchronize data from the remote DR center to the HyperMetro data centers.
To ensure the normal running of protected groups and recovery plans after reprotection, the system automatically clears protected and recovered configurations, including startup configurations of protection policies and recovery plans, self-defined execution scripts, and self-defined execution steps. In addition, reconfiguration of protection and recovery policies is recommended to ensure the continuity of DR services.
- On the menu bar, select
Recovery. - Select the recovery plan and click More > Reprotection on the Operation list.
- Carefully read the content in the Confirm dialog box that is displayed and click OK to confirm the information.
If Save user configuration data is selected, self-defined protection policies and recovery settings, such as self-defined recovery steps, will be retained. Ensure that the configuration data has no adverse impact on service running after reprotection.
Figure Data replication after the reprotection shows the state of data replication between storage arrays after the reprotection.
- On the menu bar, select
- Test recovery plans and clear data generated during tests.
Before services are migrated back, perform a DR test to verify data availability to ensure service failback success rate. After the test, clear test data to avoid failback failures caused by the test data. For details, see DR Testing.
- Perform planned migration.
Migrate services back to the HyperMetro data centers. After the migration, check the data. For details, see 1 to 2 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
Starting HyperMetro synchronization is optional. You need to edit the planned migration procedure. Select Enable the step under Recover the HyperMetro (Configurable).
Figure Data replication after the planned migration shows the state of data replication between storage arrays after the planned migration.
- Perform reprotection again.
After the planned migration is complete, application systems are working in HyperMetro data centers and protected groups become Invalid. To ensure that services migrated back to the original HyperMetro data centers can be recovered at the remote DR center after an event (planned or unplanned) happens, reprotection must be performed and the replication status from HyperMetro data centers to the remote DR center must be recovered to synchronize data generated at the HyperMetro data centers to the remote DR site and to ensure that services are protected. For details, see 3 to 4 in Performing Planned Service Migration from an HyperMetro Data Center to the Remote DR Center.
Figure Data replication after the reprotection shows the state of data replication between storage arrays after the reprotection.
- Check the environment before starting the reprotection.
