I've seen the middle.  Restores pre-empt the reclamation but it takes a
long time (30 minutes).  Haven't figure out what its waiting/looking for
before it decides to move on it.

Not very nice to my users to have to wait 30 minutes for a restore to
start.
               ... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley


On Sat, 17 Feb 2001, Mark S. wrote:

> > From: Nicholas Cassimatis
> > Was anything else using the tape drives?  If you have 2 drives, and are
> > running space reclaimation, your restore won't start until the reclamiation
> > ends.  Same thing with migrations tying up the tape drives.  This is why I
> > always recomend an odd number of tape drives, and only allowing one fewer
> > migration process (controlled by migprocess setting) than tape drives.
>
> >"Kelly J. Lipp" wrote:
> > Is it possible to set the restore priority in such a way that it will
> > preempt the other process consuming the tape drives?
>
> I've read somewhere in the TSM documentation a list of the priorities
> for tape operations, and I would bet a fair amount of money that
> restorations were on the top of the list, followed by several others
> such as space reclamation, with backups at the bottom of the list.
>
> This parallels my experience with TSM 3.7 and 4.1, where I've seen a
> restore request stop a storage pool backup and a space reclamation.
>
> --
> Mark Stapleton (stapleton AT berbee DOT com)
>