|
Bill! Please read the book! http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/books/sc415 304.pdf An Option 21 restore is not one step, it is six: 1.) RSTUSRPRF USRPRF(*ALL) 2.) RSTCFG OBJ(*ALL) 3.) RSTLIB SAVLIB(*NONSYS) 4.) RSTDLO DLO(*ALL) SAVFLR(*ANY) 5.) RST DEV('/QSYS.LIB/your tape drive.DEVD') OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT)) 6.) RSTAUT Steps 2 though 5 map into John's step 2 below. Remember that you must be in a restricted state to run a RSTUSRPRF with USRPRF(*ALL). Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 30 Aug 2005 07:59:15 -0700 from: "Bill" <brobins3d@xxxxxxxxx> subject: Re: RstUsrPrf in a Disaster Recovery John Earl wrote: > Relative to security, the steps for a complete system restore are: > > 1. Do a RSTUSRPRF from last night's SAVSECDTA > > 2. Restore the most relevant version of all of the objects you want > to put back onto the system > > 3. Stop!!! Don't let the users on yet!!! You first have to do a > RSTAUT to synch up all of the object authorities and the user > profiles. > > 4. Let your users back on. > > You do the RSTUSRPRF first because the RST* commands will assign > object ownership to QDFTOWN if an object is restored and the system > does not recognize the owner listed on the object. John, It sounds like you are saying that I should do the Restore 21, then your Step 1, correct? If so, that was going to be my plan. But doesn't that sequence of events mean that any user profiles that were deleted since the Save 21 will now be back on the system? If so, that's the piece I can't get a handle on; it would seem to me there would be a better way to handle that situation. And this will be my 3rd Scratch/Restore in the last month, so I'm getting a bit more comfortable with it. Bill
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.