
A pet subject of mine.
Firstly - sit down and consider what you need to backup.
- Tier 1 - unique data. Stuff you created that doesn’t exist elsewhere.
- Tier 2 - Stuff that would take a few days to repeat. Local configs, etc.
- Tier 3 - Stuff you can just download again. (Steam library, media etc)
Don’t backup Tier 3. I’m betting the size of data you need to back up shrinks a lot.
Secondly - automate it. If there’s anything manual, then you’ll eventually stop doing it. Automate, automate, automate - and throw in some manual or automated checks of the backups to verify they’re actually usable.
Thirdly - airgap it if you can, and if there’s much Tier 1 data. Offline disks. This gives you some protection against ransomware. Consider the risks and how to protect yourself. Obviously media failure, accidental deletion and ransomware, but also consider theft and fire. Do you really want your backups in the same location? Do they need encryption?
I wrote quite a long blog on the subject if you’re interested in more.
You’re welcome.
Yes, you can create a list of files that takes little space, in linux that’s just “tree” to produce a list of directories and files (I don’t know about Windows, sorry)
But only you can answer what you need to back up. If you judge the effort to re-download this data is more than the effort of backing it up (especially if you’re on a slow link), then backing it up makes more sense. Everyone has their own appetite for risk and their own shape of what they can spend in both time and money in sorting this. The important thing is that you’re thinking about it before you need it, that’s good!