|
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.