Ask HN: How do you backup before an upgrade (Linux)?

https://news.ycombinator.com/item?id=31239714

by curvilinear_m • 4 years ago

9 9 4 years ago

news.ycombinator.com

Which software do you use as an emergency backup right before doing a risky operation (such as an upgrade) ?

I am going through the pain of restoring my files after a bad error on my part : I used déjà-dup (the default with Ubuntu 20.04.4) to back up the default home folder.

Unfortunately, my update broke everything and I lost access to my session. I hoped that deja-dup would allow me to restore from the live CD, but found out that I need the same computer name and username, so I had to reinstall everything before being able to restore.

This seems inconvenient, and I don't understand why it is the default behavior.

What are you using to do your backups ? Have you felt the same frustration I'm facing ?

themodelplumber• 4 years ago

sudo rsync -vax --delete --ignore-errors --xattrs --acls / /media/destination/partition/

This is run periodically via your favorite method. You can then boot off the backup destination drive later if needed (GRUB picks it up when plugged in). This seems to work fine for me.

BTW generally "broke everything" ought to be listed out, clarified, etc. so you can understand or document your system better. The notes you keep about it can help future upgrades complete with fewer issues.

smoldesu• 4 years ago

This seems inconvenient, and I don't understand why it is the default behavior.

Nobody made the conscious decision to kneecap you here: it's simply dangerous to treat one computer's hardware configurations the same as another. Backing up your home folder is your best bet, as it's relatively safe to "restore" after an install. It's up to you to have a bootstrapping script ready to get your system to the same place it was before it was borked.

This is one of the things NixOS would solve quite well, but unfortunately the software just isn't quite there yet, in my opinion. Your Nix install has two configuration files: a software config and a hardware one. Your software configuration is portable, you can use it to define things like users, user configurations, permission structures, desired global applications, themes, groups, system config and more. Your hardware configuration file is specific to the machine you're running, and is auto-generated when you install a system. This separation makes it really easy to "carry around your system" as a 10kb text file. The tough part is that it doesn't work very well with most desktop environments, and it's something of a pain in the ass to set up. One day I hope we get there though, because it really would be a best-in-class solution.

LinuxBender• 4 years ago

I can describe my method that has worked well for a few decades but it might not be for everyone.

Before planning a backup I first ensure all the files I care about are isolated into unique directories not shared by anything I don't care about. e.g. /data/something_unique /opt/something_unique /home/username/something_unique and so on. something_unique just being a unique directory that contains anything or everything I care about. One could also define other shared directories in rsnapshot like /home/username/.config or the entire home directory if you have the disk space for it.

I then have rsnapshot installed and it will be a local snapshot of files I consider important enough that I want a few versions of. RSnapshot is just a perl script that uses hardlinks to reduce disk space usage of duplicate files. Rsnapshot is executed in crond. I rsync that snapshot over to a NAS. Rsync is also called by crond. If files are very important I will also copy them to a portable NAS and put it in my vehicle.

Anything not defined in /etc/rsnapshot.conf will be files I do not care about and will be treated as ephemeral just like the rest of the OS.

If one does not have their OS set up to be ephemeral (cattle vs kittens) then another lesser-secure option might be to keep your important files in a unique LVM volume and use lvchange to set that volume read-only to reduce the risk of the OS upgrade from touching it.

[1] https://rsnapshot.org/

firebaze• 4 years ago

I never dist-upgrade. i just install fresh, install all software I am using right now, have a backup partition to copy data from if required (which gets deleted when the next dist-upgrade arrives) and enjoy the loss of old stuff. This never took more than two days of tweaking and occurs at ~2 year intervals. Technically, the potential uptime is better that most SaaS offerings.

ohiovr• 4 years ago

Timeshift and storing the system backup folder in an off system portable hard drive has worked for me with system backups. I've restored timeshift backups from bare installs or live disks without issue. For home backups I just use rsync. I keep a few backup scripts in my .local/bin folder so they can be easily accessible from any directory.

Here is an example of a backup script I use: https://pastebin.com/16MPxby0

this script will show me what files have changed. So if a huge number of files have changed I can perceive that as a potential crypt attack. Or some other bonehead thing I did..

This script will DELETE files on the backup that no longer exist in my home directory. I do that so I don't have a bunch of zombie files laying around that are no longer needed.

runnerup• 4 years ago

Veeam Endpoint Backup is free and works great for me. I use it for both windows and Linux and I’ve been able to restore fine after botched upgrades or unwanted NVidia driver updates.

doubled112• 4 years ago

I just consider my machines disposable. It has saved me a ton of heartache over the years.

I have a git repo with some dotfiles and setup scripts - dotbot configures my user, Ansible configures my system.

Most files go in a self hosted Nextcloud sync folder. If it is larger it goes on a file share.

Anything else is simply forgotten. I can rebuilt in ~ 5 minutes after a clean install. I can keep multiple machines in sync like this as well.

synicalx• 4 years ago

I try and make my workstation... I guess you'd say "stateless"?

- Nothing important stored "on" the machine itself, I put it in one or more cloud storage options, git, password manager etc. Important documents like photos and legal stuff I keep in two cloud storage services + REALLY important stuff gets burned onto a DVD or BluRay that I lock up somewhere.

- I have a.... rather long "sudo apt install blah" script that has every package I've needed or wanted to install. Every time I install something new I just add another entry to that script. Although I have to say, this is looking a bit ridiculous now at 160+ lines most of which are just individual packages.

- I have another script to clone in my dot file/config file repo and move all of those into position.

- I don't have anything to setup my user account, but that's only a 5 second job so it's probably not worth the time.

I generally find actual backups are more hassle than they're worth for this kind of thing. The old fashioned sysadmin in me knows that no backup actually exists until you test it - and I really don't feel like testing my own backups all the time.

croh• 4 years ago

separate config, codebase, media files and other stuff

- config using dot files (may be some remote git repo)

- projects in git repo

- media and other stuff in different drive

Everytime you make changes in config or projects, push them to remote repo immediately. This way, you will be always ready to upgrade.

Ask HN: How do you backup before an upgrade (Linux)?

Related Stories