[rdiff-backup-users] Re: include other filesystems?

[Yuval Hager]

On Saturday 07 February 2009, Jakob Unterwurzacher wrote:
> Yuval Hager schrieb:
> > Hello,
> >
> > My directory structure is as follows:
> > / is one file system
> > /data is another
> >
> > /home is linked to /data/home
> > /usr/local/data is linked to /data/usr/local/data
> >
> > I am backing up '/', using --include-globbing-filelist that looks as
> > follows:
> >
> > + /home/user1
> > + /home/user2
> > + /usr/local/data
> > + /etc
> > - **
> >
> > How can I get both filesystems backed up? I've tried modifying the
> > filelist to have the link targets (e.g. /data/home/user1 etc) instead,
> > but it doesn't work as well.
> > Is there some way to include other filesystems in the globbing filelist?
> >
> > I believe that I'm looking for an --include-other-filesystems command
> > line option?
>
> I think you are hitting this, from the rsync manpage:
>
>        rsync finds the files to send.  If  a  pattern  excludes  a
>        particular parent directory, it can render a deeper include
> [snip]

Thanks. I didn't know I should look at rsync man page at all.. I was only 
reading rdiff-backup manual..

Anyway, I am not sure this is the problem.

I've narrowed it down to:
# this does not work:
$ rdiff-backup --include /home/user1 --exclude '**' / $DST

# neither this:
$ rdiff-backup --include /home --include /home/user1 --exclude '**' / $DST

# but this does work:
$ rdiff-backup --include /data/home/user1 --exclude '**' / $DST

(I define 'work' above, as backing up all files under /home/user1)

So I am not sure why is this happenning. I used the highest verbosity, but it 
does not explain the inclusion/exclusion reasoning.
It all started when I moved /home to the filesystem mounted at /data - and I 
expected backup to continue as normal - but it didn't. Is there a way to 
continue backing up /home although it moved to /data/home this way?

Thanks,

--yuval

signature.asc
Description: This is a digitally signed message part.