better to exclude at daemon/server or client
Quick question, Is there a difference if an --exclude-from (or just plain --exclude) is specified on the daemon or the client? I'm setting up daemons on each of my remote servers, and have a host with a RAID connected to it be the client to pull the data over the network. I'm wondering if there is a difference in memory usage, speed, etc. by specifying the excluded files on one side or the other. Thanks, Sean Kaiser -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Bad address error
I'm getting a bad address error which is causing my rsync process to bomb out. I'm running RsyncX 2.1, in daemon mode on the source machine, with a script to pull the information to the backup server. Both servers are Xserves running OS X Server 10.2.8. Rsync target is on an Xserve RAID. The RAID has 350GB free, so I'm not running into a disk full situation. My command looks like: /usr/local/bin/rsync -a --ignore-errors --exclude-from=/Volumes/backups/extras/rsync/config/exclude.txt --password-file=/etc/rsync/secure.txt --stats --eahfs --backup --backup-dir=/Volumes/backups/archives/cougar/week/tue/Users/Staff/ --delete --bwlimit=2000 -z [EMAIL PROTECTED]::rsync/Users/Staff/ /Volumes/backups/current/cougar/Users/Staff/ The error that causes the process to stop, along with the rsync stop message, is: stat /Volumes/backups/archives/cougar/week/tue/Users/Staff/bcooper/Documents/Desktop Folder failed: No such file or directory write failed on /Volumes/backups/current/cougar/Users/Staff/bcooper/Documents/Desktop Folder: Bad address rsync error: error in file IO (code 11) at receiver.c(324) rsync: connection unexpectedly closed (761151 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) Any help is greatly appreciated. Thanks, Sean -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: --backup requires remote connection?
Wayne Davison [EMAIL PROTECTED] writes: On Fri, Apr 30, 2004 at 04:19:35PM -0400, Sean M. Kaiser wrote: [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup --backup-dir=/Users/localskaiser/archive -a /Users/localskaiser/source /Users/localskaiser/target This command works fine for me when used as you described. stat /Users/localskaiser/archive/source/a/b/c/newfile.txt failed: No such file or directory I assume that message is coming from the code set_perms() code that is trying to change the permissions on the newly-created backup file. So, something may have gone wrong during the creation of that backup file. Check the permissions and such for the backup path (though it's weird if rsync didn't display some other error before the stat one). [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup --backup-dir=/Users/localskaiser/archive -a [EMAIL PROTECTED]::skaiser/current /Users/localskaiser/target That command uses a different backup dir: .../archive/current rather than .../archive/source. ..wayne.. Wayne, Here's another test. Information now looks like: source = /Applications (permissions: owner=root, group=admin, 775) target = /Volumes/backups/current/leopard (permissions: owner=root, group=admin, 775) backup-dir = /Volumes/backups/archives/leopard/week/mon (permissions: owner=root, group=admin, 777) I created a file (temp) in the source, ran rsync (command below), which backed it up. Then I removed it, and ran rsync again, and get the error. I'm running rsync as root (sudo -s to get a root shell) each time. It looks to me like it's not creating the folder hierarchy inside the backup-dir location. /usr/bin/rsync -vv -a --stats --eahfs --backup --backup-dir=/Volumes/backups/current/leopard/../../archives/leopard/week/mon --delete -z /Applications /Volumes/backups/current/leopard building file list ... expand file_list to 4000 bytes, did move expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move done expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move expand file_list to 4000 bytes, did move expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move deleting in Applications backup_dir is /Volumes/backups/current/leopard/../../archives/leopard/week/mon stat /Volumes/backups/current/leopard/../../archives/leopard/week/mon/Applications/temp failed: No such file or directory keep_backup Applications/temp - /Volumes/backups/current/leopard/../../archives/leopard/week/mon/Applications/temp deleting Applications/temp The same thing happens when I use the command: /usr/bin/rsync -vv -a --stats --eahfs --backup --backup-dir=../../archives/leopard/week/mon --delete -z /Applications /Volumes/backups/current/leopard building file list ... expand file_list to 4000 bytes, did move expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move done expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move expand file_list to 4000 bytes, did move expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move deleting in Applications backup_dir is ../../archives/leopard/week/mon stat /Volumes/backups/current/leopard/../../archives/leopard/week/mon/Applications/temp failed: No such file or directory keep_backup Applications/temp - ../../archives/leopard/week/mon/Applications/temp deleting Applications/temp Another run, with yet another way (in my eyes) to specify the backup-dir: /usr/bin/rsync -vv -a --stats --eahfs --backup --backup-dir=/Volumes/backups/archives/leopard/week/mon --delete -z /Applications /Volumes /backups/current/leopard building file list ... expand file_list to 4000 bytes, did move expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move done expand file_list to 8000 bytes, did move expand file_list to 16000 bytes, did move expand file_list to 32000 bytes, did move expand file_list to 64000 bytes, did move expand file_list to 128000 bytes, did move expand file_list to 4000 bytes, did move expand
--backup requires remote connection?
Does the --backup, --backup-dir set require that either then source or target be a remote connection? Test folder hierarchy: /Users/localskaiser/source/myfile.txt /Users/localskaiser/source/a/b/c/newfile.txt /Users/localskaiser/target /Users/localskaiser/archive I can not get the following command to work (after running it once, and then modifying newfile.txt): [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup --backup-dir=/Users/localskaiser/archive -a /Users/localskaiser/source /Users/localskaiser/target stat /Users/localskaiser/archive/source/a/b/c/newfile.txt failed: No such file or directory rsync error: some files could not be transferred (code 23) at main.c(639) However, this command works (after running it once, and then modifying newfile.txt): [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup --backup-dir=/Users/localskaiser/archive -a [EMAIL PROTECTED]::skaiser/current /Users/localskaiser/target I am running RsyncX 2.1 (rsync 2.6.0 protocol version 27) on both the local and rsync server machines. Thanks, Sean Kaiser -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync incremental backup probs
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 / [EMAIL PROTECTED]::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 -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
