I just nuked all my backups (going from gentoo to windows 10), and it was completely avoidable. >Open encrypted container to copy backup files to ventoy USB (on hd, to copy later) >forget to actually copy container to USB >maintain seperate backups on HDD, this usb was backup #2... no prob....
>windows 10 flips drive numbers, installs over backup hdd instead of sdd >backup #1 gone >backup #2 gone that's it bros
>protonmail not linked to phone for security, no recovery >nothing on android because my security >all passwords completely unknowable, offline password manager.
I was saved by veracrypt being able to recover the hdd miraculously despite windows dropping an entire installation on top of it. I lost a couple of files and that was it. It could have been much much worse.
This all could have been avoided with policy. How do you manage this? I'm thinking the only way is to literally print this out in a a handbook like I was being forced to do this at work in an emergency and force myself to abide to it.
Think this was also a problem of not having offline backups. Either way; a warning anons; back up your data
Why the fuck did you install windows with more than one drive connected? Laziness?
Cameron Wilson
Nice blog, but I only give a shit about the software. How does Restic compare just putting everything in a Veracrypt volume which itself is on removable media and using Rsync to move everything over?
Lucas Garcia
>How do you manage this? Backing up to networked locations.
Christopher Flores
>Why the fuck did you install windows with more than one drive connected? funny you say that as soon as I realized what I did I disconnected the HDD lol. it was straight laziness. All the software in the world won't save you from yourself.
>How does Restic compare just putting everything in a Veracrypt volume which itself is on removable media and using Rsync to move everything over? Restic is incremental backup not a straight mirror. I made that the OP pic because I'm also question able about it.
I lost one of my password manager databases because it got corrupted (overwritten with windows). The veracrypt drive it was inside though was recoverable despite this. Obviously some file formats are more redudant than others. I wouldn't trust a straight restic backup either.
Do you mirror your incrementals? One fuck up and those 6 years of incremental backups are gone; it's still just one copy, but then how do you keep a fucked database from propagating? Incremental backups of incremental backups?
I need to unfuck this so it never happens again. I'm thinking restic for incrementals and then offline straight mirrors once a month/week or something; with a full copy inside of restic and an additional copy of the data (on the same drive) just as regular files (the latest version)
Joshua Cox
use something like rsync.net for encrypted offsite backups easy to push there with borg or restic and they keep snapshots themselves, so if you accidentally do fuck up everything you can still recover
Thomas Garcia
>follow link to rsync.net >see mention of git-annex >google git-annex >sounds great, gonna use it This is why I come back.
Jack Hernandez
i take it though the base strategy should be multiple mirrors of incremental backups; but really what you need is multiple mirrors of incremental backups of incremental backups (backing up the restic db with restic) to safeguard against the database itself being fucked.
Lucas Myers
>Windows you get what you fucking deserve
Logan Roberts
If restic 1 gets fucked, how do you stop propagation (your words) to restic 2 and then the mirrors?
