Service Migration in the Production Center After Fault Recovery

Prerequisites

• LUN-based protection policies and recovery plans have been configured for other applications.
• For protected groups that use asynchronous remote replication, the DR center has at least one copy of intact service data.
• The datastore name cannot contain Chinese characters.

Context

If data or applications become unavailable due to disasters or faults in the production center, services will be quickly switched to and started in the DR center. After the production center recovers, the services will be switched back to it by performing planned migration.

Procedure

1. Perform a fault recovery.
   

   If Huawei UltraPath has been installed on the Linux-based DR host, ensure that I/O suspension time is not 0 and all virtual devices generated by UltraPath have corresponding physical devices. For details, see the OceanStor UltraPath for Linux xxx User Guide.

   1. On the menu bar, select Utilization > Data Restore.
   2. Select the recovery plan to be recovered and click More > Fault Recovery on the Operation list.
   3. Perform fault recovery based on protected object types.
      • If the type of protected objects is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, SAP HANA, or Microsoft Exchange Server, perform the following operations:
        1. Select DR Site.
        2. Select Host (Group) > Available DR Hosts or Host Groups.
           

           • If the storage array used at the DR site is flash storage 6.1.6 or later, the to-be-recovered host selected by a user can belong to only one host group on the storage array, and the host group can belong to only one mapping view. In addition, the remote replication secondary LUN corresponding to the storage LUN used by the protected application and the LUN to which the redo logs and archive logs of the DR cluster belong must belong to the same LUN group, and the LUN group and the host group must belong to the same mapping view.If the storage array version is flash storage 6.1.6 or later, deselect Enable Inband Command to change the mapping view attribute after the mapping view is created.

           • If the storage array is flash storage 6.1.6 or later, automatic host adding and storage mapping are provided. Ensure that the storage is connected to hosts' initiators properly. In this manner, the system can automatically create hosts, host groups, LUN groups, and mapping views on the storage. The creation principles are as follows:

             

        3. Click Fault Recovery.
        4. In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
        5. Click OK.

2. In the production center, check the application startup status.

   After the fault recovery is complete, check whether the applications and data are normal. If an application or data encounters an exception, contact Huawei technical support.

   • Note the following when checking the startup status of applications.
   • If the protection policies are based on applications, check whether the applications are started successfully and data can be read and written correctly.

3. Perform the configuration before starting reprotection.
   

   Before performing Oracle ADG fault recovery reprotection, you need to manually restore the Oracle ADG and reconfigure the replication pair of the LUN.

   • Manually repair the Oracle ADG.

     Based on fault recovery, the fault recovery site (the original secondary ADG) functions as the new primary Oracle ADG, and the original primary ADG functions as the new secondary ADG.

   • Reconfigure a LUN's replication pair.

     Delete the original remote replication, log in to the active and standby Oracle hosts, run the upadmin show vlun command to view the WWN of the current REDO disk, query the corresponding LUN based on the WWN, and re-create the remote replication.

4. Perform reprotection to protect services switched to the DR center.

   After the planned migration is complete, the application system is working in the DR center and protected groups become Invalid. You must perform reprotection to recover the replication status and synchronize the data from the DR center to the production center. Then, the original DR center becomes the new production center.

   

   To ensure that the protection and restoration configurations before reprotection do not affect the running of the protected group and recovery plan after reprotection, the system automatically clears the protection and restoration configurations after reprotection. After performing reprotection, reconfigure the protection and recovery policies to ensure that DR services are running properly.

   1. On the menu bar, select Utilization > Data Restore.
   2. Select the recovery plan and click More > Reprotection on the Operation list.
   3. Carefully read the content of the Confirm dialog box that is displayed and click OK to confirm the information.