Comment on Filesystem and virtualization decisions for homeserver build
nesc@lemmy.cafe 2 days agoI won’t use fs snapsots as backups especially one as poorly supported on linux as zfs. I would go with external qcow disk snapshots and they can be pretty easily automated.
thecoffeehobbit@sopuli.xyz 2 days ago
This is what I’m doing currently, but it’s not really feasible to have the services shut down hourly for snapshots. This is indeed why I started looking towards filesystem-level snapshotting Obviously I will have other types of backups as well, I’m simply looking to have the on-the-fly immutable snapshot capability here somehow.
nesc@lemmy.cafe 2 days ago
You do not need to shut down services to make snapshots, why would you?
thecoffeehobbit@lemmy.world 2 days ago
Uhh, from most what I have gathered from self-hosting so far, doing that is not trivial as you’d need to flush the ram contents to disk first basically. I’m starting to realize though that the same holds equally for filesystem level snapshotting. What I’m really after is making my data live on separate pass through storage that has all the fancy filesystem level stuff so I can just relax about the VM backups.
nesc@lemmy.cafe 1 day ago
You are overthinking it, without flushing ram everything works fine. OS inside VM would just boot as normal and that’s it.