HI-MB.w i le! <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <D4B07980AD4F! <[EMAIL PROTECTED]> X-ASG-Orig-Subj: RE: [ADSM-L] Collocation question Subject: RE: [ADSM-L] Collocation question Date: Fri, 21 Nov 2008 08:33:30 -0600 Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <[EMAIL PROTECTED]> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AclL2OtUeB88DCAQT0Gxau3IffSyKwACVIoA X-Virus-Scanned: by amavisd-new on lnxsrvu at winnebagoind.com X-Copyrighted-Material: Please visit http://www.company.com/privacy.htm X-Barracuda-Connect: lnxsrvu.winnebagoind.com[69.66.77.165] X-Barracuda-Start-Time: 1227278040 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0035 1.0000 -1.9983 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at marist.edu X-Barracuda-Spam-Score: -2.00 X-Barracuda-Spam-Status: No, SCORE=-2.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.10780 Rule breakdown below pts rule name description ---- ---------------------- --------------------------------------------------
We do collocation by groups, nodes, filespaces, or "none" depending on the storage pool. Here is our query to see if we've got any volumes that are out of spec as far as our collocation strategy is concerned. 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 In this query, we should see a "1" in the column corresponding to the collocation type for a storage pool. For example, the "2" in the groups column for tcopy2b shows me that this volume has information from 2 groups. This should be remedied for fastest recovery in a DR situation. TARCH1 is not collocated, so WG1016 is fine with 4 groups and 5 nodes. TPOOL2 is collocated by node, so the 3rd volume is fine, since it shows just 1 node on the volume. TCOPY3B has directory information on it and is collocated "none", so it also is fine with 131 filespaces and 84 nodes. Pool Access Volume Groups Nodes FSpaces Util Recl --------- ------------------ --------- ------ ----- ------- ------ ------ TCOPY2B OFFSITE WG1095 2 6 8 85.4 14.6 TARCH1 READWRITE WG1016 4 5 6 97.1 2.8 TPOOL2 READWRITE WG1002 1 1 5 0.6 0.0 TCOPY3B READWRITE WG1062 6 84 131 1.4 0.0 Bob -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Friday, November 21, 2008 6:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Collocation question ---- ---------------------- -------------------------------------------------- On Nov 21, 2008, at 6:20 AM, Minns, Farren - Chichester wrote: > Hi all > > Quick question. > > Am I right in thinking that if I have collocation set for a primary > storage pool and I run out of scratch volumes that TSM will just try > to put data on any other volumes with free space? The Administration Guide manual is must-reading for understanding how the product works. See "How the Server Selects Volumes with Collocation Enabled" therein for the rules table. Richard Sims 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.