This message was deleted.
# generala
adamant-kite-43734
05/19/2025, 12:31 PMThis message was deleted.
h
hundreds-evening-84071
05/19/2025, 12:36 PMthis maybe the best method but I will let others with more experience chime in here... https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster
q
quaint-soccer-60531
05/19/2025, 12:47 PMHm, not exactly what I am looking for: I am terminating my node at any random time and have them recreated and setup automatically. With BRO I'd need automation around:
1. triggering a backup before termination (which is never reliable),
2. finding the latest backup to restore when new machine is created and Rancher is deployed in Kubernetes.
w
witty-jelly-95845
05/19/2025, 1:55 PMBRO is the same approach used in https://www.suse.com/c/rancher_blog/migrating-rancher-2-5-0-single-node-docker-install-to-a-ha-kubernetes-k3s-cluster/ albeit for migrating Rancher 2.5.0+
c
creamy-pencil-82913
05/19/2025, 3:50 PMRancher does not store anything on volumes. All Rancher data is stored as resources in the Kubernetes apiserver.
💡 1
creamy-pencil-82913
05/19/2025, 3:51 PMAll you need to do is back up the entire etcd datastore, or use BRO to back up the individual resources.
q
quaint-soccer-60531
05/20/2025, 2:55 PMThanks, that helps.
quaint-soccer-60531
05/20/2025, 2:57 PMMy K3S runs with the embedded Sqlite (to keep things simple and I am aware of its flaws). I'd mount a volume to
/var/lib/rancher/3 Views