Ok, our problem is back!  Now, it does bring the pool to 0%.

Ken and John, can you verify if we are having the same problem?

At the point when migration is not moving any data, does your CPU
Utilization go up to 100% and stay there until you raise the Migration
values?

Thanks,

Tim Rushforth
City of Winnipeg

-----Original Message-----
From: Rushforth, Tim
Sent: Thursday, February 01, 2001 5:28 PM
To: 'ADSM: Dist Stor Manager'
Subject: RE: Migration doesn't end


We've had what sounds like a similar problem.
In our case, migration would not end, CPU Utilization would hit 100% at a
certain point during migration.

In our case though there was still data left on the volumes (about .1%).

Our problem was fixed by running an AUDIT DB.

Tim Rushforth
City of Winnipeg

-----Original Message-----
From: Kenneth & Susan Bury [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 01, 2001 5:08 PM
To: [EMAIL PROTECTED]
Subject: Re: Migration doesn't end


We have the same problem on our 3.7.4 server. We workaround with the low set
for 1%.

Ken

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
> John Monahan
> Sent: Thursday, February 01, 2001 17:54
> To: [EMAIL PROTECTED]
> Subject: Migration doesn't end
>
>
> TSM Server and clients 4.1.0 NT
>
> One of my disk pools is performing the never-ending migration process. I'm
> migrating from disk to one of two drives in a 3494.  Migration is started
> by
>
> update stgpool diskpool hi=0 lo=0
>
> after it is started
>
> update stgpool diskpool hi=90
>
> The migration process usually takes around 15 minutes and then the
> "migration process X ended for storage pool DISKPOOL" message comes and my
> migration values are then set back to hi=90 lo=70.
>
> For the last couple of days, I have not gotten the migration process has
> ended message and the process has been lasting for hours even though when
> I query the diskpool, the pct migr value is 0 indicating that all files
> have migrated.  The only way I have gotten it to stop is to reset my
> migration values for the diskpool back to hi=90 lo=70, and then finally
> the finished message and the process ends.
>
> I do have caching enabled on both diskpools, one works fine, the other is
> having this problem.  It has happened with different drives and tapes, so
> that pretty much eliminates a drive or tape problem.  Any other ideas?
>
>
> ===========================================
>     John Monahan
>     Network Team Coordinator
>     Liberty Diversified Industries
>     (763) 536-6677
> ===========================================
>

Reply via email to