|
I use the Appendix E. roadmap (from Backup&Recovery) but do some steps differently. I setup my DASD before the migration. I load the target system from the I_Base CD so I can run DST. I add the drives and setup RAID or Mirroring as needed then do an IPL (which will fail because of no OS, but does go through the disk management steps). This saves a lot of time before the cutover window as the DASD prep can take hours. Because I have the LIC install for the DASD work when I IPL from my Save 21 tape (D IPL) I take Opt #1 on the Install Licensed Internal Code screen "Restore licensed internal code" rather than Opt #2 as the manual states. This gets me the LIC from the old system with the MFnnn PTFs. When I run the restore Opt #21 I set Prompt to Y not N as in the book. This causes a few breaks at the beginning of the run but just take all the defaults and hit enter. The long RSTLIB *ALLUSR runs, then the DLO and IFS restores. When the RSTAUT command is prompted I abort (F3). This is the last step. At this point I take my 2nd pass restore to recover all the LFs that were not restored in the initial restore because the are dependant on PFs that are in libs not the same as the LF. RSTLIB SAVLIB(*ALLUSR) DEV(TAP01) OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL) ENDOPT(*UNLOAD) When this 2nd restore is done I run the RSTAUT. This way it also sets the authority on the LFs. If you let the RSTAUT run from the Opt 21 you will not have the file needed to run it again after the LFs are restored and you would have to run RSTUSRPRF again to rebuild the authority file. Also, do not IPL before you run RSTAUT as this also clears the auth file. Also, be sure to do all your cable change planning. Many connectors are different going from SPD to PCI, Ensure you can reach your new system with all the cables. Plan your WRKHDWPRD resource mapping before the cutover. -- The migration of spool files can be a huge problem. I have written code using API's, tried 3rd party products, and setup RMTOUTQs, to port the reports. Each method works, but each has its problems. On small systems its doable, but I'm currently planning a large system migration and not finding a workable solution. With 1,700 outqs, 150,000 splfs (not including joblogs), and many reports well over 50,000 pages (biggest 480,000 pages). The requirement to retain the report date, user, and job/usr/nbr info is a problem. I have the entire save down to about 2 hours by running 15 concurrent save jobs but that's still a lot of time out of my cutover window (Christmas day). If anyone has a great way to handle splf migration, please share it. --- Doug Hart -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Thursday, December 02, 2004 1:09 PM To: Midrange Systems Technical Discussion Subject: RE: Does Go Restore Option 21 restore ptf's??? Backup and recovery guide has an appendix D on restoring your system to another system. Doing it that way will NOT lose any ptf's. You will lose spool files. If you are running 5722AC3 you may have to delete it, restore it from IBM media and reapply it's ptf's. Apparently it doesn't like being saved from one system to another. To get ptf's, etc, over VPN working after doing unload's reload's I've always had to do this. An IPL from the tape is involved. This appendix will cover it. Read it carefully. There is an option on GO RESTORE 21 that you want to tell it that you are restoring to a different serial number. If you have special authority on output queues be prepared to fix it from scratch. We had to repair a few hundred output queues. The RSTCFG is done prior to the RSTUSRPRF is one of the problems. The other is that you cannot do a DLTOUTQ on an output queue assigned to a printer without deleting the device. Thus when you attempt to restore QUSRSYS (which had your old security settings) it won't get them back. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.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.