You haven't said if you are running the db2adutl commmand to
expire old backup versions.  Db2 backups are saved with a timestamp
so each db2 backup is an 'active version'  The only way they become
inactive and eligible for expiration is if you run the db2adutl command
that deletes the backups.

James Thompson

From: Gerhard Wolkerstorfer <Gerhard.Wolkerstorfer AT DEBIS DOT AT>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DB2/2 Backup and Policy
Date: Mon, 5 Feb 2001 15:56:44 +0100

Hi *SMer,
one of our customers is making a backup of his DB2/2 V6.1 database once a
day
and his files (One Backup = One File in the Database-Filespace!) are stored
in a
filespace where the name of the filespace is the same as the
DB2-Database-Name.
His Commands are:
1) to define the managementclass to the backup =>
"db2 update db configuration for xxxxxxxx using ADSM_MGMTCLASS DB2"
2) to start the DB2-backup =>
"db2 backup database xxxxxxxx use adsm "
(where xxxxxxxx is the databasename)

Everything works fine to the DB2-Admin... (even the restore!)

Now my problem as TSM Admin =>
Although in the Managementclass DB2 (backup copy group) is defined, that
the
files are deleted after one day - ALL Files from the beginning are still
saved
in the TSM-Storagepools. And the amount is really huge !
This is the query of the Copygroup =>
            Policy Domain Name: STANDARD
               Policy Set Name: ACTIVE
               Mgmt Class Name: DB2
               Copy Group Name: STANDARD
               Copy Group Type: Backup
          Versions Data Exists: 5
         Versions Data Deleted: 1
         Retain Extra Versions: 1
           Retain Only Version: 1
                     Copy Mode: Modified
            Copy Serialization: Shared Static
                Copy Frequency: 0
              Copy Destination: BACKUPPOOL
Last Update by (administrator): WOLKE
         Last Update Date/Time: 2001-01-26 12:13:12
              Managing profile:

(Notice: The node is assigned to the Policy Domain STANDARD!)

Why doesn't TSM use the defined policy-information and delete the files in
this
case ?

One thing I remarked:
When you delete a "normal" filespace, then the files are only marked as
deleted
and they are logically deleted from the database when the EXPIRE INVENTORY
occurs.
BUT - now I deleted a DB2-Filespace and all the tapes, where the DB2-Data
was
stored, are now empty, WITHOUT the EXPIRE INVENTORY process.

Our Server-Configuration is:
..) OS/390 V2 R9.0
..) Tivoli Storage Manager for MVS, Version 3, Release 7, Level 4.0

Any suggestions, what's going wrong ? (The problem is, that one backup uses
4
GB........and after 100 days, we had 400 GBs of data stored!)
Thanks in advance...

Gerhard Wolkerstorfer

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com