A restore is performed by creating a Restore custom resource.
- Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to migrate rancher.
- While restoring rancher on the same setup, the operator will scale down the rancher deployment when restore starts, and it will scale back up the deployment once restore completes. So Rancher will be unavailable during the restore.
- When restoring a backup into a new Rancher setup, the version of the new setup should be the same as the one where the backup is made.
Create the Restore Custom Resource
In the Cluster Explorer, go to the dropdown menu in the upper left corner and click Rancher Backups.
Create the Restore with the form, or with YAML. For creating the Restore resource using form, refer to the configuration reference and to the examples.
For using the YAML editor, we can click Create > Create from YAML. Enter the Restore YAML.
For help configuring the Restore, refer to the configuration reference and to the examples.
Result: The rancher-operator scales down the rancher deployment during restore, and scales it back up once the restore completes. The resources are restored in this order:
- Custom Resource Definitions (CRDs)
- Cluster-scoped resources
- Namespaced resources
To check how the restore is progressing, you can check the logs of the operator. Run this command to follow the logs:
kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup -f
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
In some cases, after restoring the backup, Rancher logs will show errors similar to the following:
2021/10/05 21:30:45 [ERROR] error syncing 'c-89d82/m-4067aa68dd78': handler rke-worker-upgrader: clusters.management.cattle.io "c-89d82" not found, requeuing
This happens because one of the resources that was just restored has finalizers but the related resources have been deleted so the handler cannot find it.
To eliminate the errors, we need to find and delete the resource that causes the error. See more information here