Releases: someone1/zfsbackup-go
Releases · someone1/zfsbackup-go
Bookmarks and more
New Features/Changes:
- All backends: Fix prefix usage if found in target URI
[backend-prefix]://[bucket]/[prefix:optional]
- B2 Improvements:
- Azure Improvements:
- Support
zfs send -c
flag to leverage existing compression on a pool/dataset 725c6b7 (thanks @pablofsf!) - Add support for ZFS bookmarks 039bcc7
- Support Encryption, Sign, and Encryption + Sign option combinations (7793275)
- [Breaking Change] Use Public keyring when performing encrypted backups 43903b9 (thanks @bobobo1618!)
- Refactor of codebase f8959f7
- Refactor to better organize code
- Updated to support latest version of Go and use Go modules for dependency management
- Additional tests added
- Fix misc. typos
- Update CI configuration
- Don't show usage on error return
- Fixed PGP key selection issue - passphrase no longer required for encryption sends (except smart backups)
Release Candidate 1
This release brings support for both Azure Blob and Backblaze B2 targets. This release also comes with a lot of test coverage and with the existing production use-cases, this release is being taken out of "pre-release" status.
Other enhancements:
- Fixed race bugs
- Fixed handling of
-o origin=
flag during restores - Added logging and better error handling
- Added ability to filter results of
list
command - Added JSON output option
- Added option to tweak the upload chunk size used when backing up
- Removed verify command - overlaps with
list
command - Force all manifests to use internal compression [BREAKING CHANGE]
Smart Restores and more!
This release brings smart restore options! Now you can restore to snapshots more easily than having to do a series of manual restore requests.
Other enhancements:
- Moved to multipart uploads for AWS S3
- Added test coverage for backends to test for correctness
- Added lock files to ensure that a dataset is only being operated on by a single instance of this application (e.g. if this is run in a cronjob and a backup procedure is taking longer than the next scheduled execution of the cronjob, it will block execution)
- Cleans up error handling throughout and removed all explicit panics
- Some refactoring and fixed a few bugs
- Proper removal of temp directories
Initial Release
This release is featured enough for practical use cases. Looking for feedback from users.