ADSM never delete the last BACKUP Volume from the volhistory. 
This prevents the lost of the last actual DATABASE Backup.


Elmar Gawronski                     
IZB340 - Speichermanagement
Tel.:       +49 (89) 2171-7961    
Fax:      +49 (89) 2171-5999
e-mail:   mailto:elmar.gawronski AT izb DOT de
_______________________________________
IZB
Informatik-Zentrum Bayern GmbH & Co. KG
Karolinenplatz 1
80333 München
http://www.izb.de
_______________________________________




> ----------
> Von:  Uwe Schoenacher[SMTP:uwe.schoenacher AT LZB-BAYERN.BUNDESBANK DOT DE]
> Antwort an:   ADSM: Dist Stor Manager
> Gesendet:     Montag, 3. Januar 2000 08:50
> An:   ADSM-L AT VM.MARIST DOT EDU
> Betreff:      Delete volumehistory problem with volumes created on
> 01/01/2000
> 
> our delete-volumehistory-jobs cannot delete volumes created on 01/01/2000.
> What other ways do you know to clean up your
> volume entries? I think that is a classical Y2K-Bug. Has anybody the same
> experience?
> 
> 
> Configuration:
> 
> WindowsNT      4.0 SP5
> ADSM:          3.1.2.40
> 
> 
> 
> => ADSM-Console-Copy
> --------------------------------------------------------------------------
--
> -
> -
> -----------------------------------------------------------------
> Session established with server MEDUSA: Windows NT
>   Server Version 3, Release 1, Level 2.40
>   Server date/time: 01/03/2000 08:37:56  Last access: 01/03/2000 08:36:00
> 
> 
> adsm> q volhist
> 
>        Date/Time: 01/01/2000 09:58:58
>      Volume Type: BACKUPFULL
>    Backup Series: 984
> Backup Operation: 0
>       Volume Seq: 1
>     Device Class: DLTCLASS1
>      Volume Name: DLT102
>  Volume Location:
> 
> adsm> del volhist todate=today type=all
> 
> Do you wish to proceed? (Yes/No) y
> ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were
> successfully deleted.
> --------------------------------------------------------------------------
--
> -
> -
> -----------------------------------------------------------------------
> 
>