The incremental removal/replacement works, but will take days to complete and you wind up with data that won't necessarily be distributed across the disks evenly. Performance will also likely be impacted during the removal process.
I'd do it (and have done it) the old fashioned way:
- GO SAVE/21.
- GO SAVE/21 again just in case.
- Power off.
- Pull all old drives out, noting the slot where each drive came from.
- Put the replacement drives in.
- Power up, DST, start mirroring & add to ASP.
- GO RESTORE/21.
If something goes wrong you can power off & put the old drives back in (since their slot was noted).
This has the most user downtime but you end up with the most optimal data layout (best performance).
BTW, if your apps will work on a newer OS release, upgrading to a 550 with a dozen 141GB disks would probably pay for itself in reduced maintenance and power/HVAC costs while running circles around the 730. And take 8 or 9 Us in one rack v. about two full racks worth of space for the 730 + DASD tower.
--
John A. Jones, CISSP
Sr. Analyst, Global Information Security
Jones Lang LaSalle, Inc.
Voice: +1.630-455.2787
FAX: +1.312.601.1782
Email: john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, September 24, 2008 10:18 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Replacing Disk Drives With Higher Capacity
This is an easy upgrade, just pick out a remove them from the ASP, remove
them from Mirroring, and then remove the drives from the cage, add the new
ones in (ASP & Mirror), and keep repeating. This is done via DST.
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bill
Sent: Wednesday, September 24, 2008 7:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Replacing Disk Drives With Higher Capacity
I've got a 730 on V5R2 with 48 mirrored 8GB drives, system is currently
at 70% utilization. I purchased 48 17GB drives with a plan for a full
scale replacement.
I'd really like to avoid a save/restore scenario, which I believe I
-could- do with save storage. What I'd rather do is a piecemeal
replacement. Anyone have any ideas or comments?
One idea I have would be to stop mirroring on the system. This should
give me immediately 24 unconfigured drives, correct? Could I then pull
the unconfigured 24 and replace them with 24 17GB's, configure them and
then start mirroring? Obviously the problem with this is mirroring is
stopped.
One other option would be to pick a few mirrored pairs and remove them
from the ASP. Replace them, add them back and then continue on. If
this is feasible, could this be done via SST, or would it need to be
done via DST? I'm thinking that it has to be via DST since mirroring is
involved.
Also, can the load source only be replaced with save/restore?
Backup/Restore manual doesn't seem to cover this.
Bill
--
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 is for the use of the intended recipient(s) only. If you have
received this email in error, please notify the sender immediately and then
delete it. If you are not the intended recipient, you must not keep, use,
disclose, copy or distribute this email without the author's prior
permission. We have taken precautions to minimize the risk of transmitting
software viruses, but we advise you to carry out your own virus checks on
any attachment to this message. We cannot accept liability for any loss
or damage caused by software viruses. The information contained in this
communication may be confidential and may be subject to the attorney-client
privilege. If you are the intended recipient and you do not wish to receive
similar electronic messages from us in the future then please respond to the
sender to this effect.
midrange.com
