After services are switched from the production center to the DR center through planned migration, the services must be switched back to the production center based on a drill plan.
Prerequisites
- Planned migration and reprotection have been successfully performed for the service system in the production center according to the recovery plan.
- The production host is working properly and the service system in the original production center is in standby state.
- In the Oracle application, the database is disabled but the cluster is enabled by default on the eReplication Agent. If you need to disable clusters, modify the configuration of disabling clusters. For details, see Changing the Configuration of Stopping the Oracle Cluster.
- The datastore name cannot contain Chinese characters.
Procedure
- Test the recovery plan and clear the test data on eReplication.
Before the services are switched back, you need to perform a DR test to verify the data availability to ensure that services can be switched back successfully. After the test, you must clear the test data to avoid switchback failure caused by test data. For details, see DR Testing in the DR Center.
- Perform pre-migration configurations.
- When the protected objects are databases, pre-migration configurations can be performed in the following two modes.
- Method one: Manually stop applications and delete mapping views.
- Manually stop the service system and database applications and uninstall disks on the production host.
- Delete LUN mappings (to application hosts at the production sites) from the storage array in the production center.
- In the SQL Server cluster, the cluster must be in Maintenance mode before deleting the mapped LUNs.
- In the asynchronous replication scenario of the HANA database, you need to log in to the database to create a snapshot for restoring the database before stopping the service system and database applications. For details, see Creating a HANA Snapshot File.
- Log in to eReplication at the DR site, click Resources, select the site and the storage device, and refresh the storage device status, to ensure that all LUN mappings are removed.
- Method two: Edit planned migration procedures. Before the planned migration, applications on hosts are automatically stopped and mapping views are automatically deleted.
- Log in to eReplication at the DR site, and on the menu bar select On the menu bar, select Utilization > Data Restore.
- Select the recovery plan and click the Procedure tab.
- Click Edit.
- From the drop-down list, select Planned Migration.
- Click Stop production service and click Start the step.
- Click Apply.
- Method one: Manually stop applications and delete mapping views.
- When the type of protected objects is VMware VMs, perform the following configurations:
- Without configuration, the VM IP address for the planned migration is the same as that in the production center. You can configure one for the planned migration on the Protected Object tab page of the recovery plan. For details, see Self-defining Startup Parameters for a Protected Object.
- When the asynchronous replication (NAS) DR solution is deployed, you need to create a share and configure permissions on DeviceManager of the storage array at the DR site. Permissions must be the same as those in the production center.
If you fail to create a share and configure permissions, the planned migration will fail.
- When the type of protected objects is the FusionCompute VM, perform the following configurations:
- Without configuration, the VM IP address for the planned migration is the same as that in the production center. You can configure one for the planned migration on the Protected Object tab page of the recovery plan. For details, see Self-defining Startup Parameters for a Protected Object.
- After adding or removing disks for a protected VM, refresh the information about the VM and manually enable DR for the protected group where the VM resides in time.
- When the protected objects are databases, pre-migration configurations can be performed in the following two modes.
- On eReplication of the DR center, perform a planned migration.
This step aims to switch services back to the production center from the DR center. After the migration, check the data and clear the test data. For details, see 2 to 4 in Planned Migration of Services in the Production Center.
If the protected object type is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server,SAP HANA, or Microsoft Exchange Server, select hosts or host groups in the production center as the recovery target.
- If the protected object type is VMware VM, select vCenter and clusters in the production center as the recovery target.
- If the protected object type is FusionCompute VM, select site in the production center as the recovery target.
- On eReplication of the DR center, perform reprotection.
After you complete the planned migration, the application systems are working in the original production center and protected groups become Invalid. To ensure that the production center can be recovered from the DR center in case an event (planned or unplanned) happens on it after the switchback, perform reprotection and recover the replication relationship between the production center and the DR center to synchronize data and ensure that services are protected. For details, see 5 to 6 in Planned Migration of Services in the Production Center.
Result
Once the reprotection is complete, the protected groups become normal.