The plan for the next release is to make a release candidate because the changes are mostly everywhere in the code. Due to too much (but interesting) work in my job and now surprisingly health problems in my family I'm not able to seriously plan a schedule for that release candidate. Maybe in some months!?

Next release will (hopefully) support the following (among others):
- use other checksums than md5 (this seems to work, but conversion of existing backups from <checkSum1> to <checkSum2> (eg. from md5 to shar256) is not yet ready.
- parallel replication to different targets (nothing done, but shouldn't be too difficult)
- running a backup without access (especially write access) to previous backups. (A cacker on your fileserver can delete your data and also your backups (except replications). The solution to this problem is very simple and already possible now with some scripts.)

Ok, I tried with END and it seems to work.
It's called in END only if it didn't run before in the normal way (like now).

Will be included in the next release.

Thank's for the hint(s),
Heinz-Josef

I think there are arguments for both behaviors. But - simply - it would be very time consuming and maybe difficult to change this behavior.

So there are no plans to change it in the foreseeable future.