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.

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.

  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 Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-207 lists related parameters.

          Table 5-207  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.
        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, 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. In the Storage Configuration area, select the resource pool configuration as show in Table 5-208.
          Table 5-208  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

        6. Click OK.
      • For Snapshot:Local protection solution:
        This section uses a policy of the Snapshot (SAN) type as an example. For a policy of Snapshot (VIS) type, click Reservation Policy. On the tab page that is displayed, you can change the number of Latest duplicate and Snapshot Resource Pool Ratio, where Snapshot Resource Pool Ratio defaults to 10%. The reserved logical disk capacity (data format not retained) must be larger than the source volume capacity x Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, the Snapshot Resource Pool Ratio cannot be modified.
        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-209 lists related parameters.

          Table 5-209  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-210 describes related parameters.

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

  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. When the Snapshot (VIS) or 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.
  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.
NOTE:

If a protected group uses 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

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 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.
  6. Click Next.
  7. 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 Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-211 lists related parameters.

          Table 5-211  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.
        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, 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. In the Storage Configuration area, select the resource pool configuration as show in Table 5-212.
          Table 5-212  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

        6. Click OK.
      • For Snapshot:Local protection solution:
        NOTE:
        If the policy type is Snapshot (VIS), you can modify Snapshots, Policy, and Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, Snapshot Resource Pool Ratio cannot be modified.
        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-213 lists related parameters.

          Table 5-213  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-214 describes related parameters.

          Table 5-214  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 Snapshot (VIS) or 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 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

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.
  6. Click Next.
  7. 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 Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-215 lists related parameters.

          Table 5-215  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.
        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. In the Storage Configuration area, select the resource pool configuration as show in Table 5-216.
          Table 5-216  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

        6. Click OK.
      • For Snapshot:Local protection solution:
        NOTE:
        If the policy type is Snapshot (VIS), you can modify Snapshots, Policy, and Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, Snapshot Resource Pool Ratio cannot be modified.
        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-217 lists related parameters.

          Table 5-217  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-218 describes related parameters.

          Table 5-218  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. 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:

If a protected group uses 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 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 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 Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-219 lists related parameters.

          Table 5-219  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.
        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, 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. In the Storage Configuration area, select the resource pool configuration as show in Table 5-220.
          Table 5-220  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

        6. Click OK.
      • For Snapshot:Local protection solution:
        NOTE:
        If the policy type is Snapshot (VIS), you can modify Snapshots, Policy, and Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, Snapshot Resource Pool Ratio cannot be modified.
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-221 lists related parameters.

          Table 5-221  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.
        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-222 describes related parameters.

          Table 5-222  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.
        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. 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:

If a protected group uses 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

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

Procedure

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

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

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

      hen the synchronous Snapshot (SAN) or Snapshot (NAS) DR technology is used, select Array Snapshot.

      The snapshot technology is used to protect data. Virtual snapshots are periodically created for service data within a storage system.

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

      The system automatically protects all VMs in the selected datastore.

  6. Click Next.
  7. 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 Snapshot (SAN) or Snapshot (NAS) DR technology is used, select Snapshot:Local protection 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. 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-223 lists related parameters.

        Table 5-223  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-224 describes related parameters.

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

NOTE:

If a protected group uses 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 Local File Systems

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

Prerequisites

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

Context

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

Procedure

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

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

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

      • When the synchronous Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-225 lists related parameters.

          Table 5-225  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.
        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, 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. In the Storage Configuration area, select the resource pool configuration as show in Table 5-226.
          Table 5-226  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

        6. Click OK.
      • For Snapshot:Local protection solution:
        NOTE:
        If the policy type is Snapshot (VIS), you can modify Snapshots, Policy, and Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, Snapshot Resource Pool Ratio cannot be modified.
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-227 lists related parameters.

          Table 5-227  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.
        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-228 describes related parameters.

          Table 5-228  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.
        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. 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:

If a protected group uses 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 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. Set Name and Description of the protected group.

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

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

      • LUN

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

      • Remote replication consistency group

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

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

      • When the synchronous Clone (SAN) DR technology is used, select Clone:Local protection solution.
      • When the synchronous Snapshot (SAN) or Snapshot (VIS) DR technology is used, select Snapshot:Local protection 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 Clone:Local protection solution:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. Table 5-229 lists related parameters.

          Table 5-229  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.
        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 Clone Policy tab page to set the execution policy for the clone splitting. Table 5-230 shows description about parameters.

          Table 5-230  Description about the clone policies

          Execution Policy

          Policy Description

          Delay the splitting after the protected group begins to be executed

          By default, the clone splitting starts immediately after the data replication is complete.If you select Delay the splitting after the protected group begins to be executed, the splitting starts when the split delay time comes.
          NOTE:
          • The value of Split Delay Time is not greater than 1410.
          • If the split delay time comes, the data replication will be stopped even if it is incomplete and the clone splitting will start.
          • If a user has configured a prescript or frozen script, the prescript or frozen script will be executed before splitting.

          Create a snapshot if the splitting fails

          If the splitting fails, replace the clone copy with the consistency snapshot of the primary LUN.
          NOTICE:
          If you deselect Create a snapshot if the splitting fails, the protected group will fail to be executed after the splitting fails.
        5. 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-231 describes the script template.
            Table 5-231  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

        6. Click OK.
        7. In the Storage Configuration area, select the resource pool configuration as show in Table 5-232.
          Table 5-232  Resource pool configuration

          Configuration

          Description

          Default configuration

          Please select or create the resource pool at first, the system will establish clone replationship based on LUNs in resource pool.

          Manual configuration

          Manually select the resource pool, if not, click Create, the system will establish clone replationship based on LUNs in resource pool.

      • For Snapshot:Local protection solution:
        NOTE:
        If the policy type is Snapshot (VIS), you can modify Snapshots, Policy, and Snapshot Resource Pool Ratio. If duplicates have been activated for a Snapshot (VIS) protected group, Snapshot Resource Pool Ratio cannot be modified.
        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-233 lists related parameters.

          Table 5-233  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-234 describes related parameters.

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

          Select Enable consistency protection, and then select Application Host (Group) for which the script needs to be executed.

          • If you select System script, perform the following operations:

            1. Select the system script type corresponding to the service host (group).
            2. Set script parameters.
              • On the right of Freezing Script, click Configuring Script Parameters to set parameters for the freezing script. Freezing Script: Freezing Script: this script is used to freeze application I/Os.
              • On the right of Unfreezing Script, click Configuring Script Parameters to set parameters for the unfreezing script. Unfreezing Script: this script is used to unfreeze application I/Os.
              • On the right of Freezing Status Query Script, click Configuring Script Parameters to set parameters for the freezing status query script. Freezing Status Query Script: this script is used to check whether applications are frozen.


              NOTE:
              • For details about the context parameters and parameter description automatically delivered from Server to Agent, see Parameter Description for Customized Scripts.
              • Common parameters are applicable to all scripts. Step parameters are applicable only to the current script.
              • Parameter names and values in the scripts cannot contain special characters. Otherwise, executing the scripts may fail.

                Special characters include ~!@#$%*-_=+[{}];:\,./?.

            3. On the right of Freezing Status Query Script, click Configuring Script Parameters to set parameters for the freezing status query script. Freezing Status Query Script: this script is used to check whether applications are frozen.
          • If you select Customized script, perform the following operations:
            1. Choose Unfreezing Script, Freezing ScriptFreezing Status Query Script, and configure script parameters.

              • A self-defined script is not provided by eReplication, so the script provider must ensure the script correctness. Before configuring the script, ensure that the script has been verified.To verify the LUN consistency protection script, see Verifying the LUN Protected Group Consistency Script(MySQL).
              • Parameter names and values in the scripts cannot contain special characters. Otherwise, executing the scripts may fail.

                Special characters include ~!@#$%*-_=+[{}];:\,./?.

              • On the right of Freezing Script, click Configuring Script Parameters to set parameters for the freezing script. Freezing Script: Freezing Script: this script is used to freeze application I/Os.
              • On the right of Unfreezing Script, click Configuring Script Parameters to set parameters for the unfreezing script. Unfreezing Script: this script is used to unfreeze application I/Os.
              • On the right of Freezing Status Query Script, click Configuring Script Parameters to set parameters for the freezing status query script. Freezing Status Query Script: this script is used to check whether applications are frozen.
            2. On the right of Freezing Status Query Script, click Configuring Script Parameters to set parameters for the freezing status query script. Freezing Status Query Script: this script is used to check whether applications are frozen.
            NOTE:

            For details about the context parameters and parameter description delivered from Server to Agent, see Parameter Description for Customized Scripts.

          • Freezing Timeout indicates the maximum freezing duration supported by host services. The default value is 60 seconds.
        6. 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-235 describes the script template.
          Table 5-235  Script Template Description

          Operating System

          Script

          Description

          Save Path

          Windows

          sample_freeze.bat

          Template of the freezing Oracle script

          OceanStor BCManager 6.5.0_Agent-WIN64\bin\thirdparty\sample

          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

          sample_unfreeze.sh

          Template of the unfreezing Oracle script

          sample_queryfreezestate.sh

          Template of the Oracle script for querying the freezing status

        7. Click OK.
          • When System script is selected, In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.. Click OK.
            NOTE:

            After commands are issued, the system adds the step of starting the MySQL in the test process and adds the step of stopping the MySQL in the cleanup process. You need to enable and configure the step on the Edit page of the recovery plan.

          • When Customized script is selected, the system will automatically deliver commands.

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

  6. Click Next.
  7. 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 Snapshot (SAN) DR technology is used, select Snapshot:Local protection 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. 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-236 lists related parameters.

        Table 5-236  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 minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of 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.
      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-237 describes related parameters.

        Table 5-237  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.
      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:

If a protected group uses 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.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 12181

Downloads: 64

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