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).
DR Protection

DR Protection

This section explains how to quickly configure DR services after creating the protected group following the service configuration process.

Self-defining Execution Steps in a Protected Group

The execution steps of the protected group is frozen and unfrozen database to synchronized data in eReplication, to execute protected group normally, you can customize the execution prepared steps before frozen or unfrozen. For example, checking the database status.

Prerequisites

  • At least one protected group has been created in the system.
  • The protected group's status is Normal.

Context

NOTE:

When the protected group is LUN, you can modify the execution step in a protected group.

Procedure

  1. On the menu bar, choose Protection > LUN.
  2. In the function pane, select the recovery plan to be modified and click Procedure.
  3. Click Edit.

    The Edit dialog box is displayed.

  4. Select the modified step.
  5. Select script name.

    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. Log in to the host where protected objects reside to obtain a script template and customize the execution script based on the template.

      • 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.

      • In Windows: the path is %OceanStor BCManager Agent install path%\bin\thirdparty\.
      • In Linux/UNIX: the path is /home/rdadmin/Agent/bin/thirdparty/

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

      • In Windows, settings are not required.
      • In Linux/UNIX, run the chown ICUser:LEGO xxx.sh command to set the script owner to ICUser:LEGO. 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 customized script, the script may be modified by hackers, posing security risks.

  6. Select host(Group) and input script name.
  7. In the right group box, select or deselect Enable the step to enable or disable a step and click Apply.
  8. Click Close.

Exception Handling

After protected group execution steps are modified, the modification takes effect when the protected group is executed the next time. You are advised to implement execute protected group immediately after the protected group execution steps are modified to ensure correct configurations.

Executing a Protected Group

Protected groups can be executed manually or automatically based on the timetable specified in protected policies.

Prerequisites

  • Only protected groups in the Normal state can be executed.
  • If storage devices, hosts or VMs on production site or DR site change, storage devices, hosts or VMs at the site where a protected group resides must be refreshed, for details, refer to Refreshing Resource Information.
  • Information about storage devices and hosts must be refreshed the DR sites where the protected group resides to ensure that information about the protected group is refreshed successfully.
  • If add or delete the disk in the protected VM, refresh the VM and execute this protected group of protected VMs reside manually.
  • The state of the remote replications must be Normal in the array, the state cannot be Synchronizing

Context

If execute protected groups in a Windows host, only execute a protected group in the same time.

If daylight saving time (DST) is enabled on the eReplication management server, a DR protection task whose trigger time point falls within the DST shift period cannot be executed at the scheduled time. Details are as follows: UTC-08:00) Pacific Time (United States and Canada) is used as an example. The DST starts at 2016-03-12 02:00:00, and ends at 2016-11-06 02:00:00.
  • If the start time of the protection policy falls within the first hour (2016-03-12 02:00:00 to 03:00:00) after the DST starts, for example, 2016-03-12 02:30:00, the protection group will be automatically executed with a delay of one hour, that is 2016-03-12 03:30:00.
  • If the start time of the protection policy falls with the last hour (2016-11-06 01:00:00 to 02:00:00) before the DST ends, for example, 2016-11-06 01:30:00, the protection group will be executed after the DST ends for half an hour.
  • Protected groups must be executed in off-peak hours. Execution when I/O activities are busy may fail.
  • A protected group application is frozen when protected group is executed. Different applications in the protected groups are frozen in different ways, for example, Oracle database applications are frozen by entering the hot backup mode, and DB2 and Windows applications such as Exchange and SQL Server are frozen by I/O suspension. Cache data of the protected group is updated to storage space, and then service data replication and snapshot start. When protected group is executed, its applications are unfrozen, for example, Oracle applications exit the hot backup mode, and DB2 and Windows applications such as Exchange and SQL Server end the I/O suspension.
  • In case of continuous application frozen when a fault occurs during the execution of a protected group, the host agent automatically starts to time the frozen period of applications in the protected group. If the host agent does not receive an unfreezing command within set time, it automatically unfreeze the applications. If the host agent receives an unfreezing command after set time, it returns an error message indicating unfreezing failure.
    NOTE:

    If applications are automatically unfrozen, the consistency of replication data cannot be ensured, you need to execute the protected group to ensure data consistency.

  • Protected groups in the Executing, Disabled, Locked, or Invalid state cannot be executed.
  • If timetables are specified in the protection policies of a protected group, the protected group will be automatically executed based on the timetable. Perform the following steps to manually execute a protected group.
  • If the time policy of the protected group is set to Period-based scheduling, during the execution of the protected group, the timeout period of step Monitor data replication status is the same as the time period in the time policy. If the time policy of the protected group is set to On-demand scheduling, during the execution of the protected group, the default timeout period of step Monitor data replication status is two hours.

Procedure

  1. On the menu bar, choose Protection and select the protected group which you want to execute.
  2. Select the protected group for which you want to execute and click Execute on the Operation list.

    NOTE:
    If the protection policy of the VMware VMs protected group is HyperVault, click Execute, the Execute dialog is displayed. Select the backup type: Local Backup or Remote Backup and click OK.

  3. In the Question dialog box that is displayed, read the content of the dialog box carefully. Then click OK.

    The protection policies of the protected group are executed immediately. On the Execution Records tab page, you can view the execution result and details.

    NOTE:
    If the protected group is in the Executing state for a long period, click in the upper right corner to refresh information.

Result

After the protected group is executed, a historical record is generated on the Execution Records tab page. eReplication clears the execution records of each protected group at 00:00 every day. Only the latest 1000 records are retained. If the number of historical records exceeds 1000, the system deletes the earliest records.

Modifying Protection Policies

A protection policy defines the protection mode and scheduling policy that the DR management system uses to provide protection for protected objects. It is automatically generated when the protected group is created. Protection policies need to be modified based on the site requirements in the DR management process.

Context

protected groups in the Executing, Disabled, Locked, or Invalid state cannot be modified.

If you modify the number of snapshots in a protection policy (for example, the number is modified to 15), the policy of deleting snapshots is:
  • All snapshots are activated: OceanStor BCManager will keep snapshot activation time from the recent 15 snapshots.
  • Part snapshots are activated: delete the inactivated snapshots at first and then delete the activated snapshots that snapshot activation time from the recent until keep 15 snapshots, and deleting inactivated snapshot is not in order.

Procedure

  1. On the menu bar, select Protection.
  2. Select the type of the protected group whose protection policies are to be modified.
  3. Select the protected group whose protection policies are to be modified and click the Policy tab in the details area.
  4. Click Set, and modify the scheduling, replication, retention, or consistency policy of the protected group.

    A protection policy template defines the DR technology and protection mode for protected groups. When you modify protection policies, you can only modify the corresponding policies. For example, for the Oracle database's Array-Based Replication (Asynchronous):Active-Passive DR solution protection policy, you can only modify the scheduling, replication, and consistency policies. For details about parameters and modification suggestions of protection policies, see the section showing how to create a protected group of the related DR solution.

  5. Click OK.

Adding/Deleting a Protected Object

A protected object refers to an object (such as a database or LUN) for which eReplication provides disaster recovery (DR). eReplication allows you to add, delete, and modify authentication information about protected objects of a protected group.

Adding a Protected Object

This section describes how to add a protected object to a protected group.

Prerequisites

  • At least one protected group has been created.
  • The number of protected objects in the protected group has not reached the upper limit.
  • The template type of the protected object you want to add matches the existing type.
  • If the protected group have create a recovery plan, you can only add protected objects when recovery plan is in Ready, Clear completed, Rollback completed state or Reprotection completed.
  • A remote replication relationship must be set up between the storage LUNs where log files of each database instance reside or no remote replication relationship is set up.

Procedure

  1. On the menu bar, choose Protection and select the application type of the protected group to which you want to add a protected object.
  2. Select a protected group, and in the details area, click the Protected Object tab.
  3. Click Add.

    The Add Protected Object dialog box is displayed.

  4. Select one or more protected objects, and click OK.

    NOTE:
    • If protected objects are databases, you are required to enter the database user name and password for verification.
    • If protected objects are LUN, Local File System, Exchange Server, no verification is required.
    • When the asynchronous replication (NAS) DR technology is used, ensure that all the remote replication pairs are either not or in one remote replication vStore pair.

Deleting a Protected Object

If a protected object does not need to be protected, you can remove it from the protected group.

Prerequisites
  • At least one protected group has been created.
  • Multiple protected objects have been added to a protected group.
  • If the protected group have create a recovery plan, you can only delete protected objects when recovery plan is in Ready, Clear completed, Rollback completed state or Reprotection completed.
Context
  • This operation can be performed only when the protected group status is Normal.
  • When the protected group including database and NAS protected objects, all NAS protected objects can be removed, but you cannot remove the last database protected object in a protected group.
  • When the protected group status is Normal, you can add a removed protected object to this protected group again.

Procedure

  1. On the menu bar, choose Protection and select the application type of the protected object which you want to delete.
  2. Select a protected group, and in the details area, click the Protected Object tab.
  3. Select the protected object which you want to delete and click Delete in the operation area.
  4. 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.
  5. Click OK.

Refreshing Resource Information

If storage devices, hosts or VMs change, but the changes are not synchronized to eReplication in a timely manner, you need to refresh this changed resource information before executing DR recovery. The resource information can be refreshed in either way: periodical polling using eReplication or manual refreshing.

Context
  • Periodical polling using eReplication
    eReplication periodically refreshes resource information. Table 6-3 lists the update periods of various types of resources.
    Table 6-3  Refresh periods of various types of resources

    Resource Item

    Refresh Period (Minute)

    Remote site check

    3

    Remote management server

    30

    Storage device

    720

    Host

    720

    VRG

    5

    FusionManager

    30

    FusionCompute

    30

    OpenStack

    720

    vCenter server

    30

  • Manual refreshing
    Table 6-4 describes the changed list of the storage devices, hosts or VMs and the related operation.
    Table 6-4  changed list description

    Network Element

    Changed Item

    Storage device

    Host, host group, initiator, mapping view, file system, logical port, remote replication, consistency group in a remote replication, clone, HyperMetro, HyperVault or mirroring VIS change. For example, executing adding or deleting operation, the status changed.

    VM

    • Add or delete the VMs, or move the VMs to the other storage.
    • The LUNs used by datastore change.
    • The VMs change, for example, add or delete disks on the VMs, the network card change.
    NOTE:

    If the storage devices change, you need to refresh the storage devices.

    Host

    The initiator, application or storage information change.

Procedure
  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where the network elements (storage devices, hosts, or VMs) reside and click Refresh.

    In the upper right corner of the main page, click , in Background Task, you can view details about the refreshing.

    NOTE:

    In the cluster, if the host information has changed in the host group, you can refresh the host group to refresh all the hosts information. in the shortcut button area, select the host group reside and click Refresh in the operation area.

  3. On the menu bar, select Protection, and choose the protection objects type.
  4. Click the refreshed protected group, click Refresh on the Operation list to refresh information of the protected group.

    In the upper right corner of the main page, click , in Background Task, you can view details about the refreshing.

Protected Group Report Management

This section describes how to view a report of a protected group to know the succeed and failed times of the protected group.

Context

In Protected Group Report area, the system only displays protected groups created in the local site, does not display protected groups created and synchronized in the remote site.

NOTE:

The execution times of the protected group will be cleared after performing reprotection.

Procedure

  1. Perform either of the following operations to go to the Protected Group Report page.

    • On the menu bar, choose Monitor > Report > Protected Group Report.
    • On the home page, click More in the lower right corner of the Protected Groups' RPO Compliance area.

  2. Select the protected group whose details you want to view. Table 6-5 lists the report parameters.

    Table 6-5  Parameters of a protected group report

    Parameter

    Description

    Name

    Indicates the name of the protected group.

    Protection Policy

    Indicates the protection policy of the protected group.

    Production Site

    Indicates the site where the protected objects in the group reside (the protected site). Service systems of enterprises are running on the site.

    DR Site

    Indicates the site running the DR system. This site provides DR backup services for the protected objects. If a disaster occurs, it can be used to recover services.

    Protected Object Type

    Indicates the types of the protected objects. eReplication enables you to create protected groups based on the following applications:
    • Oracle
    • IBM DB2
    • Microsoft SQL Server
    • Microsoft Exchange Server
    • Local File system
    • NAS File System
    • VMware VM
    • LUN
    • FusionSphere VM
    • SAP HANA

    Configured RPO

    • If the protection policy type is synchronous replication (SAN), host-based replication, mirroring (VIS), active-active (VIS), or HyperMetro (SAN), the expected recovery point objective (RPO) is 0 by default.
    • If the policy template type of a protected group is asynchronous replication, the RPO of the protected group is configured as follows:
      • If the protection policy is Period-based scheduling, you can specify the expected RPO manually. If none is specified, the expected RPO is --.
      • If the protection policy is On-demand scheduling, the expected RPO is --.

    Actual RPO

    • When the replication devicea is online and the protected group is valid:
      • If the protection policy type of a protected group is synchronous replication (SAN), mirroring (VIS), active-active (VIS), or HyperMetro (SAN):
        • If synchronization status is normal, the actual RPO is 0.
        • If synchronization status is abnormal, the actual RPO is --.
        • If synchronization status is synchronizing and data is consistent, the actual RPO is 0.
      • If the protection policy type of a protected group is host-based replication:
        • If synchronization status is normal, the actual RPO is 0.
        • If synchronization status is abnormal, the actual RPO is --.
        • If synchronization status is synchronizing and data is consistent, the actual RPO is 0.
      • If the protection policy type of a protected group is asynchronous replication (SAN), snapshot (SAN), snapshot (VIS), snapshot (NAS), or clone (SAN):
        • If the protection policy is Period-based scheduling, a snapshot protected group has multiple copies. If all copies are inactivated or invalid, the actual RPO is --.
        • If the protection policy is Period-based scheduling, and the start time of the last copy activation can be obtained, the actual RPO is the time difference between the current system time and start time of the last copy activation.
        • If the protection policy is Period-based scheduling, and no protected group is executed successfully, the actual RPO is --.
        • If the protection policy is On-demand scheduling and RPO statistics is not supported, the actual RPO is --.
    • If the replication device is online but the protected group is invalid, RPO statistics is not supported and the actual RPO is --.
    • If the replication device is offline, the actual RPO is --.

    Estimated RTO

    When the replication device is online and the protected group is valid:
    • If the protection policy type of a protected group is asynchronous replication (SAN), mirroring (VIS), active-active (VIS), or HyperMetro (SAN), RTO statistics is not supported. Therefore, the estimated RTO is --, an invalid value.
    • If the protection policy type of a protected group is asynchronous replication (SAN), snapshot (SAN), snapshot (VIS), snapshot (NAS), asynchronous replication (VIS), or host-based replication, the RTO is supported only when recovery plans are created and tested. Calculate the average value based on a maximum of 50 successful test records. The calculated result is used as the estimated RTO. If reprotection is performed for recovery plans. Calculate the average value based on the latest 50 successful test records.

    Execution Result

    Indicates the execution result of the protected group.

    NOTE:

    For example, the shows in the Execution Result list, means succeed 108 times, and failed one time.

    a: Replication device indicates the storage device in array-based replication DR and the host in host-based replication DR.

  3. Optional: Click Export All to export the reports and save them to a local computer.

Modifying the Authentication Information

When the properties of a storage device are changed in the system, you must synchronize the changes to the eReplication to ensure that device properties in the DR management system are correct.

Modifying a Storage Device
  1. On the menu bar, select Resources.
  2. In the navigation tree, choose the site whose storage device you want to modify and click Storage.
  3. Select the storage device whose information you want to modify and click More > Modify on the Operation list.
  4. Change the name and authentication information about the storage device and click OK.

    Before you change the authentication information, enable Modify Authentication. Adding Storage Devices lists the parameters.

Modifying a Host
  1. On the menu bar, select Resources.
  2. In the navigation tree, choose the site whose host you want to modify and click Host.
  3. Select the host whose information you want to modify and click More > Modify on the Operation list.
  4. Change the name, authentication information, or alarm reporting parameters of the host and click OK.

    Adding Hosts lists the parameters.

    • Before you change the authentication information, enable Modify Authentication.
    • Before you change the alarm reporting parameters, enable Modify Alarm. The SNMP type and environment engine ID cannot be modified.

Modifying a VRG
  1. On the menu bar, select Resources.
  2. In the navigation tree, choose the site whose VRG you want to modify and click FusionSphere.
  3. Select the VRG that you want to modify and click More > Modify on the Operation list.
  4. Change the name, authentication information, or alarm reporting parameters of the host and click OK.

    Adding a VRG lists the parameters.

    • Before you change the authentication information, enable Modify Authentication.
    • Before you change the alarm reporting parameters, enable Modify Alarm. The SNMP type and environment engine ID cannot be modified.

Modifying a FusionManager or FusionCompute
  1. On the menu bar, select Resources.
  2. In the navigation tree, choose the site whose FusionManager or FusionCompute you want to modify and click FusionSphere.
  3. Select the FusionManager or FusionCompute that you want to modify and click More > Modify on the Operation list.
  4. Change the name and authentication information about the device and click OK.

    Adding FusionManager and Adding FusionCompute lists the parameters.

Modifying a vCenter Server
  1. On the menu bar, select Resources.
  2. In the navigation tree, choose the site whose vCenter server you want to modify and click vCenter Server.
  3. Select the vCenter server whose information you want to modify and click More > Modify on the Operation list.
  4. Change the name and authentication information about the device and click OK.

    Adding vCenter Servers lists the parameters.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 17391

Downloads: 76

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