Nice to see you back here on a regular basis @Catra. Try not to let the crusty old guys here on the forum rub you the wrong way. We're mostly all harmless, but we were written in COBOL (or some other totally obsolete programming language), and there's no hope of changing the code at this late stage in the game.
Wadumeeeeeeen?
I store all my backups in floppy disks and put them with a magnet on the fridge
What I do for my private data:
Backup on a 5TB Drive split into 1TB partitions for different type of backups (Linux/Windows/Phone)
Sync this Data to a remote endpoint (little add - in my case Hetzner Storage Box since 5TB for 12.97€/m is a steal)
Once a Year: Disaster Recovery Day: A Backup is only good if it works. I am testing my backups and strategies once a year against a shot gun to the disk approach. Nuke all Data and then restore.
@Catra
Yea /dev/random is better for real format but for a fast system nuke /dev/null is faster
● Backup #1: Back-out
Snapshots like Snapper does. Protects from bungles and mistakes that hobble your system without destroying it.
● Backup #2: Oh, wasn't that… oh no.
Data/information written to a medium that can sit on a shelf. Best if older versions are kept around. Protects the point of having computers in the first place, doing stuff.
● Backup #3: Outa sight!
Data/information and system images kept somewhere other than the same place the computer is. As it allows for recovery of everything (once the hardware is fixed or replaced) it protects against fires, tornadoes, missile strikes, kids with jam and toast, and visits from M.O.D.O.K.