On Mon, Feb 17, 2003 at 08:04:49PM +0100, rb AT raphinou DOT com wrote:

> ~$ amadmin DailySet1 find localhost
> Scanning /data/backup...
> 
> date       host      disk               lv tape or file file status
> 2003-02-17 localhost /data/amanda-test/  0 HISS3           1 OK
> 2003-02-17 localhost /data/amanda-test/  1 HISS0           1 OK
> 2003-02-17 localhost /data/amanda-test/  1 HISS1           1 OK
> 2003-02-17 localhost /data/amanda-test/  2 HISS2           1 OK
> 2003-02-17 localhost /data/amanda-test/  3 HISS3           1 OK
> 
> 
> The levels of the backups are ok, following the configuration.
> What I don't understand is that on the tape HISS3, I had the level three
> backup erase the level 0.....
> 
> Shouldn't that have been prevented? Can I still recover all files (since
> the level 0 backup isn't available anymore)?
> Or could this be due to the fact that I erased files to restart from
> zero? (cf a previous mail ;-)

Can you give details on your test configuration?  Amanda doesn't
protect against a too small dumpcycle and only appends warnings to the
report mail. This is a bug, it should scream out loud and not warn. 

You amadmin output looks to me like a tapecycle 4 configuration.  This
configuration is not usable for several backups a day like you did for
testing.

   Ciao
    Dietmar
-- 
Dietmar Goldbeck, Senior Consultant, <dietmar.goldbeck AT neteligent DOT de>
Neteligent GmbH, http://www.neteligent.de/
Walter-Benjamin-Platz 6, 10629 Berlin, Germany 
fon: +49 (0)30/310182-73, fax: +49 (0)30/310182-79