Lots of people have a best-practice of always keeping at least one
drive free for user restores.
That minimizes the problem.

It makes users happy too, because
even though a restore does pre-empt another task, it may take TSM 40
minutes to finish the reclamation it was working on and give up the
drive.

So the user has to sit waiting for far too long (in some cases).


------
Lindsay Morris
Principal
www.tsmworks.com
919-403-8260
lindsay AT tsmworks DOT com



On Nov 4, 2008, at Nov 4, 12:21 PM, Bos, Karel wrote:

No :)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of
Thomas Denier
Sent: dinsdag 4 november 2008 18:14
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Offsite reclamation problem

We have a 5.4.2.0 TSM server running under mainframe Linux. We have
five
tape drives available for our primary tape storage pool and five tape
drives available for our copy storage pool. We run offsite tape
reclaimation with 'maxproc=5'. If a client runs a restore while off
reclamation is going on, TSM will take a tape drive away from
reclamation. This is done by cancelling a reclamation process, rather
than having a process go into mount point wait. TSM does not start a
replacement process when this happens. A restore that runs for a
couple
of minutes can leave a pair of tape drives sitting idle for hours. Is
there any configuration setting or release level upgrade that will
cause
TSM to handle this situation more intelligently?

<disclaimer.txt>