ADSM-L

Re: Weird tape utilization

2004-10-13 07:52:19
Subject: Re: Weird tape utilization
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 13 Oct 2004 13:52:20 +0200
Well, it took some time convincing Level 2 support, but IBM has opened APAR
IC43086 for this behavior!
So, in the future we don't have to run the SQL statement down below anymore.
Good thing, because it runs for 9 hours in my shop! A nasty side affect is
that it puts a lock on your storage pool which causes all storage pool
update commands to hang until the command has finished!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: neil.schofield AT yorkshirewater.co DOT uk
[mailto:neil.schofield AT yorkshirewater.co DOT uk]
Sent: Wednesday, September 08, 2004 22:58
To: ADSM-L AT vm.marist DOT edu
Cc: Loon, E.J. van - SPLXM
Subject: Re: Weird tape utilization


Eric

Good luck with your PMR. In the meantime, below is a script that I wrote
when I realised that we were suffering the "tape leak" that Richard
describes.

It works on the premise that with collocation turned on, there should only
be one filling read-write volume in each storage pool per node/filespace.

The select statements list the filling volumes by node for each storage
pool collocated by node, and the filling volumes by filespace for each
storage pool collocated by filespace. Each node/filespace should be listed
only once per storage pool in the output. Scan down the output and if a
node/filespace appears more than once it means you are using more tapes
than necessary.

In this case, pick one of the volumes (ideally the least utilised), update
its access-mode to read-only and issue a MOVE DATA on it. You should see
one of the other filling volumes listed be mounted as the destination.

I usually run the script once a month or so. It may take a while, but is
worth it for the tapes you get back. Now if only TSM could take care of
this itself ...

Regards
Neil Schofield
Yorkshire Water Services Ltd.

select volumeusage.node_name, volumeusage.stgpool_name,
volumeusage.volume_name from volumeusage, volumes where
volumeusage.volume_name=volumes.volume_name and volumes.status='FILLING' and
volumes.access='READWRITE' and volumeusage.stgpool_name in (select
stgpool_name from stgpools where collocate='YES') group by
volumeusage.node_name, volumeusage.stgpool_name, volumeusage.volume_name
order by stgpool_name
select volumeusage.node_Name, volumeusage.filespace_name,
volumeusage.stgpool_name, volumeusage.volume_name from volumeusage, volumes
where volumeusage.volume_name=volumes.volume_name and volumes.status
='FILLING' and volumes.access='READWRITE' and volumeusage.stgpool_name in
(select stgpool_name from stgpools where collocate='FILESPACE') group by
volumeusage.node_name, volumeusage.filespace_name,
volumeusage.stgpool_name, volumeusage.volume_name order by stgpool_name






Find out about our new Icytonic drink at http://www.yorkshirewater.com
The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>