Hello

We are running ADSM V1 R1 Level 0.16 on VM/ESA 2.1.0  and doing DB2/6000 
backups into ADSM.
We run both versions of DB2/6000 (V1.1.0 inproduction and V2.1.1 in test); the 
behavior of V2.1.1 with ADSM is not
compatible with production now (I'll explain why below)... and I hope it will 
change soon !!

The facts are :
DB2 V1 full database backup generates names like /NODE_0/ FULL_BACKUP in the 
filespace /Database_Name;
DB2 V2 full database backup generate names like  /NODE_0/ 
FULL_BACKUP.19960104120436.1 in the same filespace;

The problem is, as I said it several times in the past, that each V2 backup has 
a different name than the previous
one because of the timestamp and old backups are not deleted by the versionning 
system of ADSM.

No problem (IBM says) you use the db2adutl tool coming with 2.1.1 and you 
delete the old backups from the
client...

This is a real problem 'cause :

1) the logic of expiration is now on the client and the management of ADSM 
Storage Pool size is not possible from
a unique focal point !!
2) the delete operation mount tapes (containing the backup image ? (assumption))
3) transfers the image back to the client !!! --> Stupid thing is'nt it but WHY 
???
   it means that when you delete a 500 MB backup image you load your network 
with 500 MB for nothing !!!!!
4) does not free ADSM space (but this one may be okay if you find the magic 
copygroup parameters and I would like
   to find them somewhere in some Db2 documentation, not in Red Books anyway ).

In conclusion, we absolutely need changes (probably on the DB2/6000 dev side) 
to DB2 backups with ADSM to cope
with REAL PRODUCTION environment like our !!

I would like to have comments on this issue soon, PLEASE.

Cheers, Michel
--
Michel Gaillard
Michel Gaillard
DSI/DPI
Alcatel Telecom
Velizy France
E-Mail: Michel.Gaillard AT vz.cit.alcatel DOT fr
Voice : (33.1) 30 67 32 56