TSM Topics Feed

Wednesday, November 16, 2011

Tivoli Storage Manager Reporting and Monitoring v6.3

This is a query from the TSM v6.3 agent:

select node_name, count(distinct volume_name) from volumeusage a, stgpools b where (a.stgpool_name=b.stgpool_name) and devclass in (select DEVCLASS_NAME from devclasses where devtype in ('3570','3590','3592','4MM','8MM','DLT','DTF','ECARTRIDGE','GENERICTAPE','LTO','QIC')) group by node_name

Could you run it on a TSM v5.x.x.x productive system for me!

Do you get any result in 10 minutes?

8 comments:

  1. I ran it on a small (30 nodes) TSM 5.5.2 and it took about 10 secs to get the result.

    ReplyDelete
  2. 69 nodes, about 1 sec. 5.5.5.2 AIX

    ReplyDelete
  3. Running on an ancient P660 RS64-IV setup on TSM 5.5.5.0 the results clocked in as follows:
    Start: 16:17:15
    Stop: 16:21:33

    There are around 400 nodes on this server.

    ReplyDelete
  4. Hi,

    Recently tested on a slow and busy TSM server and it took more than 2 hours to complete... The Monitoring Agent is completely unable to work with this TSM Server and most of the Attribute Groups doesn't show in the TEP.

    ReplyDelete
  5. Erwann: Which versions (TSM and Monitoring) did you use?

    ReplyDelete
  6. Hi _flex,

    I used Tivoli Monitoing for TSM 6.3, on Windows 2008 R2 and the TSM Server was 5.5.1 on AIX. It's a busy TSM server with a moderate large database (a bit more than 100GB).

    As previously written, most of the Attribute Groups where not shown in the TEP : No data in the corresponding workspace, confirmed by the Agent Log workspace.

    I finally tried the SQL request from a dsmadmc command line, and it took then two hours to complete.

    ReplyDelete
  7. tsm: EDCWTSM1>select node_name, count(distinct volume_name) from volumeusage a,
    stgpools b where (a.stgpool_name=b.stgpool_name) and devclass in (select DEVCLAS
    S_NAME from devclasses where devtype in ('3570','3590','3592','4MM','8MM','DLT',
    'DTF','ECARTRIDGE','GENERICTAPE','LTO','QIC')) group by node_name
    ANR2963W This SQL query may produce a very large result table, or may require a
    significant amount of time to compute.

    Do you wish to proceed? (Yes (Y)/No (N)) y

    NODE_NAME Unnamed[2]
    ------------------ -----------
    ALPS 2
    ALPS_OLD 48
    ANDES 2
    ANDES_OLD 46
    CCMAPP1 46
    CCMPRDA1 61
    CCMWEB1 52
    COLLINS 33
    COLLINS_OLD 3
    DIABLO 66
    EDCWHAT1 65
    EDCWHAT2 65
    EDCWNIMLV 29
    EDCWTSM1 60
    EDCWTSM2 13
    ENTCNAG1 68
    ENTWUNXMGT1 25
    ENTZTAR4 21
    ENTZTAR5 21
    ERMCMDB 69
    ERMCMDB_DB2 163
    ERMCMRM1 66
    ERMCMTST 66
    ERMDBTST 65
    ERMDBTST_DB2 4
    ERMECLNT 66
    ERMODDB 69
    ERMODDB_DB2 180
    ERMTDS 63
    ERMTDSTST 64
    ERMTEST 66
    ERMTSM 70
    EVEREST 42
    EVEREST_DB2 156
    EXCURSION 66
    FUSION01 68
    HOD2 34
    K2 41
    K2_DB2 149
    KANGRI 66
    KANGRI_DB2 108
    more... ( to continue, 'C' to cancel)

    LVSBLS 64
    MEMBLS 64
    NEO 34
    NSM1 68
    OLYMPUS 81
    ORCPRDD1 18
    ORCPRDD1_ORACLE 10
    ORCPRDD1_ORC 57
    OZARK 2
    OZARK_DB2 162
    OZARK_OLD 50
    PALERMO 67
    PDBPRDA1 66
    PDBPRDA2 66
    PDBPRDD1 66
    PDBPRDD1_INFX 36
    PDBTSTA1 67
    PDBTSTA2 66
    PDBTSTD1 67
    RAINIER 70
    ROCKY 48
    ROCKY_DB2 101
    RTEM 66
    RUSHMORE 2
    RUSHMORE_OLD 48
    SDSEDW 38
    SDSGWDEV 6
    SDSGWDEV_OLD 2
    SDSGWDEV_OLD2 57
    SDSGWPRD 68
    SDSGWPRD2 29
    SHASTA 2
    SHASTA_DB2 156
    SHASTA_OLD 49
    SIERRA 2
    SIERRA_DB2 6
    SIERRA_OLD 50
    TOPSRV 65
    TOPSRV2 66
    VESUVIUS 84
    WASSTG1 66
    WASSTG2 64

    tsm: EDCWTSM1>

    ReplyDelete