Re: side-by-side upgrade -- MIDRANGE-L

Short of deleting all changed objects on the system, the scratch re-install is really somewhat imperative if work continued on the old system. That is because the save\restore is effectively only additive, so objects [and any members or entries within] deleted may or will not be removed on the target of the restore. Similarly for authorities removed on the source system, since the RSTAUT is additive. So that and anything else not properly performed under system change management or replication which is not then correctly applied to the target could have similar or worse outcomes [for not having been replicated], depending on the sav\rst activity that is chosen over those other means ensuring all changes will be propagated.

Those issues are resolved by ensuring the source system is fully upgraded and then saved and scratch installed & restored using the option-21 from the source.

Regards, Chuck

Ingvaldson, Scott wrote:

IMO there is no reason why you would have to re-install the V5R4M5 LIC if you didn't have any problems installing it in the first place. Just make sure that your PTF levels are the same on
both systems and start your system restore at DST using "Install
the operating system." If you want to save even more time you could just freeze changes on your production system the week before your cutover and use an Option 23 Save/Restore.

If your PTFs are current on your current system you shouldn't need to re-install those at all, they should come over with your restore.

Make sure that you have a copy of the V5R4 Backup and Recovery manual available:

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/books/sc415304.pdf

It wouldn't hurt to have the "Are You Saving the Right Stuff?" poster also:

http://www-03.ibm.com/systems/resources/systems_i_support_brms_pdf_savpost3.pdf

<<SNIP>>

Mike Cunningham wrote:

We purchased a new power 6 system as an upgrade and are able to
run both the old and new systems side by side. Our BP
installed V5R4M5 on the new system and then we did a full save
(option 21) on the current system and a full restore to the
new. They the BP installed the most recent PFTs. Total time to
backup was about 4 hours, total time to restore was about 4
hours. Adding in the PFTs added another 6. 14 hours total
downtime to make the switch. We are going to check out the new
system to be sure everything is there and running and looks
good and then schedule a weekend to make the final cutover.
Since the only thing that is going to change is our data could
we safely do a save (option 21) and then just restore
user profiles and our libraries? BP would like to blow away
everything and start from installing V5R4M5 again, then a full
restore and all the PFTs again. Looking to save that extra 6
hours of downtime.