No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Performing Fault Recovery

Performing Fault Recovery

This section describes how to perform fault recovery at the DR site if data of the production site becomes unavailable due to disasters or faults. The latest data at the DR site is used for recovery. Before performing fault recovery, you are advised to perform at least one successful DR test. Fault recovery can only be performed in the DR management system at the DR end.

Prerequisites

  • You have logged in to the DR management system at the DR site.
  • The management system and the DR environment at the DR site are working properly.
  • At least one recovery plan has been created in the system.
  • Storage devices, hosts, or VMs at the site where a protected group resides have been refreshed, if storage devices, hosts, or VMs at the production site or DR site change. For details, see Refreshing Resource Information.
The following table describes requirements for each protected object type.

Protected Object

Requirement

Oracle/IBM DB2/Microsoft SQL Server/Microsoft Exchange Server

The database configuration of the DR host must be the same as that of the production host, including instance name, database name, and storage path.

FusionSphere VM

  • If the IP address for VM recovery is not configured, the IP address of the VM after recovery is the same as that at the production end. If you want to configure a different IP address, configure one on the Protected Object tab page.
  • If disks are added to or deleted from the protected VM, refresh the VM information and manually execute the protected group where the VM resides.

VMware VM

  • The names of protected VMs cannot contain pound signs (#). Otherwise, you may fail to modify the VMs configuration file while performing fault recovery.
  • If the IP address for VM recovery is not configured, the IP address of the VM after recovery is the same as that at the production end. If you want to configure a different IP address, configure one on the Protected Object tab page.

Context

If the recovery plan is based on the snapshot or clone protection policy template, fault recovery cannot be performed.

In DR DC solutions (geo-redundant mode), if the production center becomes unavailable due to disasters, recover data and run services at the same-city DR center; if the production center and the same-city DR center become unavailable due to disasters, recover data at and run services at the remote DR center.

For FusionSphere VMs (OpenStack architecture), delete the recovery plan after a fault recovery. After the primary OpenStack is installed and the relevant protected group is deleted, contact Huawei technical support engineers to clear the remote replication relationships on the array.

If the VM where the production site resides is configured with an IP address but without any network adapter, after the fault recovery, the IP address of the VM where the DR site resides is:
  • Windows
    • Dynamically obtained when VM specifications already configured.
    • Consistent with that of the VM where the production site resides when VM specifications not configured.
  • Linux

    Dynamically obtained.

Procedure

  1. On the menu bar, select Utilization > Data Recovery.
  2. Select the remote recovery plan for which you want to perform fault recovery and click More > Fault Recovery on the Operation list.
  3. Perform fault recovery based on the protected object type.

    NOTE:
    If Huawei multipathing software has been installed on the Linux DR host, ensure the configured I/O suspension time is not 0 and all virtual devices generated by the software have corresponding physical devices. For details, see the OceanStor UltraPath for Linux V100R008C00 User Guide.
    • If the protected object type is type LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, or Microsoft Exchange Server, perform the following:
      1. Select a DR site.
        • If T series V2 or a later version is deployed at the DR site, the DR host whose services you want to recover can belong to only one host group that belongs to only one mapping view. The secondary LUN of the remote replication pair that corresponds to the storage LUN used by the protected applications can belong to only one LUN group, and the LUN group must belong to the same mapping view as the host group. If T series V200R001C00 is deployed, after creating mapping view, you cannot select the Enable Inband Command to modify the properties of the mapping view.
        • If the storage is T series V2R2 or a later version or 18000 series, the storage support automatic host adding and storage mapping. If the connection between the storage device and the host initiator is normal, the hosts, host groups, LUN mappings, and mapping views will be created in the storage device automatically.
      2. Select a DR host or host group and click OK.
      3. 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.
      4. Click OK.
    • If the protected object type is VMware VM, perform the following:
      1. Select the cluster you want to recover.

        VMs will be recovered to the cluster. You need to set DR Site, DR vCenter, and DR Cluster.

      2. Select a network.

        The default recovery network is the network relevant to the resource mapping. If you want to change it, plan or select another network based on site requirements.

        NOTE:

        If Production Resource and DR Resource are not mapped, select Production Resource and DR Resource and click Add to the mapping view for mapping.

      3. Select non-critical VMs.

        In the Available VMs list, select non-critical VMs you want to stop to release computing resources.

      4. Click Fault Recovery.
      5. 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.
      6. Click OK.
    • If the protected object type is FusionSphere VM, perform the following steps:
      1. Select the cluster you want to recover.

        VMs will be recovered in the test cluster. Select DR Site.

        NOTE:

        Upon the first test network selection, you need to set the cluster information.

      2. Select an available powered-on host.

        The available powered-on host can provide resources for VMs.

      3. Select non-critical VMs.

        In the Available VMs list, select non-critical VMs you want to stop to release computing resources.

      4. Click Fault Recovery.
      5. 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.
      6. Click OK.
    • If the recovery plan is based on the HyperVault or snapshot protection policy template, select Test Host and then select the tested copy, and click Test.
      NOTE:

      In the Protected Object area, click View. In the Associate protected objects dialog box that is displayed, you can view information about copies and change information about the objects under protection.

Result

After a fault recovery starts, you can view the execution process and result. If the fault recovery fails, you can resolve the problem and try again.

Follow-up Procedure

After the fault recovery, services are running at the DR site. If the original production site reconstructs in non-site level (such as power supply recovery after a power outage) and the service switchback is required, perform the following:
  1. Perform reprotection.

    Before switching back services, performing reprotection can protect running data at the DR site and automatically recover the service data generated at the DR site to the original protection site based on the specified policy.

  2. Test the recovery plan.

    After reprotection, the service data at the DR site is recovered to the production site. Before service failback, you need to perform a DR test to ensure data usability.

  3. Clear test data.

    This operation will automatically clear the test data generated during the DR test to ensure the successful rate of service failback.

  4. Perform planned migration.

    This operation will automatically migrate services back to the original production site.

  5. Perform reprotection again.

    To ensure that services can be recovered at the DR site during failback, reprotection needs to be performed again.

For recovery plans whose protected object type is FusionSphere VM (non-OpenStack architecture), after the fault recovery is successfully executed, you can export the configuration file, and view information about the FusionSphere VMs before and after the fault recovery, such as resource mappings. The configuration file can be exported by performing the following:
  1. Select the recovery plan used to perform the fault recovery and click the Protected Object tab in the lower area.
  2. Click Export to save the exported configuration file locally.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10884

Downloads: 55

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next