Thanks for the detailed information. Sorry about the delay in replying.
No worries on the delay, I'm just trying to help track down the issues to help squash any potential bugs, either in my implementation (which may help others) or in the code.
To clarify your second email, do rsync backups now work correctly? The rsync_bpc commands in your original email look correct - it appeared for some reason that the ssh to the backup client was failing for some reason. Perhaps there was some other orphan setting that was causing a problem.
This could be, but yes, they do seem to be working properly now which is a plus. :) I should have trimmed down the set of client machines, as it is taking a lot of time moving backups to v4 format and such while simultaneously trying to backup some other systems. But I thought it was a good stress test, I just have to be more patient to see the results.
Good point on rsync in MacOSX. 2.6.9 is almost 7 years old.
Thankfully it is easy to push a new binary out to all the remote systems, so this is just something to put in the upgrade/install notes for v4 as a warning.
I'd like to learn more about the empty download for zip and tar. Were you selecting files from a old (pre-4.x) backup, or a new (4.x) backup?
They were from a pre-v4 backup
How many files did you select? A couple of individual files, or an entire directory?
I was viewing the contents of a directory and selected all the individual items in there, ~260 items.
I will continue to post back information as I find it, but things are looking much better now after I adjusted my client configurations. I am very thankful for all the hard work you have put into this, and I just wanted to give you some feedback on an upgrade in an active environment. v4 is going to be great!
As an aside, since v4 will no longer be using so many hard links, my assumption is that backup of the pool to tape via bacula or something else will also be magnitudes easier?