view the rest of the comments
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!
What are the use cases? More RAM is nice but could be overkill if you're bottlenecked by CPU, and if this is for running a few simple VMs or as storage then you may not need much of this.
RAID is generally a good thing but don't get complacent, follow the 3-2-1 method. I.e. you might be better off saving the cash and using a backup script to push stuff you really care about to the cloud, and pay for cloud fees vice hw.
To expand on that: Redundant drive setup and backups serve completely different purposes. The only overlap is in case of a single disk failure, where RAID (or similar) may save the data.
Redundancy is all about reducing downtime in case of single hardware failures. Backups not only protect you from data loss in case of multiple simultaneous failures, but also from accidental deletion. Failures that require restoration of data almost always involve downtime. In short: You always need backups (unless it's strictly a local cache, and easily recreatable), but if you want high availability, redundancy may help.
3-2-1-rule for backups, in case you're unfamiliar: 3 copies of important data, on 2 different media, with 1 off-site.
Use case is a few simple VMs, Nextcloud, storage, maybe a minecraft server and probably something like Jellyfin later on.
This will be fine. But assume you'll want to swap out the hard drives in the future for more, larger, NAS appropriate disks.
If you're as paranoid as me about data integrity, SAS drives on a host adapter card in "Initiator Target" (IT) mode with write-cache on the disks disabled is the safest. It will degrade performance when writing many small files concurrently, but not as badly as with SATA drives (that's for spinning disks, of course, not SSD). With a good error-correcting redundant system such as ZFS you can probably get away with enabled write cache in most cases. Until you can't.
What's the storage capacity on this motherboard? I know with their office PCs, you only get 2 SATA ports and typically only a single PCIE slot so you're forced to choose between a GPU or LSI SAS card. I have a huge media library so this was one of my primary concerns when I specced mine out years ago. Also consider 3.5" drive capacity. Are you limited to just two HDDs?
I'm currently limited to 1 2.5" drive and 1 m.2 ssd. The 2.5" ssd slot was filled when I bought it. The m.2 slot is still empty.