RE: load source migration

 
No DST has a function for just copying the load source drive.  This is a
special copy as this is the boot drive.  The drives are flagged after
the copy so they must be removed and relocated right after the copy and
at the powerdown before IMPL.  It does not change the data on other
drives and the system does not need to be reloaded, no scattering done.
If you want you can run a load balance after your are up and running
again but not really needed.

--
Doug Hart 
 

-----Original Message-----
From: midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+doug.hart=itt.com@xxxxxxxxxxxx] On Behalf Of
Pat Barber
Sent: Thursday, February 22, 2007 1:47 PM
To: Midrange Systems Technical Discussion
Subject: Re: load source migration

I doubt you can really control where data goes on a "specific" drive
since the system does a scatter load.

The source load is only "specific" load you can really do to my
knowledge.

The CE function using DST of "gig-mig" or "pumping"
a drive will move data to a specific drive but that can get awfully
tricky since it's a disaster recovery method.


I believe a unload/load is still the best method.


Chris Bipes wrote:

I have just added 4 new drives to my system and built the raid-5 set.
Before adding to the ASP I would like to migrate my load source to one

of these new, larger drives.  This would be in preparation for 
replacing the smaller drives with larger faster drives.  Is this a DST

function cause I could not see how in SST.

************************************
This e-mail and any files transmitted with it are proprietary and intended 
solely
for the use of the individual or entity to whom they are addressed. If you have
received this e-mail in error please notify the sender. Please note that any 
views
or opinions presented in this e-mail are solely those of the author and do not
necessarily represent those of ITT, Inc. The recipient should check
this e-mail and any attachments for the presence of viruses. ITT accepts
no liability for any damage caused by any virus transmitted by this e-mail.
************************************