-
Notifications
You must be signed in to change notification settings - Fork 42
Description
I'm the author of zbackup, which is in use here on 5 production fileservers replicating 100s of TB of data. Rather than implement it in my own repo, seperate from zfs-tools, I decided to contribute it to the zfs-tools repo, mainly because of the close integration with the underlying scripts and library. In hindsight, that may have been a mistake.
I submitted a pull request for an enhancement I made to zbackup in September 2014 in my repo. This was not accepted, but in my view is essential if zbackup is to be used safely in a large-scale environment.
So, for now I recommend that any serious users of zbackup use my original version.
I see another issue (#18) has been raised about zbackup functionality, but the author of this repo is not able to respond meaningfully because he is not the author of zbackup itself.
I am therefore wondering whether zbackup should now be decoupled from the underlying zfs-tools, so that proper maintenance may be performed by the original author, without getting bogged down in inconsequential disagreements (like the location of the lock directory).
What do you think?