The db2 backups are taking using TSM API client. In order to
remove/delete these files from TSM, the deletes must be initiated from
DB2 API.
For example,
If NUM_DB_BACKUP = 3
Step-1: All backup images <= 3 days will be in active state.
Step-2: All backup images 3 days will be marked inactive state and
the retention period kicks in now.
Step-3: All backups will be retained for "x" days after marking it
inactive.
Step-4: All backups past "x" days will be marked as expired backups.
Step-5: All backups marked expired will be deleted by TSM expire
inventory.
After Step-2, DBA script may run db2adutl to delete the backups and
it's related log files (Or) Run a script to automatically delete
backups and logs using db2adutl command.
After Step-4, TSM should run expire inventory to remove expired
objects.
Check the Management Class settings and Backup/Archive Copy Group
settings for retention and expiration periods.
Please read this Redbook titled "Backing up DB2 with IBM TSM":
http://www.redbooks.ibm.com/redbooks/pdfs/sg246247.pdf
The pdf comes with scripts to automate the process of deleting backups
and log archives.
Another article on managing backups in TSM:
http://www.databasejournal.com/featu...0896_3330171_1
Regarding the files, history file will provide information on active,
inactive and expired objects. The db2adutl tells you what's in TSM. The
information between history file and TSM is different because files are
not being delete from TSM. We have to run db2adutl to delete these
files from TSM.
- Vijay
Polani wrote:
Hi Guys ,
I am taking DB2 Online backups through TSM API daily. When i check the
database configuration parameters , it shows me " Number of database
backup verions to maintain"= 12.
This is also shown when i check " db2 list history db " it showed me 12
versions of backups which is ok, but problem is that when i run
"db2adutl query" it showed me 69 or 70 entries like that:::
1 Time: 20060730142501 Oldest log: S0014176.LOG DB Partition Number: 0
Sessions: 1
2 Time: 20060729142501 Oldest log: S0014141.LOG DB Partition Number: 0
Sessions: 1
3 Time: 20060728142502 Oldest log: S0014100.LOG DB Partition Number: 0
Sessions: 1
4 Time: 20060727142502 Oldest log: S0014074.LOG DB Partition Number: 0
Sessions: 1
5 Time: 20060726142502 Oldest log: S0014048.LOG DB Partition Number: 0
Sessions: 1
So my question is that how can i know whether DB2 is expiring backup
versions or not, should i try " Expire inventory " explicitly for
expiring DB2 backups or if there are any scripts to expire DB2
backups????
And most annoying , why is the difference between db2 list history db
and db2adutl command, On which command should i rely ????
Env is Db2 8.1.3 with TSM 5.3
Regards
Khurram
