this email is to Sean M. Kaiser skaiser at northmont.k12.oh.us
post was: Tue Feb 24 23:38:32 GMT 200
hi,
did you get a solution for the --backup-dir problem (stat error
messages)?
I ran into the same thing...
Thanks
Christian
the original message was:
>
>
> I am having a problem with implementing a slight modification of the
> "backup to a central backup server with 7 day incremental"
example from
> <http://rsync.samba.org/examples.html>. When rsync runs, I end up
> getting
> stat errors that the file doesn't exist in the backup-dir location.
> The
> backup server is running rsyncd, and without the --backup and
> --backup-dir
> options set, I get a good clean backup.
>
> I'm also not quite clear on the fact that from the stat error messages
> (below), the --backup-dir option is not clearing the --suffix option as
> stated in the man page. I'm thinking maybe I have an issue somewhere
> involving the --backup-dir option.
>
> My rsync command looks like this (from tonight's attempts):
>
> backup: command /usr/bin/rsync --force --ignore-errors
> --delete-excluded
> --exclude-from=/etc/rsync/exclude.txt --delete --backup
> --backup-dir=/tue
> -a --eahfs --numeric-ids --password-file=/etc/rsync/secure.txt --stats
> --delete-after --bwlimit=120 -z / puma at rsyncserver::puma/current
>
> The stat error messages look like this (snipped for bandwidth
> considerations):
>
> stat "tue/private/var/db/dhcpd_leases~" (in puma) failed: No such
file
> or
> directory
> stat "tue/private/var/log/cups/access_log~" (in puma) failed: No
such
> file
> or directory
> stat "tue/private/var/log/cups/access_log.O~" (in puma) failed:
No such
> file or directory
> stat "tue/private/var/log/daily.out~" (in puma) failed: No such
file or
> directory
> stat "tue/private/var/log/diskspacemonitor.log~" (in puma)
failed: No
> such
> file or directory
> stat "tue/private/var/log/mail.log~" (in puma) failed: No such
file or
> directory
> stat "tue/private/var/log/system.log~" (in puma) failed: No such
file
> or
> directory
> stat "tue/private/var/log/system.log.0.gz~" (in puma) failed: No
such
> file
> or directory
>
> The module root for the above module looks like this (via ls -al):
>
> drwxr-xr-x 8 root admin 272 Feb 12 13:27 .
> drwxrwx--- 16 root admin 544 Feb 20 11:38 ..
> drwxrwxr-t 24 root admin 816 Feb 2 11:24 current
> drwxr-xr-x 2 root wheel 68 Feb 20 16:15 fri
> drwxr-xr-x 2 root wheel 68 Feb 23 16:15 mon
> drwxr-xr-x 2 root wheel 68 Feb 19 16:15 thu
> drwxr-xr-x 2 root wheel 68 Feb 24 16:15 tue
> drwxr-xr-x 2 root wheel 68 Feb 18 16:15 wed
>
> The rsyncd.conf file section for the above module is:
>
> logfile = /var/log/rsyncd.log
> pidfile = /var/run/rsyncd.pid
> lockfile = /var/run/rsyncd.lock
> secrets file = /etc/rsyncd.secrets
> uid = root
> transfer logging = no
>
> [puma]
> path = /Volumes/backups/xserves/puma
> comment = Puma Xserve backup space
> auth users = puma
> read only = no
>
> The --stats output provides:
>
> Number of files: 62552
> Number of files transferred: 38
> Total file size: 1522090824 bytes
> Total transferred file size: 3095727 bytes
> Literal data: 2152606 bytes
> Matched data: 951076 bytes
> File list size: 2828136
> Total bytes written: 2961050
> Total bytes read: 25891
>
> wrote 2961050 bytes read 25891 bytes 7649.02 bytes/sec
> total size is 1522090824 speedup is 509.58
> rsync error: some files could not be transferred (code 23) at
> main.c(639)
> backup: rsync complete from puma at Tue Feb 24 16:21:34 EST 2004,
> status=23
>
> I am running 2.6.0 (via RsyncX 2.0 for Mac OS X) on Mac OS X servers
> (10.2.8 on both ends).
>
> Any assistance is greatly appreciated. I have searched the archives
> and
> faq-o-matic and can't seem to find anything.
>
> Sean
