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).
Creating a Protected Group

Creating a Protected Group

eReplication provides policy-based automatic protection for different protected objects. To implement policy-based automatic protection, you must create protected groups for the protected objects on eReplication. Once the protected groups are created, they will be automatically executed based on the preset policies.

Creating a Protected Group for Oracle Databases

This section describes how to create a protected group at the production site for Oracle databases that need DR protection. The system automatically identifies suitable protection policies for the protected group when creating the protected group.

Prerequisites

  • At least one production site has been created.
  • Hosts or host groups and storage devices for host applications have been added to the production site.

Context

In the HyperMetro (SAN) and asynchronous replication (SAN) or HyperMetro (SAN) and synchronous replication (SAN) scenario, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have this LUNs.

In the HyperMetro (SAN) and asynchronous or synchronous replication (SAN) scenario, all created asynchronous or synchronous remote replications and HyperMetro are configured in one replication consistency group.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Select the protected object.
    1. Set Production Site and Production Host(Group).
    2. In the Available Databases area, select a database to be protected.
    3. In the Verification dialog box that is displayed, enter necessary authentication information and click OK.

      Set Authentication Mode, which can be Database Authentication or OS Authentication.

      • Database Authentication: based on an Oracle database user name.

        Enter the sys user name and its password as the authentication information. If you use another user name for authentication, the database cannot be started when you recover or test it.

      • OS Authentication: based on an operating system user name.

        For a single-instance database or Oracle RAC cluster deployed on ASM disk groups, you need to enable OS Authentication for the DR database as required by Oracle officially. After data is recovered, select Database Authentication for security purposes.

    4. In the Archive Log Protection list of the Available Databases area, set whether to enable protection for archive logs.

      Archive logs record all operations on the databases. They are used to recover data of Oracle databases that are abnormally stopped, maximizing data security.

      When you enable the archive log mode but not enable Archive Log Protection for the production Oracle database, disable the archive log mode or configure an archive directory for the DR database. Otherwise, the DR database cannot be started when you perform DR operations.

  4. Click Next.
  5. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the active-active (VIS) and asynchronous replication (SAN) or HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      • If the HyperMetro (SAN) + asynchronous replication (SAN) DR technology is used in the DR Star network, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).
      • When the HyperMetro (SAN) and synchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      • For HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution protection policy, you need to set consistency policy and replication policy in synchronous end.
      NOTE:
      • When multiple protected groups with different time policies are configured, ensure that the time policies do not overlap each other. Otherwise, applications cannot be frozen or unfrozen when these time policies are executed.
      • Archive log space setting cannot work on raw devices; that is, space thresholds cannot be detected.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-103 lists related parameters.

        Table 5-103  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-104 lists related parameters.

        Table 5-104  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click the Consistency Policy tab, select Enable hot backup mode and Configure Min. Archive Space Threshold, and set the threshold.
        To enable the hot backup mode, the archive log mode must be enabled for the database. Otherwise, protected groups cannot be executed after the hot backup mode is enabled. If you do not select Enable hot backup mode, when protected groups are executed based on specified policies, the database remains online but the hot backup mode is not enabled. In this case, data consistency totally relies on storage devices' ability to ensure consistency.
        NOTE:
        If you select Enable hot backup mode, when protected groups are executed based on specified policies, the database remains online. Before storage array-based replication or taking snapshots, the system will set the database to the hot backup mode to ensure data consistency. After the hot backup mode is enabled, database services may stop because the archive log space is used up during DR execution. Therefore, you are advised to select Configure Min. Archive Space and configure it after enabling the hot backup mode. After the archive log space threshold is specified, DR execution will fail if the archive log space is lower than the specified threshold.
      5. Click OK.

  6. Click Next.
  7. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  8. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  9. Click Finish.
  10. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for IBM DB2 Databases

This section describes how to create a protected group at the production site for IBM DB2 databases that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • Hosts or host groups and storage devices for host applications have been added to the production site.

Context

In the HyperMetro (SAN) and asynchronous replication (SAN) or HyperMetro (SAN) and synchronous replication (SAN) scenario, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have this LUNs.

In the HyperMetro (SAN) and asynchronous or synchronous replication (SAN) scenario, all created asynchronous or synchronous remote replications and HyperMetro are configured in one replication consistency group.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

One protected group can only contain IBM DB2 databases that belong to the same instance.

The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select the protected object.
    1. Set Production Site and Production Host(Group).
    2. In the Available Databases area, select the databases that you want to protect.
    3. In the Verification dialog box that is displayed, enter necessary authentication information and click OK.
  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      • If the HyperMetro (SAN) + asynchronous replication (SAN) DR technology is used in the DR Star network, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).
      • When the HyperMetro (SAN) and synchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      • For HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution protection policy, you need to set consistency policy and replication policy in synchronous end.
      NOTE:
      When a protected object is added to multiple protected groups, ensure that the time policies do not overlap each other. Otherwise, applications cannot be frozen or unfrozen when these time policies are executed.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-105 lists related parameters.

        Table 5-105  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-106 lists related parameters.

        Table 5-106  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click the Consistency Policy tab and select Quiesce database.

        Consistency between databases is ensured by hanging write I/Os. After write I/Os are hung, the storage device starts replication or generates snapshots. Afterwards, the eReplication Agent renews write I/Os.

      5. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for Microsoft SQL Server Databases

This section describes how to create a protected group at the production site for Microsoft SQL Server databases that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • Hosts or host groups and storage devices for host applications have been added to the production site.

Context

In the HyperMetro (SAN) and asynchronous replication (SAN) or HyperMetro (SAN) and synchronous replication (SAN) scenario, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have this LUNs.

In the HyperMetro (SAN) and asynchronous or synchronous replication (SAN) scenario, all created asynchronous or synchronous remote replications and HyperMetro are configured in one replication consistency group.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select the protected object.
    1. Set Production Site and Production Host(Group).
    2. In the Available Databases area, select the databases that you want to protect.
    3. In the Verification dialog box that is displayed, enter necessary authentication information and click OK.
  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the active-active (VIS) and asynchronous replication (SAN) or HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      • If the HyperMetro (SAN) + asynchronous replication (SAN) DR technology is used in the DR Star network, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).
      • When the HyperMetro (SAN) and synchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      • For HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution protection policy, you need to set consistency policy and replication policy in synchronous end.
      NOTE:
      When a protected object is added to multiple protected groups, ensure that the time policies do not overlap each other. Otherwise, applications cannot be frozen or unfrozen when these time policies are executed.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-107 lists related parameters.

        Table 5-107  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-108 lists related parameters.

        Table 5-108  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click the Consistency Policy tab and select Quiesce database.

        VSS is a framework provided by Microsoft for backing up and recovering applications. For SQL Server, the OceanStor BCManager Agent uses VSS to freeze or unfreeze application I/Os. After I/Os are frozen, the storage device starts replication or generating snapshots. Afterwards, the OceanStor BCManager Agent unfreezes write I/Os.

      5. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for Microsoft Exchange Server Databases

This section describes how to create a protected group at the production site for Microsoft Exchange Server databases that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • Hosts or host groups and storage devices for host applications have been added to the production site.

Context

The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select the protected object.
    1. Set Production Site and Production Host(Group).
    2. Select the Exchange Server version and the protected object.

      • For Exchange 2007, select the storage group to which the database to be protected belongs.

        The system automatically protects all databases in that storage group.

      • For Exchange 2010 or later, directly select a database to be protected.

  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the active-active (VIS) and asynchronous replication (SAN) or HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      NOTE:
      When a protected object is added to multiple protected groups, ensure that the time policies do not overlap each other. Otherwise, applications cannot be frozen or unfrozen when these time policies are executed.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-109 lists related parameters.

        Table 5-109  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-110 lists related parameters.

        Table 5-110  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click the Consistency Policy tab and select Quiesce database.

        VSS is a framework provided by Microsoft for backing up and recovering applications. For SQL Server, the OceanStor BCManager Agent uses VSS to freeze or unfreeze application I/Os. After I/Os are frozen, the storage device starts replication or generating snapshots. Afterwards, the OceanStor BCManager Agent unfreezes write I/Os.

      5. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for VMware VMs

This section describes how to create a protected group at the production site for VMware VMs that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • A vCenter server and storage array have been added to the production site. A vCenter server and storage array have been added to the DR site.

Context

In the HyperMetro (SAN) and asynchronous replication (SAN) or HyperMetro (SAN) and synchronous replication (SAN) scenario, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have this LUNs.

In the HyperMetro (SAN) and asynchronous or synchronous replication (SAN) scenario, all created asynchronous or synchronous remote replications and HyperMetro are configured in one replication consistency group.

When the HyperMetro (NAS) and asynchronous replication (NAS) DR technologies are used, ensure that HyperMetro vStore pairs have been created at both HyperMetro ends and remote replication vStore pairs have been created at both replication ends. HyperMetro pairs and remote replication pairs must be in the same vStore pair. In addition, the status of HyperMetro pairs and remote replication pairs must be normal.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

The protected objects belonging to one protected group reside on the same storage device.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select the protected object.
    1. Select Production Site, vCenter, and Protection Type.

      Select Protection Type based on the used DR technologies.
      • When the datastores where the VMs managed by vCenter use the cascading replication (synchronous and asynchronous), parallel replication (synchronous and asynchronous), cascading replication (asynchronous and asynchronous), or parallel replication (asynchronous and asynchronous), set Array-Based Replication.

        The storage array provides the remote replication feature to implement protection.

      • When the datastores where the VMs managed by vCenter reside use the HyperMetro (SAN) and asynchronous replication (SAN) DR, set Array-Based Replication.

        The service data is written into the production center and same-city DR center in real time using the HyperMetro feature provided by the storage array.The production center and remote DR center are protected using the HyperReplication feature provided by the storage array.

      • When the datastores where the VMs managed by vCenter reside use the HyperMetro (NAS) and asynchronous replication (NAS) DR, set Array-Based Replication.

        The service data is protected using the HyperMetro and asynchronous replication features provided by the storage array and written into multiple data centers. In addition, the system periodically copies the data to the remote DR site based on the time policy, providing storage layer-based multi-point DR protection.

    2. Select the datastore group where the VMs to be protected reside.

      The system automatically protects all VMs in the selected datastore group.

      NOTE:

      A datastore group is a set of VMs on vCenter. After vCenter is added, the system will calculate the number of and group datastores on vCenter. VMs in independent remote replication pairs are in one datastore group and VMs in one consistency group are in one datastore group.

  6. Click Next.
  7. Configure a protection policy.
    1. On the Protection Policy page, the system automatically identifies suitable protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      • When the HyperMetro (SAN) and synchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution.
      • If the HyperMetro (SAN) + asynchronous replication (SAN) DR technology is used in the DR Star network, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).
      • When the HyperMetro (NAS) and asynchronous replication (NAS) DR technologie is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      • For HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution protection policy, you need to set consistency policy and replication policy in synchronous end.
      NOTE:
      For protection policy Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution or Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, it must cover local protection and remote protection.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-111 lists related parameters.

        Table 5-111  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click the Consistency Policy tab and select Generate quiesced snapshot.
        NOTE:
        • To generate a quiesced snapshot, you need to install VMware Tools or Open VM Tools on the VM.
        • When the Time Policy of a protection policy is set to Seconds, you cannot select Generate quiesced snapshot.

        vCenter is used to generate quiesced VM snapshots for VM consistency protection. After quiesced snapshots are generated, the system enables the client in the startup state to be in the quiesced state during DR protection, that is, the VM pauses temporarily and the data in the memory of the VM will be updated to a disk. After the replication starts, the vCenter Server is notified to delete these quiesced snapshots.

      4. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-112 lists related parameters.

        Table 5-112  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      5. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.
NOTE:

In the active-passive, geo-redundant, HyperMetro (using HyperMetro SAN or mixed HyperMetro SAN and snapshot SAN), and local protection DR scenarios, refresh operations on the storage device. On the menu bar, select Resources. Choose the site in the management server and in the site node, click vCenter Server. Click Refresh in the operation button area of the vCenter server to refresh information about the vCenter server. Then, the information about the protected group is automatically refreshed.

Creating a Protected Group for FusionSphere VMs

This section describes how to create a protected group at the production site for FusionSphere VMs that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • Resource mappings have been created.
  • The FusionSphere VM must be added to the production center, same-city DR center and remote DR center, and the replication is normal.

Context

In the HyperMetro (SAN) and asynchronous replication (SAN) or HyperMetro (SAN) and synchronous replication (SAN) scenario, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have this LUNs.

In the HyperMetro (SAN) and asynchronous or synchronous replication (SAN) scenario, all created asynchronous or synchronous remote replications and HyperMetro are configured in one replication consistency group.

If the HyperMetro (SAN) + asynchronous replication (SAN) DR technology is used in the DR Star network, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).

After a protected group is created, it may change due to increase or decrease of VMs or VM capacity. After the change, previous DR requirements cannot be met and adjustments must be made.

NOTE:
After adding or removing disks for a protected VM, refresh the information about the VM and manually enable DR for the protected group where the VM resides in time. For details, see Executing a Protected Group.
Table 5-113 describes the protection status of a VM after its protected group changes.
Table 5-113  Protection status description

DR Technology

Protection Status Description

Storage replication

Protected after the change

  • Capacity of VM disks increases or decreases.
  • Some disks are deleted from the VM.
  • New disks are mounted to the VM and reside in the current datastore group.
  • Disks mounted to the newly-created VM must reside in the current datastore group and in the same FusionCompute and FusionManager as the VM. When FusionCompute and FusionManager of the VM are refreshed, the VM is added to the protected group and protected automatically.

Unprotected after the change

  • New disks are mounted to the VM but do not reside in the current datastore group.

    If you want to protect the VM, migrate the newly-mounted disks to the datastore group to which the protected group belongs by referring to the Event Reference of the User Guide.

  • Not all disks mounted to a newly-created VM reside in the current datastore group. Therefore, the VM is not totally residing the current datastore group. The system reports an alarm.

    If you want to protect the VM, migrate the newly-mounted disks to the current datastore group by referring to the Event Reference of the User Guide. Alternatively, add LUNs of disks that are not residing in the current datastore group to the consistency group of remote replication.

  • A VM is deleted from the protected group or some or all disks of a VM are moved out of the current datastore group.
  • The remote replication pair or consistency group corresponding to the protected group is deleted or not active.
  • Configuration information about a protected VM changes. As a result, resource mappings no longer exist and the system reports an alarm.
  • If resource mappings configured for a newly-created VM do not exist, an alarm is reported.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Select a protected object.
    1. Select Production Site, FusionSphere Component and Protection Type.
    2. If Protection Type is set to Array-Based Replication, select the datastore group where the VMs to be protected reside.

      The system automatically protects all VMs in the selected datastore group.

      NOTE:

      A datastore group is the minimum independent unit for failure switchover or failure test. It corresponds to a remote replication pair or consistency group on the storage array. Every datastore in a datastore group must contain at least one VM.

  4. Click Next.
  5. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the active-active (VIS) and asynchronous replication (SAN) or HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      • If the datastore where VMs reside managed by FusionCompute or FusionManager uses the HyperMetro (SAN) + asynchronous replication (SAN) DR technology of DR Star, select HyperMetro and Array-Based Replication(DR Star): Disaster Recovery Data Center Solution (Geo-Redundant Mode).
      • When the HyperMetro (SAN) and synchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are matched protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there are no matched protection policies, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, click Resources, select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Refresh the FusionCompute or FusionManager information too and recreate a protected group.

    2. Click Set to set the protection policy for the protected group.

      • For the HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution protection policy:
        1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-114 lists related parameters.

          Table 5-114  Time policies

          Time Policy

          Description

          On-demand scheduling

          Manually starts protection tasks.

          Period-based scheduling

          Automatically starts protection tasks based on a period set by the system.
          NOTE:
          • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
          • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
          • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
          • 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.
        2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

          Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
          NOTE:

          If days and hours are not set, the Expected RPO is 15 minutes by default.

        3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-115 lists related parameters.

          Table 5-115  Replication policies

          Replication Policy

          Description

          Default configuration

          The remote replication rate is the default one set on the storage array.

          Manual configuration

          • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

          • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

        4. Click OK.
      • For the HyperMetro and Array-Based Replication (Synchronous):Geo-Redundant DR solution protection policy:
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-116 lists related parameters.

          Table 5-116  Replication policies

          Replication Policy

          Description

          Default configuration

          The remote replication rate is the default one set on the storage array.

          Manual configuration

          • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

          • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

        2. Click OK.

  6. Click Next.
  7. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  8. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  9. Click Finish.
  10. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for Local File Systems

This section describes how to create a protected group at the production site for NTFS local file systems that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • Hosts or host groups and storage devices for host applications have been added to the production site.

Context

If there are multiple NTFSs on one primary LUN of the remote replication pair or consistency group or DR Star, these NTFSs must be added to one protected group. (NTFSs must be created based on simple volumes.)

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Set a protection object.
    1. Set Production Site and Production Host(Group).
    2. Select the file systems that you want to protect.
  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the active-active (VIS) and asynchronous replication (SAN) or HyperMetro (SAN) and asynchronous replication (SAN) DR technology is used, select HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-117 lists related parameters.

        Table 5-117  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-118 lists related parameters.

        Table 5-118  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.

Creating a Protected Group for NAS File Systems

This section describes how to create a protected group at the production site for NAS File Systems that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • A production site and DR site have been created and added one another.
  • At least one storage device has been added.

Context

When the HyperMetro (NAS) and asynchronous replication (NAS) DR technologies are used, ensure that HyperMetro vStore pairs have been created at both HyperMetro ends and remote replication vStore pairs have been created at both replication ends. HyperMetro pairs and remote replication pairs must be in the same vStore pair and are in normal state.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select a protected object.
    1. Select Production Site and Disk Array.

      In HyperMetro (NAS) and asynchronous replication (NAS) scenarios, only OceanStor V3 series V300R006C10 and later versions can be used to create protected groups for NAS file systems.

    2. Select the file systems that you want to protect.

      When HyperMetro (NAS) DR is used, select vStore for Available File System.

  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      When the HyperMetro (NAS) and asynchronous replication (NAS) DR technologies are used, choose HyperMetro and Array-Based Replication (Asynchronous):Geo-Redundant DR solution from the protection policies matched by the system.

      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. When the HyperMetro (NAS) and asynchronous replication (NAS) DR technologies are used, click Set to set a protection policy for the protected group.

      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-119 lists related parameters.

        Table 5-119  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-120 lists related parameters.

        Table 5-120  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations

Creating a Protected Group for LUNs

This section describes how to create a protected group at the production site for LUNs that need DR protection. After the protected group is created, the system automatically matches suitable protection policies for the protected group.

Prerequisites

  • At least one production site has been created.
  • At least one storage device has been added.

Context

Protected objects in a protected group must reside on the same storage device.

When the network is DR Star, ensure that the LUNs used by protected objects in the protected group are in one DR Star, and only the LUNs used by protected objects exist in the DR Star.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  4. Click Next.
  5. Select a protected object.
    1. Select Production Site and Disk Array.
    2. In LUN and Consistency Groups, select the protect object.

      • LUN

        If you want to protect one LUN only or multiple LUNs that reside in different remote replication consistency groups, set the protected object type to LUN.

      • Remote replication consistency group

        If you want to protect all LUNs of one remote replication consistency group, set the protected object type to Remote replication consistency group.

  6. Click Next.
  7. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.

      • When the parallel replication (synchronous and asynchronous) or cascading replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (synchronous and asynchronous) or parallel replication in the DR Star network (synchronous + asynchronous) DR technology is used, select Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution.
      • When the cascading replication (asynchronous and asynchronous) DR technology is used, select Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      • When the parallel replication (asynchronous and asynchronous) DR technology is used, select Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution.
      NOTE:
      • If there are suitable protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
      • If there is no suitable protection policy, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, select Resources. Select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Then, recreate the protected group.

    2. Click Set to set the protection policy for the protected group.

      NOTE:
      • For Parallel Replication (Synchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Synchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy in synchronous end, set scheduling policy, consistency policy and replication policy in asynchronous end.
      • For Parallel Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution, Cascading Replication (Asynchronous and Asynchronous):Geo-Redundant DR solution protection policy, you need to set scheduling policy, consistency policy and replication policy in two asynchronous end.
      1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-121 lists related parameters.

        Table 5-121  Time policies

        Time Policy

        Description

        On-demand scheduling

        Manually starts protection tasks.

        Period-based scheduling

        Automatically starts protection tasks based on a period set by the system.
        NOTE:
        • To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours.
        • Tasks can be executed at multiple time points of a day, a week, or a month. Alternatively, at a specific time segment of a day, a week, or a month with a fixed frequency.
        • It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization.
        • 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.
      2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

        Expected RPO can be set to 0-31 days, 0-23 hours, and 15-59 minutes.
        NOTE:

        If days and hours are not set, the Expected RPO is 15 minutes by default.

      3. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-122 lists related parameters.

        Table 5-122  Replication policies

        Replication Policy

        Description

        Default configuration

        The remote replication rate is the default one set on the storage array.

        Manual configuration

        • Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period.

        • Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

      4. If Enable consistency protection is selected, the system runs the application freezing script on a specific host (or host group) to ensure replica data consistency when a protection task is being executed. After replicas are generated or applications are not unfrozen within the allowed freezing timeout duration, the system automatically runs the unfreezing script to ensure normal service operation.

        • If Enable consistency protection is selected, select Application Host (Group) of the executed script and fill in Freezing Script, Unfreezing Script, Freezing Status Query Script, and Freezing Timeout.

          The scripts are not delivered with the eReplication. The script provider needs to ensure the correctness of the script. Before configuring a script, check whether the script is verified by tests. For details, see Verifying the LUN Protected Group Consistency Script (Oracle).

          • Freezing Script: this script is used to unfreeze application I/Os.
          • Unfreezing Script: this script is used to check whether applications are frozen.
          • Freezing Status Query Script: this script is used to check whether applications are frozen.
          • Freezing Timeout indicates the maximum freezing duration supported by host services. The default value is 60 seconds.
        • Users can define scripts using the script template and save self-defined scripts to %OceanStor BCManager Agent install path%\bin\thirdparty\(on Windows) or /home/rdadmin/Agent/bin/thirdparty/(on No-Windows). Table 5-123 describes the script template.
          Table 5-123  Script Template Description

          Operating System

          Script

          Description

          Save Path

          Windows

          sample_freeze.bat

          Template of the freezing Oracle script

          %OceanStor BCManager Agent install path%\bin\thirdparty\

          sample_unfreeze.bat

          Template of the unfreezing Oracle script

          sample_queryfreezestate.bat

          Template of the Oracle script for querying the freezing status

          No-Windows

          sample_freeze.sh

          Template of the freezing Oracle script

          /home/rdadmin/Agent/bin/thirdparty/

          sample_unfreeze.sh

          Template of the unfreezing Oracle script

          sample_queryfreezestate.sh

          Template of the Oracle script for querying the freezing status

      5. Click OK.

  8. Click Next.
  9. Set Name and Description of the protected group.

    • Name: contains 4 to 32 characters, including letters, digits, underscores (_), and hyphens (-), but cannot start with a hyphen (-).
    • Description: contains 0 to 255 characters.

  10. Optional: If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
  11. Click Finish.
  12. Click OK.
Related Operations
  • If the protected objects of a protected group or their used storage devices change. On the menu bar, select Resources. And refresh resources or storage devices where the protected objects reside. Then go to the protected group page and refresh protected objects of the protected group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
    NOTE:

    If a recovery plan has been created for a protected group, you can refresh protected objects only when the recovery plan status is Ready, Clear completed, Rollback completed, or Reprotection completed.

  • To ensure that information about protected groups is refreshed successfully, you must refresh information about storage devices and hosts at both the production site and DR site.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 12219

Downloads: 64

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