I don't have first-hand experience with this, but the documentation
supports Muthu's statement. MIGCONTINUE=YES should allow migration
to migrate data that doesn't meet the MIGDELAY threshold if it needs
to. If it doesn't work this way, that's a defect and should have
been reported.
At 12:03 PM 3/1/2006, Orville Lantto wrote:
The MigDelay parameter was introduced to work with Content Manager
OnDemand. I have seen this parameter cause transactions (in a check
image archive at a major bank) to fail because the disk pool was
full. It is enforced in an absolute fashion. You are responsible
to assure that the disk pool has enough room for the number of days
you specify for MigDelay.
Muthukumar Kannaiyan wrote:
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM MIGDelay and MIGContinue Question
Lantto,
I thought, MIGContinue parameter would take care of migrating
data. What
algorithm TSM uses to migrate the data off from staging. I think it
goes by the
file size rather than the arrival date. I am not sure.!!
Regards
Muthu
--
Paul Zarnowski Ph: 607-255-4757
Manager, Storage Systems Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
