No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

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

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Creating a Protected Group

Creating a Protected Group

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

Creating a Protected Group for Oracle Databases

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

Prerequisites

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

Context

In HyperMetro (SAN) and snapshot (SAN) scenarios, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have these LUNs.

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

Procedure

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

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

  4. Click Next.
  5. Select the protected object.
    1. Set Production Site and Production Host(Group).
    2. In the Available Databases area, select 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.

  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 active-active (VIS) or HyperMetro (SAN) DR technology is used, select HyperMetro:HyperMetro data center solution.
      • When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, select HyperMetro and Snapshot:HyperMetro data center 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. When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
      1. Select a snapshot type.
        • Snapshot: The read and write permissions of the generated snapshot are readable and writable.
        • HyperCDP: The read and write permissions of the generated snapshot are readable.
        NOTE:
        • If you have purchased the HyperCDP license, HyperCDP is recommended. HyperCDP provides high-density protection, ultra-large specifications, and lossless performance.
        • Create a second-level protected group. BCManager creates a scheduled plan on the storage array. The scheduled plan can be managed only by BCManager. You cannot delete the scheduled plan from the storage array.
      2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-173 lists related parameters.

        Table 5-173  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 second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, a day, a week, or a month with a fixed frequency.
          • When Snapshot Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing protected groups is 30 seconds.
          • When Snapshot Type is set to HyperCDP and Time Period is set to Second, the minimum interval for executing protected groups is 10 seconds.
        • 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.
      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 Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-174 describes related parameters.

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

        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.
        • If the scheduling time period is second, the copy retention policy is automatically executed by the storage device.
      5. 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.
      6. 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. When the HyperMetro (SAN) ,HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
  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:

If a protected group uses HyperMetro (SAN) and snapshot (SAN), a snapshot copy being used by a recovery plan cannot be deleted. To delete such a snapshot copy, wait until the recovery plan finishes clearing.

Creating a Protected Group for IBM DB2 Databases

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

Prerequisites

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

Context

In HyperMetro (SAN) and snapshot (SAN) scenarios, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have these LUNs.

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

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

Procedure

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

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

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

      • When the active-active (VIS) or HyperMetro (SAN) DR technology is used, select HyperMetro:HyperMetro data center solution.
      • When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, select HyperMetro and Snapshot:HyperMetro data center 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. When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
      1. Select a snapshot type.
        • Snapshot: The read and write permissions of the generated snapshot are readable and writable.
        • HyperCDP: The read and write permissions of the generated snapshot are readable.
        NOTE:
        • If you have purchased the HyperCDP license, HyperCDP is recommended. HyperCDP provides high-density protection, ultra-large specifications, and lossless performance.
        • Create a second-level protected group. BCManager creates a scheduled plan on the storage array. The scheduled plan can be managed only by BCManager. You cannot delete the scheduled plan from the storage array.
      2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-175 lists related parameters.

        Table 5-175  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 second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, a day, a week, or a month with a fixed frequency.
          • When Snapshot Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing protected groups is 30 seconds.
          • When Snapshot Type is set to HyperCDP and Time Period is set to Second, the minimum interval for executing protected groups is 10 seconds.
        • 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.
      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 Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-176 describes related parameters.

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

        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.
        • If the scheduling time period is second, the copy retention policy is automatically executed by the storage device.
      5. 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.

      6. 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. When the HyperMetro (SAN), HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
  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:

If a protected group uses HyperMetro (SAN) and snapshot (SAN), a snapshot copy being used by a recovery plan cannot be deleted. To delete such a snapshot copy, wait until the recovery plan finishes clearing.

Creating a Protected Group for Microsoft SQL Server Databases

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

Prerequisites

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

Context

In HyperMetro (SAN) and snapshot (SAN) scenarios, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have these LUNs.

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

Procedure

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

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

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

      • When the active-active (VIS) or HyperMetro (SAN) DR technology is used, select HyperMetro:HyperMetro data center solution.
      • When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, select HyperMetro and Snapshot:HyperMetro data center 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. When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
      1. Select a snapshot type.
        • Snapshot: The read and write permissions of the generated snapshot are readable and writable.
        • HyperCDP: The read and write permissions of the generated snapshot are readable.
        NOTE:
        • If you have purchased the HyperCDP license, HyperCDP is recommended. HyperCDP provides high-density protection, ultra-large specifications, and lossless performance.
        • Create a second-level protected group. BCManager creates a scheduled plan on the storage array. The scheduled plan can be managed only by BCManager. You cannot delete the scheduled plan from the storage array.
      2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-177 lists related parameters.

        Table 5-177  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 second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, a day, a week, or a month with a fixed frequency.
          • When Snapshot Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing protected groups is 30 seconds.
          • When Snapshot Type is set to HyperCDP and Time Period is set to Second, the minimum interval for executing protected groups is 10 seconds.
        • 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.
      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 Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-178 describes related parameters.

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

        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.
        • If the scheduling time period is second, the copy retention policy is automatically executed by the storage device.
      5. 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.

      6. 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. When the HyperMetro (SAN), HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
  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:

If a protected group uses HyperMetro (SAN) and snapshot (SAN), a snapshot copy being used by a recovery plan cannot be deleted. To delete such a snapshot copy, wait until the recovery plan finishes clearing.

Creating a Protected Group for VMware VMs

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

Prerequisites

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

Context

  • In HyperMetro (SAN) and snapshot (SAN) scenarios, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have these LUNs.

  • When HyperMetro (NAS) or HyperMetro (NAS) and HyperVault DR is used, ensure that the local vStore and remote vStore are in a HyperMetro vStore pair, and their file system are also paired. In addition, ensure that the HyperMetro vStore pair and the HyperMetro pairs of file systems are all working properly.

  • When HyperMetro (NAS) and HyperVault DR is used, ensure that remote integrated backups are created on all the file systems in the active-active local vStore and active-active remote vStore and are stored on the same storage device.

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

After HyperMetro (NAS) and HyperVault DR is used to create a protection group, the policy of performing integrated backup automatically on the storage array will be disabled.

Procedure

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

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

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

      Select Protection Type based on the networking mode and DR technologies.
      • When the datastore group where the VMs to be protected reside using the active-active (VIS) DR technology, select HyperMetro.

        The VIS device active-active technologies are used for protection. You need to select VMs that you want to protect one by one.

      • When the datastore group where the VMs to be protected reside using the HyperMetro (SAN) DR technology, select HyperMetro.

        The HyperMetro technology enables service data to be written into two data centers in real time. If you select a datastore group, all VMs in this group are protected.

      • When the datastore group where the VMs to be protected reside using the HyperMetro (SAN) and Snapshot (SAN) DR technologies, select HyperMetro.

        The snapshot technology is used to protect data. Virtual snapshots are periodically created for service data within a storage system. If you select a datastore group, all VMs in this group are protected.

      • When the datastore group where the VMs to be protected reside using the HyperMetro (NAS) DR technology, select HyperMetro.

        The HyperMetro technology enables service data to be written into two data centers in real time. If you select a datastore group, all VMs in this group are protected.

      • When the datastore group where the VMs to be protected reside using the HyperMetro (NAS) and HyperVault DR technology, select HyperMetro.

        HyperMetro enables service data to be written to two data centers in real time and the system to periodically generate virtual copies of the service data in the storage device of the remote DR data center based on the time policy.

      NOTE:

      If partial VMs under the management of vCenter use active-active VIS and the rest use HyperMetro, Protection Type is VIS Active-Active and SAN HyperMetro. Check the device before selecting the protection type.

    2. Select the protected object.

      • When the datastore group where the VMs to be protected reside using active-active (VIS) DR technology, after selecting HyperMetro, select VMs that you want to protect from Available VMs and move them to Selected VMs.
      • When the datastore group where the VMs to be protected reside using HyperMetro (SAN) or HyperMetro (SAN) and Snapshot (SAN) or HyperMetro (NAS) or HyperMetro (NAS) and HyperVault DR technology, after selecting HyperMetro. After you select the datastore group that you want to protect, the system automatically protects all VMs in the selected datastore group.
      • When the datastore group where the VMs to be protected reside using active-active (VIS) and HyperMetro (SAN):
        • If the datastore group are supplied by VIS, When the after selecting VIS Active-Active. Select VMs that you want to protect from Available VMs and move them to Selected VMs.
        • If the datastore group are supplied by storage, after selecting SAN HyperMetro. After you select the datastore group that you want to protect, the system automatically protects all VMs in the selected 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 active-active (VIS) or HyperMetro (SAN) or HyperMetro (NAS) DR technology is used, select HyperMetro:HyperMetro data center solution.
      • When the HyperMetro (NAS) and HyperVault DR technology is used, select HyperMetro and HyperVault: Disaster Recovery Data Center Solution (HyperMetro Mode).
      • When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, select HyperMetro and Snapshot:HyperMetro data center 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. When the HyperMetro (SAN) and Snapshot (SAN) or HyperMetro (NAS) and HyperVault DR technology is used, click Set to set the protection policy for the protected group.

      1. Select a snapshot type.
        • Snapshot: The read and write permissions of the generated snapshot are readable and writable.
        • HyperCDP: The read and write permissions of the generated snapshot are readable.
        NOTE:
        • If you have purchased the HyperCDP license, HyperCDP is recommended. HyperCDP provides high-density protection, ultra-large specifications, and lossless performance.
        • Create a second-level protected group. BCManager creates a scheduled plan on the storage array. The scheduled plan can be managed only by BCManager. You cannot delete the scheduled plan from the storage array.
      2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-179 lists related parameters.

        Table 5-179  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 second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, a day, a week, or a month with a fixed frequency.
          • When Snapshot Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing protected groups is 30 seconds.
          • When Snapshot Type is set to HyperCDP and Time Period is set to Second, the minimum interval for executing protected groups is 10 seconds.
        • 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.
      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 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.

      5. Click the Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-180 describes related parameters.

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

        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.
        • If the scheduling time period is second, the copy retention policy is automatically executed by the storage device.
      6. 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. When the HyperMetro (NAS), HyperMetro (SAN) or HyperMetro (NAS) and HyperVault or HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.

NOTE:

If a protected group uses HyperMetro (SAN) and snapshot (SAN), a snapshot copy being used by a recovery plan cannot be deleted. To delete such a snapshot copy, wait until the recovery plan finishes clearing.

Creating a Protected Group for FusionSphere VMs

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

Prerequisites

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

Context

In HyperMetro (SAN) and snapshot (SAN) scenarios, storage LUNs used by protected objects in a protected group must reside in a same HyperMetro consistency group, and the HyperMetro consistency group only have these LUNs.

When HyperMetro (NAS) or HyperMetro (NAS) and HyperVault DR is used, ensure that the local vStore and remote vStore are in a HyperMetro vStore pair, and their file system are also paired. In addition, ensure that the HyperMetro vStore pair and the HyperMetro pairs of file systems are all working properly.

Procedure

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

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

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

      Select one Protection Type based on the networking mode and DR technologies.
      • When the datastore group where the VMs to be protected reside using active-active (VIS) DR technology, select HyperMetro.

        The VIS device active-active technologies are used for protection. You need to select VMs that you want to protect one by one.

      • When the datastore group where the VMs to be protected reside using HyperMetro (SAN) DR technology, select HyperMetro.

        The HyperMetro technology enables service data to be written onto two data centers in real time. If you select a datastore group, all VMs in this group are protected.

      • When the datastore group where the VMs to be protected reside using HyperMetro (SAN) and Snapshot (SAN) DR technology, select HyperMetro.

        The snapshot technology is used to protect data. Virtual snapshots are periodically created for service data within a storage system. If you select a datastore group, all VMs in this group are protected.

      • When the datastore group where the VMs to be protected reside using HyperMetro (NAS) DR technology, select HyperMetro.

        The HyperMetro technology enables service data to be written onto two data centers in real time. If you select a datastore group, all VMs in this group are protected.

      NOTE:

      The datastore group where the VMs to be protected reside using active-active (VIS) and HyperMetro (SAN), the Protection Type is VIS Active-Active, SAN HyperMetro. Check the device before selecting the protection type.

    2. Select the protected object.

      • When the datastore group where the VMs to be protected reside using active-active (VIS) DR technology, after selecting HyperMetro, select VMs that you want to protect from Available VMs and move them to Selected VMs.
      • When the datastore group where the VMs to be protected reside using HyperMetro (SAN) or HyperMetro (SAN) and Snapshot (SAN) or HyperMetro (NAS) DR technology, after selecting HyperMetro. After you select the datastore group that you want to protect, the system automatically protects all VMs in the selected datastore group.
      • When the datastore group where the VMs to be protected reside using active-active (VIS) and HyperMetro (SAN):
        • If the datastore group are supplied by VIS, When the after selecting VIS Active-Active. Select VMs that you want to protect from Available VMs and move them to Selected VMs.
        • If the datastore group are supplied by storage, after selecting SAN HyperMetro. After you select the datastore group that you want to protect, the system automatically protects all VMs in the selected 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 active-active (VIS), HyperMetro (SAN) or HyperMetro (NAS) DR technology is used, select HyperMetro:HyperMetro data center solution.
      • When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, select HyperMetro and Snapshot:HyperMetro data center 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. When the HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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-181 lists related parameters.

        Table 5-181  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 second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, 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 Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 5-182 describes related parameters.

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

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

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

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

  10. When the HyperMetro (NAS), HyperMetro (SAN) or HyperMetro (SAN) and Snapshot (SAN) DR technology is used, 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.
  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:

If a protected group uses HyperMetro (SAN) and snapshot (SAN), a snapshot copy being used by a recovery plan cannot be deleted. To delete such a snapshot copy, wait until the recovery plan finishes clearing.

Creating a Protected Group for InterSystems Caché

This section describes how to create a protected group at the production end for InterSystems Caché databases. 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.

Procedure

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

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

  4. Click Next.
  5. Select the protected object.
    1. Select Production Site and Production Host(Group).

      Production Site is a local site.

    2. In the Available Databases area, select the instance name of the InterSystems Caché databases that you want to protect.
  6. Click Next.
  7. Set a protection policy.
    1. In the Protection Policy area, the system automatically matches HyperMetro:HyperMetro data center solution protection policies.
  8. Click OK.
  9. Click Next.
  10. 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.

Creating a Protected Group for NAS File Systems

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

Prerequisites

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

Context

  • When HyperMetro (NAS) or HyperMetro (NAS) and HyperVault DR is used, ensure that the local vStore and remote vStore are in a HyperMetro vStore pair, and their file system are also paired. In addition, ensure that the HyperMetro vStore pair and the HyperMetro pairs of file systems are all working properly.

  • When HyperMetro (NAS) and HyperVault DR is used, ensure that remote integrated backups are created on all the file systems in the active-active local vStore and active-active remote vStore and are stored on the same storage device.

After HyperMetro (NAS) and HyperVault DR is used to create a protection group, the policy of performing integrated backup automatically on the storage array will be disabled.

Procedure

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

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

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

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

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

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

      Select vStore for Available File System.

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

      When the HyperMetro (NAS) DR technology is used, select HyperMetro: Disaster Recovery Data Center Solution (HyperMetro Mode).

      • When the HyperMetro (NAS) and HyperVault DR technology is used, select HyperMetro and HyperVault: Disaster Recovery Data Center Solution (HyperMetro 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. When the HyperMetro (NAS) and HyperVault DR technology is used, 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-183 lists related parameters.

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

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

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

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

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

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

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

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

Document ID: EDOC1100075861

Views: 10646

Downloads: 55

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