121–130 of 244 posts
This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…
What would happen if after long period of inactivity the server become a “silent” device i.e. device that does not transmit traffic for extended periods of time because can result in a loss of service binding? These periods of inactivity, thus making the device effectively unreachable (for example for a WAKE-ON-LAN packet) [1]. The diagrams in the article are just gorgeous, can you share the drawing tools being used…
Match host desktop.local exec /bla/bla/send-wol
I wonder how many sleep/wake cycles would it take a day to outweigh the TCO decrease of the power bill with the TCO increase of the increased stress/amortization of the hardware, especially HDDs.
I often power it on and off 1-2 times a day, and the drives are set to spin down when not in use. The SMART data for these drives shows approximately 37,000 power on hours and 17,000 start/stop cycles. That's about 4 years 3 months of actual power on time, and about 3 power cycles per year over the past 16 years.
The spec sheet says these drives use 8W idle. So:
192 months - 51 months = 141 months of non-use
141 months * 0.730 kilohours / month = 102.93 kilohours
102.93 kilohours * 32 watts = 3293.76 kwh
Assuming 15 cents per kwh, that comes to $494 saved by shutting the drives down over the past 16 years. And I paid $232 total for the drives back in 2007.
Obviously YMMV, just thought it would be fun to calculate :)
Earlier quoted context omitted.
Roughly 40% (and rising) of Google users use IPv6. https://www.google.com/intl/en/ipv6/statistics.html
Without realising and without having had to set it up themselves.
Earlier quoted context omitted.
> you can almost go IPv6 only nowadays if you wanted to. I think that is the reason why many aren't enthusiastic about it.
Again, I disabled IPv4 purely for testing reasons , to guarantee nothing was using IPv4 without me knowing it. There’s no reason to actually disable IPv4 as a fallback. Over 99.999% of traffic through my home network is IPv6 now. The tiny remainder that has to use IPv4 does, without issue. 5 months on, and nary a complaint. Just works. The world is ready for IPv6 as your primary, with IPv4 as the fallback.
This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…
I agree, but you could argue that the Raspberry Pi is not performant enough during restores or browsing the backups. During the backup itself performance should not have to be that big of an issue as it's mostly a background operation you will not be waiting on. You could also use the RPi as a stepping stone which syncs it's files to the 'real' backup server which is on a daily/weekly timer instead of on-demand setup…
> You'll need: An always-on Linux device on the same network as your server, e.g. a Raspberry Pi > First, a bit about my hardware, as this solution is somewhat hardware-dependent: HP ProDesk 600 G3 SFF I seriously doubt any of this can be gotten to work on a Pi in a way that actually reduces power usage in any notable way. Hell the Pi 4 uses almost full idle current when completely powered off unless you turn off jus…
Many people who would do this sort of thing likely already have an always-on pi (pi-hole, dns, ssh jump box, etc). And even at full bore, pi 4 is about 6.5W, so 90% savings over the HP. https://www.pidramble.com/wiki/benchmarks/power-consumption
Another option, if your needs are relatively modest, is to choose a low power mini PC. The one I chose idles at around 5W under Linux before any tweaking. It is based on the Intel N5105. I have a few 2.5” external HDDs attached for backup which are configured to sleep after a short time.