1 - 48 hours is a good guess-a-mint. First off how many drives are you
replacing? What is your DASD controller? Can you add the new drives to
the system prior to removal of the old drives? To add the drives and
build your raid set, do not add to ASP at this time. Next in restricted
state, full backup to cover your butt, then do the load source
migration. Now add the new drives to your ASP. (load source should
have been added by the migration.) Now there is a command to remove the
old 8 GB drives from service. This will move all the data off the old
drives except a very small amount. This step can be done during
production thus reducing your down time. Next you need to be in
restricted state to remove the old drives. This is very quick since the
previous step moved the majority of the data.
Once the system is back up, you can monitor your DASD using with the
TRCASPBAL for a day, best during working hours. Then at night,
Now if you cannot add the new drives until you remove the old drives,
well you have a whole different process to follow. But time all depends
on CPW, MEMORY, DISK controllers, and number of drives.
Director of Information Services
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John.BresinaJr
Sent: Wednesday, October 10, 2007 7:53 AM
Subject: Load Source Migration
We are swapping out all our old slow 8gb drives for 70gb 15000rpm drives
next weekend in out 840. We are also going to be doing a load source
migration. Does anyone have a clue to about how long this will take?
We are needing to put a rough estimate in our plan so the business knows
what their downtime will be.
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact