hmm... i'm having Thoughts on how to handle self-hosting stuff locally for friends & taking good backups...
It might just be enough? The PBS box would be pretty basic, just a few core Ryzen chip with enough storage space & network speed to accommodate the throughput of backups coming in (which should be MORE than enough unless I can get like, an M.2 E-key to 10Gbps plug shoved into a box). The Optiplex box would be handling most of the heavy lifting, so i might bias towards an i7-based unit for some extra compute power when it comes to taking, compressing, and encrypting the suspend-mode backups before making them the PBS server's problem. who then gets to deal with shoving it to Backblaze as well.
the PBS server would really just be doing that and sitting idle most of the time, just making sure it keeps the girlies together. I don't think? it'd really need all that much power in the grand scheme of things. the fleet of Optiplex boxes could all run their own set of tasks, I could get a 12th-gen box for my personal stuff (Jellyfin included) and re-purpose my current 10th-gen box as the host device (swapping out the WiFi E-key for a faster wired network plug) and put in more robust storage (and swap the memory for at least decent ECC stuff, so long that the Optiplex Micro's support it).
The PBS server should? at least support un-buffered ECC DDR4. From what I'm seeing, Asrock and Gigabyte B550 boards typically do across the price range, so that should be OK there. Toss an Intel X550 network card for 10GbE local backup network to guarantee only the read/write process is the bottleneck. I'd probably have the Optiplex box built-in 1GbE port be the actual service network? At least keeps the two separate so you can't physically interfere with the backup comms? IDFK here lol this is theoretical.
Anyways I think that might be the best? way to go about things. I could build in a Jonsbo N4 and get even more hard drives, but IDK more hard drives = more cost and more (idle) power draw, and since shit is backed up in like, twelve spots anyways it should be OK to have a smaller box whose whole job is backups?
shrug
=> More informations about this toot | More toots from senil@booping.synth.download
please know that this isn't even getting into if I run Owncast/Peertube and Restreamer for myself so I can broadcast in a higher quality, and then have another local box (whose specs would probably be more on-par with the PBS server, though it'd need to have either enough compute power to software transcode from AV1 to x264 in a few bitrates, or be built with hardware transcoding from day one) handle the Restreamer/Peertube side of things - the compute and network throughput to manage all that jazz, and enough storage space to hold who knows how much video in a variety of bitrates.
tbh I think PBS would only take backups of the actual container setup there, and none of the data on it since a) that means having to back up a TON more shit (which means instantly needing to build in an N4 or even N5) when I could just. build in one of those for the Owncast/Peertube and Restreamer box and call it a day (and just have a decent RAID setup so drive failure is at least less harmful when it comes to video storage)
can you tell I'm way too obsessed with data backups and reliability?
(as if all of this matters if my internet dies and I lose that uptime, but ALSO at least the advantage of doing full container backups on shit means extended outages could be as simple as just spinning up a VPS with the same container specs and tossing the latest B2 backup onto it? though IDK how well fediverse stuff would play with that...)
=> More informations about this toot | More toots from senil@booping.synth.download
okay I THINK! I have an idea on how to handle this totally not convoluted setup.
Odds are I'll just forgo the Owncast side of things since that's complexity and the only benefit it really offers is "there is a way to watch that Avoids Twitch". It is tempting to still have a Restreamer box, but I might make it 12th-fen Intel based instead for better hardware transcoding across the board, since AMD's is still kinda bleh when it comes to real-time work.
But the Optiplex Micro fleet & Proxmox Backup Server specs are more or less what I'm thinking. If I could run a reverse proxy on that thing too I would, but I feel like that's getting into the weeds of setup and shit.
(An option is to forgo PBS entirely and have that box basically be a glorified network drive with a reverse proxy that only the homelab stuff & my desktop get direct access to, and have each relevant Proxmox VE handle shit directly, but that also means they have to handle All Of It directly, instead of letting PBS handle the grunt work)
=> More informations about this toot | More toots from senil@booping.synth.download
FUCK NEVERMIND A NEW OPTION HAS PRESENTED ITSELF!
Run PBS as a full VM inside of Proxmox VE. I would only want this box to run that & personal stuff as to avoid being a single point of failure, and that box still acts as a controlled access point to the remaining homelab network.
The biggest kind of benefit here is that it incentivizes building in a much bigger case, like the N4, which means I could also get a decent low-profile dGPU to handle hardware transcoding for Jellyfin and/or Restreamer (if desired down the line). It also has a couple more 3.5" drive bays, so it's easier for me to fine-tune my drive layout and whatnot.
(it also has two 2.5" bays that I could pop a decent datacenter SATA SSD in RAID1 or equivalent and use that for fast-but-marginally-safe storage? idk)
If I go that route, my thought is to get six big 3.5" drives (NAS/server grade of course), maybe two datacenter friendly SATA SSDs for idk, PBS? and then a boot NVMe drive that houses the guts for some basic shit that doesn't need the kind of uptime that anything ran for friends justified. Stuff like Jellyfin & other odds and ends containers. It might also house the nginx reverse proxy container & everything gets routed through her, so it'd warrant backing up specifically the container since Jellyfin's media would point to the hard drives (probably two 3.5" drives sitting aside from the primary four?) and the size of that container would be way, WAY smaller than the size I'd let fedi-related containers get.
Though it also might be worth giving it its own container entirely so that pulling it elsewhere is minimal hassle & could maybe? be convinced to operate on the same IPs since I'd use Proxmox VE to pull the backups in from B2 or whatever.
Hmm. That's definitely a "we get there when we get there" question because it depends on how I want to structure things, and PBS only really matters once there's anything running for others that I care about.
=> More informations about this toot | More toots from senil@booping.synth.download
rolling out PBS would totally happen before adding anything for others too, so that I can have The Setup locked down so that it's minimal hassle & I know what I'm doing before bringing anything for friends online, since I'd wanna hook that shit up to PBS right away.
(also I think if I add the two datacenter SATA SSDs to the N4, those would house the PBS data store that houses the backups & is what gets copied over to B2.)
The most ridiculous option here is to build the massive cube that is the Jonsbo N5, shove my current motherboard into it, and use its sheer number of drives to house so much data. My current motherboard can bifurcate to PCIe 4.0x8 on its primary two slots, and that means I could safely toss in a fucking Intel Battlemage dGPU for hardware transcode which will run fine since it was build for those lanes, have 4.0x8 available to a PCIe to SATA expander, and still have a slot for a faster network card.
Yes I'd toss a Ryzen 9 into it, and yes power draw is basically out the window for The Cube at that point, but also! it'd bw worth it xD so much storage space, so much room for activities.
it would be HELLA expensive though, but I'd probably add drives in groups of four for RAID10 (or equivalent), and then install two (or three) datacenter SATA SSDs in RAID1 for PBS so if one drive dies, there's still two to spare (plus everything backed up to B2 that I could pull back down)
=> More informations about this toot | More toots from senil@booping.synth.download
ladies, gentlemen, and those of us who know better, my slapped together build in the N5 going all out is now over $3200. It also still does not have RAM, which will be ECC unbuffered.
This box might as well be the primary box for The Everything at this rate.
edit to add: If I fill out the memory with four 32GB unbuffered ECC sticks, it will add another $400 to this thang.
=> More informations about this toot | More toots from senil@booping.synth.download
@senil you're self hosting apps not powering a starship
=> More informations about this toot | More toots from stefenauris@furry.engineer This content has been proxied by September (ba2dc).Proxy Information
text/gemini
