github psy0rz/zfs_autobackup v3.0

latest releases: v3.3-rc1, v3.3-beta3, v3.3-beta2...
4 years ago

This is the first v3.0 stable release. No changes since v3.0-rc12.

Recent changes in release candidates:

  • Snapshots will always be made, even if target host/dataset cant be contacted.
  • Now usable as a snapshot tool, without needing to specify target-path.
  • Can now destroy missing source-dataset on target (--destroy-missing)
  • Also display dataset-name on stderr when there's an error.
  • Closed all milestone issues of 3.0 release. This might be it the final v3.0 release :)
  • Completed regression testing, fixes #49
  • Added detection of pool features, and automatic resume support (--resume option not needed anymore)
  • Removed soon to be deprecated zfs recv -D option.
  • Various small fixes (stale filehandles etc)
  • Fix: common snapshot could get deleted. (this happend due to a recent change in zfs-autobackup)
  • Also thin out target-datasets that dont exist on the source anymore.
  • Fix: Return correct error code, indicating the number of failed datasets.
  • Fix: Flush all outputs to make sure stdout and stderr are synced.
  • Automaticly enable --progress if output is a TTY.
  • exposed --min-change value as a parameter. (was hardcoded at 200000)
  • Issue #25, disable colors on non-tty
  • 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.
  • Added support for custom ssh client config
  • Improved --rollback and incompatible snapshot detection. added --destroy-incompatible.
  • --min-change is now has 1 instead of 200000 as default. fixes #37
  • added thinner documentation and cleared up thinner output texts.

Don't miss a new zfs_autobackup release

NewReleases is sending notifications on new releases.