At 03:32 PM 4/26/2002 -0500, Terry McCoy, you wrote:
>I have a file system on a client that I want to exclude directories
>from being backed. Every time the client runs the excluded directories
>are backed up anyway.
>
>
>
>I have a dump type that has exclude list specified as shown
>below:
>
>
>define dumptype listserv-root {
> global
> comment "listserv has directories within the root file system to
> always exclude"
> exclude list "/local/amanda/sysconfdir/Email/excludelist_listserv"
>}
>
>
>This file system is on a client. Hence I have placed this file on the
>client at the location specified above has the contents shown below:
>
>
>listserv> cat /local/amanda/sysconfdir/Email/excludelist_listserv
>./var/log
>./var/spool/mqueue
>./usr/products/listserv/spool
>
>
>
>Any ideas on how to troubleshoot this or what to look for?
Are /var and /usr on different filesystems? If so, then this portion of
the documentation might help you:
Note that the `full pathname' of a file within its filesystem starts with
`./', because of the way amanda runs gnutar: `tar -C $mountpoint -cf -
--lots-of-options .' (note the final dot!) Thus, if you're backing up
`/usr' with a diskfile entry like ``host /usr gnutar-root', but you don't
want to backup /usr/tmp, your exclude list should contain the pattern
`./tmp', as this is relative to the `/usr' above. Please refer to the
man-page of gnutar for more information. If a relative pathname is
specified as the exclude list, it is searched from within the directory
that is going to be backed up.
So IF /var and /usr are different filesystems then your exclude list should
look like this:
./log
./spool/mqueue
./products/listserv/spool
Oscar
