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).
Self-defining Execution Steps in a Recovery Plan

Self-defining Execution Steps in a Recovery Plan

During DR, if you want to reset the DR network or stop some services at the DR site to release system resources for smooth service recovery, you can self-define the execution steps on eReplication. This operation can be performed only on eReplication of the DR site.

Prerequisites

You have logged in to the DR management server at the DR site.

Context

The management server provides the default recovery plan execution steps for different types of recovery, including testing, clearing, planned migration, to ensure correct recovery and switchover. The existing functions of eReplication cannot meet all service recovery requirements. For example, during DR, the DR network of the DR site must be reset or non-critical services must be stopped at the DR site to release the system resources to recover critical services. Therefore, eReplication allows you to modify the steps of a recovery plan.

Execution steps in a recovery plan are classified into two types, as described in Table 6-27.
Table 6-27  Recovery plan execution steps

Type

Description

Default execution steps

For default recovery plan execution steps, eReplication defines which steps can be selected and which steps can be modified and provides default configurations to meet basic recovery requirements. You can modify the default recovery plan execution steps to control whether some steps take effect in recovery plan execution based on functions to be achieved using steps and service recovery requirements.

Self-defined execution steps

If the default recovery plan execution steps cannot meet recovery service requirements, you can self-define your recovery plan execution steps by adding script steps to flexibly meet recovery requirements in a wide range of scenarios. Note that you cannot add a step before the first or after the last step of the default recovery plan execution steps. You can modify or delete steps when site conditions change.

For testing and clearing, two opposite operations, if testing execution steps are self-defined, you must determine whether opposite operations must be performed during test environment clearing to correctly recover the environment. If opposite operations must be performed, ensure that opposite operations are added to the clearing process. For example, add setting the DR routing network into the testing process, and add clearing the DR routing network into the clearing process.

Procedure

  1. On the menu bar, select Utilization > Data Recovery.
  2. Select the recovery plan whose execution steps you want to self-define and click the Procedure tab below it.
  3. Click Edit.

    The Edit dialog box is displayed.

  4. Select the phase whose steps you want to self-define, for example, test, or clear.
  5. Click Add.

    The Add Step dialog box is displayed.

  6. Based on your requirements, self-define an execution script for recovery plans.

    A self-defined script is not provided by eReplication, so the script provider must ensure the script correctness. Before configuring the script, ensure that the script has been verified by tests.

    1. The name of a self-defined execution script must contain 4 to 32 characters, including letters, digits, underscores (_) and hyphens (-), but cannot start with a hyphen (-). The script name extension must be .bat (for Windows) or .sh (for Linux/UNIX).

      Log in to the host where the protected object resides and obtain the script template for self-defining the execution script.

      • In Windows, the script path is %OceanStor BCManager Agent install path%\bin\thirdparty\sample and the script sample name is sample.bat.
      • In Linux/UNIX, the script path is /home/rdadmin/Agent/bin/thirdparty/sample and the script sample name is sample.sh.

    2. Log in to the DR management server at the DR site or to the service host, place the self-defined execution script in a specified path.

      • The path for placing the script is as follows:
        • In Windows: the script path is %OceanStor BCManager Agent install path%\bin\thirdparty\
        • In Linux/UNIX: the script path is /home/rdadmin/Agent/bin/thirdparty/

    3. Set the owner and execute permission of the self-defined execution script.

      • The setting requirements are as follows:
        • In Windows, settings are not required.
        • In Linux/UNIX, run the chown root xxx.sh command to set the script owner to root. Run the chmod 500 xxx.sh command to set the script execute permission to 500,

          where xxx is the name of the self-defined script.

        If you do not set the owner and execute permission of the self-defined script, the script may be modified by hackers, posing security risks.

  7. Enter Step Name and Script Name.
  8. Select Step Execution Policy and Step Location, and click OK.

    Step Execution Policy is described as follows:

    • After failure process to be continued: The recovery plan execution continues for DR after this step fails.
    • After failure process termination: The recovery plan execution stops for DR after this step fails.

    The value of Step Location can be Before the selected step or After the selected step. You can set the step execution sequence, but you cannot add a step before the first or after the last step of the default recovery plan execution steps.

  9. 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.Click OK.
  10. In the right group box, select or deselect Start the step to enable or disable a step and click Apply.
  11. Click Close.

Follow-up Procedure

After recovery plan execution steps are modified, the modification takes effect when the recovery plan is executed the next time. When a recovery plan is executed, eReplication combines the default recovery plan execution steps, self-defined recovery plan execution steps and sequentially performs the steps in workflow mode. You are advised to implement recovery plan testing and clearing immediately after the recovery plan execution steps are modified to ensure configuration correctness.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 18305

Downloads: 76

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