Self-Hosting like it's 2025

(kiranet.org)

221 points finnlab | 1 comments | 01 Apr 25 10:11 UTC | HN request time: 0.201s | 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 #

marceldegraaf ◴[01 Apr 25 12:47 UTC] No.43546151[source]▶

>>43545753 #

Best decision of last year for my homelab: run everything in Proxmox VMs/containers and back up to a separate Proxmox Backup Server instance.

Fully automated, incremental, verified backups, and restoring is one click of a button.

replies(1): >>43546756 #

1. FloatArtifact ◴[01 Apr 25 13:49 UTC] No.43546756[source]▶

>>43546151 #

Yes, I'm considering that if I can't find a solution that is plug-and-play for containers Independent of the OS and file system. Although I don't mind something abstracting on top of ZFS. ZFS Mental overhead through the snapshot paradigm can lead to its own complexities. A traditional backup and restorer front end would be great.

I find it strange that, especially with a docker which already knows your volumes, app data, and config, can't automatically backup and restore databases, and configs. Jeez, they could have built it right into docker.

↑