The customer is NOT always right; find out what problem he's really trying
to solve -- that's what you're gonna hear eventually, so get to it now
(right after you explain that you could list all the tapes, if that's what
he really wants, but he's probably trying to discern how many tapes he'd
need to mount in case of disaster... which, of course, is a typically
different question.)
If you want a "cheap" way to answer the "real" question (and much faster
than SELECT), run export (of the node) in preview mode, use
FILEData=BACKUPActive option and (if desired, only) the filespaces that he
wants, to get a realistic sense of the tapes required.
Another even "cheaper" answer is the old SELECT DISTINCT from VOLUMEUSAGE
table; this can get you the tapes used on a per node, per storage pool,
and/or per filespace basis -- something like the following:
select filespace_name,volume_name from volumeusage where node_name='____' -
and copy_type='backup' and stgpool_name='<YourBkupStgpoolName>'
or, maybe...
select distinct volume_name,stgpool_name from volumeusage \
where node_name in ('F1N11_ADSM','VARCEDT2_ADSM','VARCEDT3_ADSM',-
'VARCMDT1_ADSM','VARCEST1_ADSM','LTCAEST','LTCACST','LTCARC1_ADSM')
and -stgpool_name='PTARCTPOOL' >>
c:\whyowhy\select-volumeusage-PT-Decom-2.txt
or, the simplest...
select distinct node_name,volume_name,stgpool_name from volumeusage \
where node_name='EXCHMO05_EXC' and stgpool_name='3570TAPEPOOL'
the truly-long-running version is in the archives (August 8, 2002).
We did submit a requirement to Tivoli development for the "true" issue that
arises; if a customer has an over-subscribed silo (ie, insufficient
capacity to hold all the backup volumes), he's typically used MOVE MEDIA (or
some such checkout/checkin procedure) to make room for more data... this
customer gets irate when he learns he must provide round-the-clock tape
operator to respond to tape mounts when he has a total-server-recovery to
do,,, so, we think this could be mitigated by getting a consolidated (ala,
classic restore does this) list of tapes before starting the restore, then
loading up the silo with enough of them to get thru the unmanned portion of
the restore period.
We have requested a "preview" option for restore/retrieve that provides
similar info as export-preview (ie, the list of volumes, number of bytes to
be restored, etc. --- classic restore does at least TWO important things
we'd like: (1) consolidates tape mounts (I think no-query might have finally
been changed to do this, so as to minimize tape mounts), and (2) only
requests the data that is needed, as per restore/retrieve specifications
(which NQR can never do,,, that's how it gets to be so fast, just sending
all the data down the network and letting the client choose which data to
accept vs. ignore).
Don France
Technical Architect -- Tivoli Certified Consultant
Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390
San Jose, Ca
(408) 257-3037
mailto:don_france AT att DOT net
Professional Association of Contract Employees
(P.A.C.E. -- www.pacepros.com)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Pitur Ey~srsson
Sent: Thursday, October 17, 2002 3:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SQL Script
Hi TSM Friends.
I am looking for a SQL Script, that a client of mine wants.
He wanst to be able to see on what volume a spesific file is. and secondly
he wants to be able to see on what volume(s) a filespace is on.
has anyone a script like that. I know this script will be realy heavy in
process. but you know "the customer is always right"
Kvedja/Regards
Petur Eythorsson
Taeknimadur/Technician
IBM Certified Specialist - AIX
Tivoli Storage Manager Certified Professional
Microsoft Certified System Engineer
peddi AT itn DOT is
Nyherji Hf Simi TEL: +354-569-7700
Borgartun 37 105 Iceland
URL: http://www.nyherji.is
|
