Releases: psy0rz/zfs_autobackup
Releases · psy0rz/zfs_autobackup
v3.3-rc1
Some major changes in this version:
- Mounting is now more consistent after initial dataset transfer: Previously newly received datasets would never be mounted. In this version a dataset will be mounted according to the same logic as a zfs mount -a. #112 Also see https://github.com/psy0rz/zfs_autobackup/wiki/Mounting
- Empty parent datasets that are created will now have canmount=off. Previously they would be created with on.
- The guid of common snapshots is now checked, and mismatching ones can be destroyed by --destroy-incompatible. (#218)
- --rollback is now only run at the start of an actual transfer. #217 (previously all target datasets where rolled back always when --rollback was specified)
- #264: Snapshot exclude patterns
- Reduced verbosity and improved output.
- A bunch of other bugfixes and improvements.
Note that we now have a v3.4 branch that has some major internal improvements to prepare for bookmarks and other features. Please test that version as well if you're daring :)
v3.3-beta3
Some major changes in this version:
- Mounting is now more consistent after initial dataset transfer: Previously newly received datasets would never be mounted. In this version a dataset will be mounted according to the same logic as a zfs mount -a. #112 Also see https://github.com/psy0rz/zfs_autobackup/wiki/Mounting
- Empty parent datasets that are created will now have canmount=off. Previously they would be created with on.
- The guid of common snapshots is now checked, and mismatching ones can be destroyed by --destroy-incompatible. (#218)
- --rollback is now only run at the start of an actual transfer. #217 (previously all target datasets where rolled back always when --rollback was specified)
- Reduced verbosity and improved output.
- A bunch of other bugfixes and improvements.
v3.2.2
New in v3.2:
- --help output is split up in nice sections now.
- Moved documentation to wiki and split it up.
- Allow non-recursive selection of datasets by setting autobackup:name=parent. (usefull for /var/lib/docker)
- Some major internal class restructuring. (shouldn't affect functionality)
New tools, still in progress:
- zfs-check: a tool to generate checksum streams of zfs datasets, to compare datasets with eachother. (Will be used in conjuction with zfs-autoverify) This still has issue #176 and #206
- Note that zfs-check can also be used on regular directories or files
- Prepared for zfs-autoverify tool to actually verify your backups. (this took some refactoring and extracting common code to a ZfsAuto baseclass) Still work in progress.
v3.2-beta1
New in v3.2 so far:
- --help output is split up in nice sections now.
- Moved documentation to wiki and split it up.
- Created zfs-check, a tool to generate checksum streams of zfs datasets, to compare datasets with eachother. (Will be used in conjuction with zfs-autoverify)
- Started working on an zfs-autoverify tool to actually verify your backups. (this took some refactorring and extracting common code to a ZfsAuto baseclass) Still work in progress.
- Allow non-recursive selection of datasets by setting autobackup:name=parent. (usefull for /var/lib/docker)
v3.1.3
v3.1.2
v3.2-alpha2
- --help output is split up in nice sections now.
- Moved documentation to wiki and split it up.
- Created zfs-check, a tool to generate checksum streams of zfs datasets, to compare datasets with eachother. (Will be used in conjuction with zfs-autoverify)
- Started working on an zfs-autoverify tool to actually verify your backups. (this took some refactorring and extracting common code to a ZfsAuto baseclass) Still work in progress.
v3.1.2-rc2
v3.1.2-rc1
v3.2-alpha1
(This alpha release is just to allow me to test it with real world data, dont use it)
- --help output is split up in nice sections now.
- Moved documentation to wiki and split it up.
- Started working on an zfs-autoverify tool to actually verify your backups. (this took some refactorring and extracting common code to a ZfsAuto baseclass) Still work in progress.