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

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

  • If multiple applications are deployed on the primary LUN of the same remote replication pair or consistency group, ensure that all the applications belong to the same protected group. If they belong to different protected groups, some applications may become unavailable during data synchronization, planned migration, or fault recovery of the protected groups.
  • When I/O loads of applications are heavy, consistency protection with quiesced databases enabled may fail. Therefore, implement consistency protection for applications during off-peak hours or disable consistency protection.
  • After the eReplication Agent is re-installed on the host after being uninstalled, you need to recreate protected groups on the host.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Select a 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.

    5. Optional: If service data is stored in both databases and NAS file systems, click Add NAS File System to add the NAS file systems.
  4. Click Next.
  5. Set 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 synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When the asynchronous replication (SAN), asynchronous replication (VIS), or asynchronous replication (SAN&NAS All-In-One) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive DR solution.
      • When the mirroring (VIS) and asynchronous replication (SAN) DR technology is used, select Mirror and Array-Based Replication (Asynchronous):Active-Passive 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:
      • 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.
      • For the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy:
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-37 lists related parameters.

          Table 5-37  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive DR solution or Mirror and Array-Based Replication (Asynchronous):Active-Passive 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-38 lists related parameters.

        Table 5-38  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-39 lists related parameters.

        Table 5-39  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

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

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. Select a 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.
    4. Optional: If service data is stored in both databases and NAS file systems, click Add NAS File System to add the NAS file systems.
  4. Click Next.
  5. Set a protection policy.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a protection policy based on your data protection solution.

      • When using the synchronous replication (SAN) DR technology, select Array-Based Replication (Synchronous):Active-Passive DR solution as the protection policy.
      • When using the asynchronous replication (SAN) or SAN&NAS All-In-One asynchronous replication DR technology, select Array-Based Replication (Asynchronous):Active-Passive DR solution as the protection policy.
      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:
      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.
      • For the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-40 lists related parameters.

          Table 5-40  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive 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-41 lists related parameters.

          Table 5-41  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-42 lists related parameters.

          Table 5-42  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.

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

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 a 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.
    4. Optional: If service data is stored in both databases and NAS file systems, click Add NAS File System to add the NAS file systems.
  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 synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When using the asynchronous replication (SAN) or SAN&NAS All-In-One asynchronous replication DR technology, select Array-Based Replication (Asynchronous):Active-Passive DR solution as the protection policy.
      • When the mirroring (VIS) and asynchronous replication (SAN) DR technology is used, select Mirror and Array-Based Replication (Asynchronous):Active-Passive 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:
      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.
      • For the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-43 lists related parameters.

          Table 5-43  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive DR solution or Mirror and Array-Based Replication (Asynchronous):Active-Passive 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-44 lists related parameters.

          Table 5-44  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. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-45 lists related parameters.

          Table 5-45  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.

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

        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.

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. 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 protection policies.
    1. On the Protection Policy page, the system automatically matches supported protection policies. Select a protection policy based on your data protection solution.

      • When using the synchronous replication (SAN) DR technology, select Array-Based Replication (Synchronous):Active-Passive DR solution as the protection policy.
      • When using the asynchronous replication (SAN) DR technology, select Array-Based Replication (Asynchronous):Active-Passive DR solution as the protection policy.
      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:
      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.
      • For the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-46 lists related parameters.

          Table 5-46  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive 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-47 lists related parameters.

          Table 5-47  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-48 lists related parameters.

          Table 5-48  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

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

When the asynchronous replication (NAS) DR technology is used, ensure that all the remote replication pairs are either not or in one remote replication vStore pair.

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, vCenter, and Protection Type.

      Select a Protection Type based on the used DR technologies.
      • When the datastores where the VMs managed by vCenter reside uses the synchronous replication (SAN), asynchronous replication (SAN), or asynchronous replication (NAS) DR technology, select Array-Based Replication.

        Employ remote replication of storage devices to implement protection.

      • When the datastores where the VMs managed by vCenter reside uses the HyperVault DR technology, select HyperVault.

        HyperVault retains multiple snapshot copies of service data within a storage system or on different storage systems, enabling DR protection at the storage layer.

    2. If Protection Type is set to Array-Based Replication or HyperVault, 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 the vCenter. After a vCenter server is added, the system will calculate the number of datastores on the vCenter, the VMs on a remote replication pair or consistency group will be allocated to a datastore 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 synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When the asynchronous replication (SAN) or asynchronous replication (NAS) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive DR solution.
      • When the HyperVault DR technology is used, select HyperVault:Active-Passive 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 the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-49 lists related parameters.

          Table 5-49  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.
      • For the Array-Based Replication (Synchronous):Active-Passive 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-50 lists related parameters.

          Table 5-50  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-51 lists related parameters.

          Table 5-51  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 storages 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.
      • For the HyperVault:Active-Passive DR solution protection policy,
        NOTE:
        Set both the local backup protection policy and the remote backup protection policy.
        1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-52 lists related parameters.

          Table 5-52  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 the Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-53 describes related parameters.

          Table 5-53  Retention policies

          Retention Policy

          Description

          Latest duplicate

          The number of duplicates cannot exceed the maximum number of snapshots that can be taken for a storage resource such as a LUN or file system.

          Duplicate retention

          The duplicate retention policy defines the retention policy of duplicates generated during the protected group protection. When the system starts duplicate maintenance, expired and invalid duplicates will be deleted based on the duplicate retention policy. By default, the time to maintain duplicates is the 39th minute of every hour.
          NOTE:

          After a user resets Latest duplicate, the duplicate maintenance will be triggered immediately.

          You can set the minimum number of duplicates to be retained. The system will not delete valid duplicates until the number of invalid duplicates exceeds the minimum number of duplicates you set.
          • The value range for a daily policy is 0–31. The default value is 0, meaning to retain no duplicates.
          • The value range for a weekly policy is 0–6. The default value is 0, meaning to retain no duplicates.
          • The value range for a monthly policy is 0–12. The default value is 0, meaning to retain no duplicates.
          When determining the number of retained duplicates, consider the following:
          • Data importance and DR requirements. If data of the latest five months must be retained, you are advised to set the retention period by month.
          • Available storage space of a storage device. If the available space of a storage device is sufficient, you are advised to retain more duplicates that are more important.
          NOTE:
          For example, if the current time is 2017/4/11 08:40:00, configure the protected group as following:
          • Set the execution policy to be performed at every hour exactly.
          • Set the retention policy to keep five latest duplicates, three daily duplicates, two weekly duplicates, and one monthly duplicate.
          If the protected group is under the automatically scheduled protection for a long time, the duplicates retained are as follows after the duplicate maintenance is complete at the current time:
          • Latest duplicates were generated at: 2017-04-11 08:00, 2017-04-11 07:00, 2017-04-11 06:00, 2017-04-11 05:00, and 2017-04-11 04:00.
          • Daily duplicates are generated at: 2017-04-10 23:00, 2017-04-09 23:00, and 2017-04-08 23:00.
          • Weekly duplicates were generated at: 2017-04-09 23:00 and 2017-04-02 23:00.
          • The monthly duplicate was generated at: 2017-03-31 23:00.
          NOTICE:
          If the duplicate maintenance is not triggered, or daily, weekly, or monthly duplicate retention is configured, the number of retained duplicates may exceed the number of latest duplicates being retained.
        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 (Non- OpenStack Architecture)

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.
  • In host-based replication DR scenarios, FusionSphere components and virtual replication gateways (VRGs) have been added to eReplication of both the production center and DR center.
  • In storage array-based replication DR scenarios, FusionSphere components and storage devices have been added to eReplication of both the production center and DR center. Besides, the status of replication between storage devices is normal.
NOTE:

You are advised to disable power-off notification in Windows running on the production end. For details, see Disabling Power-Off Notification.

Context

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-54 describes the protection status of a VM after its protected group changes.
Table 5-54  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.

Host-based replication

  • When disks are being deleted from or added to a VM, disks on the placeholder VM at the DR site are updated simultaneously.
  • If resource mappings are not established between datastores where newly-added disks reside and the DR site, protected objects cannot be protected and an alarm is reported.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Select a protected object.
    1. Select Production Site.
    2. Select FusionSphere Component.
    3. Select Protection Type.

      Select a Protection Type based on the used DR technologies.
      • When datastores where the VMs managed by FusionCompute or FusionManager reside use the synchronous replication (SAN), asynchronous replication (SAN), or mirroring (VIS) and asynchronous replication (SAN) DR technology, select Array-Based Replication.

        Employ remote replication of storage devices to implement protection.

      • When datastores where the VMs managed by FusionCompute or FusionManager reside use the host-based replication (SAN) DR technology, select Host-Based Replication.

        Employ the host-based I/O replication function to replicate VM data from the production center to the DR center.

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

    5. If Protection Type is set to Host-Based Replication, move VM to be protected from the Available VMs to the Selected VMs list.
  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 synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When the asynchronous replication (SAN) or mirroring (VIS) and asynchronous replication (SAN) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive DR solution.
      • When the host-based replication DR technology is used, select Host-Based Replication:Active-Passive 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 Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-55 lists related parameters.

          Table 5-55  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive 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-56 lists related parameters.

          Table 5-56  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-57 lists related parameters.

          Table 5-57  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 Host-Based Replication:Active-Passive 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-58 describes related parameters.
          Table 5-58  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.
          • When executing the protection policy for a protected group, consistency snapshots must be taken for the DR VM, which affects the VM performance. Therefore, you are advised to set the execution time to a time when the VM is idle or to increase the RPO to reduce the impact of snapshots on VM performance.

          Compress Setting

          Specifies whether to compress data transferred between VRGs.

          Encryption Setting

          Specifies whether to encrypt data transferred between VRGs.

          Replication Rate

          Specifies the rate at which the host transfers data to VRGs.

          NOTE:
          For FusionCompute V100R005C10, you can also set the number of recovery points.
        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. 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 at the lower left corner.

    For the Host-Based Replication:Active-Passive DR solution protection policy, if you select Start baseline synchronization immediately, the protected group starts data synchronization instantly. If you do not select Start baseline synchronization immediately, you need to manually start data synchronization for protected objects and select baseline synchronization.

  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.

Follow-up Procedure

When the host-based replication DR is used, after creating a protected group, in the details area, click the Protected Object tab and start the selected VMs. The three methods to start VMs are as follows:

  • Baseline synchronization: VMs are specified as DR VMs. Select this operation when data is not fully synchronized between the DR site and production site. Execute baseline synchronization to copy all data from the disks in the production site to those in the DR site.
  • Consistency verification: If an unexpected power failure or process interruption occurs during the data synchronization process, the data records that are to be sent in the production site will be lost. Data will be inconsistent after data is synchronized between the production site and DR site again. After the exception is resolved, select this operation to verify data consistency between the production site and DR site and synchronize the differential data to the DR site.
  • Incremental replication: The data volume is large upon initial synchronization of VMs. However, the available bandwidth cannot meet data transfer requirements. The incremental data replication solution is provided to resolve the problem. After exporting a template from the production site, import the template to VMs in the DR site. Then start incremental replication. Only the incremental data is replicated.

Creating a Protected Group for FusionSphere VMs (OpenStack Architecture)

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

  • One site has been created.
  • Correct resource pools and volume types have been configured on OpenStack at both the production site and DR site.
  • When a shared volume is used by a protected object, all VMs on that shared volume must reside in the same protected group.
  • The tenant has applied for CSDR.

Context

  • If multiple VMs share one volume, add these VMs to the same protected group. Otherwise, VMs outside the protected group cannot access the shared volume.
  • If multiple VMs share one volume, remove these VMs from the protected group if you are to delete the protected objects. Otherwise, VMs sharing the volumes cannot be recovered during the DR recovery.
  • Add all VMs in a FusionSphere OpenStack vApp to one protected group for protection.

Procedure

  1. Log in to eReplication. For details, see Log In To eReplication.
  2. In the menu bar, Choose Protection.
  3. Click Create.
  4. Select a protected object.
    1. Select Production Site.
    2. In FusionSphere Component, select FusionSphere OpenStack.
    3. Select Production Region.

      A region refers to a physical region. In this region, one or multiple data centers may exist.

    4. Select Production Project.

      Project is also called tenant, which is the scope of resource services that provide Infrastructure as a Service (IaaS) resources for one or multiple applications. IaaS resources can contain resources of availability zones in multiple regions.

    5. Select Production Availability Zone.

      Availability zone is the scope of IaaS resources. Computing resources in one availability zone share storage devices and networks. Resources of one availability zone can be used by multiple projects.

    6. In the Available VMs area, select a VM. Click to add the selected VM to the Selected VMs area.
  5. Click Next.
  6. 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.

      Based on your DR requirements, select Array-Based Replication (Synchronous):Active-Passive DR solution or Array-Based Replication (Asynchronous):Active-Passive DR solution as the protection policy.

      • Array-Based Replication (Synchronous):Active-Passive DR solution: Based on the synchronous remote replication technology provided by storage devices, replicates data from the production site to the DR site in real time, providing DR with a zero RPO based on the storage layer.
      • Array-Based Replication (Synchronous):Active-Passive DR solution: Based on the asynchronous remote replication technology provided by storage devices, replicates data from the production site to the DR site periodically, providing DR based on the storage layer.

    2. Set the protection policy for the protected group.

      • For the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. In the Volume area, click Set.

        2. Select DR Region, DR Project, and DR Availability Zone.
        3. In DR Volume Type, select the DR volume type automatically matched by the system.

          Ensure that the replication links between the storage devices and DR devices corresponding to the DR volume type meet bandwidth requirements. Otherwise, I/O performance of production VMs reduces.

          NOTE:

          Click Batch configure DR volume types of VMs. In the Batch Configure DR Volume dialog box that is displayed, batch configure DR volume types.

        4. Click OK.
        5. In the Protection Policy area, click Set.
        6. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-59 lists related parameters.

          Table 5-59  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.

        7. Click OK.
      • For the Array-Based Replication (Asynchronous):Active-Passive DR solution protection policy,
        1. In the Volume area, click Set.

        2. Select DR Region, DR Project, and DR Availability Zone.
        3. In DR Volume Type, select the DR volume type automatically matched by the system.

          Ensure that the replication links between the storage devices and DR devices corresponding to the DR volume type meet bandwidth requirements. Otherwise, I/O performance of production VMs reduces.

          NOTE:

          Click Batch configure DR volume types of VMs. In the Batch Configure DR Volume dialog box that is displayed, batch configure DR volume types.

        4. Click OK.
        5. In the Protection Policy area, click Set.
        6. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-60 lists related parameters.

          Table 5-60  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.
        7. 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.

        8. Click OK.
        9. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-61 lists related parameters.

          Table 5-61  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.

        10. Click OK.

  7. Click Next.
  8. 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.

  9. 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.
  10. Click Finish.
  11. 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.
If a volume type to be configured does not exist in the automatically-matched DR volume types, confirm that the following configurations have been made on OpenStack:
  1. The DR volume type has been created.
  2. The SN of the local device for the DR volume type has been set correctly.
  3. The storage resource pool corresponding to the DR storage device has been configured correctly.
  4. Replication links have been created between the production storage and the DR storage and the link status is normal.

Follow-up Procedure

When creating a protected group, on OpenStack at the DR site, create DR volumes and the remote replication relationship between production volumes and the DR volumes. The number of DR volumes may vary with the number of VM volumes to be protected.

After the protected group is created, in the details area, choose Protection Object > Volume Management to view the information about Protected Volume, Addible Volume, and Releasable Volume.

After a protected group is created, it may change due to increase or decrease of FusionSphere OpenStack volumes. After the change, previous DR requirements cannot be met and volume management operations must be performed. Perform the following steps:
  1. In the details area, click the Protection Object tab.
  2. Click Volume Management.
  3. In the drop-down list, click Protected Volume, Addible Volume, or Releasable Volume to view volume information.

    Descriptions of volume management configurations are as follows:

    • Protected Volume: indicates a volume used by production VMs. Its protection relationship with a DR volume has been established. The volume is a protected object and being protected.
    • Addible Volume: indicates a volume used by production VMs but has no protection relationship with DR volumes. If a volume is added to the protected objects of FusionSphere OpenStack, you can refresh the protected group to view information about the unprotected volume. Then, you need to specify the DR volume type and establish the protection relationship between a DR volume and the unprotected volume. After the protection relationship is established, the newly added volume becomes a protected object and is protected. You can set DR Volume Type to establish its protection relationship with a DR volume.
    • Releasable Volume: indicates a volume whose mapping relationship with production VMs is removed but its protection relationship with the DR volume is not. If a volume is removed from the protected objects of FusionSphere OpenStack, you can refresh the protected group to view information about the unused volume. Then, you need to remove the protection relationship between the unused volume and a DR volume. After this, DR resources of the volume are released and deleted from the configuration information about protected objects. You can manually remove its protection relationship with a DR volume.
  4. Click OK.
NOTE:
  • If the protected group fails to be created, check whether a Failed to Clear the DR Configuration of a VM alarm is displayed. If yes, automatically or manually clean created DR resources according to the alarm handling suggestion.
  • After creating the protected group, if there is no other operation is required, manually refresh OpenStack to add created DR resources to eReplication.

Creating a Protected Group for Local File Systems

This section describes how to create a protected group at the production site for NTFS, EXT3, EXT4, or XFS 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 NTFS/EXT3/EXT4/XFS local file systems on one primary LUN of the remote replication pair or consistency group, these NTFS/EXT3/EXT4/XFS local file systems must be added to one protected group. (NTFS/EXT3/EXT4/XFS local file systems must be created based on simple volumes.)

Procedure

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

      • When the synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When the asynchronous replication (SAN) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive 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 the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy,
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-62 lists related parameters.

          Table 5-62  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.
      • For the Array-Based Replication (Asynchronous):Active-Passive 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-63 lists related parameters.

        Table 5-63  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-64 lists related parameters.

        Table 5-64  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

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

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

When the asynchronous replication (NAS) DR technology is used, ensure that all the remote replication pairs are either not or in one remote replication vStore pair.

Procedure



  1.  
  2. In the menu bar, Choose Protection.
  3. Click Create.
  4. Select a protected object.
    1. Select Production Site and Disk Array.

      Only disk array V300R002C10 of the OceanStor V3 series can be used to create protected groups for NAS file systems.

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

      Set Available File System to vStore or File system.

  5. Click Next.
  6. 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 asynchronous replication (NAS) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive 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.

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

        Table 5-65  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-66 lists related parameters.

        Table 5-66  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.

  7. Click Next.
  8. 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.

  9. 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.
  10. Click Finish.
  11. 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 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.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. 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.

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

      • When the synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous):Active-Passive DR solution.
      • When the asynchronous replication (SAN) DR technology is used, select Array-Based Replication (Asynchronous):Active-Passive 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 the Array-Based Replication (Synchronous):Active-Passive DR solution protection policy, perform the following:
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-67 lists related parameters.

          Table 5-67  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. 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-68 describes the script template.
            Table 5-68  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

        3. Click OK.
      • For the Array-Based Replication (Asynchronous):Active-Passive 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-69 lists related parameters.

        Table 5-69  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-70 lists related parameters.

        Table 5-70  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-71 describes the script template.
          Table 5-71  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.

  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 SAP HANA Databases

This section describes how to create a protected group at the production site for SAP HANA 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

  • The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.
    • When I/O loads of applications are heavy, consistency protection with quiesced databases enabled may fail. Therefore, implement consistency protection for applications during off-peak hours or disable consistency protection.
    • After the eReplication Agent is re-installed on the host after being uninstalled, you need to recreate protected groups on the host.
  • In the asynchronous replication scenario, you can determine whether to create a remote replication relationship for the storage LUNs where log files reside.

Procedure

  1. In the menu bar, Choose Protection.
  2. Click Create.
  3. Select a protected object.
    1. Set Production Site and Production Host(Group).
    2. Under Available Databases, select the database that needs to be protected.

      After the selection, the Verification dialog box is displayed. Enter the user name and password of the corresponding database instance and click OK.

      NOTE:

      After the user name and password of the database instance are entered, the system will verify the user name and password immediately. If Verification Result indicates that the user failed in the verification, verify the user name and password and select the instance again.

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

      • When the synchronous replication (SAN) DR technology is used, select Array-Based Replication (Synchronous): Disaster Recovery Data Center Solution (Active-Passive Mode).
      • When the asynchronous replication (SAN) DR technology is used, select Array-Based Replication (Asynchronous): Disaster Recovery Data Center Solution (Active-Passive Mode).
      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 and set a protection policy in the Set Execution Policy dialog box.

      • For Array-Based Replication (Synchronous): Disaster Recovery Data Center Solution (Active-Passive Mode):
        1. Click Replication Policy tab to set the remote replicate rate between storage arrays. Table 5-72 lists related parameters.

          Table 5-72  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.

      • For Array-Based Replication (Asynchronous): Disaster Recovery Data Center Solution (Active-Passive Mode):
        1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-73 lists related parameters.

          Table 5-73  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-74 lists related parameters.

          Table 5-74  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.

          During the protection, the quiesce database is used to ensure data consistency.

          NOTE:

          In the asynchronous replication scenario, when the user does not set up a remote replication relationship between the storage LUNs where log files reside, the system will forcibly select Quiesce database.

  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
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10624

Downloads: 55

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