diff --git a/content/rancher/v2.5/en/backups/migrating-rancher/_index.md b/content/rancher/v2.5/en/backups/migrating-rancher/_index.md
index ec5820097a4..1fc70aee590 100644
--- a/content/rancher/v2.5/en/backups/migrating-rancher/_index.md
+++ b/content/rancher/v2.5/en/backups/migrating-rancher/_index.md
@@ -21,11 +21,12 @@ Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes
 - [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
 
 ### 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 update
-helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace
-helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system
+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 --version $CHART_VERSION
 ```
 
 ### 2. Restore from backup using a Restore custom resource
diff --git a/content/rancher/v2.5/en/backups/restoring-rancher/_index.md b/content/rancher/v2.5/en/backups/restoring-rancher/_index.md
index 2791485efed..d6ab3d801e1 100644
--- a/content/rancher/v2.5/en/backups/restoring-rancher/_index.md
+++ b/content/rancher/v2.5/en/backups/restoring-rancher/_index.md
@@ -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
-
+```
 
 ### Cleanup
 
-If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
\ No newline at end of file
+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)
diff --git a/content/rancher/v2.6/en/backups/migrating-rancher/_index.md b/content/rancher/v2.6/en/backups/migrating-rancher/_index.md
index ff0e8c08f3c..0154b6b1bd7 100644
--- a/content/rancher/v2.6/en/backups/migrating-rancher/_index.md
+++ b/content/rancher/v2.6/en/backups/migrating-rancher/_index.md
@@ -19,11 +19,12 @@ Rancher can be installed on any Kubernetes cluster, including hosted Kubernetes
 - [K3s Kubernetes installation docs]({{<baseurl>}}/k3s/latest/en/installation/)
 
 ### 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 update
-helm install rancher-backup-crd rancher-charts/rancher-backup-crd -n cattle-resources-system --create-namespace
-helm install rancher-backup rancher-charts/rancher-backup -n cattle-resources-system
+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 --version $CHART_VERSION
 ```
 
 ### 2. Restore from backup using a Restore custom resource
diff --git a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md
index f7ed081c124..0d9925329a1 100644
--- a/content/rancher/v2.6/en/backups/restoring-rancher/_index.md
+++ b/content/rancher/v2.6/en/backups/restoring-rancher/_index.md
@@ -57,4 +57,13 @@ kubectl logs -n cattle-resources-system -l app.kubernetes.io/name=rancher-backup
 
 ### Cleanup
 
-If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
\ No newline at end of file
+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)