Discuss
So i’ve reinstalled my server on new hardware from a backup:
- install yunohost on the new hardware (i did from ISO)
- after post-install rsync’d the backup (the .tar) onto the new install at the right place that being
/home/yunohost.backup/archivesand once its visible as option on the server i selected it.
Rsync (remote sync) was only on my laptop where i had downloaded a backup the command was pretty much looking like this
sudo rsync /where-the-backup-is-on-current-machine/backup.tar ynh_user@server-ip:/home/yunohost.backup/archives
- then i did diagnostic, fixed the ports, dns records like its a classic install
and then i took a lil pause to fix my user groups, because imported everything (including users), i couldn’t even access some folders. That part wasnt fun especially with homonyms users.
- After that i hit update.
i still had the kernel update to do even from new install after all that jazz
and after that, few apps were not updating at all. While i didn’t want to troubleshoot them, assuming they lacked some requirement (Piped, Searxng, Tiddlywiki) a simple unistall/reinstall was ok (be sure to have backup your preferences/files from those).
And after that i was good to go, i guess.
- Once i hit the all green lights in diagnostic at the very end, i did a proper backup.
it was fairly easy but was done with the documentation open just in case. And except for the installation follow-up (i dont reinstall ynh a lot) i didn’t consult it. Except rsync (which could be replaced by something else like ftp with elevated rights) i didnt used command line, and felt nice to see that’s a possibility for people afraid of CLI.
And at first i just wanted to slap my old drive in some newer hardware. Glad i didn’t.