Selfhosted

40728 readers

374 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 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!

founded 2 years ago

MODERATORS

You just finished setting up all your services and it works fine - how do you now prepare for eventual drive failure? (kbin.social)

submitted 1 year ago by [email protected] to c/selfhosted

57 comments fedilink hide all child comments

I know that for data storage the best bet is a NAS and RAID1 or something in that vein, but what about all the docker containers you are running, carefully configured services on your rpi, installed *arr services on your PC, etc.?

Do you have a simple way to automate backups and re-installs of these as well or are you just resigned to having to eventually reconfigure them all when the SD card fails, your OS needs a reinstall or the disk dies?

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

[–] [email protected] 1 points 1 year ago (1 children)

You should get another node, otherwise when node1 fails node2 will reboot itself and then do nothing because it has no quorum

[–] ikidd 1 points 1 year ago (1 children)

pvecm expected 1

[–] [email protected] 2 points 1 year ago (2 children)

I know, but every time I had to do that it felt like it's a jank solution. If you have a raspberry pi or smth like that you can also set it up as a qdevice.

...and if you're completely fine with how it is you can also just leave it like it is

[–] ikidd 3 points 1 year ago

So I started to write a reply that said basically that I was OK doing that manually, but thought that "hell, I have a PBS box on the network that would do that fine". So it took about 3 minutes to install the corosync-qdevice packages on all three and enable it. Good to go.

Thanks for the kick in the ass.

[–] ikidd 2 points 1 year ago (1 children)

So since I now had a "quorate" cluster again, I thought I'd try out HA. I'd always been under the impression that unless you had a shared storage LUN, you couldn't HA anything. But I thought I'd trigger a replication and then down the 2nd node just as a test. And lo and behold, the first node brought up my OPNsense VM from the replicated image about 2 minutes after the second node lost contact, and internet starts working again.

I'm really excited about having that feature working now. This was a good night, thank you.

[–] [email protected] 2 points 1 year ago (1 children)

If you need another thing to do, you could try to make your opnsense HA and never have your internet stop working while rebooting a node. It's pretty simple to set up, you might finish it in 1-2 evenings. Happy clustering!

[–] ikidd 2 points 1 year ago

I'll look into that. I did see the option in opnsense once upon a time but never investigated it.