Linux

52030 readers

1134 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 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How do you backup? (lemm.ee)

submitted 10 hours ago by Zenlix@lemm.ee to c/linux@lemmy.ml

38 comments fedilink hide all child comments

I recently implemented a backup workflow for me. I heavily use restic for desktop backup and for a full system backup of my local server. It works amazingly good. I always have a versioned backup without a lot of redundant data. It is fast, encrypted and compressed.

But I wondered, how do you guys do your backups? What software do you use? How often do you do them and what workflow do you use for it?

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

[–] ferric_carcinization@lemmy.ml 1 points 8 hours ago

I haven't used either, much less benchmarked them, but the performance differences should be negligible due to the IO-bound nature of the work. Even with compression & encryption, it's likely that either the language is fast enough or that it's implemented in a fast language.

Still, I wouldn't call the choice of language insignificant. IIRC, Go is strongly typed while Python isn't. Even if type errors are rare, I would rather trust software written to be immune to them. (Same with memory safety, but both languages use garbage collection, so it's not really relevant in this case.)

Of course, I could be wrong. Maybe one of the tools cannot fully utilize the network or disk. Perhaps one of them uses multithreaded compression while the other doesn't. Architectual decisions made early on could also cause performance problems. I'd just rather not assume any noticeable performance differences caused by the programming language used in this case.

Sorry for the rant, this ended up being a little longer than I expected.

Also, Rust rewrite when? :P