On 7/24/08, Ward... James Ward <jeward AT torzo DOT com> wrote:

-rwxr-x--- 1 root   root 205 2007-05-12 15:21 ADPass

-rwxr-x--- 1 root   root 193 2008-07-21 12:33 createWin

-rwxr-xr-x 1 jeward dev  465 2007-06-20 15:56 ldap2mail

-rwxr-x--- 1 root   root 977 2008-06-02 14:14 setWin

-rwxr-x--- 1 root   root 636 2008-07-24 09:44 shutdownWin

Let me start by taking a wild guess and assume you are using rsyncd.  The system your are backing up is *nix based and you don't have a uid=0, gid=0 in your module definition for /etc/rsyncd.conf.  If that's all true (or maybe at least most of it), then the system is working as designed, but not how you intended.  "rsync" sets uid=gid=-2 when placed in daemon mode.  This means that it can only read or write things readable/writable by the user "nobody".  Trust me, its for your own protection :-) 

The file that is showing up in your list is world "readable" while all the others aren't.  Check your Xferlogs and you should see a bunch of permissions errors (number 13 appears on those lines).  Go fix your rsyncd.conf, restart the daemon, and take a fresh backup of all the affected systems as their current backups are dubius at best.  I believe that all the files that were backed up are perfectly fine as rsync captures the permissions and BackupPC stores them in the "attrib" files sprinkled throughout your backup archive directory structure.  If its not this, then please provide some more details surrounding your configuation (config.pl, [host].pl, rsyncd.conf, all properly scrubbed for passwords and hostname details).

I would also suggest that you get a chance to excersize the recovery functions so that you know how they work and that they do in fact work.  Without the uid=0 you would have been unable to restore files with the proper owner/group/perms (they would have come back as user "nobody" I believe).  Don't forget to set the "read _only_ = false" for the module when you intend to restore.

--
Jonathan Craig