https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
c
that person was trying to restore to a different version than the backup was taken on. Is that also what you are doing?
Follow the instructions from this page when:
• The running Rancher instance is at the same version as when the backup was made.
• The upstream (local) cluster is the same as where the backup was made.
Are both of those things true for your environment?
a
I took it as only one has to be true, apologies then. I am trying to restore to a past version, is that not possible then?
as in my current version is 2.8.5 and my backup file is from 2.7.7
c
no. you should restore to the same version, and then upgrade.
especially when you’re talking about completely different versions, not just different patch releases
a
c
Rancher has to be started with the lower/previous version after a rollback.
which document are you following? the one linked from the issue you previously mentioned, or this document?
a
I'm following the rancher document, trying to better understand what a rollback procedure would look like from a failed rancher upgrade.
c
which rancher doc? The person who created the issue you linked is following a completely different set of steps, from https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher
so I assumed you were also following that document. now you’ve mentioned you’re doing something else completely.
a
Both seem to suggest to start by creating the restore CRD, which is as far as I have gotten before encountering that error above
I ended up running a helm rollback on the rancher helm chart and then re-running the restore, now it's back to the previous version.
4 Views
Open in Slack
PreviousNext
Powered by