Is it supposed to take forever and 2 days to reclaim my Copy Dirs pool?
Not for the price of the product...
You haven't told us if you are checking for tape drive contention,
as in drives busy with higher priority tasks.
If no contention, you may have some difficult tapes, consuming costly
Rushforth, Tim
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
PEG.CA cc:
Sent by: ADSM: Subject: Re: Reclaimation of Copy Dirs
Dist Stor
Manager
the storage pool and have the reclaimation
stop,
I have to kill the specific process number.
So everyday I setup a schedule to kill the job number of the copy dirs
reclaimation at 3:00 am.
More tape drives are coming, but there's got to be a better way.
Windows 2003 Server
SP3
TSM 5.1.5.0
It seems
pool and have the reclaimation stop,
I have to kill the specific process number.
So everyday I setup a schedule to kill the job number of the copy dirs
reclaimation at 3:00 am.
More tape drives are coming, but there's got to be a better way.
Windows 2003 Server
SP3
TSM 5.1.5.0
It seems like maybe
Richard mentioned the APAR - IC34386 - looks like this appeared in 5.1.5.2.
-Original Message-
From: Debi Randolph [mailto:[EMAIL PROTECTED]
Sent: August 5, 2003 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Reclaimation of Copy Dirs
Yes, the on-site copy on Disk.
We're running V5R1L5.0
So
:
Sent by: ADSM: Subject: Re: Reclaimation of Copy Dirs
Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
08/05/2003 01:20
PM
We've had multiple discussions on this list about slow copy pool
reclamations; a common culprit is a cached disk pool, which forces TSM
to use the copies of files still existing in your disk pool, but only
*one at a time*, rather than the batched file moves that take place from
a primary tape pool
PROTECTED]
PEG.CA cc:
Sent by: ADSM: Subject: Re: Reclaimation of Copy Dirs
Dist Stor
Manager
[EMAIL PROTECTED]
.EDU
08/05
