Re: copying mailboxes

On Wed 02 Aug 2006, Drew Weaver wrote: > conversion. Is it possible to do a incremental rsync on an entire > directory? Say rsync /var/spool/mail on one machine to /test which is > /var/spool/mail (nfs) on another machine? Note that it's much more efficient to rsync to the system where the data i

Re: Behaviour that I don't understand

On Wed 02 Aug 2006, Alan Chandler wrote: > The /etc/rsyncd.conf file has the following in it > > chroot = false > strict modes = false > hosts allow = 192.168.0.0/24 127.0.0.1 > > [system] > path = /cygdrive/c > comment = the complete c drive > > > [alan] > path = /cygdrive/c/Documents and S

Backup Exchange mailboxes using rsync

Hi all, Has anyone got any advice on the best way to backup Exchange mailboxes (Exchange 5.5) running on a Windows 2000 server? We already use rsync on a number of other Windows boxes for general file backup. I've read that even if you get backups of the Exchange mailbox files, then it's rea

Re: Backup Exchange mailboxes using rsync

Hello Reuben, Exchange database files are lock. You have several options. 1) The easy one is to backup exchange to the local disk using ntbackup and then the rsync the backup file. 2) Stop Exchange, rsync the files and then start it. The drawback is that you will have dowm time. Th

RE: code 12 error when specifying files

Matt, That works brilliantly, but I think I'm still doing something wrong. rsync --exclude="*" --include=".*" -Lputzogv [EMAIL PROTECTED]::folder /home/user/folder result: client: nothing to do: perhaps you need to specify some filenames or the --recursive option? I've also tried adding trai

Re: code 12 error when specifying files

On Thu 03 Aug 2006, Erik Jacobs wrote: > > That works brilliantly, but I think I'm still doing something wrong. > > rsync --exclude="*" --include=".*" -Lputzogv [EMAIL PROTECTED]::folder > /home/user/folder > > result: > client: nothing to do: perhaps you need to specify some filenames or the

RE: code 12 error when specifying files

Paul, Almost all permutations of trailing slashes and no trailing slashes seem to produce the same results... rsync --exclude="*" --include=".*" -Lputzogv [EMAIL PROTECTED]::folder/ /home/user/folder skipping directory . client: nothing to do rsync --exclude="*" --include=".*" -Lputzogv [EMAIL

RE: code 12 error when specifying files

On Thu, 3 Aug 2006, Erik Jacobs wrote: Paul, Almost all permutations of trailing slashes and no trailing slashes seem to produce the same results... I have to agree, I see the same behavior when using rsyncd transport instead of ssh transport (as Erik is): trailing slashes seem to be ignored

Re: code 12 error when specifying files

On Thu 03 Aug 2006, nathan r. hruby wrote: > > I have to agree, I see the same behavior when using rsyncd transport > instead of ssh transport (as Erik is): trailing slashes seem to be > ignored, and instead of directory contents, you get the directory name. >From the manpage: Note also that

RE: code 12 error when specifying files

# {***user***}/home/user> rsync --version rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal

RE: Backup Exchange mailboxes using rsync

Title: RE: Backup Exchange mailboxes using rsync Hi, I am not an Exchange expert, so I may have it totally wrong, but what I do is to have the ntbackup doing an online Exchange backup, then rsync this to another server over SSH.  If you do a rsync of the Exchange DB, you would have to do an

Re: code 12 error when specifying files

BTW, I see no difference when using an rsync daemon or an ssh connection, with the given problem: remote# mkdir /tmp/test; cd /tmp/test; touch a b c .a .b .c remote# ls -la total 0 drwxr-xr-x 2 root root 57 Aug 3 15:06 . drwxrwxrwt 3 root root 80 Aug 3 15:05 .. -rw-r--r-- 1 root root 0 Aug

Re: code 12 error when specifying files

On Thu, 3 Aug 2006, Paul Slootman wrote: On Thu 03 Aug 2006, nathan r. hruby wrote: I have to agree, I see the same behavior when using rsyncd transport instead of ssh transport (as Erik is): trailing slashes seem to be ignored, and instead of directory contents, you get the directory name.

Re: code 12 error when specifying files

On Thu, 3 Aug 2006, nathan r. hruby wrote: For example, for module x with path set to /home, tying to sync the contents of "server::home/user1/public_html/" yields me the directory public_html, the the files within it. s/::home/::x/ Someday I'll learn to type like a big person :) -n -- -

Re: code 12 error when specifying files

On Thu 03 Aug 2006, nathan r. hruby wrote: > > > >>From the manpage: > > > > Note also that host and module references don't require a trailing > > slash to copy the contents of the default directory. > > > >So in this case the trailing slash wouldn't make a difference. > > In my case I'm

Re: Behaviour that I don't understand

Paul Slootman writes: On Wed 02 Aug 2006, Alan Chandler wrote: The /etc/rsyncd.conf file has the following in it chroot = false strict modes = false hosts allow = 192.168.0.0/24 127.0.0.1 [system] path = /cygdrive/c comment = the complete c drive [alan] path = /cygdrive/c/Documents a

Re: code 12 error when specifying files

On Thu, 3 Aug 2006, Paul Slootman wrote: On Thu 03 Aug 2006, nathan r. hruby wrote: From the manpage: Note also that host and module references don't require a trailing slash to copy the contents of the default directory. So in this case the trailing slash wouldn't make a differenc

Re: code 12 error when specifying files

On Thu 03 Aug 2006, nathan r. hruby wrote: > > > >It's not what I'm seeing: > > > > Hurm. What OS are you running this on? Hint: check my email address :-) > After upgrading my local/receiver rsync to 2.6.8 I get this: > > local# rsync remote::users/grp012/12/nhruby/public_html/ > drwxr-xr-x

RE: code 12 error when specifying files

With 2.5.5 on QNX I get the folder contents list when I do: rsync [EMAIL PROTECTED]::module or rsync [EMAIL PROTECTED]::module/ if I do rsync -v [EMAIL PROTECTED]::module poo (or module/ poo) i get "nothing to do" Adding a (-av) causes it to pull in all the files and the subdirs (recursive),

Re: code 12 error when specifying files

On Thu, 3 Aug 2006, Paul Slootman wrote: On Thu 03 Aug 2006, nathan r. hruby wrote: It's not what I'm seeing: Hurm. What OS are you running this on? Hint: check my email address :-) Heh. Just checking :) After upgrading my local/receiver rsync to 2.6.8 I get this: local# rsync rem

RE: code 12 error when specifying files

Paul, I think the question is why he doesn't get a directory list for rsync remote::users/grp012/12/nhruby/public_html/ The CORE question really is: How do you make rsync transfer the contents of a single directory without recursing and without using wildcards in the SRC expression (with or wit

Patch to handle ACL differences

A while ago (2.6.2), I built and posted a patch which caused rsync to "do the right thing" where --link-dest was being used and where files had been changed only in their ACLs. I've recreated this for 2.6.8 (there were some small differences). I've tested this using --link-dest copying from Linu

Re: code 12 error when specifying files

Erik, Include/exclude rules that you specify earlier have higher priority. If you say --exclude="*" --include=".*", all the files will match the first rule, and they will all get excluded. You probably want to put the include rule first. To transfer the immediate contents of a directory without

Re: code 12 error when specifying files

On Wed, Aug 02, 2006 at 02:30:29PM -0400, Erik Jacobs wrote: > It works and lists fine. But if I choose a wildcard which contains a LOT of > files: rsync [EMAIL PROTECTED]::filefolder/.7.* > I get error in rsync protocol data stream (code 12) Older rsync versions had a limit of 1000 filenames

Re: code 12 error when specifying files

On Thu, Aug 03, 2006 at 08:16:54AM -0400, Erik Jacobs wrote: > If I add the recursive option, it works, but I don't want to recurse > -- I only want to look at the files in this folder... On a modern rsync, you specify -d instead of -r to copy directories by name, or the immediate contents of a di

Re: code 12 error when specifying files

On Thu, Aug 03, 2006 at 03:12:40PM +0200, Paul Slootman wrote: > Note that the trailing slash *is* needed on the ssh connection, see > without: > > local# rsync --exclude='*' --include='.*' remote:/tmp/test > Password: > (nothing) That's because you excluded the directory "test", which is the f

Re: code 12 error when specifying files

On Thu, Aug 03, 2006 at 10:22:57AM -0400, Erik Jacobs wrote: > is there any reason why telling rsync what files you want it to > INCLUDE doesn't seem to tell it what files to include? Without -r or -d, rsync completely skips directories (just like it skips symlinks without -l). Just because a nam

Re: rsync giving directory by name, instead of contents

On Wed, Aug 02, 2006 at 05:25:36PM -0400, nathan r. hruby wrote: > rsync -avz server.edu::home/user1/public_html/ /dest/path/user1/www > I get > /dest/path/user1/www/public_html > which has the correct contents. So things are being copied, just with an > extra directory. Something has

Re: Patch to handle ACL differences

On Thu, Aug 03, 2006 at 02:17:33PM -0400, Andrew Gideon wrote: > A while ago (2.6.2), I built and posted a patch which caused rsync to "do > the right thing" where --link-dest was being used and where files had been > changed only in their ACLs. I've recreated this for 2.6.8 (there were > some sma

Re: Packages for rsync 2.6.8 with ACLs

On Wed, Aug 02, 2006 at 06:49:11PM -0400, Andrew Gideon wrote: > First of all, the patch places sysacls.[hc] one directory too high. > These need to be in the libs directory, lest 'make' will fail. This means that you didn't use a -p option to patch -- you should use either -p1 (modern patches) or

Re: rsync giving directory by name, instead of contents

On Thu, 3 Aug 2006, Wayne Davison wrote: On Wed, Aug 02, 2006 at 05:25:36PM -0400, nathan r. hruby wrote: rsync -avz server.edu::home/user1/public_html/ /dest/path/user1/www I get /dest/path/user1/www/public_html which has the correct contents. So things are being copied, just