CouncilOfFriends
Correct, it's not obvious when first diving in but the main use for RAID is increasing performance and availability by allowing up to a specific number of drive failures. For that to work, ideally in an enterprise you'd have a primary and secondary controller to mitigate that point of failure which is not typical for most homelabs and makes backup even more important.
The only reason I liked using their remote app was being able to do Bluetooth listening. Now the app no longer runs on my phone, and after reinstalling and rebooting I deleted that and am back to using the Chromecast. Time to cut the internet to the TV so I don't get an update with this ad feature
Anyone who has read a single NTSB accident report will understand what an insane idea this is.
When I moved into my otherwise shitty apartment, having Google Fiber was the selling point. Paying Comcast a monthly fee for unlimited bandwidth is something I vow never again to do.
This is correct. As the article says employees are using their phones as hotspots so it's not as if it's a Faraday cage. Their IT guy should do a Wi-Fi site survey and install a few AC Pros.
After using some grandfathered T-Mobile family plan for over a decade I moved us to Tello. Still the same towers, but with our usage it's half the price.
- Don't make him angry
- If Hulk is already angry, light a lavender candle and play some calming music
One note which may not apply to you, I installed my Proxmox to boot from 2 256G SSDs as a basic RAID 1 mirror and only have the bare minimum data in VM storage to reduce size of backups. Backup retention on the boot drives is limited because a cron job on the VM handles copying backups to the MergerFS pool for longer term storage.
Moving docker's data directory to the 'slow' drives was a helpful decision, this post covers the old/wrong ways to do that and the way which worked (data-root). Docker data doesn't take up a huge amount of space, but it saved me some work recently when I found my media server had been down for a while and couldn't remember when it worked last to identify a working backup. I spun up a fresh Debian image and ran through the steps to reinstall the stack, and point to the same Docker data path. Running the same Docker compose command got most services working with the old metadata, though others i renamed/removed the service's path and reconfigured.
My docker-compose and its revisions are the extent of a backup I need for a piracy box as my internet is quick enough to recreate my library within a couple days if needed.
With a PA message that there is a free meal in the aisle for whoever wants it