I finished the 'copy disk unit data' and everything worked great. One critical step, and Larry Bolhuis talked about this. IBM technical document says to physically remove all non-configured disks AND the original LS disk after power down. Then take the new LS disk (non-configured) and place it in the same slot as the old LS disk and IPL to DST. Mapping disk slots and serial numbers, as Pete suggests, really is critical.
Since I am not moving the new LS disk to the old LS slot and I am tagging a new disk controller as the load source, the old LS disk must remain in the system until next IPL or you will receive an error at IPL. After the 'copy disk unit data' completes, disk configuration is unchanged; the new LS remains non-configured and the old LS remains in the ASP as disk unit 1. After power down and IPL to DST, the system will automatically perform the final step; the old LS will be non-configured and the new LS will be in the ASP as disk unit 1. Then you can power down and physically remove the old LS disk if desired.
Again, much appreciation to Larry, Chris and Pete for helping me through this project. Now I can get on will moving my iASP from external storage to internal storage.
Robert
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, March 25, 2009 2:08 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Copy Load Source
Chris makes some great points, and all I would add is no each serial number
of every drive before you start. Have a map on paper, and your external tag
that Chris talks about should associate with a serial number.
I have done dozens and dozens of these, and that paper map with serial
numbers and associated tags numbers has always been a blessing.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Wednesday, March 25, 2009 2:20 PM
To: Midrange Systems Technical Discussion
Subject: RE: Copy Load Source
Once you have added the 3 drive to your ASP, which can be done live, I
would deallocate and move data while the system is up and running. This
can be done the day before your planned down time and greatly reduce the
time it takes to remove the drives from the raid set. Yes you can
deallocate and move data off the load source. You will see that it
retains a high percentage of usage over the non load source drives.
Don't forget to remove the old drives once you power down. Also label
each drive with the location you remove them from, just in case you
cannot locate the new load source.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Gray
Sent: Wednesday, March 25, 2009 10:40 AM
To: Midrange Systems Technical Discussion
Subject: RE: Copy Load Source
Thanks Chris, those are the steps I have listed, it was the option to
copy the disk unit data to the one unallocated disk that had me a little
baffled. I couldn't get around how to add the non-configured disk to the
ASP without losing the data. I've learned that when you copy the disk
unit data and bring the system back up with the HMC pointing to the new
load source disk, the disk will be in the ASP.
Sorry for any confusion, I doing basically what IBM calls an Upgrade
load source disk unit with device parity protection. Out with the 35GB
drives and in with the 141GB drives, all within the same ASP. I was
concerned about the move to a different IOA because of the instructions.
It used to be necessary to copy the load source data to the new 141GB
disk and then physically move the 141GB disk to where the original load
source resided (i.e. same CEC, same IOA, same slot).
Now with LPAR and HMC, you can point to the new load source disk (i.e.
new CEC, new IOA, new slot) and power up the system.
Of course, you want to have a good full backup so you can go to option
2, scratch install, if it fails.
This is my plan
1. Raid all four 141GB drives
2. Add 3 to the ASP. Leave the first drive in the RAID set out for
my load source.
3. Deallocate the 35GB drives
4. IPL to DST
3. Remove the 35GB drives from the ASP all except the load source.
4. Then from DST, 'Copy disk unit data' from load source (35) to
the non-configured 141GB.
5. Power down system
7. The on the HMC, I set my load source to point to the IOP
controlling my 141GB drives.
8. IPL and STRASPBAL *capacity.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Friday, March 20, 2009 1:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: Copy Load Source
The proper steps are roughly:
1. Add new disk to CEC using SST (System can be live but I have better
luck when shutting the system off before adding new disks.)
2. Build raid set with the 4 new disk
3. Add 3 of the 4 drives to the ASP (1 if for system and load source.)
4. Deal locate the old drives using STRASPBAL TYPE(*ENDALC)
5. Move the data off of the drives, this can include the load source as
well. (note that this does not move the necessary boot data off of the
load source.)
6. The rest is done in DST, so boot to DST.
7. Move the load source to the drive that was not added to the ASP. It
should be the only unallocated drive in the system.
8. Remove all the old drives from the ASP at this time. Since you live
moved the data, it should not take long.
9. End the raid on these old drives.
10. Shut the system off and remove the old drives.
11. Now IBM says you should put the new load source in the same spot as
the old one but I believe you can use your HMC to relocate the load
source.
I basically did this not too long ago, but replaced 12 17GB with 12
35GB's and had to do it a piece at a time as I had no empty drive slots.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Friday, March 20, 2009 10:52 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Copy Load Source
Kirk,
I agree with you 110%, but there was something in this post that
was
bothering me and I think he wants to do more than what you give him the
correct instructions for.
Robert states " I'm moving data and load source from 12 35GB
drives
to 4 141GB drives in a different CEC. I will need to add the disk to the
ASP
filled with the other 141GB drives after this 'copy disk' operation."
He can't take the set of copied disks and just add that set of
disks
to an existing ASP. That would be like adding two sets of ASPs
together.
Perhaps I am just reading what he wrote incorrectly.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This email and any attachment(s) is intended solely for the person or
entity to which it is addressed and may contain confidential and/or
privileged information of AAA Cooper Transportation. Unless expressly
agreed to the contrary, no representation is made by this email and it
must only be used for the purpose for which it was supplied. Unintended
recipients must not make or resend copies of this email, nor use its
contents for any purpose.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This email and any attachment(s) is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information of AAA Cooper Transportation. Unless expressly agreed to the contrary, no representation is made by this email and it must only be used for the purpose for which it was supplied. Unintended recipients must not make or resend copies of this email, nor use its contents for any purpose.
midrange.com
