|
Richard Shealy makes a good point: First, each installation should have a Disaster Recovery Plan and test it. It is real easy to say "We have every thing backed up." But when was the last time you actually used it either in a test or in a real business recovery situation? It amazes me how many operators are competent at performing backups, but have never had to perform a restore. "What's a save file ?" If I need a source member restored I always submit the command myself, sadly perpetuating the cycle, but I am averse to having an entire QRPGSRC restored with one member! In our case, having to move objects & libs between 15 ASPs has been a wonderful crash course in object restores & dependencies. Please, please, anyone who is responsible for training operations staff, ensure they delete & restore objects as part of the course. Issuing backup commands like a straight SAVLIB *ALLUSR is only the beginning of the process. I always had my programming students personally restore anything they deleted in error. It empowered them, I felt; caused less panic later in life! Certainly they sat with the manual for a bit, asked a couple of questions & came back in triumph with their missing object restored, with the correct authorities, feeling they had done something productive rather than daft (zapping it in the first place 2 days before an exam by taking option 4 to compile!). We back up changes nightly, all libs weekly & run a pgm to identify & save NEW libraries nightly, as these changes don't save otherwise. (Email me privately if you would like a copy of the SAVNEWLIBS CL) I know many depts. regard running a backup exposure report for the auditors as routine, but not many auditors come back & ask who is actually responsible for following up on the unsaved objects. Fiona +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.