|
Hi, To give you a truly crisp reply, I need to have access to a system, which I do not have here. I will not be back in the office until next Tuesday. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Evan Harris <spanner@ihug.co.nz To: midrange-l@midrange.com > cc: Sent by: Subject: Re: go restore optn 21 source code midrange-l-admin@mi drange.com 03/27/02 02:39 PM Please respond to midrange-l Al Note that I am not disputing what you say just searching for some clarity <g> If I RSTUSRPRF for _all_ user profiles on a system can I then restore some libraries from a save and RSTAUT then restore some more libraries and run another RSTAUT ? This would allow me to recover, for instance, my order entry applications and leave the reporting applications till later in the recovery. I certainly remeber doing this on a B60 and D60 after the RSTLIB and then again after the RSTDLO. As I understand it, if I restore all the user profiles, then each object that I restore will have all the profiles specified in its authority table in existence at restore time. I understand that RSTAUT does something like rebuilds the internal references between the objects authority table and the user profile internals allowing the object to be used as designed. My experience is that the above works and is what is documented and that is what I was referring to. I'll have to check the manuals later today, but are you saying this won't work or some other process ? I was not referring to the idea of restoring some user profiles then restoring others later (how would you actually do that ?) just the strategy of staging the restores form one system save to return the system partially. Regards Evan Harris >For each and every RSTAUT, you need to do a previous RSTUSRPRF. RSTAUT >propagates the specific authorities from the user profiles to the objects >themselves. It is critical that you do NOT to a RCLSTG between RSTUSRPRF >and RSTAUT, because RCLSTG takes the authorities on the objects, and >spruces up the user profiles. The would be tantamount to the MAKEAMESS >command. > >Al - in Framingham > >Al Barsa, Jr. >Barsa Consulting Group, LLC > >400>390 > >914-251-1234 >914-251-9406 fax > >http://www.barsaconsulting.com >http://www.taatool.com > > > > > > > Evan Harris > <spanner@ihug.co.nz To: midrange-l@midrange.com > > cc: > Sent by: Subject: Re: go restore > optn 21 source code > midrange-l-admin@mi > drange.com > > > 03/26/02 01:54 AM > Please respond to > midrange-l > > > > > > >Kirk > >my recollection is that Tom's suggestion will work. I have done this a few >times to get parts of applications working again before the entire restore >is completed. > >So you could RSTUSRPRF then -> RSTLIB -> RSTAUT -> RSTLIB -> RSTAUT as many >times as necessary. > >In the old days - slow tape drives and no raid (not to mention 3370's and >9332's) - a staged recovery allowed a business to be restarted well before >the entire recovery was completed. > >Maybe this has changed but I'd be surprised. > >regards >Evan Harris > > > >Won't work again without restoring profiles again... > > > >thomas@inorbit.com wrote: > > > > > > Steve: > > > > > > I've never had to do this, but for future reference it might work > > > for somebody. Maybe someone could verify this. > > > > > > Given the sequence that you first ran the commands in, it seems > > > possible that simply running RSTAUT a second time after you ran > > > the others would've fixed most problems. I wouldn't expect > > > running RSTAUT twice like that to cause more trouble. > > > > > > Tom Liotta > > > > > > On Mon, 25 March 2002, "Steve Richter" wrote > > > > > > > The reason I asked is because the procedure in backup and > > > recovery , chapter > > > > titled: "How to restore specific types of information" ( chap > > > 17 in my v4r3 > > > > version ) has the wrong sequence of events. > > > > > > > > It says "the topics are presented in the same order as the > > > recovery > > > > operations should occur". > > > > First is RSTUSRPRF, next is RSTAUT !!, then RSTCFG, RSTLIB, ... > > > Following > > > > these steps caused all sorts of problems which I corrected by > > > restarting the > > > > scratch install. > > > > > > > > -----Original Message----- > > > > From: midrange-l-admin@midrange.com > > > > [mailto:midrange-l-admin@midrange.com]On Behalf Of Kirk Goins > > > > > > > > It may be there somewhere... The Backup and Recovery guide > > > gives you each > > > > cmd > > > > > > > > Here's the short version > > > > RSTUSRPRF > > > > RSTCFG > > > > RSTLIB *NONSYS > > > > RSTDLO > > > > RST > > > > RSTAUT > > > > > > -- > > > Tom Liotta > > > The PowerTech Group, Inc. > > > 19426 68th Avenue South > > > Kent, WA 98032 > > > Phone 253-872-7788 > > > Fax 253-872-7904 > > > http://www.400Security.com > > > ___________________________________________________ > > > The ALL NEW CS2000 from CompuServe > > > Better! Faster! More Powerful! > > > 250 FREE hours! Sign-on Now! > > > http://www.compuserve.com/trycsrv/cs2000/webmail/ > > > > > > _______________________________________________ > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >list > > > To post a message email: MIDRANGE-L@midrange.com > > > To subscribe, unsubscribe, or change list options, > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > > or email: MIDRANGE-L-request@midrange.com > > > Before posting, please take a moment to review the archives > > > at http://archive.midrange.com/midrange-l. > >_______________________________________________ > >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing >list > >To post a message email: MIDRANGE-L@midrange.com > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > >or email: MIDRANGE-L-request@midrange.com > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/midrange-l. > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. > > > > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.
midrange.com
