Executing a Protected Group

Prerequisites

• At least one protected group has been created in the system.
• The status of the protected group is Normal.
• If the Kubernetes cluster or application resource information changes, manually refresh the protected group. For details about the change items and operations, see Updating a Protected Group.

If the data protection solution is data volume cross-cluster active-active (AA) or data volume cross-cluster active-active (AP), protected groups cannot be executed.

Context

• Protected groups in the Executing, Disabled, Locked, or Invalid state cannot be executed.
• If a periodic scheduling task is started when the protected group is in the Executing state, the task is postponed to the next periodic scheduling.
• The interval for executing a protection group must be greater than or equal to 4 minutes.
• If a schedule is configured in the protection policy of the protected group, the protected group is automatically executed according to the schedule. If you need to manually execute a protected group, perform the following operations:
• If eReplication has multiple periodically scheduled container protected groups, the execution time of periodically scheduled tasks in the container cluster environment is not affected. However, the historical execution time of periodically executed tasks in the eReplication protected group is minute-level offset. For details, see Function Management > Backup Job Management > Deleting a Backup Job and Function Management > Protection Job Management > Deleting a Protection Job in the eSDK Enterprise Storage Plugins 2.6.0 User Guide (CDR) of the latest version to clear completed backup and protection jobs in the container cluster to reduce the impact.

Procedure

1. On the menu bar, choose Protection.
2. Select the desired protected group and click Execute in the Operation area.
   • If the protection policy is local storage backup for application resources or cross-storage backup for application resources, select the site where the protected group is executed. This operation will generate a local copy for the protected objects at the selected site.
   • If the protection policy is cross-cluster replication for application resources and cross-cluster replication for data volumes, select the local site and DR site where the protected group is executed. This operation will synchronize data from the local site to the DR site.

3. Click OK to deliver the command.

   After the protected group starts to be executed, click the protected group. On the Execution Records tab page, you can view the execution result and details of the protected group.

   

   If the protected group remains in the Executing state, click in the upper right corner of the page to refresh the page.

4. Click OK on the execution result page.

Operation Results

After the protected group is executed, a historical record is generated on the Execution Records tab page. The eReplication system clears the execution history of each protected group at 00:00 a.m. every day. Only the latest 1000 records are retained for each protected group. If the number of historical records exceeds 1000, the system deletes the earliest records.