× 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.



Hi Everybody

We have a customer who is wanting to replace 8 X 35gb drives in a 520 running V5R3 with 8 X 70gb drives.

There seem to be at least a couple of options:

1. Move storage around to free one or two drives/replace that drive with a 70/repeat until all replaced
2. Simple unload reload using option 21
3. Use SAVSTG/RSTSTG

Option 1 is just too much messing around and involves running unprotected and powering up and down several times. Option 2 is absolutely do-able but involves losing spool files in the process, and is a little time consuming and fiddly (we've done this many times for all sorts of customers).

My reading of the Backup and Recovery Guide says that we can use SAVSTG/RSTSTG to do the rebuild so long as the new box will have at least the same number of drives of at least the same capacity, which in this case is true, so Option 3 might be a viable choice,

We've done a test of the procedure on an old 170 we had hanging round - although only back to the exact same hardware - and it certainly seems pretty straight forward, so my question is, is this a reasonable way to go about the job ? Are there any hidden gotchas with using this procedure ? Any other comments ? Is there any time advantage to using SAVSTG/RSTSTG ? For the curious, we are planning on doing at least one 21 save before the SAVSTG if we go this route.

All replies/comments welcome - thanks in advance.

Regards
Evan Harris

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.