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

HUAWEI CLOUD Stack 6.5.0 Backup and Restoration Guide 03

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).
Restoring eReplication Data

Restoring eReplication Data

If eReplication encounters anomalies after an upgrade or key data adjustment, you can import the backed up system configuration data to eReplication to implement restoration.

Prerequisites

  • The data encryption password configured during configuration data backup has been obtained.
  • A cross-platform file transfer tool, such as WinSCP, has been installed.
  • A cross-platform remote access tool, such as PuTTY, has been obtained.
  • The login password of user root or DRManager in Linux has been obtained.
  • The version of the backed up configuration data must be consistent with the current software version. Otherwise, protection or restoration services may become abnormal.
  • eReplication has been stopped before backup data is imported. After eReplication is stopped, you cannot use eReplication to perform DR management. Stop eReplication only for fault diagnosis.

Context

If the original management server is configured with a remote management server, modify the information about the remote management server on the current management server after the backup data of the original management server is imported into the current management server. Otherwise, exceptions may occur during service operation. For example, A and B are the original management servers and are the local and remote management servers of each other. C and D are the current management servers and are the local and remote management servers of each other. After the backup data of A and B is imported into C and D respectively, you must change the remote management servers on C and D to D and C respectively.

  • After restoration, data generated between the backup point in time to the restoration point in time is lost.
  • After restoration, data on eReplication may become inconsistent with that on storage devices, hosts, vCenter servers, FusionManager, FusionCompute, or VRG. The system automatically checks data consistency. Alarms are reported if data inconsistency is detected. You can troubleshoot the problem based on reported alarms.

Procedure

The following describes how to import backup data in Linux.

  1. Use WinSCP to copy the exported backup file ConfigData.zip to any directory on the eReplication Server, for example, /home/configdata.
  2. Use PuTTY to log in to the eReplication management server.

    Log in as user DRManager, and run the su root command to switch to user root.

    NOTE:

    The default password of user DRManager is Huawei@CLOUD8. The default password of user root is Huawei@CLOUD8!.

  3. Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run exit command to exit the system after completing your operations.

  4. Run cd /opt/BCManager/Runtime/bin to enter the path.

    NOTE:

    In Linux, the installation path of eReplication is /opt/BCManager. The path is fixed.

  5. Run the sh shutdownSystem.sh command and enter y to stop eReplication.

    eReplication is stopped successfully if the following command output is displayed:

    The DR system is shut down successfully.
    NOTE:

    Before proceeding to the next step, ensure that eReplication is stopped.

  6. Run the sh import.sh command to import backup data.
  7. After ensuring that eReplication is stopped, type y in the prompt message and press Enter.

    The following command output is displayed:

    Please input the restore file:

  8. Enter the save path of the backup data to be imported as prompted and press Enter. For example, the save path can be /home/configdata/ConfigData.zip.

    The following command output is displayed:

    Please input old encrypt password:

  9. Enter the data encryption password that is configured during the backup data export and press Enter.

    Backup data is imported successfully if the following command output is displayed:

    restore successfully. Please restart the Server.

  10. Run the sh startSystem.sh command to start the eReplication.

    eReplication is started successfully if the following command output is displayed:

    System started completely.

Translation
Download
Updated: 2019-06-14

Document ID: EDOC1100062366

Views: 840

Downloads: 10

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