Hey All,

According to my research and the TSM Admin Guide, a restore process should
preempt reclamation when mount points are short. Obviously, I'm not seeing
that behavior. :)

Here's my setup:

TSM 5.3.4

Server option NOPREEMPT set to 'NO'.

I have 2 IBM 3494 libraries. Each library has 4 drives (8 drives total).

TAPEPOOL: Primary storage pool is on Reclamation is running for Lib A.
COPYPOOL: Copy pool is on Lib A.
DRMPOOL : Offsite Copy pool is on Lib B.

Scenario:

Reclamation is running for TAPEPOOL, COPYPOOL, with MAXPROCS=2. All four
drives in Lib A are in use.

Lib B is using two drives for reclamation of DRMPOOL, 2 idle drives.

Client starts a restore and waits...waits...waits...

Why doesn't one of the reclamation processes get preempted?

--
Bill Carlson
--
Systems Administrator bill-carlson AT uiowa DOT edu  | Anything is possible,
HCIS                                          | given time and money.
University of Iowa Hospitals and Clinics      |
Opinions are mine, not my employer's.         |