Releases: oetiker/znapzend
Releases · oetiker/znapzend
The Protector
- do not destroy src snapshots if something went wrong while backing up
- add support for %z in tsformat
- better zfs on linux support
- updated perlmodules included with package
A Great Release, trust me!
- Improved pre/post send and receive commands
- make daemon NOT abort even if there is no configuration found
- change smf dependency to multi-user so that iscsi is running
In the Light of Dawn
Bugfixes
- autocreate working properly ... finally (?)
New
- ubuntu upstart script
- per destination pre and post SEND commands (complementary to the pre and post snap commands)
- send delay property
The Fat Pack
- improved systemd integration
- new fat release so that znapzend dependencies can be built without internet access
- better osx portability
- sudo/pfexec fixes
- no more multiline error messages
0.15.7 makes --autoCreation actually work ...
KetchUp
push it, push it, push it some more
- build dependencies directly with make
- optionally prefix pfexec|sudo to zfs|zpool|test comands
- set mbuffer timeout to 60 seconds this might help with timeout situations seen on solaris
- fix string replacement in manifest file
- let smf manage pids instead of a pid file
Can you hear the drums?
- if you want znapzend to reload your config, kill -HUP will do the trick
- improved handling of TERM for a graceful shutdown
- new option for znapzend: --connectTimeout=x
Facing The Truth III
- exception handling for more stable behaviour in case of trouble
- new --features=recvu to make the filesystems non mounted at the receive end
- new --features=oracleMode to activate things we put in just to make znapzend work on oracle zfs
- improved output from znapzendztatuz
0.12.2
- don't throw and exception object, just die
0.12.3
- import missing blessed test for handling exception objects
Reading Corrupts the Mind
- fix pid handling
- only use mbuffer port when working on remote destinations
Speed is of the Essence
- specify a port number with the --mbuffer option and your data will be transferred directly from mbuffer to mbuffer (unencrypted) but very fast.
--mbuffer=/path/to/mbuffer:some-port-number
- better logging (less chatty at info level)
- more robust handling of pid files