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 P
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
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
202-458-8340 - Work
Orville Lantto
You cannot migrate the data without reducing the MIGDelay value. TSM will fail
the backup before violating the MIGDelay specification. So, yes, by lowering
the MIGDelay, you can get the oldest data off first.
Orville L. Lantto
Glasshouse Technologies, Inc.
Cell: 952-738-1933
_
