Got it, thanks. That makes sense to me. I think there would still be the limitation of a single working directory per configuration file.
Well, not necessarily am issue. Finally, it's just…
What about not unmounting any part of the original FS and mount the whole hierarchy of zfs snapshots in a subdirectory and then backup just that subdirectory using "relative directory" stuff?…
Well what I had in mind would use
unshare()to create a private mount namespace, unmount the old mount and mount the snapshot (I know this works in zfs at least). But what if someone would…
It could also work something like this (assuming this is turned into a proper hook like the db backups are):
- Create zfs snapshots
- Unshare with mount namespace
- Create a new…
[...] Or would stdout/stderr be sufficient if borgmatic actually "supported" them properly for hook commands?
Of course, it'd be fine, however as I see, there are at least three "input…
[...] is there any other way (stream/file descriptor) for a hook script to use appropriatelly logging facility (as an alternative to stdout/stderr)?
The short answer is no, not…
Hi,
I'm just testing the following setup, which seems to work quite well:
On my (source) machine I have three ZFS pools: rpool (root FS /), bpool (for /boot) and dpool…