eReplication provides policy-based automatic protection for different protected objects.
To implement policy-based automatic protection, you need to create protected groups for protected objects on eReplication. Once a protected group is created, it will be automatically executed based on the preset policy.
This section describes how to create a protected group at the production site for Kubernetes 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.
- In the backup scenario, a Kubernetes cluster has been added to the production site, and application resources have been added to the cluster.
- In the DR scenario, a Kubernetes cluster has been added to both the production site and DR site. In addition, application resources have been added or data volumes exist in the production cluster.
Context
Protected objects in a protected group must reside on the same storage device.
Procedure
- In the menu bar, choose Protection.
- Click Create.
- Select a protected object.
- Select kubernetes as the protected object type.
- Select Production Site and kubernetes Cluster where Kubernetes to be protected resides.
- Select kubernetes Object to be protected. You can select Application resource or Data volume.
- If you select Application resource as the kubernetes object to be protected, select the application resources to be protected.
If you need to refresh the application resource information, click Refresh in the Operation column of the corresponding resource.
- If you select Data volume as the kubernetes object to be protected, you can select Replication or HyperMetro as the protection type.
- If you select Replication, you need to select the storage backend where the data volume resides and select one or more data volumes as protected objects as required.
- If you select HyperMetro, you need to select the HyperMetro domain where the data volume resides. The system automatically selects all data volumes in the HyperMetro domain and cannot deselect them.
- If the protected object is an application resource, only one application resource can be added to one protected group.
- If protected objects are data volumes and the protection type is Replication, a maximum of 128 data volumes can be added to a protected group when the protected group is created. After a protected group is created, you can add protected data volumes by adding protected objects. A maximum of 128 protected data volumes can be added at a time. If you want to add more than 128 protected data volumes, add them in batches. The number of data volumes supported by a protected group is the number of storage NAS remote replication pairs minus one. For details about how to add a protected object, see Adding/Deleting a Protected Object.
- If the protected objects are data volumes and the protection type is HyperMetro, the number of data volumes supported by the protected group are the number of pairs of storage active-active file systems minus 1.
- Click Next.
- The system automatically matches supported protection policies. Select a proper protection policy and configure a time policy based on your data protection solution. If application consistency is involved, configure an application consistency policy.
- If you select application resources as protected objects, perform the following operations to set a protection policy:
Click Settings. In the Set Protection Policy dialog box, set the protection policy.
- If the selected data protection solution is Local Storage Backup for Application Resources, set protection policy parameters as described in Table 1.
Table 1 Parameters of the local storage backup policyParameter
|
Description
|
Setting
|
Execution Policy
|
Protected group execution policy.
|
Select On-demand scheduling or Period-based scheduling as required.
If you select Period-based scheduling, you also need to set the execution period.
NOTE: - When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable RPO Requirement Satisfaction Check, the actual RPO will be checked 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 to 31 days and 0 to 23 hours.
|
Execution Period
|
- Set the execution time of the protected group.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
Hour, Day, Week, Month.
Select as required. By default, all options are not selected.
|
Hour
|
- The time policy can be configured by hour.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 0 to 59 minutes.
- The number of retained copies ranges from 1 to 256.
|
Day
|
- The time policy can be configured by day.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 00:00 to 23:59.
- The number of retained copies ranges from 1 to 256.
|
Week
|
- The time policy can be configured by week.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Month
|
- The time policy can be configured by month.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Pre-hook
|
Select the HOOK to be executed before the backup. This parameter is optional.
|
Select a value as required.
|
Post-hook
|
Select the HOOK to be executed after the backup. This parameter is optional.
|
Select a value as required.
|
Consistent Snapshot
|
Whether to enable the consistent snapshot function during backup.
|
Enable, Disable.
This function is disabled by default.
|
- If the selected data protection solution is Cross-Storage Backup for Application Resources, set protection policy parameters as described in Table 2.
Table 2 Parameters of a cross-storage backup policyParameter
|
Description
|
Setting
|
Target storage for volume backup
|
Backend of the target storage to be backed up.
|
Select a value as required.
|
Execution Policy
|
Protected group execution policy.
|
Select On-demand scheduling or Period-based scheduling as required.
If you select Period-based scheduling, you also need to set the execution period.
NOTE: - When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable RPO Requirement Satisfaction Check, the actual RPO will be checked 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 to 31 days and 0 to 23 hours.
|
Execution Period
|
- Set the execution time of the protected group.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
Hour, Day, Week, Month.
Select as required. By default, all options are not selected.
|
Hour
|
- The time policy can be configured by hour.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 0 to 59 minutes.
- The number of retained copies ranges from 1 to 256.
|
Day
|
- The time policy can be configured by day.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 00:00 to 23:59.
- The number of retained copies ranges from 1 to 256.
|
Week
|
- The time policy can be configured by week.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Month
|
- The time policy can be configured by month.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Pre-hook
|
Select the HOOK to be executed before the backup. This parameter is optional.
|
Select a value as required.
|
Post-hook
|
Select the HOOK to be executed after the backup. This parameter is optional.
|
Select a value as required.
|
Consistent Snapshot
|
Whether to enable the consistent snapshot function during backup.
|
Enable, Disable.
This function is disabled by default.
|
Sync Rate
|
Rate of synchronizing data to the target storage during backup.
|
The default value is Medium.
- Low: 0 MB/s to 5 MB/s. The restoration takes a long time. This mode is applicable to scenarios where the service load is heavy.
- Medium: 10 MB/s to 20 MB/s. The restoration takes a relatively short period of time. This mode is applicable to scenarios where the service load is relatively heavy.
- High: 50 MB/s to 70 MB/s. The restoration takes a short time. This mode is applicable to scenarios where the service load is relatively light.
- Highest: Above 100 MB/s. The restoration takes the shortest time. This mode is applicable to scenarios where the service load is light.
|
- If the selected data protection solution is Cross-Cluster Replication for Application Resources, set protection policy parameters as described in Table 3.
Table 3 Parameters of a cross-cluster replication policy for application resourcesParameter
|
Description
|
Setting
|
DR Site
|
DR site.
|
Select a value as required.
|
Disaster Recovery Cluster
|
Cluster at the DR site.
|
Select a value as required.
|
Disaster Recovery Storage Backend
|
Storage backend at the DR site.
|
Select a value as required.
|
Execution Policy
|
Protected group execution policy.
|
Select On-demand scheduling or Period-based scheduling as required.
If you select Period-based scheduling, you also need to set the execution period.
NOTE: - When the Scheduling Policy is set to Period-based scheduling, in the Expected RPO area, if you select Enable RPO Requirement Satisfaction Check, the actual RPO will be checked 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 to 31 days and 0 to 23 hours.
|
Execution Period
|
- Set the execution time of the protected group.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
Hour, Day, Week, Month.
Select as required. By default, all options are not selected.
|
Hour
|
- The time policy can be configured by hour.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 0 to 59 minutes.
- The number of retained copies ranges from 1 to 256.
|
Day
|
- The time policy can be configured by day.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
- The time ranges from 00:00 to 23:59.
- The number of retained copies ranges from 1 to 256.
|
Week
|
- The time policy can be configured by week.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Month
|
- The time policy can be configured by month.
- This option is displayed when the execution policy of the protected group is Period-based scheduling.
|
|
Consistency Group
|
Whether to select Remote replication relationship for Consistency Group.
|
Enable, Disable.
This function is disabled by default.
|
Sync Rate
|
Rate of synchronizing data to the target storage during protection execution.
|
The default value is Medium.
- Low: 0 MB/s to 5 MB/s. The restoration takes a long time. This mode is applicable to scenarios where the service load is heavy.
- Medium: 10 MB/s to 20 MB/s. The restoration takes a relatively short period of time. This mode is applicable to scenarios where the service load is relatively heavy.
- High: 50 MB/s to 70 MB/s. The restoration takes a short time. This mode is applicable to scenarios where the service load is relatively light.
- Highest: Above 100 MB/s. The restoration takes the shortest time. This mode is applicable to scenarios where the service load is light.
|
- If you select a data volume as the protected object, perform the following operations to set a protection policy:
- Click OK.
- Click Next.
- Set Name and Description of the protected group.
- Name: contains 4 to 32 characters, including letters, digits, hyphens (-), and underscores (_), but cannot start with a hyphen (-).
- Description: contains 0 to 255 characters.
- Click Finish.
- Click OK.
- If the data protection solution is Cross-Cluster Replication for Application Resources, after a protected group is created, the Kubernetes cluster at the standby end automatically creates an application resource that is the same as that at the active end and cannot be deleted.
- After a protected group is created, ensure that the primary and secondary ends of the CDR protection plan are in the Normal state before performing other operations except refreshing and deleting the protected group. Click the protected group, click the Abstract tab, and check whether Protection plan at the active site and Protection plan at the standby site under CDR protection plan status are Normal.
Copyright © Huawei Technologies Co., Ltd.