Well, not really.  Normally you would limit the number of tapes Admin
processes can have mounted at any one time so that you always have at
least 1 drive free for just such events.  Hence the reason some time
back so many folks opted for an odd number of tape drives (like 9) so
that they could run 4 reclaim processes and have a drive free.

Also, you don't want all your drives busy all the time.  While this may
seem efficient, it can really hinder a lot of things you may want to do
at different times.  Such as run a first time backup of a direct to tape
client, or run a quick needed db backup, etc.  So, even though you have
10 drives I would strive to keep at least 1 or 2 available at all times.

See Ya'
Howard


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Bos, Karel
> Sent: Tuesday, November 04, 2008 11:52 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Offsite reclamation problem
> 
> Still kinda strange that TSM can't simply pause a task instead of
> blundly canceling it.
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Mark Stapleton
> Sent: dinsdag 4 november 2008 18:47
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Offsite reclamation problem
> 
> To expand that "no", TSM has a hardset list of tape tasks, restores
> being at the top. Backups are at the bottom of this hierarchy, and
> other tape operations are kinda amorphously between them. It makes
> sense, actually. Restores are the real reason why we're all here,
> right?
> 
> There is nothing to be done for resuming tape operations after a
> restore is done, short of an external script that looks for the number
> of reclamation processes running. You can't start the old one up again
> (to get your count back to five) without stopping them all, and then
> restarting them.
> 
> --
> Mark Stapleton (mark.stapleton AT cdw DOT com)
> CDW Berbee
> System engineer
> 7145 Boone Avenue North, Suite 140
> Brooklyn Park MN 55428-1511
> 763-592-5963
> www.berbee.com
> 
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf
> > Of Bos, Karel
> > Sent: Tuesday, November 04, 2008 11:22 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] Offsite reclamation problem
> >
> > 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?