this post was submitted on 31 Jan 2026
44 points (100.0% liked)
Selfhosted
59897 readers
520 users here now
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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Both dhcpd and bind support failover.
If you want to have failover storage you might want to look into beegfs, as storage targets can be mirrored across hosts.
Source: Using all of the above at work. I've had motherboards die on me without causing downtime.
Not heard of BeeGFS, had a quick look on the Arch wiki... looks quite involved...
But, ok, at least I know that the DHCP part can be dealt with - thanks.
I use beegfs at work for the redundancy and clustering aspect. 1.8PB of storage with 100% redundancy.
While it supports a lot and CAN be quite involved, a very basic setup is in fact pretty simple:
A filesystem on a machine is a storage target.
A machine with storage targets is a storage node. (beegfs-storage)
A management server (beegfs-mgmtd) connects these together into a filesystem.
Any machine runs beegfs-client to mount this filesystem.
One machine needs to run beegfs_meta for the Metadata. It doesn't require a lot.