this post was submitted on 27 Mar 2024
634 points (93.0% liked)
linuxmemes
20777 readers
273 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Bloat multiplies when you have to back it up.
You realize you don't have to backup the actual "bloated" programs. Just maybe their configs and any files those programs generate that you'd like to keep, right?
I remember what my idea of making backups was when I was a wee grasshopper.
Making a backup of the whole OS instead of just the configs and user files.
I have come a long way since then.
That's committing the cardinal sin of cherrypicking your backup contents. You may end up forgetting to include things that you didn't know you needed until restore time and you're creating a backup that is cumbersome to restore. Always remember: you should really be creating a restore strategy rather than a backup strategy.
As a general rule I always backup the filesystem wholesale, optionally exclude things of which I'm 100% sure that I don't need it, and keep multiple copies (daylies and monthlies going some time back) so I always have a complete reference of what my system looked like at a particular point in time, and if push comes to shove I can always revert to a previous state by wiping the filesystem and copying one of the backups to it.