Say backups should be restored into same Rancher version as the backup #3375

2026-09-25 20:48:11 +00:00 · 2021-07-01 21:52:21 -07:00
parent 53447fd396
commit 60203446ff
6 changed files with 10 additions and 0 deletions
@@ -11,6 +11,8 @@ As of Rancher v2.5, the `rancher-backup` operator is used to backup and restore

 The backup-restore operator needs to be installed in the local cluster, and only backs up the Rancher app. The backup and restore operations are performed only in the local Kubernetes cluster.

+> 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.
+
 - [Changes in Rancher v2.5](#changes-in-rancher-v2-5)
  - [Backup and Restore for Rancher v2.5 installed with Docker](#backup-and-restore-for-rancher-v2-5-installed-with-docker)
 - [How Backups and Restores Work](#how-backups-and-restores-work)
@@ -9,6 +9,8 @@ In this section, you'll learn how to back up Rancher running on any Kubernetes c

 The backup-restore operator needs to be installed in the local cluster, and only backs up the Rancher app. The backup and restore operations are performed only in the local Kubernetes cluster.

+> 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.
+
 ### Prerequisites

 Rancher version must be v2.5.0 and up
@@ -12,6 +12,7 @@ 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.]({{<baseurl>}}/rancher/v2.5/en/backups/migrating-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

@@ -12,6 +12,8 @@ The backup-restore operator needs to be installed in the local cluster, and only

 The Rancher version must be v2.5.0 and up to use this approach of backing up and restoring Rancher. 

+> 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.
+
 - [Changes in Rancher v2.5](#changes-in-rancher-v2-5)
  - [Backup and Restore for Rancher v2.5 installed with Docker](#backup-and-restore-for-rancher-v2-5-installed-with-docker)
  - [Backup and Restore for Rancher installed on a Kubernetes Cluster Before v2.5](#backup-and-restore-for-rancher-installed-on-a-kubernetes-cluster-before-v2-5)
@@ -9,6 +9,8 @@ In this section, you'll learn how to back up Rancher running on any Kubernetes c

 The backup-restore operator needs to be installed in the local cluster, and only backs up the Rancher app. The backup and restore operations are performed only in the local Kubernetes cluster.

+> 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.
+
 ### Prerequisites

 Rancher version must be v2.5.0 and up
@@ -12,6 +12,7 @@ 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.](../migrating-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