On Thu, Oct 11, 2012 at 12:34 AM, Robert E. Wooden <rbrtewdn@comcast.net> wrote:
I ran "admin@wdnbkup01:~$ sudo -u backuppc rsync -aP root@[myclientip]:/tmp /tmp/client
[sudo] password for admin:
receiving incremental file list
created directory /tmp/client

I was hoping for some kind of informative failure.  But we got none.  That rules out the .ssh keys and any obvious mis-configurations.

When you rund "BackupPC_dump" part of what it runs is an rsync server on the client to be backed up.   The rest of the script is a perl based rsync receiver.

backuppc 32396 24278  2 09:31 ?        00:00:00 /usr/bin/perl /usr/share/BackupPC/bin/BackupPC_dump -i hostname
backuppc 32406 32396  0 09:31 ?        00:00:00 /usr/bin/ssh -q -x -l root hostname /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group -D --links --hard-links --times --block-size=2048 --recursive . 

This is where my knowledge breaks down  BackupPC_dump tries to talk to the "rsync --server..."   running on the client, but in your case it is failing.  In our environment that's usually because the client disconnects from the network before any data is transferred.  (We backup a lot of laptops that wander around).   You'll have to see if there's any evidence that the client becomes "unavailable" after a backup is started.   Also check that the 'rsync --server' is actually getting started on the client.

Ray Frush               "Either you are part of the solution
T:970.288.6223               or part of the precipitate."
 Avago Technologies, Inc. | Technical Computing | IT Engineer