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

Addressing issue #154 #379

Closed flixman closed 5 years ago

flixman commented 5 years ago

As the sending of the ZFS streams is per stream, we can disable children ZFS from being snapshot/sent by setting the property "org.znapzend:enabled" to "off" on them. For the dataset being processed, in case the recursive flag is set, its children will be checked and their recently created snapshots removed.

coveralls commented 5 years ago

Coverage Status

Coverage decreased (-0.06%) to 87.613% when pulling 0347c9a2b22e12c45849e77dddefce22da5b0bf5 on flixman:patch-1 into 1d8a0960eaa72b75d4f7332986f4c6171a33d15c on oetiker:master.

flixman commented 5 years ago

Seems the project has a build error with perl 5.26, but is an amazon s3 error :-S @oetiker ; I think I can do nothing to get this fixed?

oetiker commented 5 years ago

Sorry I am on the road, but I get the impression that the error is from a missing module: Test::Exception ... adding this to PERL_MODULES could fix the problem

flixman commented 5 years ago

But, AFAIK, I can not modify travis configuration, right? (Just to confirm whether I can or I cannot fix it)

oetiker commented 5 years ago

you can modify everything ... just edit .travis.yml to control how travis works, or edit the PERL_MODULES file

flixman commented 5 years ago

I think the issue was caused by a glitch accessing the PERL packages in s3. I did a dummy modification to the pull request, and now the travis CI has passed properly. If you can approve that, I think we are good to go.

oetiker commented 5 years ago

thanks

oetiker commented 5 years ago

refers to #154