Selfhosted

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

8 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.

[Thread #567 for this sub, first seen 3rd Mar 2024, 16:05] [FAQ] [Full list] [Contact] [Source code]

when you say some services on your network are you talking about machines or softwares?

for machines yes ups makes sense for softwares writing some scripts to run on start up should be enough another alternative can be setting up wake on Lan that way you can bring all up again wherever you are

Two pitfalls I had that you can avoid:

• look at efficiency. It's not always neglible, was like 40% of my energy usage because I oversized the UPS. The efficiency is calculated from top power the UPS can supply. 96% efficient 3kW UPS eats 4% of 3kW, 120 watts, even if the load you connected is much smaller than 3kW
• look at noise level. Mine was loud almost like a rack server, because of all the fans.

I replaced that noisy, power hungry beast with a small quiet 900W APC and I couldn't be happier

Exact same thing happened to me the other day. Like exactly. Maybe we live in the same area.

In addition to ups, an LTE failover. I've had my Comcast crap be offline for hours.

Could also be a good opportunity to add a service monitor like Uptime Kuma. That way you know what services are still down once things come back online with less manual discovery on your part.

My suggestion just changes your threat model, so may not be a good one based on your wants.

Perhaps consolidate systems? Managing less devices = less points of failure. But adds the risk of any given failure being more severe.

I feel your pain. Just the other day the disk on my home assistant machine died after a power outage and I had to replace it with another disk and restore from backup.