Creating a Protected Group

Context

• The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.
• Only when the underlying storage supports the snapshot function, you can create protected objects that can be scheduled in seconds.
• When the protected objects are DB2 databases, a protected group can include DB2 databases that are in the same instance.

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 and then click Create at the upper right corner for the page.
2. Select the protected object type. This operation varies with the protected object type.

   Table 1 Protected objects

   Protected Object	Operation
   Oracle	Set Production Site and Production Host(Group) and select a database to be protected. 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 user name and password of the database instance and the user name and password of the ASM instance is used for verification. 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. NOTE: 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. 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. NOTE: 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.
   DB2 SQL Server SAP HANA	Set Production Site and Production Host(Group) and select a database to be protected. In the Available Databases dialog box that is displayed, enter necessary authentication information and click OK. Set Authentication Mode, which can be Database Authentication or OS Authentication. NOTE: The system starts authenticates the server immediately after you enter the instance user name and password. If the authentication fails, confirm the user name and password and then reselect the server.
   LUN	Select values from the drop-down list of Production Site and Disk Array. In LUN and Consistency Groups, select the object to be protected. You can search for objects to be protected using LUN name, LUN group name, or Remote replication consistency group.
   VMware	Select Production Site, vCenter, and Protection Type. Set Protection Type to HyperVault DR. HyperVault DR retains multiple snapshot copies of service data within a storage system or on different storage systems, enabling DR protection at the storage layer. Select the datastore group where the VMs to be protected reside. The system automatically protects all VMs in the selected datastore group. NOTE: A datastore group is a set of VMs on the vCenter. After a vCenter server is added, the system will calculate the number of datastores on the vCenter, the VMs on a remote replication pair or consistency group will be allocated to a datastore group.

3. Click Next.
4. On the Protection Policy page, select HyperVault: Disaster Recovery Data Center Solution (Active-Passive Mode).

   

   

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

5. Click Settings under Storage Replication (Asynchronous) to set the scheduling period for generating snapshot copies at the production end as well as the replication policy and consistency policy for snapshot copies.

   In the CDM solution, snapshot backup scheduling, replication, and consistency policies can be configured for local and remote storage. The local backup policy supports backup at the minimum interval of 30 seconds (Dorado V3) and HyperCDP supports backup at the minimum interval of 10 seconds (Dorado V3) or 3 seconds (Dorado V6). If the snapshot must meet the requirements of the application consistency policy, backup interval must be greater than or equal to 15 minutes.

   

   The restrictions on OceanStor Dorado V6 are as follows:

   • Synchronous replication is not supported.
   • The scheduled snapshot plan in seconds for common snapshots is not supported.
   • The HyperCDP scheduled snapshot plan is supported.
   1. Click the Scheduling Policy tab. In the Time Policy area, set the time policy, that is, policy for generating snapshots at the production end, for the protected group. Table 2 lists related parameters.

      

      Table 2 Time policies

      Time Policy	Description
      On-demand scheduling	Manually starts protection tasks.
      Period-based scheduling	Automatically starts protection tasks based on a given period. Tasks can be executed at multiple time points of a second, a minute, an hour, a day, a week, or a month. 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, a day, a week, or a month. Alternatively, at a specific time segment of a minute, 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 is used as an example. The DST starts at 2016-03-12 02:00:00, and ends at 2016-11-06 02:00:00. If the start time of the protection policy falls within the first hour (2016-03-12 02:00:00 to 03:00:00) after the DST starts, for example, 2016-03-12 02:30:00, the protection group will be automatically executed with a delay of one hour, that is 2016-03-12 03:30:00. If the start time of the protection policy falls with the last hour (2016-11-06 01:00:00 to 02:00:00) before the DST ends, for example, 2016-11-06 01:30:00, the protection group will be executed after the DST ends for half an hour.

   2. When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable PRO Requirement Satisfaction Check, the actual RPO is check against the configured RPO. If the actual RPO exceeds the expected RPO, the system generates an alarm, indicating that the RPO requirement is not satisfied.

      

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

      

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

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

      Table 3 Replication policies

      Replication Policy	Description
      Default configuration	The remote replication rate is the default one set on the storage array.
      Manual configuration	Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period. Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

   4. Click the Consistency Policy tab. Select Enable consistency protection to configure the consistency policy. Consistency parameters vary with the protected object type.
      

      Tips for enabling the consistency policy:

      • If the scheduling policy is On-demand scheduling, Consistency Policy is enabled by default. You can determine whether to deselect Consistency Policy.
      • If the scheduling policy is Time-based scheduling, the Time Period is not Second and more than 15 minutes, you can determine whether to select Consistency Policy.

      Table 4 Consistency parameters for different protected object types

      Protected Object	Parameter	Description
      Oracle	Enable hot backup mode and Configure Min. Archive Space Threshold 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.	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.
      DB2	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.	Quiescing databases to ensure data consistency may fail if the application I/O load is heavy. For this reason, you are advised to perform this operation in off-peak hours or do not enable consistency protection.
      SQL Server	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.
      LUN	Enable consistency protection 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.	For details about script names and descriptions, see Table 5. 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/sbin/thirdparty/(on No-Windows). Table 6 describes the script template. NOTICE: 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).
      VMware	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.	To generate a quiesced snapshot, you need to install VMware Tools or Open VM Tools on the VM. NOTICE: If the silent snapshot fails to be created, the backup operation can be performed without affecting the backup of other VMs.

      Table 5 Script names and descriptions

      Parameter	Used To
      Freezing script	Freeze application I/Os and flush dirty data of applications.
      Unfreezing script	Unfreeze application I/Os.
      Script for querying freezing status	Query whether applications are frozen.
      Freezing timeout duration	Specify the timeout duration of freezing. The default value is 60 seconds.

      Table 6 Script template description

      Operating System	Script	Description	Save Path
      Windows	sample_freeze.bat	Template of the Oracle freezing script	%OceanStor BCManager Agent install path%\bin\thirdparty\
      	sample_unfreeze.bat	Template of the Oracle unfreezing script
      	sample_queryfreezestate.bat	Template of the Oracle script for querying the freezing status
      No-Windows	sample_freeze.sh	Template of the Oracle freezing script	/home/rdadmin/Agent/sbin/thirdparty/
      	sample_unfreeze.sh	Template of the Oracle unfreezing script
      	sample_queryfreezestate.sh	Template of the Oracle script for querying the freezing status

   5. Click OK.

6. Click Set. Set the scheduling policy, retention policy, and consistency policy for data synchronization and snapshot copy generation at the production/DR end.

   The CDM solution uses BCManager eReplication to coordinate replication and snapshot modules to ensure data consistency at the remote backup.

   The remote backup policy supports the backup interval of a minimum of 30 seconds. If the snapshot meets the application consistency policy, the backup interval must be greater than or equal to 15 minutes.

   1. Select Enable Quick Backup.
   2. Select the snapshot type.
      • If you select Snapshot, the generated snapshots can be read and written.
      • If you select HyperCDP, the generated snapshots are read-only.
      

      • If you have bought the HyperCDP license, you are advised to select HyperCDP which offers high security and super large specifications and has minimum impact on performance.
      • If you want to create a protected group that can be scheduled in seconds, eReplication will create a scheduled snapshot plan. This plan can be managed only by eReplication, and manual deletion is not supported.
   3. Click the Scheduling Policy tab. In the Time Policy area, set the time policy for the protected group. That is, policy for data synchronization and snapshot copy generation at the production end. The execution policy at the DR end can only be Execute Immediately After Replication. Table 7 lists related parameters.

      Table 7 Time policies

      Time Policy	Description
      On-demand scheduling	Manually starts protection tasks.
      Period-based scheduling	Automatically starts protection tasks based on a given period. Tasks can be executed at multiple time points of a second, a minute, an hour, a day, a week, or a month. When Snapshot Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing a protected group is 30 seconds. When HyperCDP Type is set to Snapshot and Time Period is set to Second, the minimum interval for executing a protected group is 10 seconds or 3 seconds (Dorado V6). 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, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, 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 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.

   4. When the Scheduling Policy is set to Period-based scheduling and set time period to be greater than Second, 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 5-59 minutes.

      

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

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

      

      Table 8 Retention policies

      Retention Policy	Description
      Latest duplicate	The number of duplicates cannot exceed the maximum number of snapshots that can be taken for a storage resource such as a LUN or file system.
      Duplicate retention	The duplicate retention policy defines the retention policy of duplicates generated during the protected group protection. When the system starts duplicate maintenance, expired and invalid duplicates will be deleted based on the duplicate retention policy. By default, the time to maintain duplicates is the 39th minute of every hour. NOTE: After a user resets Latest duplicate, the duplicate maintenance will be triggered immediately. You can set the minimum number of duplicates to be retained. The system will not delete valid duplicates until the number of invalid duplicates exceeds the minimum number of duplicates you set. The value range for a daily policy is 0–365. The default value is 0, meaning to retain no duplicates. The value range for a weekly policy is 0–52. The default value is 0, meaning to retain no duplicates. The value range for a monthly policy is 0–60. 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. Duplicates are unique. If a duplicate is the same as an existing one, only one of them will be retained. If the scheduling period is Second, the retention policy is executed by the storage.

   6. Click the Consistency Policy tab and set the data consistency policy for each protected object. For details about the parameters, see Table 4.
   7. Click OK.

7. Optional: If you want to use the cloud backup service, click Settings under Cloud Backup.
   1. Select Enable Cloud Backup.
   2. Click the Scheduling Policy tab. In the Time Policy area, set the execution policy of the protected group, that is, the policy for generating snapshots on the production site. Table 9 describes related parameters.

      Table 9 Time policies

      Time Policy	Description
      On-demand scheduling	Manually starts protection tasks.
      Period-based scheduling	Automatically starts protection tasks based on a given period. Tasks can be executed at multiple time points of a minute, an hour, a day, a week, or a month.and at a fixed frequency for a certain period of time at a minute, an hour, a day, a week, or a month. 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, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, 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 5-59 minutes.

      

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

   4. Click the Reservation Policy tab. Set Latest duplicate and the duplicate retention policy. Table 10 describes related parameters.

      

      Table 10 Retention policies

      Retention Policy	Description
      Latest duplicate	The number of duplicates cannot exceed the maximum number of snapshots that can be taken for a storage resource such as a LUN or file system.
      Duplicate retention	The duplicate retention policy defines the retention policy of duplicates generated during the protected group protection. When the system starts duplicate maintenance, expired and invalid duplicates will be deleted based on the duplicate retention policy. By default, the time to maintain duplicates is the 39th minute of every hour. NOTE: After a user resets Latest duplicate, the duplicate maintenance will be triggered immediately. You can set the minimum number of duplicates to be retained. The system will not delete valid duplicates until the number of invalid duplicates exceeds the minimum number of duplicates you set. The value range for a daily policy is 0–365. The default value is 0, meaning to retain no duplicates. The value range for a weekly policy is 0–52. The default value is 0, meaning to retain no duplicates. The value range for a monthly policy is 0–60. 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. Duplicates are unique. If a duplicate is the same as an existing one, only one of them will be retained. If the scheduling period is Second, the retention policy is executed by the storage.

   5. Configure the consistency policy. Consistency parameters vary with the protected object type. Table 11 describes configuring the consistency policy
      

      Tips for enabling the consistency policy:

      • If the scheduling policy is On-demand scheduling, Consistency Policy is enabled by default. You can determine whether to deselect Consistency Policy.
      • If the scheduling policy is Time-based scheduling and the Time Period is not Second and more than 15 minutes, you can determine whether to select Consistency Policy.

      Table 11 Consistency parameters for different protected object types

      Protected Object	Parameter	Description
      Oracle	Enable hot backup mode and Configure Min. Archive Space Threshold 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.	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.
      DB2	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.	Quiescing databases to ensure data consistency may fail if the application I/O load is heavy. For this reason, you are advised to perform this operation in off-peak hours or do not enable consistency protection.
      SQL Server	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.
      SAP HANA	Quiesce database	In the asynchronous replication scenario, when the user does not set up a remote replication relationship between the storage LUNs where log files reside, the system will forcibly select Quiesce database.
      LUN	Enable consistency protection 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.	For details about script names and descriptions, see Table 12. 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/sbin/thirdparty/(on No-Windows). Table 13 describes the script template. NOTE 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). NOTICE: 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).
      VMware	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.	To generate a quiesced snapshot, you need to install VMware Tools or Open VM Tools on the VM. NOTICE: If the silent snapshot fails to be created, the backup operation can be performed without affecting the backup of other VMs.

      Table 12 Script names and descriptions

      Parameter	Used To
      Freezing script	Freeze application I/Os and flush dirty data of applications.
      Unfreezing script	Unfreeze application I/Os.
      Script for querying freezing status	Query whether applications are frozen.
      Freezing timeout duration	Specify the timeout duration of freezing. The default value is 60 seconds.

      Table 13 Script template description

      Operating System	Script	Description	Save Path
      Windows	sample_freeze.bat	Template of the Oracle freezing script	%OceanStor BCManager Agent install path%\bin\thirdparty\
      	sample_unfreeze.bat	Template of the Oracle unfreezing script
      	sample_queryfreezestate.bat	Template of the Oracle script for querying the freezing status
      No-Windows	sample_freeze.sh	Template of the Oracle freezing script	/home/rdadmin/Agent/sbin/thirdparty/
      	sample_unfreeze.sh	Template of the Oracle unfreezing script
      	sample_queryfreezestate.sh	Template of the Oracle script for querying the freezing status

   6. Click OK.

8. Optional: If you want the system to automatically create a level-2 copy of a snapshot copy and mount it to a specified application hosts for data reuse, set the mounting policy here.

   The administrator sets a specified time for mounting in advance. eReplication records the event and uses the snapshot copy at the production or DR site to create a level-2 copy at the specified time, automatically mount the copy to the specified application host so that data can be analyzed and tested in unattended mode.

   1. In the Mounting Policy area, click Settings to set whether the level-2 copy is automatically created and mounted.

      

   2. Select Automatic mounting. Backup copies can be automatically mounted to the host or host group after being generated.
   3. Select the period, site, and host group to which the copy is mounted.If the protected object is VMware, select Site, vCenter, and Cluster, and configure the network required by the scenario of copy reuse. The default network is the network corresponding to the resource mapping. You are advised to use a network different from that used by the production VM to avoid IP address conflict.

      The system automatically creates a level-2 copy based on the snapshot copy generated at the production or DR site within the specified period and automatically mounts the copy to the host or hosts in the host group. By default, the system mounts copies generated at all time points to the same host, host group, or cluster.

   4. Set mounting items. Table 14 describes related parameters.

      Table 14 Mounting parameters

      Parameter	Description	Remarks
      Unmount Mounted Copies Before Mounting	Before mounting copies for multiple times, unmount the mounted copies. Otherwise, the copies may fail to be mounted. If this parameter is selected, the system automatically unmounts current copies.	This parameter can be configured for supported protected objects.
      Delete the copies automatically after the unmounting	If this parameter is selected, the system automatically deletes the unmounted copy.	This parameter can be configured for supported protected objects.
      Start the database after the mounting	If this option is selected, the database is automatically started after the copy is mounted to the target host or host group. If this option is not selected, you need to log in to the host and manually start the database after the copy is mounted to the target host or host group.	This parameter can be configured when the protected object is Oracle, DB2, or SQL Server.

   5. Optional: If you want scripts to be executed automatically on the host to adapt to special data usage scenarios, for example, invoke the script to execute data decryption, or disable or start a process, log in to the host to download the script template and customize the script, click Mount Script to set the name of the pre-script and post-script to be mounted.
      

      For customized scripts are not provided by eReplication, you must ensure the script correctness. Before configuring the script, ensure that the script has been tested and verified.

   6. Click OK.

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.
11. Click Finish.
12. Click OK.

Customizing a Script

Perform the following steps to log in to the host to obtain the script template, customize a script, and save the script in the specified path:

1. You can log in to the host where the protected object resides, obtain the script template, and customize the execution script based on the template.
   • In Windows, the script path is %OceanStor BCManager Agent install path%\bin\thirdparty\.
   • In Linux or Unix, the script path is /home/rdadmin/Agent/sbin/thirdparty/.
2. Place the customized execution script in a specified path of the host where the protected object resides.
   • In Windows, the script path is %OceanStor BCManager Agent install path%\bin\thirdparty\.
   • In Linux or Unix, the script path is /home/rdadmin/Agent/sbin/thirdparty/.
3. Set the owner and execute permission of the customized execution script.
   • In Windows, settings are not required.
   • In Linux or Unix, run chown root xxx.sh to set the script owner to root. Run chmod 500 xxx.sh to set the script execute permission to 500.

     In the preceding commands, xxx indicates the customized script name.

   

   If you do not set the owner and execute permission of the customized script, the script may be modified by hackers, posing security risks.

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.
  

  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.