In scenarios where application resources are backed up locally or across storage devices, if service data at the production end is lost or damaged, you can use the backups created during protection to restore the backup.
Prerequisites
- At least one recovery plan has been created in the system.
- The recovery plan is in the Ready, Rollback failed, or Rollback completed state.
- The backup of the protected group corresponding to the recovery plan is available.
- If the Kubernetes cluster information at the production end changes, manually refresh the device information. For details about the change items and operations, see Updating a Protected Group.
- Currently, resources with labels cannot be backed up to the current namespace. If you want to back up resources with tags to the current namespace, delete the original resources with tags from the namespace.
- By default, the maximum number of pods supported by a single Kubernetes node is 110. You can change the maximum number by modifying the maxPods configuration item in the /var/lib/kubelet/config.yaml configuration file. Before restoring the backup, ensure that the total number of pods does not exceed the upper limit after the restoration.
Context
If backups, currently protected objects, and used storage resources are changed, risks may arise during backup recovery. For details about the backup recovery scenarios and handling measures, see Copy-based Recovery and Risk Handling Measures.
Procedure
- Log in to eReplication in the DR Center
- Use the backups created during protection to restore the backup.
- On the menu bar, choose Utilization > Data Restore.
- Select the desired recovery plan. In the Operation area, choose More > Backup and Restore.
- Select the peer namespace of the recovery plan, and perform advanced settings and backup selection as required. Table 1 describes the parameters.
Table 1 Basic backup and restoration parametersParameter
|
Description
|
Setting
|
Namespace
|
Select the target namespace for backup and restoration.
|
Select a value from the drop-down list box.
NOTE: - If a backup is restored to a new namespace, you need to create a protected group to protect the resources generated during the restoration. The original protected group is no longer used. You need to manually delete the original protected group.
- In the cross-storage backup scenario, the original protected group becomes invalid after data is restored to the current namespace. You need to manually delete the original protected group. To protect the resources generated during the restoration, you need to create a protected group.
|
Resource Prefix
|
Prefix of the resource name during backup and restoration. This parameter is optional.
|
The value can contain only lowercase letters and hyphens (-) and must start with a lowercase letter. The length cannot exceed 31 characters.
|
Post-hook
|
Select the HOOK to be executed after the backup and restoration. This parameter is optional.
|
Set this parameter as required.
|
Reserve Original IP Address
|
Whether to retain the original IP address after backup and restoration.
|
This option is not selected by default.
|
Retain Original Port
|
Whether to retain the original port after backup and restoration.
|
This option is not selected by default.
|
Sync Rate
|
Restoration speed during backup and restoration.
|
- 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.
|
Time Range
|
Specifies the point in time of the backup to be restored.
After you select a point in time, available backups are automatically displayed. If no backup is displayed, no backup is available.
|
Including the start date and end date, which can be accurate to seconds.
|
- Click OK to start backup and restoration.
- After the backup is restored, check the application startup and data consistency at the DR site.
After the backup restoration is complete, check whether the application and data are normal. If the application or data is abnormal, contact Huawei technical support.
Operation Results
After the backup restoration is complete, the status of the protected group is automatically restored to normal.
Copyright © Huawei Technologies Co., Ltd.