Expiring DB2 Backup Data

[rowl]

As part of an audit of our environment I have run a few select * from backups to see if our DB backups were staying within their agreed upon retention. I was suprised to find some of our largest DB2 instances have backup data going back years, not weeks.

On further investigation it seems much of this data is made up of a .tar file that was backed up along with the DB. For example

NODE_NAME HL_ADDRESS LL_ADDRESS BACKUP DATE
DB2_SERVER1 / FIN_20070403150834.tar 4/9/2007
DB2_SERVER2 / SAL_20090809142934.tar 8/9/2009

These are relatively small files, but I would have thought they would be deleted along with the DB2 database backup. All of these backups are run using the DB2 API (TDP) and expired from the API client.

Does anyone know why these .tar files are not being expired along with the database backulps?

-Rowl

 

[rowl]

After further investigation I discovered that the DBA was running dsmc with the same node name used for the API client to backup this .tar file. So it will never expire.