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).
What Can I Do If Protected Groups and Recovery Plans Cannot Be Deleted at the Production Center When the DR Center Encounters an Irrecoverable Fault?

What Can I Do If Protected Groups and Recovery Plans Cannot Be Deleted at the Production Center When the DR Center Encounters an Irrecoverable Fault?

Symptom

In a DR scenario where the host-based replication DR technology is used, when the DR site encounters an irrecoverable fault, the DR environment data must be deleted at the production site and DR reconfiguration is required. However, any data (such as protected groups, recovery plans, and resource mappings) cannot be deleted at the production site.

Possible Causes

When the DR environment data is deleted at the production site, the data at the DR site will also be deleted. As a result, any data at the production site cannot be deleted.

Procedure

  1. Check whether backup data exists at the DR site.

    • If yes, go to 2.
    • If no, go to 3.

  2. When backup data exists at the DR site:
    1. Re-install eReplication at the DR site. For details, see Installing the eReplication Server.
    2. Import the backup data to the DR site to restore its data. For details, see Restoring Configuration Data.

      NOTE:

      After performing this operation, you do not need to delete the data and reconfigure the DR environment at the production center if the DR site recovers.

  3. Backup data does not exist at the DR site.
    1. Re-install eReplication at the DR site. For details, see Installing the eReplication Server.

      NOTE:

      During the installation, ensure that the management IP address of the eReplication and admin's password are those used before the fault occurs.

    2. After the installation is complete, wait 5 to 10 minutes. After the eReplication Server is started, log in to eReplication at the DR center. If the login succeeds, the installation is successful.
    3. On eReplication at the production center, delete recovery plans, protected groups, resource mappings, and sites configured on eReplication at the DR center before the fault occurrence.
    4. On eReplication at the DR center, add resources to the newly created site.
    5. On eReplication at the production and DR centers, add each other's management server as the remote management server.
    6. On eReplication at the production center, create resource mappings and recovery plans.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 13851

Downloads: 68

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