|
Again, it all depends on your definition of a disaster. Just keeping to the technical aspects of the 400. And, keeping to what this 'manual' would be targeted for. Did someone accidentally delete a payroll file on the day we run payroll? If so, do we do a SAVCHGOBJ on a routine basis? Do we journal? etc... Are we using BRMS? Did we lose a disk drive of which we ignored the messages about other disk drives in the raid set failing? Will we be restoring to this same machine, or to a different machine? ... Then you could copy/paste each scenario from the Backup and Recovery Guide, (which I was going to but I am getting some sort of proxy error accessing it). I think you are asking them to solve your particular scenario as the one which, obviously to you, occurs most often. I'd rather have a manual I can lift, but still uses many of the possible scenarios. Rob Berendt ================== A smart person learns from their mistakes, but a wise person learns from OTHER peoples mistakes. Jeff Bull <Jeff.Bull@ITM-grou To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> p.co.uk> cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: AS/400 Disaster Recovery drange.com 09/17/2001 08:29 AM Please respond to midrange-l Hi Alan, Of course, you are right, but ... I am not actually looking for a full d/r plan : d/r scenarios, management and staff call-out contact details etc etc. ... that could/should be wrapped around the technical bit. A generic system-restore sequence list should be possible, in fact I know it is, I have used same many times in d/r practices. If a given AS/400 uses journalling and another not, fine, bypass the steps where not relevant; and the instructions would say as much, and in the appropriate chronological sequence. -----Original Message----- From: alan shore [mailto:SHOREA@dime.com] Sent: 17 September 2001 14:18 To: midrange-l@midrange.com Subject: RE: AS/400 Disaster Recovery In my opinion, this is NOT exactly re-inventing the wheel. A generic manual can be created, but will it exactly match what you want? How often are full system saves completed (If this is in fact possible)? How often are Save Changed objects completed? How often are SAVSEC completed? Is the data library saved prior to a DAY-END cycle as part of the DAY-END cycle? Does the system use journalling? Mirroring? How is the data saved and sent off site? Is a copy of the data that is sent off site, also on site? How should all these saves be re-applied and in what order? Where is the disaster recovery site? How do you communicate with that site.? The number of questions grows in leaps and bounds, with each question suppliying numerous answers. >>> Jeff Bull <Jeff.Bull@ITM-group.co.uk> 09/17/01 08:53AM >>> ... yes ... I have many practice D/Rs under my belt, and two real ones, both successful. Each time I have used a script provided by a professional d/r organisation, who preumably know their business well. I do not have access to such a d/r plan where I am now; sure I could develop one myself, but if this is not re-inventing the wheel then nothing is - I merely trying to avoid this chore if at all possible. I am staggered there is no IBM Red Book on the subject - as I said in an earlier posting, it would almost certainly go to the top of the best seller list. If I do have to write my own 'book' on this, for sure I will publish it through Midrange-L. Jeff Bull. -----Original Message----- From: David.X.Kahn@gsk.com [mailto:David.X.Kahn@gsk.com] Sent: 17 September 2001 13:54 To: midrange-l@midrange.com Subject: Re: AS/400 Disaster Recovery Rob wrote: > Granted you have to be an experience 400 person to understand the lingo > 'load source disk' and stuff. But he is, though. >> Jeff Bull >> AS/400 Software Support Consultant >> IBM Certified AS/400 System Administrator Dave... =========================== The opinions expressed in this communication are my own and do not necessarily reflect those of my employer. _______________________________________________ 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 message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. DISCLAIMER Any opinions expressed in this email are those of the individual and not necessarily the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company, are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. If you have received this email in error please notify the IT manager by telephone on +44 (0)208 4762000 or via email to Administrator@itm-group.co.uk, including a copy of this message. Please then delete this email and destroy any copies of it. _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. _______________________________________________ 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 message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. DISCLAIMER Any opinions expressed in this email are those of the individual and not necessarily the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company, are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. If you have received this email in error please notify the IT manager by telephone on +44 (0)208 4762000 or via email to Administrator@itm-group.co.uk, including a copy of this message. Please then delete this email and destroy any copies of it. _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service. _______________________________________________ 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-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.