

AWS is the modern IBM.
That’s basically why we use it at work. I hate it, but that’s how things are.
Mama told me not to come.
She said, that ain’t the way to have fun.


AWS is the modern IBM.
That’s basically why we use it at work. I hate it, but that’s how things are.


Absolutely this. We are based out of one region, but also have a second region as a quick disaster recovery option, and we have people 24/7 who can manage the DR process. We’re not big enough to have live redundancy, but big enough that an hour of downtime would be a big deal.


Yeah, the long s is what i was talking about.


That flow chart is overwhelming.
How about, just use what you want? If it doesn’t work the way you like, try something else. Nvidia works fine on pretty much any distro, find a PPA or repo or something and it’s largely OK.
How about:


Bleating.


Thanks, I hate it.
BTW, you missed the funky S thing in old English for “f”.


Yes. I’d rather have small breakage every so often on small updates where it’s easy to tell what happened than large breakage on a release upgrade.
Eh, I’ve broken laptop ethernet ports by accidentally plugging in passive POE into it. It happens if you’re an unfortunate soul who needs to debug those devices.
Active POE is fine. Passive POE is an accident waiting to happen when someone inevitably plugs it into the wrong device.


This is the self-hosted community, so that’s the context I was assuming.


My point is, how often do you actually need to restore from backup? If it’s frequent, consider a dedicated tool for whatever that thing is. If it’s infrequent, it’ll probably easier to just learn how to do it every five years or whatever.
If you like borg/restic/etc, by all means, use it.
My point is that most people probably don’t need it. Snapshots are something you set up once, and you should probably use them even if you’re using something like borg for any files that aren’t covered (e.g. config files on the server). Rsync is also something you set up once, and checking it is the same as any other service.


Sure, but you should probably be aware of what it is and what it does. It’s incredibly common and will be referenced in a ton of documentation for Linux server stuff.


I use rsync for all kinda of things:
I only really use scp if the system doesn’t already have rsync.


Yes, async copies files to the remote server, the remote server takes regular snapshots.
Why not just use a backup utility instead?
What is that utility providing that snapshots + rsync doesn’t. If rsync + snapshots is sufficient, why overcomplicate it with a backup utility?


Why not just cp?


And not waste time copying duplicate data. And for the typical home user, it’s probably mo slower than other options.


Yup, just configure a snapshot policy and you can recover deleted and modified files going back as long as you choose. And it is probably more space efficient than both/restic too.


Blogs can have ads.
Are you an IT contractor or something?