That works if the primary and copy tape pools are in the same library.
With people using multiple logical libraries (with encrypted tape drives
for the offsite pool) it isn't necessarily an easy win.

I'd rather have IBM keep a spare at the depot, instead of paying ongoing
maintenance on one more drive. YMMV.

[RC]

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bob Levad (641-585-6770)
Sent: Tuesday, November 04, 2008 10:28 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Offsite reclamation problem

I've always liked running with an odd number of tape drives to make it
"more difficult" to busy them all at once.  Plus you have a spare for
when one is ACTUALLY down.

Bob.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
lindsay morris
Sent: Tuesday, November 04, 2008 11:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Offsite reclamation problem

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>

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.


DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.