Linux

57056 readers

682 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Why do atomic distros not contain good backup tooling by default? (lemmy.ml)

submitted 1 week ago by OhVenus_Baby@lemmy.ml to c/linux@lemmy.ml

17 comments fedilink hide all child comments

I have tested a lot of atomic and traditional distributions lately. Tons of desktop environments strictly for fun and branching out. Having a 1 2 3 backup strategy and not just having it in place, but being able to restore your backup in a timely manner to keep continuity is paramount. You can list infinite reasons why.

Why do atomic distros which are supposed to me more stable, superior to some degree immutable environments lack good backup options? You can hack things together and there are somewhat installable tools. Like timeshift or etc etc. But it seems they place a lot more emphasis on rolling back poor updates in the event than total system backups.

By default it you should have true backups then layer in rollbacks. Not the other way around. Am I missing something?

you are viewing a single comment's thread
view the rest of the comments

[–] HelloRoot@lemy.lol 1 points 1 week ago* (last edited 1 week ago)

I install or configure something every week.

In addition to doing the config, I'd have to edit a script as well, which seems like more hassle. At this point, why not go for nixOS and have just the latter part of the hassle without having to also edit config files in / ?

Instead, I run the backup command after I change something. When I want to restore, I can mount any of the last 20 backups from the borg repo and either manually revert a file or use rsync to mass overwrite.

I was thinking of using btrfs send, which would probably be even better for the purposes of recovering from disk failure, but borg file based backup takes way less space and works well so far. And I don't have the extra effort of a declarative os or setup scripts.

Also works offline as long as I am with my NAS unlike a script that installs a list of packages from the repos.