ADSM-L

TSM DB growing, but number of files remains the same ...

2004-05-04 06:58:23
Subject: TSM DB growing, but number of files remains the same ...
From: PAC Brion Arnaud <Arnaud.Brion AT PANALPINA DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 4 May 2004 12:50:20 +0200
Hi *SM'ers,

I'm facing a strange problem, in that my DB began to grow at an abnormal
rate, a couple of weeks ago. I tried to find out the reason why, and
build a query based on the occupancy table, which was counting the
number of files found for all existing storage pools. Problem is that I
don't find any relation between Db increase and number of files existing
on the server, which remains more or less the same. However,
questionning the activity log about expiration process shows me that I
have more and more objects in the DB, to wit :

25.04.2004 15:25:10  ANR0812I Inventory file expiration process 2292
completed:examined 5687868 objects, deleting 361530 backup objects, 0
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 359257, PROCESS: 2292)

26.04.2004 16:58:42  ANR0812I Inventory file expiration process 2372
completed:examined 5867120 objects, deleting 421743 backup objects, 0
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 475376, PROCESS: 2372)

27.04.2004 21:31:16  ANR0812I Inventory file expiration process 2487
completed:examined 5885631 objects, deleting 359570 backup objects, 4
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 491543, PROCESS: 2487)

28.04.2004 18:16:26  ANR0812I Inventory file expiration process 2589
completed:examined 5961005 objects, deleting 408001 backup objects, 4
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 500118, PROCESS: 2589)

30.04.2004 18:12:55  ANR0812I Inventory file expiration process 2801
completed:examined 6015077 objects, deleting 320742 backup objects, 5
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 522523, PROCESS: 2801)

01.05.2004 16:22:45  ANR0812I Inventory file expiration process 2870
completed:examined 6130527 objects, deleting 396887 backup objects, 10
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 531082, PROCESS: 2870)

02.05.2004 15:44:38  ANR0812I Inventory file expiration process 2921
completed:examined 6186830 objects, deleting 335723 backup objects, 17
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 542353, PROCESS: 2921)

03.05.2004 16:03:46  ANR0812I Inventory file expiration process 2998
completed:examined 6271664 objects, deleting 361712 backup objects, 5
archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered. (SESSION: 626203, PROCESS: 2998)


I'm certain that no modification has been made on our copygroups, no new
nodes have been added, and the only notable modifications that have been
made where 
A) Upgrade from TSM server 5.1.6.2 to 5.2.2.1 
B) creation of a collocated stgpool for our AIX nodes, which points to
the same copypool as the old non collocated one + move of several nodes
in the policy domain pointing to this collocated pool and  move nodedata
from old non collocated stgpool to collocated pool for involved nodes.

Does anybody have an explanation for this, as it goes far behind my
understanding :-(
TIA

Arnaud Brion

***********************************************************************
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
***********************************************************************