search

oetiker / znapzend

zfs backup with remote capabilities and mbuffer integration.
www.znapzend.org
GNU General Public License v3.0
608 stars 137 forks source link

Want a mode to run a separate daemon for each defined retention policy #390

Closed jimklimov closed 3 years ago

jimklimov commented 5 years ago

From what I see in practice (at least as of the release in cswznapzend, but I think later too) is that the daemonized mode tracks all backup schedules in a common setup. In particular, hiccups sending snapshots of one configuration seem to impact others, whether intended or not. If the situation is persistent (e.g. someone created unexpected datasets/snaps in the target) all our sent snapshots can't get removed, even from other ZFS trees - clogging up the original pool.

Also, sending independent-policy sources in parallel could end up faster in wallclock, as we often see (near-)zero sized snapshots taking one or more minutes to complete the send/recv/sync/lock/whatever takes so long under the hood, so with an otherwise quick hardware we see hours spent for a few gigabytes of real traffic, and with schedules like hourly snaps it just does not keep up :(

Ideas welcome, maybe I'm reading something wrong?

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.