Yes, if you want to examine this on a global basis, the BACKUPS table would have that info. You can craft a SELECT statement to show you which nodes are using which management classes, or which nodes are using a specific management class if you want that level of detail. Note that SELECTing against the BACKUPS table is a rather expensive and time-consuming process, so it might be better to go after more general data, redirecting the output to a file, then using some other tool (like MS Access or other database) to mine the data; as opposed to repeated SELECTs against the BACKUPS table on the TSM server.
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 08/02/2006 10:16:02 AM: > Can anyone please tell me if there is a command to look at all my nodes > and display which might be using a particular management class's backup > group ? > > Thanks, > Ralph > > > _____________________________________________ > > From: Levi, Ralph > > Sent: Wednesday, August 02, 2006 9:00 AM > > To: 'ADSM: Dist Stor Manager' > > Subject: Data expiration > > > > I am still working understanding why my TSM DB continues to grow and > > think I may have come upon something. I have many retention policies > > in the management class for all my file servers. The goal was to keep > > most data for only 90 days after it was deleted and to keep 90 > > versions if it was a file that would be updated daily. > > Incremental backups are run nightly. TSM is AIX 5.3 and TSM 4.2.7. > > The file servers are mostly W2K with backup-restore client 5.1.x - > > 5.3.x. > > > > My expiration runs successfully daily but I believe what is happening > > is the majority of data being expired are the files that are > > overwritten daily. It looks to me like the files that someone > > overwrites once or twice lives out in TSM forever, certainly beyond > > the 90 days I was expecting it to be there. > > > > Here are my management classes. Is the unlimited "retain extra > > versions" overriding my 90 days in the primary management class ? > > > > Any help would be appreciated. > > Thanks, > > Ralph > > > > > > The default management class is defined as: > > > > versions data exist: unlimited > > versions data deleted: 9 > > retain extra versions: 9 > > retain only version: 9 > > > > The primary management class used (95% of all data) > > > > versions data exist: unlimited > > versions data deleted: 90 > > retain extra versions: 90 > > retain only version: 90 > > > > The 2 long retention management classes are: > > > > versions data exist: unlimited > > versions data deleted: 366 > > retain extra versions: 366 > > retain only version: 366 > > > > versions data exist: unlimited > > versions data deleted: unlimited > > retain extra versions: unlimited > > retain only version: unlimited > >