× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Last night, I concluded a 177 SSD to 775 SSD Disk Swap, including load source.
There are few points I would like to document for the archives, revising my original plan to minimize downtime.
No HA/DR LPAR solution in place.
This was a Power7, 8205-E6C, 5913 dual controllers 5887 EXP24S mode 1 , 18 177 SSD, 2 RAID-5, no hot spare. 2.9 TB, 93% capacity.
Afterwards, 13 775 SSD, 2 RAID-5, 2 hot spares. 7 TB, 37% capacity.

1) When starting RAID-5 with hot spare, I lost 2 units to hot spare, originally I was informed only 1 would be needed, not sure why?
Documentation states you only need 1 hot spare per IOA.
Not sure if I can correct this, possibly remove the 2nd hot spare.

2) When adding disks, if empty disk slots available,, use 8. Device Concurrent Maintenance and avoid IPL.
IPL marks drives as "dirty" and forces an initialize during prep. 140 minutes for a single 775 SSD.
Last week I had to cancel option 9, disk to disk copy of load source because of this added prep time.

3) "Prep" or "Initialize" times.

According to IBM, when Option 9, copy disk unit data, requests the destination disk.
IBM sends a command to the disk.
If it comes back as a "clean" disk, then initialize is NOT done.
If it comes back as a "dirty" disk, then IBM issues the command to format the drive.
Each drive manufacture may do formatting differently.
Currently, there is no known method to determine if a drive is "clean" or "dirty"

This also applies when "Adding to ASP"

So it's not IBM's code, but the various disk manufactures format procedures and if a disk is "clean" or "dirty" that determine the time needed for "load source disk to disk copy" and/or "add to asp".

My other 5 drives must have been "clean" only 1 minute to "Add to ASP"
When drives where smaller, 4, 8, 17, 35 etc, these times were much smaller.

IBM is working to reduce these "Prep" times in future release as these times keep increasing as drives get larger.

4) When moving the load source, IPL to DST,
A) Add new drives concurrent.
B) Start RAID-5 with hot spare, 1 minute
C) Load source move - option 9, disk to disk copy.
D) Load source "prep" only 1 minute, "clean" drive and new parity set.
E) Load source copy from old 177 SSD to new 775 SSD, 40 minutes.
F) Delay adding other drives to ASP, do after IPL using SST, not DST. 3 to 4 hours.

5) After all new disks are added
STRASPBAL TYPE(*CAPACITY) TIMLMT(*NOMAX) PRIORITY(*MEDIUM)

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/







Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.