Rolling Back to Rancher v2.5.0+

Rancher has to be started with the lower/previous version after a rollback.

A restore is performed by creating a Restore custom resource.

  1. In the Cluster Explorer, go to the dropdown menu in the upper left corner and click Rancher Backups.
  2. Click Restore.
  3. Create the Restore with the form, or with YAML. For creating the Restore resource using form, refer to the and to the examples.

  4. For help configuring the Restore, refer to the and to the examples.

  5. Click Create.

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:

  1. Custom Resource Definitions (CRDs)
  2. Namespaced resources

Roll back to the previous Rancher version

Rancher can be rolled back using the Rancher UI.

  1. In the Rancher UI, go to the local cluster.
  2. Go to the System project.
  3. Edit Rancher deployment and modify image to version that you are rolling back to.
  4. Save changes made.

Rolling Back to Rancher v2.2-v2.4+

To roll back to Rancher before v2.5, follow the procedure detailed here: Restoring a snapshot of the Rancher server cluster will revert Rancher to the version and state at the time of the snapshot.

For information on how to roll back Rancher installed with Docker, refer to this page.

Rolling Back to Rancher v2.0-v2.1

Rolling back to Rancher v2.0-v2.1 is no longer supported. The instructions for rolling back to these versions are preserved here and are intended to be used only in cases where upgrading to Rancher v2.2+ is not feasible.