mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-27 05:28:22 +00:00
Merge pull request #3597 from jiaqiluo/update-backup-docs
update the docs for rancher-backup
This commit is contained in:
@@ -21,11 +21,12 @@ Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes
|
|||||||
- [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
|
- [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
|
||||||
|
|
||||||
### 1. Install the rancher-backup Helm chart
|
### 1. Install the rancher-backup Helm chart
|
||||||
|
Install version 1.x.x of the rancher-backup chart.
|
||||||
```
|
```
|
||||||
helm repo add rancher-charts https://charts.rancher.io
|
helm repo add rancher-charts https://charts.rancher.io
|
||||||
helm repo update
|
helm repo update
|
||||||
helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace
|
helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace --version $CHART_VERSION
|
||||||
helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system
|
helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system --version $CHART_VERSION
|
||||||
```
|
```
|
||||||
|
|
||||||
### 2. Restore from backup using a Restore custom resource
|
### 2. Restore from backup using a Restore custom resource
|
||||||
|
|||||||
@@ -56,8 +56,17 @@ To check how the restore is progressing, you can check the logs of the operator.
|
|||||||
|
|
||||||
```
|
```
|
||||||
kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup -f
|
kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup -f
|
||||||
|
```
|
||||||
|
|
||||||
### Cleanup
|
### Cleanup
|
||||||
|
|
||||||
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
|
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
|
||||||
|
|
||||||
|
### Known Issues
|
||||||
|
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](https://github.com/rancher/rancher/issues/35050#issuecomment-937968556)
|
||||||
|
|||||||
@@ -19,11 +19,12 @@ Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes
|
|||||||
- [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
|
- [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
|
||||||
|
|
||||||
### 1. Install the rancher-backup Helm chart
|
### 1. Install the rancher-backup Helm chart
|
||||||
|
Install version 2.x.x of the rancher-backup chart.
|
||||||
```
|
```
|
||||||
helm repo add rancher-charts https://charts.rancher.io
|
helm repo add rancher-charts https://charts.rancher.io
|
||||||
helm repo update
|
helm repo update
|
||||||
helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace
|
helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace --version $CHART_VERSION
|
||||||
helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system
|
helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system --version $CHART_VERSION
|
||||||
```
|
```
|
||||||
|
|
||||||
### 2. Restore from backup using a Restore custom resource
|
### 2. Restore from backup using a Restore custom resource
|
||||||
|
|||||||
@@ -58,3 +58,12 @@ kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup
|
|||||||
### Cleanup
|
### Cleanup
|
||||||
|
|
||||||
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
|
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
|
||||||
|
|
||||||
|
### Known Issues
|
||||||
|
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](https://github.com/rancher/rancher/issues/35050#issuecomment-937968556)
|
||||||
|
|||||||
Reference in New Issue
Block a user