Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
My new motherboard actually has a RAID controller for the M.2 slots. I know people frown on hardware raid, but given it's the boot drive, it might just be easiest to count on it for daily operation and backup to the software RAID/something else every night.
Make sure, if you use hardware RAID, you know what happens if your controller dies.
Is the data in a format you can access it easily? Do you need a specific raid controller to be able to read it in the future? How are you going to get a new controller if you need it?
That's a big reason why people nudge you to software raid: if you're using md and doing a mirror, then that'll work on any damn drive controller on earth that linux can talk to, and you don't need to worry about how you're getting your data back if a controller dies on you.
So I’m kind of on the fence about this. I ran a raid boot disk system like 12 years ago, and it was a total pain in the ass. Just getting it to boot after an update was a bit hit or miss.
Right now I’m leaning towards hardware nvme raid for the boot disk just to obfuscate that for Linux, but still treat it delicately and back up anything of importance nightly to a proper software raid and ultimately to another medium as well.
Oh I wasn't saying to not, I was just saying make sure you're aware of what recovery entails since a lot of raid controllers don't just write bytes to the disk and can, if you don't have spares, make recovery a pain in the ass.
I'm using MD raid for my boot SSDs and yeah, the install was a complete pain in the ass since the debian installer will let you, but it's very much in the linux sense of 'let you': you can do it, but you're figuring it out on your own.
Where I've landed now is
A) just migrate everything over so I can continue working. B) Migrate my mdadm to ZFS C) Buy another NVME down the road and configure it with the onboard RAID controller to prevent any sudden system downtime. D) Configure nightly backups of anything of import on the NVME RAID to the ZFS pool. E) Configure nightly snapshots of the ZFS pool to another webserver on-site. F) rsync the ZFS pool to cold storage every six months and store off-site.