On Jun 18, 2008, at 9:34 AM, Peter Wilkinson wrote:

> This is very appealing and timely. Other than somehow flagging when
> packs have been done on the source database it would seem to be
> quite usable. Have you done tests to see what happens when an --
> append is run when the content has changed earlier in the file than
> the destinations end? Is the keeping of that inline left up to the
> driver?


I haven't tested anything except the basic operation of this.
If, between two runs of rsync3 with --append, the database is packed
and subsequently grows larger than
it was on the last run of rsync3, I think the --append would produce a
bad backup file.
If you run it with --append at high frequency, the probability of this
is situation is low,
but not zero.
That's where the extra time spent by --append-verify would be justified.

I suppose you could also run an rsync on the log and run rsync with --
append-verify
when you see new Pack log messages.