ok sorry, I found the example in example/disklist
it work fine :)
howener, I have noticed that server AND client machine must be in 2.4.3 version.

Brunet Eric wrote:
are you sure of this functionnality, because I tested the 2.4.3 with multiple same disklist entry, like this:
80.65.xxx.yyy /home/test comp-user-tar-incr-adherent_a
80.65.xxx.yyy /home/test comp-user-tar-incr-adherent_b
(only excluding rule change in these 2 dumptypes)
but I have always this message (duplicate disk record...).
I have read the docs, but nothing about this.

Jean-Louis Martineau wrote:

On Thu, Oct 17, 2002 at 08:00:08PM -0400, Jon LaBadie wrote:

On Thu, Oct 17, 2002 at 06:42:13PM -0400, Jean-Louis Martineau wrote:

Hello Eric,

On Thu, Oct 17, 2002 at 03:59:14PM +0200, Brunet Eric wrote:

I tested with a wildcard file path and all worked fine; my idea was to simulate "hash dirs" with the "exclude" option:
./[b-zB-Z]* -> exclude which takes only subdirs begins by 'B' or 'b'

But when I applied these dumptypes on this dir amanda detected that "duplicate disk record"

Upgrade to 2.4.3, it allow multiple disklist entry for the
same directory.

Does it back it up multiple times?
Should it?


It follow your include/exclude specification for each entry.

Jean-Louis



Reply via email to