Skip to content
Discussion options

You must be logged in to vote

Just copy the db dir over, and specify the token in the config on the new node. That's it. Do NOT copy anything else, or if you must, use a tool like rsync that can retain file modification times.

If you had previously started K3s on the node you are restoring to, you should clean that up first (just rm -rf /var/lib/rancher/k3s if you didn't have anything in there you care about) - or it will complain that you have other, newer files present from the new cluster you created when you started it.

With regards to stopping all the pods - the pods are not the cluster. If you want to cleanly stop your workloads, you should drain the node first, then run the killall script to terminate any strag…

Replies: 3 comments 5 replies

Comment options

You must be logged in to vote
1 reply
@brandond
Comment options

brandond Nov 6, 2026
Collaborator

Answer selected by andrewbogott
Comment options

You must be logged in to vote
3 replies
@brandond
Comment options

brandond Nov 6, 2026
Collaborator

@andrewbogott
Comment options

@brandond
Comment options

brandond Nov 6, 2026
Collaborator

This comment was marked as low quality.

@brandond
Comment options

brandond Nov 9, 2026
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants