ADSM-L

Re: Space reclamation of copypool

2002-08-02 17:07:27
Subject: Re: Space reclamation of copypool
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 1 Aug 2002 11:55:51 +0200
Hi Geirr!
Updating the storagepool does not stop reclamation immediately. TSM stops
reclaiming when the reclamation of the current volume has finished.
Do you see different behavior?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Halvorsen Geirr Gulbrand [mailto:gehal AT WMDATA DOT COM]
Sent: Thursday, August 01, 2002 11:15
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Space reclamation of copypool


Hello everyone,
I have the following problem with Space Reclamation of my copypool.
To start reclamation I have a script running UPDATE STG COPYPOOL RECLAIM=50
Three hours later, I run another script to stop reclamation - UPDATE STG
COPYPOOL RECLAIM=100
but reclamation never stops. This affects all of my daily operations
(migration, backup stgp..) because the
reclamation process uses both drives.
Question is, why does space reclamation not stop after updating?
Is there a way of canceling the process (by TSM script)?

Best regards
Geirr G. Halvorsen


**********************************************************************
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>