ShellMonkey

Image

Nope

Borg is it’s own thing, just handy to have it built in and preconfigured to work. If you run VMs on your working host instead of directly on the machine you could just back those up for pretty much the same effect, though it wouldn’t usually be a realtime backup.

The next cloud data is fine being remote, when I say realtime I guess it could be better said as time sensitive. A database needs to update something and read it back in the right sequence for it to work properly. Just retrieving a file doesn’t have those issues.

If you happened to use it in a way like shared collaboration of a document with realtime updates it might be an issue, but I expect in that case the revisions would hit the DB first and then be put to the file as a secondary operation. Never tried that myself though.

Without getting into things like a SAN it’s generally not a good plan to put anything that needs realtime access remote to the device processing it. DBs are constantly making updates and introducing the odd bit of latency or a disconnect can make for lots of issues. I also have a worker/storage split setup and for a while tried just running the VMs as a whole using remote storage to host the vdisk, it wasn’t pretty even with a separate network dedicated to it.

For NC particularly, if you use their official AIO docker setup there is a built in borg backup you can store remotely and it makes restoration pretty painless.

You can buy whole kits to build your own, the capacity to control what is made with the is about as much as if you tried to ban someone with a table saw from building a birdhouse.

Encrypt before send, and if you want to have protection against deletions of the data have a cold backup offline other than during the copy.

My go to for messing with chat bots is Kobold that’ll let you split the work between multiple GPUs. I get the impression the actual processing is only done on one but it lets you load larger models with the extra memory.

I was using a Nvidia 3060 for a while, then had 2 in one box, then switched to a 3090.

The amount of vram is a big factor for decent performance. Getting it to not sound like a predictably repetitive bot though is a whole separate thing that is still kind of elusive.

I was probably using Emby already by then, had bought a lifetime license since it didn't require bouncing things off and outside server like Plex did (or was it that Plex was a renewing subscription, I forget) , so it just stayed out of inertia.

I can't say I've given Jellyfin a proper try (as in using it and the clients exclusively for a long period) but we have been using Emby for quite a while before I knew it existed.

If I'm not mistaken Jellyfin is actually a fork of Emby so they're pretty similar, but one is a bit older.