Try these:
select distinct node_name as "Node Name ",filespace_name as "Filespace
Name ",class_name as "Management Class Name" from backups
where TYPE='FILE' group by node_name,filespace_name,class_name
Node Name Filespace Name Management
Class Name
------------------ ----------------------------------
---------------------
TSMCLI01 / DEFAULT
TSMCLI01 /home DEFAULT
TSMCLI01 /opt DEFAULT
TSMCLI01 /tmp DEFAULT
TSMCLI01 /tsm DEFAULT
TSMCLI01 /usr DEFAULT
TSMCLI01 /var DEFAULT
TSMCLI01 /wn001 DEFAULT
and the same for the archives table
you could always use the ~where node_name='HMPG1018'~ to limit the output to
just that node
select distinct node_name,filespace_name,class_name from backups group by
node_name,filespace_name,class_name
will show you everything, including directory information...
NODE_NAME FILESPACE_NAME CLASS_NAME
------------------ ------------------ ------------------
TSMCLI01 / B7.3_R35.95_A370_-
DIRMC
TSMCLI01 / DEFAULT
TSMCLI01 /home B7.3_R35.95_A370_-
DIRMC
TSMCLI01 /home DEFAULT
<...>
TSMCLI01 /wn001 B7.3_R35.95_A370_-
DIRMC
TSMCLI01 /wn001 DEFAULT
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Moyer, Joni M
Sent: Tuesday, March 02, 2010 2:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] How to find what management class is used per node
Hi,
I was just wondering if anyone knows a script that I can run to find out
what management class is utilized by node hmpg1018? Would I need to run:
select * from backups where node_name='HMPG1018'?
Thanks in advance for any help!!!!
Joni Moyer
Storage Administrator III
(717)302-9966
joni.moyer AT highmark DOT com
________________________________
This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed. If
you have received this e-mail in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this e-mail without the author's
prior permission. The views expressed in this e-mail message do not
necessarily represent the views of Highmark Inc., its subsidiaries, or
affiliates.
|