> 01 Because of dump don't support exclude file lists/patterns, I have to
>use
> gtar, if I want to benefit from this feature?
Correct.
Dump also does not support (in general) anything other than a whole file
system, so that also points you toward using GNU tar.
> 02 If I create an exclude file for the '/home' disklist entry, what about
> the files in '/' ? If I include an entry like '/*' in those exclude
>list,
> '/home' won't be tar'ed too?
I think the idea is that you do *not* define an exclude list in the base
dumptype used for / and /home, and you use that "as is" for /home (i.e.
everything under /home will be processed), but in the disklist entry for /
(or an alternate dumptype) you have an exclusion for /home (etc).
your.host /home root-tar
your.host /var root-tar
your.host / {
root-tar
exclude list "/path/to/file"
}
> 01 My assumption is, that the amanda exclude "string" (not using the
>list
> option) is passed to the tar parameter that expects the globbing
>file
> PATTERN?
Correct.
> 02 If yes, can I define in the local dumptype an exclude PATTERN for
>the
> appropriate disk entry, so I don't have to create and maintain a
> corresponding exclude list file at the client side? Which will
>mean,
> can I maintain all exclude PATTERNS in the disklist file?
Yes, as long as you only need one pattern, since you can only pass one
--exclude parameter to GNU tar (or at least that's all Amanda can handle).
But in your case, that's not going to work because you want to exlude
both /home and /var from the / dump. Unless you can come up with a
pattern that will do that.
>mike
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
