fix url for pypi

Merge branch 'master' of github.com:psy0rz/zfs_autobackup
transparancy
2020-03-31 20:01:28 +02:00 · 2020-03-31 19:33:26 +02:00 · 2020-03-31 19:33:09 +02:00 · 2020-03-31 19:23:04 +02:00 · 2020-03-31 19:06:46 +02:00 · 2020-03-29 23:47:26 +02:00
11 changed files with 1582 additions and 464 deletions
--- a/.gitignore
+++ b/.gitignore
@ -1 +1,8 @@
 .vscode/settings.json
+token
+tokentest
+dist/
+build/
+zfs_autobackup.egg-info
+.eggs/
+__pycache__
--- a/838
+++ b/838
@ -1,281 +1,622 @@
                    GNU GENERAL PUBLIC LICENSE
-                       Version 2, June 1991
+                       Version 3, 29 June 2007

- Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

                            Preamble

-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.)  You can apply it to
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
 your programs, too.

  When we speak of free software, we are referring to freedom, not
 price.  Our General Public Licenses are designed to make sure that you
 have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.

-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.

  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.

-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.

-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.

-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.

  The precise terms and conditions for copying, distribution and
 modification follow.

-                    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+                       TERMS AND CONDITIONS

-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
+  0. Definitions.

-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
+  "This License" refers to version 3 of the GNU General Public License.

-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.

-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.

-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.

-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
+  A "covered work" means either the unmodified Program or a work based
+on the Program.

-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.

-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.

-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.

-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
+  1. Source Code.

-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.

-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.

-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.

-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.

-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.

-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
+  The Corresponding Source for a work in source code form is that
+same work.

-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
+  2. Basic Permissions.

-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.

-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.

-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
 this License.

-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
 otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.

-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
+  13. Use with the GNU Affero General Public License.

-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.

-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
+  14. Revised Versions of this License.

-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
 be similar in spirit to the present version, but may differ in detail to
 address new problems or concerns.

-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.

-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.

-                            NO WARRANTY
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.

-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
+  15. Disclaimer of Warranty.

-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.

                     END OF TERMS AND CONDITIONS

@ -287,15 +628,15 @@ free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
 to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
+state the exclusion of warranty; and each file should have at least
 the "copyright" line and a pointer to where the full notice is found.

-    {description}
-    Copyright (C) {year}  {fullname}
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>

-    This program is free software; you can redistribute it and/or modify
+    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
+    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
@ -303,38 +644,31 @@ the "copyright" line and a pointer to where the full notice is found.
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

-    You should have received a copy of the GNU General Public License along
-    with this program; if not, write to the Free Software Foundation, Inc.,
-    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.

 Also add information on how to contact you by electronic and paper mail.

-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:

-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

 The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".

-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  {signature of Ty Coon}, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.

+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.
--- a/README.md
+++ b/README.md
@ -1,18 +1,559 @@
-# ZFS autobackup v3 - TEST VERSION
+# ZFS autobackup

-Official releases are here: https://github.com/psy0rz/zfs_autobackup/releases
+## New in v3

-New in v3:
- * Complete rewrite, cleaner object oriented code.
- * Python 3 and 2 support.
- * Backwards compatible with your current backups and parameters.
- * Progressive thinning (via a destroy schedule. default schedule should be fine for most people)
- * Cleaner output, with optional color support (pip install colorama). 
-   * Clear distinction between local and remote output.
-   * Summary at the beginning, displaying what will happen and the current thinning-schedule.
- * More effient destroying/skipping snaphots on the fly. (no more space issues if your backup is way behind)
- * Progress indicator (--progress)
- * Better property management (--set-properties and --filter-properties)
- * Better resume handling, automaticly abort invalid resumes.
- * More robust error handling.
- * Prepared for future enhanchements.
+* Complete rewrite, cleaner object oriented code.
+* Python 3 and 2 support.
+* Installable via [pip](https://pypi.org/project/zfs-autobackup/).
+* Backwards compatible with your current backups and parameters.
+* Progressive thinning (via a destroy schedule. default schedule should be fine for most people)
+* Cleaner output, with optional color support (pip install colorama).
+* Clear distinction between local and remote output.
+* Summary at the beginning, displaying what will happen and the current thinning-schedule.
+* More efficient destroying/skipping snapshots on the fly. (no more space issues if your backup is way behind)
+* Progress indicator (--progress)
+* Better property management (--set-properties and --filter-properties)
+* Better resume handling, automatically abort invalid resumes.
+* More robust error handling.
+* Prepared for future enhancements.
+* Supports raw backups for encryption.
+* Custom SSH client config.
+
+## Introduction
+
+This is a tool I wrote to make replicating ZFS datasets easy and reliable. You can either use it as a backup tool or as a replication tool.
+
+You can select what to backup by setting a custom `ZFS property`. This allows you to set and forget: Configure it so it backups your entire pool, and you never have to worry about backupping again. Even new datasets you create later will be backupped.
+
+Other settings are just specified on the commandline. This also makes it easier to setup and test zfs-autobackup and helps you fix all the issues you might encounter. When you're done you can just copy/paste your command to a cron or script.
+
+Since its using ZFS commands, you can see what its actually doing by specifying `--debug`. This also helps a lot if you run into some strange problem or error. You can just copy-paste the command that fails and play around with it on the commandline. (also something I missed in other tools)
+
+An important feature thats missing from other tools is a reliable `--test` option: This allows you to see what zfs-autobackup will do and tune your parameters. It will do everything, except make changes to your zfs datasets.
+
+Another nice thing is progress reporting with `--progress`. Its very useful with HUGE datasets, when you want to know how many hours/days it will take.
+
+zfs-autobackup tries to be the easiest to use backup tool for zfs.
+
+## Features
+
+* Works across operating systems: Tested with Linux, FreeBSD/FreeNAS and SmartOS.
+* Works in combination with existing replication systems. (Like Proxmox HA)
+* Automatically selects filesystems to backup by looking at a simple ZFS property. (recursive)
+* Creates consistent snapshots. (takes all snapshots at once, atomic.)
+* Multiple backups modes:
+  * Backup local data on the same server.
+  * "push" local data to a backup-server via SSH.
+  * "pull" remote data from a server via SSH and backup it locally.
+  * Or even pull data from a server while pushing the backup to another server.
+* Can be scheduled via a simple cronjob or run directly from commandline.
+* Supports resuming of interrupted transfers. (via the zfs extensible_dataset feature)
+* Backups and snapshots can be named to prevent conflicts. (multiple backups from and to the same filesystems are no problem)
+* Always creates a new snapshot before starting.
+* Checks everything but tries continue on non-fatal errors when possible. (Reports error-count when done)
+* Ability to 'finish' aborted backups to see what goes wrong.
+* Easy to debug and has a test-mode. Actual unix commands are printed.
+* Keeps latest X snapshots remote and locally. (default 30, configurable)
+* Uses zfs-holds on important snapshots so they cant be accidentally destroyed.
+* Easy installation:
+  * Just install zfs-autobackup via pip, or download it manually.
+  * Written in python and uses zfs-commands, no 3rd party dependency's or libraries.
+  * No separate config files or properties. Just one zfs-autobackup command you can copy/paste in your backup script.
+
+## Installation
+
+### Using pip
+
+The recommended way on most servers is to use [pip](https://pypi.org/project/zfs-autobackup/):
+
+```console
+[root@server ~]# pip install --upgrade zfs-autobackup
+```
+
+This can also be used to upgrade zfs-autobackup to the newest stable version.
+
+### Using easy_install
+
+On older servers you might have to use easy_install
+
+```console
+[root@server ~]# easy_install zfs-autobackup
+```
+
+### Direct download
+
+Its also possible to just download <https://raw.githubusercontent.com/psy0rz/zfs_autobackup/master/bin/zfs-autobackup> and run it directly.
+
+The only requirement that is sometimes missing is the `argparse` python module. Optionally you can install `colorma` for colors.
+
+It should work with python 2.7 and higher.
+
+## Example
+
+In this example we're going to backup a machine called `pve` to a machine called `backup`.
+
+### Setup SSH login
+
+zfs-autobackup needs passwordless login via ssh. This means generating an ssh key and copying it to the remote server.
+
+#### Generate SSH key on `backup`
+
+On the server that runs zfs-autobackup you need to create an SSH key. You only need to do this once.
+
+Use the `ssh-keygen` command and leave the passphrase empty:
+
+```console
+root@backup:~# ssh-keygen
+Generating public/private rsa key pair.
+Enter file in which to save the key (/root/.ssh/id_rsa):
+Enter passphrase (empty for no passphrase):
+Enter same passphrase again:
+Your identification has been saved in /root/.ssh/id_rsa.
+Your public key has been saved in /root/.ssh/id_rsa.pub.
+The key fingerprint is:
+SHA256:McJhCxvaxvFhO/3e8Lf5gzSrlTWew7/bwrd2U2EHymE root@backup
+The key's randomart image is:
+---[RSA 2048]----+
+|    + =          |
+|   + X *    E .  |
+|  . = B +  o o . |
+|   .   o +  o  o.|
+|        S o   .oo|
+|         . + o= +|
+|          . ++==.|
+|            .+o**|
+|           .. +B@|
+----[SHA256]-----+
+root@backup:~#
+```
+
+#### Copy SSH key to `pve`
+
+Now you need to copy the public part of the key to `pve`
+
+The `ssh-copy-id` command is a handy tool to automate this. It will just ask for your password.
+
+```console
+root@backup:~# ssh-copy-id root@pve.server.com
+/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
+/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
+/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
+Password:
+
+Number of key(s) added: 1
+
+Now try logging into the machine, with:   "ssh 'root@pve.server.com'"
+and check to make sure that only the key(s) you wanted were added.
+
+root@backup:~#
+```
+
+### Select filesystems to backup
+
+Its important to choose a unique and consistent backup name. In this case we name our backup: `offsite1`.
+
+On the source zfs system set the ```autobackup:offsite1``` zfs property to true:
+
+```console
+[root@pve ~]# zfs set autobackup:offsite1=true rpool
+[root@pve ~]# zfs get -t filesystem,volume autobackup:offsite1
+NAME                                    PROPERTY             VALUE                SOURCE
+rpool                                   autobackup:offsite1  true                 local
+rpool/ROOT                              autobackup:offsite1  true                 inherited from rpool
+rpool/ROOT/pve-1                        autobackup:offsite1  true                 inherited from rpool
+rpool/data                              autobackup:offsite1  true                 inherited from rpool
+rpool/data/vm-100-disk-0                autobackup:offsite1  true                 inherited from rpool
+rpool/swap                              autobackup:offsite1  true                 inherited from rpool
+...
+```
+
+Because we don't want to backup everything, we can exclude certain filesystem by setting the property to false:
+
+```console
+[root@pve ~]# zfs set autobackup:offsite1=false rpool/swap
+[root@pve ~]# zfs get -t filesystem,volume autobackup:offsite1
+NAME                                    PROPERTY             VALUE                SOURCE
+rpool                                   autobackup:offsite1  true                 local
+rpool/ROOT                              autobackup:offsite1  true                 inherited from rpool
+rpool/ROOT/pve-1                        autobackup:offsite1  true                 inherited from rpool
+rpool/data                              autobackup:offsite1  true                 inherited from rpool
+rpool/data/vm-100-disk-0                autobackup:offsite1  true                 inherited from rpool
+rpool/swap                              autobackup:offsite1  false                local
+...
+```
+
+### Running zfs-autobackup
+
+Run the script on the backup server and pull the data from the server specified by --ssh-source.
+
+```console
+[root@backup ~]# zfs-autobackup --ssh-source pve.server.com offsite1 backup/pve --progress --verbose
+
+  #### Settings summary
+  [Source] Datasets on: pve.server.com
+  [Source] Keep the last 10 snapshots.
+  [Source] Keep every 1 day, delete after 1 week.
+  [Source] Keep every 1 week, delete after 1 month.
+  [Source] Keep every 1 month, delete after 1 year.
+  [Source] Send all datasets that have 'autobackup:offsite1=true' or 'autobackup:offsite1=child'
+
+  [Target] Datasets are local
+  [Target] Keep the last 10 snapshots.
+  [Target] Keep every 1 day, delete after 1 week.
+  [Target] Keep every 1 week, delete after 1 month.
+  [Target] Keep every 1 month, delete after 1 year.
+  [Target] Receive datasets under: backup/pve
+
+  #### Selecting
+  [Source] rpool: Selected (direct selection)
+  [Source] rpool/ROOT: Selected (inherited selection)
+  [Source] rpool/ROOT/pve-1: Selected (inherited selection)
+  [Source] rpool/data: Selected (inherited selection)
+  [Source] rpool/data/vm-100-disk-0: Selected (inherited selection)
+  [Source] rpool/swap: Ignored (disabled)
+
+  #### Snapshotting
+  [Source] rpool: No changes since offsite1-20200218175435
+  [Source] rpool/ROOT: No changes since offsite1-20200218175435
+  [Source] rpool/data: No changes since offsite1-20200218175435
+  [Source] Creating snapshot offsite1-20200218180123
+
+  #### Sending and thinning
+  [Target] backup/pve/rpool/ROOT/pve-1@offsite1-20200218175435: receiving full
+  [Target] backup/pve/rpool/ROOT/pve-1@offsite1-20200218175547: receiving incremental
+  [Target] backup/pve/rpool/ROOT/pve-1@offsite1-20200218175706: receiving incremental
+  [Target] backup/pve/rpool/ROOT/pve-1@offsite1-20200218180049: receiving incremental
+  [Target] backup/pve/rpool/ROOT/pve-1@offsite1-20200218180123: receiving incremental
+  [Target] backup/pve/rpool/data@offsite1-20200218175435: receiving full
+  [Target] backup/pve/rpool/data/vm-100-disk-0@offsite1-20200218175435: receiving full
+  ...
+```
+
+Note that this is called a "pull" backup: The backup server pulls the backup from the server. This is usually the preferred way.
+
+Its also possible to let a server push its backup to the backup-server. However this has security implications. In that case you would setup the SSH keys the other way around and use the --ssh-target parameter on the server.
+
+### Automatic backups
+
+Now every time you run the command, zfs-autobackup will create a new snapshot and replicate your data.
+
+Older snapshots will eventually be deleted, depending on the `--keep-source` and `--keep-target` settings. (The defaults are shown above under the 'Settings summary')
+
+Once you've got the correct settings for your situation, you can just store the command in a cronjob.
+
+Or just create a script and run it manually when you need it.
+
+### Thinning out obsolete snapshots
+
+The thinner is the thing that destroys old snapshots on the source and target.
+
+The thinner operates "stateless": There is nothing in the name or properties of a snapshot that indicates how long it will be kept. Everytime zfs-autobackup runs, it will look at the timestamp of all the existing snapshots. From there it will determine which snapshots are obsolete according to your schedule. The advantage of this stateless system is that you can always change the schedule.
+
+Note that the thinner will ONLY destroy snapshots that are matching the naming pattern of zfs-autobackup. If you use `--other-snapshots`, it wont destroy those snapshots after replicating them to the target.
+
+#### Thinning schedule
+
+The default thinning schedule is: `10,1d1w,1w1m,1m1y`.
+
+The schedule consists of multiple rules separated by a `,`
+
+A plain number specifies how many snapshots you want to always keep, regardless of time or interval.
+
+The format of the other rules is: `<Interval><TTL>`.
+
+* Interval: The minimum interval between the snapshots. Snapshots with intervals smaller than this will be destroyed.
+* TTL: The maximum time to life time of a snapshot, after that they will be destroyed.
+* These are the time units you can use for interval and TTL:
+  * `y`: Years
+  * `m`: Months
+  * `d`: Days
+  * `h`: Hours
+  * `min`: Minutes
+  * `s`: Seconds
+
+Since this might sound very complicated, the `--verbose` option will show you what it all means:
+
+```console
+  [Source] Keep the last 10 snapshots.
+  [Source] Keep every 1 day, delete after 1 week.
+  [Source] Keep every 1 week, delete after 1 month.
+  [Source] Keep every 1 month, delete after 1 year.
+```
+
+A snapshot will only be destroyed if it not needed anymore by ANY of the rules.
+
+You can specify as many rules as you need. The order of the rules doesn't matter.
+
+Keep in mind its up to you to actually run zfs-autobackup often enough: If you want to keep hourly snapshots, you have to make sure you at least run it every hour.
+
+However, its no problem if you run it more or less often than that: The thinner will still do its best to choose an optimal set of snapshots to choose.
+
+If you want to keep as few snapshots as possible, just specify 0. (`--keep-source=0` for example)
+
+If you want to keep ALL the snapshots, just specify a very high number.
+
+#### More details about the Thinner
+
+We will give a practical example of how the thinner operates.
+
+Say we want have 3 thinner rules: 
+
+* We want to keep daily snapshots for 7 days.
+* We want to keep weekly snapshots for 4 weeks.
+* We want to keep monthly snapshots for 12 months.
+
+So far we have taken 4 snapshots at random moments:
+
+![thinner example](https://raw.githubusercontent.com/psy0rz/zfs_autobackup/master/doc/thinner.png)
+
+For every rule, the thinner will divide the timeline in blocks and assign each snapshot to a block.
+
+A block can only be assigned one snapshot: If multiple snapshots fall into the same block, it only assigns it to the oldest that we want to keep.
+
+The colors show to which block a snapshot belongs:
+
+* Snapshot 1: This snapshot belongs to daily block 1, weekly block 0 and monthly block 0. However the daily block is too old. 
+* Snapshot 2: Since weekly block 0 and monthly block 0 already have a snapshot, it only belongs to daily block 4.
+* Snapshot 3: This snapshot belongs to daily block 8 and weekly block 1.
+* Snapshot 4: Since daily block 8 already has a snapshot, this one doesn't belong to anything and can be deleted right away. (it will be keeped for now since its the last snapshot)
+
+zfs-autobackup will re-evaluate this on every run: As soon as a snapshot doesn't belong to any block anymore it will be destroyed.
+
+Snapshots on the source that still have to be send to the target wont be destroyed off course. (If the target still wants them, according to the target schedule)
+
+## Tips
+
+* Use ```--debug``` if something goes wrong and you want to see the commands that are executed. This will also stop at the first error.
+* You can split up the snapshotting and sending tasks by creating two cronjobs. Use ```--no-send``` for the snapshotter-cronjob and use ```--no-snapshot``` for the send-cronjob. This is usefull if you only want to send at night or if your send take too long.
+* Set the ```readonly``` property of the target filesystem to ```on```. This prevents changes on the target side. (Normally, if there are changes the next backup will fail and will require a zfs rollback.) Note that readonly means you cant change the CONTENTS of the dataset directly. Its still possible to receive new datasets and manipulate properties etc.
+* Use ```--clear-refreservation``` to save space on your backup server.
+* Use ```--clear-mountpoint``` to prevent the target server from mounting the backupped filesystem in the wrong place during a reboot.
+* Use ```--resume``` to be able to resume aborted backups. (not all zfs versions support this)
+
+### Speeding up SSH
+
+You can make your ssh connections persistent and greatly speed up zfs-autobackup:
+
+On the backup-server add this to your ~/.ssh/config:
+
+```console
+Host *
+    ControlPath ~/.ssh/control-master-%r@%h:%p
+    ControlMaster auto
+    ControlPersist 3600
+```
+
+Thanks @mariusvw :)
+
+### Specifying ssh port or options
+
+The correct way to do this is by creating ~/.ssh/config:
+
+```console
+Host smartos04
+    Hostname 1.2.3.4
+    Port 1234
+    user root
+    Compression yes
+```
+
+This way you can just specify "smartos04" as host.
+
+Also uses compression on slow links.
+
+Look in man ssh_config for many more options.
+
+## Usage
+
+Here you find all the options:
+
+```console
+[root@server ~]# zfs-autobackup --help
+usage: zfs-autobackup [-h] [--ssh-config SSH_CONFIG] [--ssh-source SSH_SOURCE]
+                      [--ssh-target SSH_TARGET] [--keep-source KEEP_SOURCE]
+                      [--keep-target KEEP_TARGET] [--other-snapshots]
+                      [--no-snapshot] [--no-send] [--min-change MIN_CHANGE]
+                      [--allow-empty] [--ignore-replicated] [--no-holds]
+                      [--resume] [--strip-path STRIP_PATH]
+                      [--clear-refreservation] [--clear-mountpoint]
+                      [--filter-properties FILTER_PROPERTIES]
+                      [--set-properties SET_PROPERTIES] [--rollback]
+                      [--destroy-incompatible] [--ignore-transfer-errors]
+                      [--raw] [--test] [--verbose] [--debug] [--debug-output]
+                      [--progress]
+                      backup_name target_path
+
+zfs-autobackup v3.0-rc8 - Copyright 2020 E.H.Eefting (edwin@datux.nl)
+
+positional arguments:
+  backup_name           Name of the backup (you should set the zfs property
+                        "autobackup:backup-name" to true on filesystems you
+                        want to backup
+  target_path           Target ZFS filesystem
+
+optional arguments:
+  -h, --help            show this help message and exit
+  --ssh-config SSH_CONFIG
+                        Custom ssh client config
+  --ssh-source SSH_SOURCE
+                        Source host to get backup from. (user@hostname)
+                        Default None.
+  --ssh-target SSH_TARGET
+                        Target host to push backup to. (user@hostname) Default
+                        None.
+  --keep-source KEEP_SOURCE
+                        Thinning schedule for old source snapshots. Default:
+                        10,1d1w,1w1m,1m1y
+  --keep-target KEEP_TARGET
+                        Thinning schedule for old target snapshots. Default:
+                        10,1d1w,1w1m,1m1y
+  --other-snapshots     Send over other snapshots as well, not just the ones
+                        created by this tool.
+  --no-snapshot         Dont create new snapshots (usefull for finishing
+                        uncompleted backups, or cleanups)
+  --no-send             Dont send snapshots (usefull for cleanups, or if you
+                        want a separate send-cronjob)
+  --min-change MIN_CHANGE
+                        Number of bytes written after which we consider a
+                        dataset changed (default 1)
+  --allow-empty         If nothing has changed, still create empty snapshots.
+                        (same as --min-change=0)
+  --ignore-replicated   Ignore datasets that seem to be replicated some other
+                        way. (No changes since lastest snapshot. Usefull for
+                        proxmox HA replication)
+  --no-holds            Dont lock snapshots on the source. (Usefull to allow
+                        proxmox HA replication to switches nodes)
+  --resume              Support resuming of interrupted transfers by using the
+                        zfs extensible_dataset feature (both zpools should
+                        have it enabled) Disadvantage is that you need to use
+                        zfs recv -A if another snapshot is created on the
+                        target during a receive. Otherwise it will keep
+                        failing.
+  --strip-path STRIP_PATH
+                        Number of directory to strip from path (use 1 when
+                        cloning zones between 2 SmartOS machines)
+  --clear-refreservation
+                        Filter "refreservation" property. (recommended, safes
+                        space. same as --filter-properties refreservation)
+  --clear-mountpoint    Set property canmount=noauto for new datasets.
+                        (recommended, prevents mount conflicts. same as --set-
+                        properties canmount=noauto)
+  --filter-properties FILTER_PROPERTIES
+                        List of properties to "filter" when receiving
+                        filesystems. (you can still restore them with zfs
+                        inherit -S)
+  --set-properties SET_PROPERTIES
+                        List of properties to override when receiving
+                        filesystems. (you can still restore them with zfs
+                        inherit -S)
+  --rollback            Rollback changes to the latest target snapshot before
+                        starting. (normally you can prevent changes by setting
+                        the readonly property on the target_path to on)
+  --destroy-incompatible
+                        Destroy incompatible snapshots on target. Use with
+                        care! (implies --rollback)
+  --ignore-transfer-errors
+                        Ignore transfer errors (still checks if received
+                        filesystem exists. usefull for acltype errors)
+  --raw                 For encrypted datasets, send data exactly as it exists
+                        on disk.
+  --test                dont change anything, just show what would be done
+                        (still does all read-only operations)
+  --verbose             verbose output
+  --debug               Show zfs commands that are executed, stops after an
+                        exception.
+  --debug-output        Show zfs commands and their output/exit codes. (noisy)
+  --progress            show zfs progress output (to stderr)
+
+When a filesystem fails, zfs_backup will continue and report the number of
+failures at that end. Also the exit code will indicate the number of failures.
+```
+
+## Troubleshooting
+
+### It keeps asking for my SSH password
+
+You forgot to setup automatic login via SSH keys, look in the example how to do this.
+
+### It says 'cannot receive incremental stream: invalid backup stream'
+
+This usually means you've created a new snapshot on the target side during a backup:
+
+* Solution 1: Restart zfs-autobackup and make sure you don't use --resume. If you did use --resume, be sure to "abort" the receive on the target side with zfs recv -A.
+* Solution 2: Destroy the newly created snapshot and restart zfs-autobackup.
+
+### It says 'internal error: Invalid argument'
+
+In some cases (Linux -> FreeBSD) this means certain properties are not fully supported on the target system.
+
+Try using something like: --filter-properties xattr
+
+## Restore example
+
+Restoring can be done with simple zfs commands. For example, use this to restore a specific SmartOS disk image to a temporary restore location:
+
+```console
+root@fs1:/home/psy#  zfs send fs1/zones/backup/zfsbackups/smartos01.server.com/zones/a3abd6c8-24c6-4125-9e35-192e2eca5908-disk0@smartos01_fs1-20160110000003 | ssh root@2.2.2.2 "zfs recv zones/restore"
+```
+
+After that you can rename the disk image from the temporary location to the location of a new SmartOS machine you've created.
+
+## Monitoring with Zabbix-jobs
+
+You can monitor backups by using my zabbix-jobs script. (<https://github.com/psy0rz/stuff/tree/master/zabbix-jobs>)
+
+Put this command directly after the zfs_backup command in your cronjob:
+
+```console
+zabbix-job-status backup_smartos01_fs1 daily $?
+```
+
+This will update the zabbix server with the exit code and will also alert you if the job didn't run for more than 2 days.
+
+## Backuping up a proxmox cluster with HA replication
+
+Due to the nature of proxmox we had to make a few enhancements to zfs-autobackup. This will probably also benefit other systems that use their own replication in combination with zfs-autobackup.
+
+All data under rpool/data can be on multiple nodes of the cluster. The naming of those filesystem is unique over the whole cluster. Because of this we should backup rpool/data of all nodes to the same destination. This way we wont have duplicate backups of the filesystems that are replicated. Because of various options, you can even migrate hosts and zfs-autobackup will be fine. (and it will get the next backup from the new node automatically)
+
+In the example below we have 3 nodes, named h4, h5 and h6.
+
+The backup will go to a machine named smartos03.
+
+### Preparing the proxmox nodes
+
+On each node select the filesystems as following:
+
+```console
+root@h4:~# zfs set autobackup:h4_smartos03=true rpool
+root@h4:~# zfs set autobackup:h4_smartos03=false rpool/data
+root@h4:~# zfs set autobackup:data_smartos03=child rpool/data
+```
+
+* rpool will be backuped the usual way, and is named h4_smartos03. (each node will have a unique name)
+* rpool/data will be excluded from the usual backup
+* The CHILDREN of rpool/data be selected for a cluster wide backup named data_smartos03. (each node uses the same backup name)
+
+### Preparing the backup server
+
+Extra options needed for proxmox with HA:
+
+* --no-holds: To allow proxmox to destroy our snapshots if a VM migrates to another node.
+* --ignore-replicated: To ignore the replicated filesystems of proxmox on the receiving proxmox nodes. (e.g: only backup from the node where the VM is active)
+* --min-change 200000: Ignore replicated works by checking if there are no changes since the last snapshot. However for some reason proxmox always has some small changes. (Probably house-keeping data are something? This always was fine and suddenly changed with an update)
+
+I use the following backup script on the backup server:
+
+```shell
+for H in h4 h5 h6; do
+  echo "################################### DATA $H"
+  #backup data filesystems to a common place
+  ./zfs-autobackup --ssh-source root@$H data_smartos03 zones/backup/zfsbackups/pxe1_data --clear-refreservation --clear-mountpoint  --ignore-transfer-errors --strip-path 2 --verbose --resume --ignore-replicated --min-change 200000 --no-holds $@
+  zabbix-job-status backup_$H""_data_smartos03 daily $? >/dev/null 2>/dev/null
+
+  echo "################################### RPOOL $H"
+  #backup rpool to own place
+  ./zfs-autobackup --ssh-source root@$H $H""_smartos03 zones/backup/zfsbackups/$H --verbose --clear-refreservation --clear-mountpoint  --resume --ignore-transfer-errors $@
+  zabbix-job-status backup_$H""_smartos03 daily $? >/dev/null 2>/dev/null
+done
+```
--- a/bin/init.py
+++ b/bin/init.py
--- a/bin/zfs-autobackup
+++ b/bin/zfs-autobackup
--- a/bin/zfs_autobackup.py
+++ b/bin/zfs_autobackup.py
@ -0,0 +1 @@
+zfs-autobackup
--- a/doc/thinner.odg
+++ b/doc/thinner.odg
--- a/doc/thinner.png
+++ b/doc/thinner.png
--- a/18
+++ b/18
@ -0,0 +1,18 @@
+#!/bin/bash
+
+set -e 
+
+
+rm -rf dist
+python3 setup.py sdist bdist_wheel
+# python2 setup.py sdist bdist_wheel
+
+
+gnome-keyring-daemon
+source token
+
+
+python3 -m twine check dist/*
+python3 -m twine upload dist/*
+
+git push --tags
--- a/17
+++ b/17
@ -0,0 +1,17 @@
+#!/bin/bash
+
+set -e 
+
+
+rm -rf dist
+python3 setup.py sdist bdist_wheel
+# python2 setup.py sdist bdist_wheel
+
+
+gnome-keyring-daemon
+source tokentest
+
+
+python3 -m twine check dist/*
+python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/* --verbose
+
--- a/setup.py
+++ b/setup.py
@ -0,0 +1,33 @@
+import setuptools
+import bin.zfs_autobackup
+import os
+
+os.system("git tag -m ' ' -a v{}".format(bin.zfs_autobackup.VERSION))
+
+with open("README.md", "r") as fh:
+    long_description = fh.read()
+
+setuptools.setup(
+    name="zfs_autobackup", 
+    version=bin.zfs_autobackup.VERSION,
+    author="Edwin Eefting",
+    author_email="edwin@datux.nl",
+    description="ZFS autobackup is used to periodicly backup ZFS filesystems to other locations. It tries to be the most friendly to use and easy to debug ZFS backup tool.",
+    long_description=long_description,
+    long_description_content_type="text/markdown",
+    
+    url="https://github.com/psy0rz/zfs_autobackup",
+    scripts=["bin/zfs-autobackup"],
+    packages=setuptools.find_packages(),
+    classifiers=[
+        "Programming Language :: Python :: 2",
+        "Programming Language :: Python :: 3",
+        "License :: OSI Approved :: GNU General Public License v3 (GPLv3)",
+        "Operating System :: OS Independent",
+    ],
+    python_requires='>=2.7',
+    install_requires=[
+        "colorama",
+        "argparse"
+    ]
+)
Author	SHA1	Message	Date
Edwin Eefting	8a960389d1	fix url for pypi	2020-03-31 20:01:28 +02:00
Edwin Eefting	c7cd73ae1f	Merge branch 'master' of github.com:psy0rz/zfs_autobackup	2020-03-31 19:33:26 +02:00
Edwin Eefting	c8c1d0fd27	transparancy	2020-03-31 19:33:09 +02:00
Edwin Eefting	c090979f3e	spelling and links	2020-03-31 19:23:04 +02:00
Edwin Eefting	3a4062c983	tried to clear up thinner documetion and output	2020-03-31 19:06:46 +02:00
Edwin Eefting	bcf73c6e5c	--min-change is now has 1 instead of 200000 as default. fixes #37	2020-03-29 23:47:26 +02:00
Edwin Eefting	9cf5ce188a	added thinner documentation. fixes #21	2020-03-29 23:23:47 +02:00
Edwin Eefting	a226309ce5	spelling	2020-03-29 23:22:18 +02:00
Edwin Eefting	231f41e195	update	2020-03-17 23:52:57 +01:00
Edwin Eefting	7c1546fb49	improved --rollback code. detect and show incompatible snapshots on target. added --destroy-incompatible option. fixes #34	2020-03-17 23:51:16 +01:00
Edwin Eefting	b1dd2b55f8	improved error logging	2020-03-17 19:55:16 +01:00
Edwin Eefting	4ed53eb03f	fix linter isue	2020-03-15 23:02:03 +01:00
Edwin Eefting	6f8c73b87f	rc7	2020-03-15 22:59:21 +01:00
Edwin Eefting	ee03da2f9b	exposed --min-change value as a parameter. (was hardcoded at 200000)	2020-03-15 22:54:14 +01:00
Edwin Eefting	e737d0a79f	improved example and cleaned up	2020-03-15 21:42:09 +01:00
DatuX	cbd281c79d	Merge pull request #32 from mariusvw/feature/ssh-keygen Feature/ssh keygen	2020-03-14 22:49:26 +01:00
Edwin Eefting	dfd38985d1	Merge remote-tracking branch 'remotes/mariusvw/feature/ssh-config'	2020-03-14 22:46:53 +01:00
DatuX	f1c15cec18	Merge pull request #30 from mariusvw/feature/issue-25 Issue #25, disable colors on non-tty	2020-03-14 22:15:43 +01:00
Edwin Eefting	1bc35f5812	explained splitting of jobs	2020-03-14 22:14:11 +01:00
Edwin Eefting	805a3147b5	added --no-send option. snapshots that are obsolete are now destroyed at the beginning of each dataset-transfer. this allows using --no-send as way to just thinout old snapshots. cleaned up stderr output when resuming.	2020-03-14 22:04:16 +01:00
Marius van Witzenburg	944435cbd1	Added another ssh-keygen example without passphrase	2020-03-09 10:16:40 +01:00
Marius van Witzenburg	022a7d75e2	Updated readme with ssh-keygen example	2020-03-09 10:13:48 +01:00
Marius van Witzenburg	14ac525525	Issue #25 , disable colors on non-tty	2020-03-08 23:55:07 +01:00
Marius van Witzenburg	3a45951361	Updated README	2020-03-08 23:16:37 +01:00
Marius van Witzenburg	2a300bbcba	Added support for custom ssh client config	2020-03-08 23:16:11 +01:00
Marius van Witzenburg	bdeb4c40fa	Cleanup whitespace	2020-03-08 23:05:49 +01:00
Marius van Witzenburg	e8b90abfde	Cleaned whitespace	2020-03-08 22:05:48 +01:00
Edwin Eefting	1d9c25d3b4	prevent emitting useless error messages in some cases when holding/release/destroying snapshots	2020-02-25 20:15:11 +01:00
Edwin Eefting	56d7f8c754	rc5	2020-02-25 18:41:04 +01:00
Edwin Eefting	ef5bca3de1	start at correct snapshot when full send	2020-02-25 18:35:35 +01:00
Edwin Eefting	3b2a19d492	migrate/other-snapshot feature almost done	2020-02-25 00:58:25 +01:00
Edwin Eefting	d2314c0143	imp is not used	2020-02-24 14:30:07 +01:00
Edwin Eefting	f3a80991c9	fix release stuff	2020-02-24 14:20:42 +01:00
Edwin Eefting	bd3321e879	actually set canmount=noauto instead of filtering it.	2020-02-23 23:36:34 +01:00
Edwin Eefting	55e18cc613	fix #18	2020-02-23 23:00:37 +01:00
Edwin Eefting	9d5534c11e	create snapshots per pool. fixes #20	2020-02-23 22:25:47 +01:00
Edwin Eefting	93d0823c82	fixes	2020-02-23 21:29:47 +01:00
Edwin Eefting	0285eb31a7	fixes	2020-02-23 21:27:01 +01:00
Edwin Eefting	4c4cd36f9f	get rid of the _ . its confusing	2020-02-21 18:16:22 +01:00
Edwin Eefting	9e8c6f7732	explained readonly property better	2020-02-20 09:40:50 +01:00
Edwin Eefting	f305f00d91	fix	2020-02-20 01:21:00 +01:00
Edwin Eefting	3e06a8e2fa	--buffer not suppoert (yet/anyomre)	2020-02-20 01:17:25 +01:00
Edwin Eefting	241716cf6d	clearer	2020-02-20 01:13:26 +01:00
Edwin Eefting	1b7f7fd140	added clearity	2020-02-20 01:09:13 +01:00
Edwin Eefting	2e3ce2168d	auto tag	2020-02-20 00:10:57 +01:00
Edwin Eefting	ef5a164774	merge v3 back to master	2020-02-19 23:59:00 +01:00
DatuX	a41644c84f	Update README.md	2020-02-19 23:44:57 +01:00
DatuX	0e9f68d754	Update README.md	2020-02-19 23:33:07 +01:00
Edwin Eefting	3ceb815432	loose the stupid underscore	2020-02-19 21:00:17 +01:00
Edwin Eefting	c3630ded45	url	2020-02-19 20:44:51 +01:00
Edwin Eefting	bf1f0fc35b	ready to release on pip	2020-02-19 20:43:34 +01:00
Edwin Eefting	6c168ff867	fix	2020-02-19 20:20:15 +01:00
Edwin Eefting	383a3669db	moore fixes	2020-02-19 20:19:02 +01:00
Edwin Eefting	d8fa868ce1	fixes	2020-02-19 20:14:52 +01:00
Edwin Eefting	1dd683c1e2	fix markup	2020-02-19 20:10:07 +01:00
Edwin Eefting	c6d45e4441	fixing	2020-02-19 19:41:07 +01:00
Edwin Eefting	24164fe215	cleaning up	2020-02-19 18:51:50 +01:00
Edwin Eefting	ec95bd127e	update version	2020-02-07 19:56:05 +01:00
Edwin Eefting	932ff7abe2	important bugfix: look at OUR snapshot instead of all snapshots when determining if we need a new snapshot	2020-02-07 19:55:16 +01:00
Edwin Eefting	e1e6a87eba	preparing for PyPi	2020-01-20 00:25:58 +01:00
Edwin Eefting	11608fdea7	be more forgiving when determing if a dataset is unchanged (if written-property is under 200.000 bytes, we assume its unchanged)	2019-12-11 12:48:44 +01:00
Edwin Eefting	ec1628a8ff	update version	2019-12-05 23:33:51 +01:00
Edwin Eefting	4f9a84536e	update	2019-12-05 23:32:56 +01:00
Edwin Eefting	a215b0fedc	support --raw, to backup encrypted filesystems	2019-12-05 23:25:43 +01:00
Edwin Eefting	793f87d6a9	tip	2019-11-27 10:34:16 +01:00
Edwin Eefting	0b996f239f	fix	2019-11-13 22:34:48 +01:00
Edwin Eefting	881e6f7b89	ignore "skipping snapshot" output when using --progress	2019-11-13 12:32:13 +01:00
DatuX	17445ec54a	Update README.md	2019-11-10 01:16:48 +01:00
DatuX	07a150618a	Update README.md	2019-11-10 01:01:08 +01:00
DatuX	067f3b92d1	Update README.md	2019-11-10 00:51:20 +01:00
Edwin Eefting	71a394cfc7	rollback	2019-10-19 14:54:10 +02:00
Edwin Eefting	bfc36ac87f	rollback	2019-10-19 14:53:31 +02:00
Edwin Eefting	ad47b26f56	Revert "fixing quota issues" This reverts commit `d973905303`.	2019-10-17 10:42:54 +02:00
Edwin Eefting	f38da17592	v3.0: no longer replicate all properties by default. this made things unnecessary complicated. now use the --properties option to specify the properties you want.	2019-10-16 13:37:31 +02:00
Edwin Eefting	d973905303	fixing quota issues	2019-10-16 12:51:12 +02:00
Edwin Eefting	82465acd5b	clearification of testmode	2019-10-16 10:27:35 +02:00
Edwin Eefting	514131d67c	update docs	2019-10-16 09:45:08 +02:00
Edwin Eefting	dfcae1613b	clearify the target path is a zfs filesystem, not an regular path	2019-10-16 09:43:28 +02:00
DatuX	67b21b4015	bugfix: exitcode always was 255	2019-10-16 09:28:21 +02:00
DatuX	3907c850a6	Update zfs_autobackup	2019-10-02 22:58:50 +02:00
Edwin Eefting	3b9b96243b	dont destroy stale snapshots if we're using --ignore-replicated	2019-10-02 19:39:31 +02:00
Edwin Eefting	54235f455a	zfs_autobackup 2.4: try to continue on non-fatal errors	2019-10-02 18:21:24 +02:00
DatuX	c176b968a9	forgot to return exit code when not using debug mode :(	2019-03-26 23:06:03 +01:00
Edwin Eefting	921f7df0a5	updated readme	2019-02-19 11:24:10 +01:00
Edwin Eefting	edee598cf8	updated readme	2019-02-19 11:19:16 +01:00
Edwin Eefting	80b3272f0f	disable destroy-stale for now. updated readme	2019-02-19 11:09:54 +01:00
Edwin Eefting	617e0fb69b	fix/revisit stale filesystem detection	2019-02-19 11:04:59 +01:00
Edwin Eefting	46a85fd170	updated readme	2019-02-19 10:26:52 +01:00
Edwin Eefting	1f59229419	fixes	2019-02-19 01:28:22 +01:00
Edwin Eefting	fcd98e2d87	much cleaner output and layout. removed useless error output. general cleanup.	2019-02-19 00:17:20 +01:00
Edwin Eefting	dd8b2442ec	options for proxmox HA: no-holds, ignore-new and ignore-replicated	2019-02-18 18:53:54 +01:00
Edwin Eefting	291040eb2d	obsolete, now that we have resume support in zfs	2019-02-16 22:28:15 +01:00
Edwin Eefting	d12a132f3f	added buffering	2019-02-16 21:51:30 +01:00
Edwin Eefting	2255e0e691	add some performance options	2019-02-16 21:00:09 +01:00
Edwin Eefting	6a481ed6a4	do not create snapshots for filesystems without changes. (usefull for proxmox cluster that use internal replication)	2019-02-16 20:30:44 +01:00
Edwin Eefting	11d051122b	now hold important snapshots to prevent accidental deletion by administrator or other scripts	2019-02-16 02:06:06 +01:00
Edwin Eefting	511311eee7	nicer error output. you can also set autobackup:blah=child now, to only select childeren (recursively) of the dataset	2019-02-16 00:38:30 +01:00
Edwin Eefting	fa405dce57	option to allow ignoring of transfer errors. this will still check if the filesystem was received. i used it to ignore a bunch of acltype property errors on smartos from proxmox.	2019-02-03 21:52:59 +01:00
DatuX	bf37322aba	Update README.md	2019-02-03 21:07:48 +01:00
Edwin Eefting	a7bf1e8af8	version bump	2019-02-03 21:05:46 +01:00
Edwin Eefting	352c61fd00	Merge branch 'master' of github.com:psy0rz/zfs_autobackup	2019-02-03 21:04:53 +01:00
Edwin Eefting	0fe09ea535	use ~/.ssh/config for these options	2019-02-03 21:04:46 +01:00
DatuX	64c9b84102	Update README.md	2019-02-03 21:00:39 +01:00
DatuX	8a2e1d36d7	Update README.md	2019-02-03 20:59:16 +01:00
DatuX	a120fbb85f	Merge pull request #11 from psy0rz/revert-9-feature/ssh-mux Revert "Feature/ssh mux"	2019-02-03 20:57:44 +01:00
DatuX	42bbecc571	Revert "Feature/ssh mux"	2019-02-03 20:57:00 +01:00
Edwin Eefting	b8d744869d	doc	2019-02-03 20:56:45 +01:00
Edwin Eefting	c253a17b75	info	2019-02-03 20:38:26 +01:00
Edwin Eefting	d1fe00aee2	Merge branch 'master' of github.com:psy0rz/zfs_autobackup	2019-02-03 20:23:52 +01:00
DatuX	85d2e1a635	Merge pull request #9 from mariusvw/feature/ssh-mux Feature/ssh mux	2019-02-03 20:23:44 +01:00
Edwin Eefting	9455918708	update docs	2018-06-07 14:08:59 +02:00
Edwin Eefting	5316737388	update docs	2018-06-07 14:06:16 +02:00
Edwin Eefting	c6afa33e62	option to filter properties on zfs recv	2018-06-07 14:01:24 +02:00
Marius van Witzenburg	a8d0ff9f37	Restored stderr handing to previous state	2018-04-05 18:05:10 +02:00
Marius van Witzenburg	cc1725e3be	Compacted code bit into a function	2018-04-05 10:01:23 +02:00
Marius van Witzenburg	42b71bbc74	Write STDERR to STDOUT	2018-04-05 10:00:53 +02:00
Marius van Witzenburg	84d44a267a	Exit persistent connection when everything is finished	2018-04-05 09:23:59 +02:00
Marius van Witzenburg	ba89dc8bb2	Use persistent connections for 600 seconds (10min)	2018-04-05 09:23:39 +02:00
Marius van Witzenburg	62178e424e	Added argument to return exit code	2018-04-05 09:23:08 +02:00
Edwin Eefting	b0ffdb4893	fix: atomic snapshots can only be created per pool. now uses a seperate zfs snapshot command for each pool	2018-03-06 15:54:00 +01:00
DatuX	cc45122e3e	Update zfs_autobackup not needed module	2018-03-06 15:03:30 +01:00
Edwin Eefting	e872d79677	conflicting name	2017-09-25 13:46:20 +02:00
DatuX	e74e50d4e8	Update README.md	2017-09-20 10:28:34 +02:00