(kiranet.org)

221 points finnlab | 1 comments | 01 Apr 25 10:11 UTC | HN request time: 0s | source

Show context

FloatArtifact ◴[01 Apr 25 12:06 UTC] No.43545753[source]▶

Self-Hosting like it's 2025...uhhgg...

Don't get me wrong I love some of the software suggested. However yet a another post that does not take backups as seriously as the rest of the self-hosting stack.

Backups are stuck in 2013. We need plug and play backups for containers! No more roll your own with zfs datasets, back up data on the filesystem level (using sanoid/syncoid to manage snapshots or any other alternatives.

replies(3): >>43546151 #>>43547094 #>>43547135 #

nijave ◴[01 Apr 25 14:23 UTC] No.43547135[source]▶

>>43545753 #

Why not zfs snapshots? Besides using Hyper-V machine snapshots, that's been the easiest way, by far, for me. No need to worry about the 20 different proprietary tools that go with each piece of software.

Each VM or container gets a data mount on a zvol. Containers go to OS mount and each OS has its own volume (so most VMs end up with 2 volumes attached)

replies(1): >>43573855 #

1. FloatArtifact ◴[03 Apr 25 18:57 UTC] No.43573855[source]▶

>>43547135 #

Well, one argument not to use ZFS is simply the resources it takes. It eats up a lot of ram. Also I'm under the impression that one should never live-snapshot a database without risk of corruption.

↑