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


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


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).
Rolling Back the Patch of the eReplication Server

Rolling Back the Patch of the eReplication Server


After the patch of the eReplication Server has been installed, the eReplication Server cannot be restarted or the eReplication Server service cannot be accessed even though the eReplication Server is started successfully. In such conditions, patch rollback cannot restore the eReplication Server to the source status.


  • Windows: rollBackPatch.bat
  • Linux:



Usage Guidelines

  • In a network that has two eReplication deployed, patch rollback must be performed on both nodes.
  • In HA mode, you must stop the eReplication Server and then perform patch rollback on both the active and standby ends.
  • After patch rollback, the eReplication Server will be restored to the status before the patch was installed. All eReplication configuration data, such as created protected groups and recovery plans, generated after the patch was installed will be deleted. Only in the following conditions, you are advised to roll back the patch:
    • After the patch is installed, the eReplication service cannot be started.
    • After the patch is installed, the eReplication service cannot be accessed.
  • Windows
    1. Log in to the eReplication Server as an administrator.
    2. Go to path installation path\Runtime\bin.
      In Windows, the default installation path of the eReplication Server is C:\BCManager.
    3. Double-click rollBackPatch.bat. Perform the rollback as prompted.
  • Linux
    1. Use PuTTY to log in to the eReplication Server management server.
      • In template-based installation mode: Log in as user DRManager, and run the su root command to switch to user root.
      • In software package-based installation mode: Log in as user root.
      In template-based installation mode, the default password of user DRManager is Huawei@CLOUD8 and that of user root is Huawei@CLOUD8!.
    2. Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.

      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 to exit the system after completing your operations.

    3. Run the cd /opt/BCManager/Runtime/bin command to go to the save path of the script.
    4. Run the sh command and perform the rollback as prompted.


Linux is used as an example.

CTU1000028078:~ # cd /opt/BCManager/Runtime/bin
CTU1000028078:/opt/BCManager/Runtime/bin # sh
You are about to roll back a patch.
This operation will stop the DR system. All protected groups and recovery plans will be stopped.
To roll back a patch will restore the system configurations to the source status. All service data 
generated after the patch was installed will be deleted.

Suggestion: This operation is only recommended when the eReplication services cannot be started normally. 

Are you sure you want to continue? (y/n): y

Rolling back the patch... Please wait.

Patch rollback succeeded.
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14579

Downloads: 70

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