On Thu, 21 Apr 2005 at 3:58pm, Kuas wrote
> Now, In a situation I want to give flexibility to users, that they are
> the one that knows if a directory needs to be excluded or backup to be
> more efficient in the backup process. From the howto and some trial I
> can specify in the dumptype, instead of the absolute path to the exclude
> file, but just the name of the file:
>
> exclude list "exclude.list"
>
> So each user needs to create this file and has full authority to change
> it. The effect I saw (from amcheck) is that it will try to find that the
> file in each of the DLE that uses that dumptype. But the problem I saw,
> when there is a problem like the file doesn't exist. That will stop all
> backup processes or at least for that DLE. Has anybody else seen this,
> or it's just normal behavior when there's a problem, they just stop the
> backup. Is the syntax of that exclude behavior is prohibited. Has
> anybody tried doing similiar purpose like this before? Would there be a
> better way to do it?
>From 'man amanda':
exclude [ list|file ][[optional][ append ][ "string" ]+]
Default: file. There is two exclude list exclude file and
exclude list. With exclude file , the string is a gnutar
exclude expression. With exclude list , the string is a file
name on the client containing gnutar exclude expression.
All exclude expression are concatenated in one file and passed
to gnutar as a --exclude-from argument.
With the append keyword, the string are appended to the current
value of the list, without it, the string overwrite the list.
=> If optional is specified for exclude list, then amcheck will not
=> complain if the file doesn't exist or is not readable.
For exclude list, If the file name is relative, the disk name
being backed up is prepended. So if this is entered:
exclude list ".amanda.excludes"
the actual file use would be /var/.amanda.excludes for a backup
of /var, /usr/local/.amanda.excludes for a backup of /usr/local,
and so on.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
|