|
Building parity is done via DST (dedicated service tools - normally a CE function). Once built, recovery can be performed concurrent. You might find that less time would be spent by reloading your system. At V4R3 on a 620 configuring and protecting five 6607s in a new parity set took literally minutes. Recovering protection on one disk of a 10 disk parity set took two hours concurrent with users. Mirroring is definitely a step above raid 5. Lost a cache card recently and lost all data on my system causing a scratch reload. No cache involved with mirroring. Alex A. Moore ~ CIO Ellis Hosiery Mills, Inc. alexm@ellishosiery.com <mailto:alexm@ellishosiery.com> > Can anyone tell me how the actual upgrade will work - will the machine > re-allocate the storage over the new dasd arms & create the parity > information during IPL, or is there anything else that needs to be done? > Any ideas as to how long this will take if so? > Also, would it be better to do a reclaim storage before or after the upgrade > (or both)? > > Lastly, i have heard that it would be better to mirror the load source, and > raid the rest. Any views on this listers? +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.