Kubernetes Restore
To restore Kubernetes, please go to Data Resilience > Kubernetes page to create a Kubernetes restore job. Please follow the below steps to create the job.
Step 1. Select Restore Point
In the Backup Point dropdown list, select a Kubernetes backup porint to restore. It will be listed on the right box.
By expanding the namespace on the Selected restore point, you can select or exclude the resource to restore, click the Resource details to check the resource information.
Once the resource and namespace have been selected, please click Next.
Step 2. Select Restore Destination
In the Restore to cluster list, please select the target cluster to restore, it can be original cluster or different one.
After you select the cluster, system will list the current Namespace, you can enable Keep Source Namespace ,restores resources to a target namespace with the same name as the original. If you disable it, it will Allows restoring the original namespace data to a target namespace with a different name, facilitating resource isolation or testing without affecting the existing namespace.
On the Target Namespace list, you can restore the data to the other namespace.
Notice
If the target namespace already exists, it may affect existing resources. Proceed with caution.
Click Next to set restore strategy.
Step 3. Configure Restore Strategy
General Strategy
For the job schedule, you can configure the Kubernetes restore job as once-off restore or restore as scheduled.
If you choose Once-off Restore, the restore job will start running right after the job has been created. If you choose Restore As Scheduled, you need to set restore schedules. After this, the job will run as scheduled.
Notice
A "once-off" restore job will run only once and will only restore the selected Instance(s) for one time, after that the job will be moved into history job list as a history record. But a "restore as scheduled" restore job will run and restore the selected Instance(s) regularly according to the time schedules, so, users should be aware of that, a "restore as scheduled" job could cause a lot of duplicated data!
For Throttling Policy, which works the same principle as for backup jobs.
Transmission Strategy
The Encryption, Transmission Network, and Transmission Thread can be configured in the transmission policy.
Encrypted transmission: Backup data is transmitted using SSL encryption, using the RSA algorithm. Enabling transmission encryption encrypts data transferred from the backup source to the backup storage, ensuring data security. Encrypted transmission is off by default.
Transmission Network: Select a backup node network that ensures connectivity with the host. The default is the backup node network.
Transmission Threads: You can set multiple threads for transferring backup data. The default is 3 threads, and you can configure up to 8 threads.
For Advanced Strategy, Snapshot Recovery Preferred will recover using snapshot if the instance has snapshot corresponding to the selected restore point, otherwise recover using the backup data.
Security Strategy
Including Integrity check strategy, select the behavior when an anomalies occur.
Advanced Strategy
Snapshot, enable it will use the local snapshot within the cluster.
On Resource Monitoring, can Skip or Override Resources and set the Release Wordload Node Limits.
Retry: When a job fails due to network, API, or other exceptions, the task can be retried.
Overload Protection: If the node has resource limiation, you could enable the Ignore Node Resource Limits for this job.
Script configuration
The Hook script is disabled by default. If enabled, it supports executing the script before backup, after backup success, and after backup failure. The execution container environment supports execution in all Pods, execution in specified Pods, execution in matching Pods, and execution in self-propelled container images.
Step 4. Review and Confirm Job Settings
After finishing the above settings, you are able to review and confirm all settings here. Click on Submit to confirm creating this job. When the job is created, you will be redirected to the Monitor Center > Jobs page. If this Kubernetes restore job is configured as Once-off Restore, it will start restoring the resource right after the creation of this job.