Creating a Protected Group for FusionCompute VMs

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

Prerequisites

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

Context

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

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

Procedure

In the menu bar, Choose Protection.
Click Create.
Select the protected object.
1. Select Production Site, FusionCompute Component and Protection Type.
  Select one Protection Type based on the networking mode and DR technologies.
  - If the datastore where the VMs managed by FusionCompute reside uses only the HyperMetro (SAN) DR technology, select HyperMetro.The HyperMetro technology of storage arrays is used for protection. Service data is written to two data centers in real time.
  - If the datastore where the VMs managed by FusionCompute reside uses only the HyperMetro (SAN) + backup (SAN) DR technology, select HyperMetro.The HyperMetro technology of storage arrays is used for protection. Service data is written to the two data centers in real time. In addition, the system periodically generates virtual copies of service data in the two data centers based on the time policy.
  - If the datastore where the VMs managed by FusionCompute reside uses only the HyperMetro (NAS) DR technology, select HyperMetro.The HyperMetro technology of storage arrays is used for protection. Service data is written to two data centers in real time.
2. Select the protected object.
  - If the datastore where the VMs managed by FusionCompute reside uses only the HyperMetro (SAN), HyperMetro (SAN) + backup (SAN), or HyperMetro (NAS) DR technology, select the datastore where the VMs to be protected reside after selecting the HyperMetro protection type, the system automatically protects VMs in the selected datastore.
Click Next.

Set a protection policy.

On the Protection Policy page, the system automatically matches supported protection policies. Select a policy based on your data protection solution.
- When the HyperMetro (SAN) and Backup (SAN) DR technology is used, select HyperMetro and Backup:HyperMetro data center solution.
  - If there are matched protection policies, you can select a protection policy based on your data protection solution and modify the time policy of the protection policy.
  - If there are no matched protection policies, check whether the storage devices used by protected objects have been configured as planned. If the storage devices have not been configured, configure them as planned. After configuration, perform the following operations: On the menu bar, click Resources, select a node under the management server. In the site node, click Storage, in the line where the storage device resides, click Refresh to refresh the storage device information under the site. Refresh the FusionCompute information too and recreate a protected group.

When the HyperMetro (SAN) and Backup (SAN) DR technology is used, click Set to set the protection policy for the protected group.

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

**Table 1** Time policies
Time Policy	Description
On-demand scheduling	Manually starts protection tasks.
Period-based scheduling	Automatically starts protection tasks based on a period set by the system. NOTE: To ensure data consistency, the execution timetable for a protected group policy template must be set. You are advised to set the execution time to off-peak hours. Tasks can be executed at multiple time points of a second, a minute, an hour, a day, a week, or a month. Alternatively, at a specific time segment of a second, a minute, an hour, a day, a week, or a month with a fixed frequency. It is recommended that the starting time of the validate period is set to a time later than the completion of the initial synchronization. If daylight saving time (DST) is enabled on the eReplication management server, a DR protection task whose trigger time point falls within the DST shift period cannot be executed at the scheduled time. Details are as follows: (UTC-08:00) Pacific Time (United States and Canada) is used as an example. The DST starts at 2016-03-12 02:00:00, and ends at 2016-11-06 02:00:00. If the start time of the protection policy falls within the first hour (2016-03-12 02:00:00 to 03:00:00) after the DST starts, for example, 2016-03-12 02:30:00, the protection group will be automatically executed with a delay of one hour, that is 2016-03-12 03:30:00. If the start time of the protection policy falls with the last hour (2016-11-06 01:00:00 to 02:00:00) before the DST ends, for example, 2016-11-06 01:30:00, the protection group will be executed after the DST ends for half an hour.

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.

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

**Table 2** 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–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. NOTE: 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.

Click OK.

Click Next.
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.
When the HyperMetro (NAS), HyperMetro (SAN) or HyperMetro (SAN) and Backup (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.
Click Finish.
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.

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

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

If a protected group uses HyperMetro (SAN) and backup (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.