←back to thread

Self-Hosting like it's 2025

(kiranet.org)
221 points finnlab | 4 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 #
1. nunez ◴[01 Apr 25 14:20 UTC] No.43547094[source]▶
rclone is great for this.

One could set up a Docker Compose service that uses rclone to gzip and back up your docker volumes to something durable to get this done. An even more advanced version of this would automate testing the backups by restoring them into a clean environment and running some tests with BATS or whatever testing framework you want.

replies(1): >>43547276 #
2. nijave ◴[01 Apr 25 14:34 UTC] No.43547276[source]▶
Rclone won't take a consistent snapshot so you either need to shutdown the thing or use some other tool to export the data first
replies(1): >>43549442 #
3. auxym ◴[01 Apr 25 17:31 UTC] No.43549442[source]▶
zfs/btrfs snapshot and then rclone that snapshot?
replies(1): >>43551993 #
4. nijave ◴[01 Apr 25 22:33 UTC] No.43551993{3}[source]▶
I think that'd break deleting incremental snapshots unless you tried uploading a gigantic blob of the entire filesystem, wouldn't it?

Meaning you'd need to upload full snapshots on a fixed interval