You might try this query:
select cast(vu.stgpool_name as char(9)) as "Pool", -
(select access from volumes where volume_name=vu.volume_name) as "Access", -
cast(vu.volume_name as char(9)) as "Volume", -
cast(count(distinct nd.collocgroup_name) as decimal(4,0)) as "Groups", -
cast(count(distinct vu.node_name) as decimal(3,0)) as "Nodes", -
cast(count(distinct vu.filespace_name) as decimal(5,0)) as "FSpaces", -
(select pct_utilized from volumes where volume_name=vu.volume_name) as "Util", -
(select pct_reclaim from volumes where volume_name=vu.volume_name) as "Recl" -
from volumeusage vu, nodes nd -
where vu.node_name=nd.node_name -
group by vu.stgpool_name, vu.volume_name -
order by "Groups" desc, "Nodes" desc, "FSpaces" desc
We assign all nodes to collocation groups, even if it is only one node.
Good luck.
Bob.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Colwell, William F.
Sent: Wednesday, April 17, 2013 9:44 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Collocation anomaly report
Hi Grant,
I used to track collocation group spill overs when my servers were version 5
and used tapes. Now I am on v6 and almost all disk, so I don't do that anymore.
Anyway, I used a mysql database on my desktop system. I would dump data from
the tsm servers and load it into mysql where I could do manipulations not
allowed in the tsm servers. Then I would run a report which showed
among other things volumes which have data from more than 1 collocation group.
The key bit of data from tsm is "q nodedata *" which provides
almost all the same info as a select from volumeusage, but is much faster.
I can send you a sample report if you are interested.
Bill Colwell
Draper Lab
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Grant Street
Sent: Tuesday, April 16, 2013 7:40 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Collocation anomaly report
Hello
We use collocation to segment data into collocation groups and nodes,
but recently found that collocation is on a "best efforts" basis and
will use any tape if there is not enough space.
I understand the theory behind this but it does not help with compliance
requirements. I know that we should make sure that there are always
enough free tapes, but without any way to know we have no proof that we
are in compliance.
I have created an RFE
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=33537
. Please vote if you agree:-)
While I wait a more than two years for this to be implemented, I was
wondering if anyone had a way to report on any Collocation anomalies?
I created the following but still not complete enough
select volume_name, count(volume_name) as "Nodes_per_volume" from
(select Unique volume_name , volumeusage.node_name from volumeusage,
nodes where nodes.node_name = volumeusage.node_name and nodes.
collocgroup_name is null) group by (volume_name) having count
(volume_name) >1
and
select unique volume_name, count(volume_name) as "Groups_per_volume"
from (select Unique volume_name , collocgroup_name from volumeusage,
nodes where nodes.node_name = volumeusage.node_name ) group by
(volume_name) having count(volume_name) >1
Thanks in advance
Grant
This electronic transmission and any documents accompanying this electronic
transmission contain confidential information belonging to the sender. This
information may be legally privileged. The information is intended only for the
use of the individual or entity named above. If you are not the intended
recipient, you are hereby notified that any disclosure, copying, distribution,
or the taking of any action in reliance on or regarding the contents of this
electronically transmitted information is strictly prohibited.
|
