Hi
Here it what I did and it worked .But the question is why it left little
data in disk sequential volumes before.
Till now I am yet to get reply from IBM.
I basically deleted all the residual data left over reclamation undone.Thn
Then once again the process took place yesterday from tape to sequential
disk pool then migrated back to tape pool.
It went fine.
Then how come before it left some disk sequential volumes with little data.
This shows at next time migration went down to 0%.But not at the first time.
My question is why .Will I face problems in future?
Balanand pinni
-----Original Message-----
From: PINNI, BALANAND (SBCSI)
Sent: Tuesday, April 24, 2001 1:04 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: PROBLEM IN MIGRATION FROM SEQUENTIAL DISK POOL TO TAPEPOOL.
Importance: Low
Sims
Thanks I did force migration and I get ANR1082W SPACE RECLAIMATION
TERMINATED FRO VOLUME
INSUFFICIENT MOUNT POINTS AVAILABLE.How come it is doming reclaimation on
left over volume
when i ask forced migration.
balanand.
-----Original Message-----
From: Richard Sims [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: PROBLEM IN MIGRATION FROM SEQUENTIAL DISK POOL TO TAPEPOOL.
>Though migration is limited at 0% lower limit on disk pool with next pool
as
>tape pool.
>
>My problem is why it does not migrate the end volume data and keeps little
>data in it.
Balanand - I wonder if you are encountering the situation described under
the description of the LOwmig operand in DEFine STGpool, in
the Admin Ref manual:
"When the storage pool reaches the low migration threshold, the server
does not start migration of files from another volume. You can set the
low
migration threshold to 0 to permit migration to empty the storage pool."
They seem to be saying that if you tap it on the shoulder, via an UPDate
STGpool command with LOwmig=0, that it might go on to address the remnants
of
the data. See if that does it, and let us know. In any case, it's a
nuisance, so it's good that you reported it to Tivoli. It might be that
migration stops when the amount drops to the decimal value 0.something, as
opposed to integer 0.
Richard Sims, BU
