1 / 13

Disaster Recovery

Disaster Recovery. Disaster Recovery Program. Knowing what to do when systems “go down” so that disruption is minimized Having a documented plan and practice Moving beyond mainframe systems to focus on the growing number of Unix and Intel server applications. Systems / Applications.

urania
Download Presentation

Disaster Recovery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Disaster Recovery Disaster Recovery

  2. Disaster Recovery Program • Knowing what to do when systems “go down” so that disruption is minimized • Having a documented plan and practice • Moving beyond mainframe systems to focus on the growing number of Unix and Intel server applications Disaster Recovery

  3. Systems / Applications Disaster Recovery

  4. DR Objectives • Q/A existing data • Add new applications • Drop applications that have been sunset • Check data for completeness and accuracy • Y=Yes, N=No • Date of Most Recent Recovery Test • Ensure Operating System (L) and Data Base (M) version are up-to-date. Disaster Recovery

  5. DR Spreadsheet Inventory • Changed Columns • Classification (C) 1-Fatal, 2-Critical, 3-Manageable, 4-Marginal Numbers added to facilitate sorting • New Columns • (K) Platform Type: M=Mainframe, U=Unix, I=Intel, O=Other • (Q) Comment: To be used for comments • (T) Agency Contact Name • (U) Agency Contact Phone number • (V) Application Dependencies: Does this application depend on another to function. Disaster Recovery

  6. Application Impact Categories • 1-Fatal - agency will be unable to complete required legal obligations or business functions Many people would be affected, either inside or outside the agency. • Potential liability exists. • 2-Critical – agency will continue to operate partially. Calculations will produce incorrect results. Workarounds are short-term and highly invasive until the problem is resolved. • 3-Manageable - agency will continue to operate partially or some calculations will produce incorrect results. However, could be sustained for a longer period of time. • 4-Marginal - minor inconvenience, annoyance, or irritation. Business will continue to function. Disaster Recovery

  7. System / Application Categories Disaster Recovery

  8. Agency Documented Recovery Plans Disaster Recovery

  9. Last Disaster Recovery Test • Very successful mainframe test • Increased Agency participation • Limited Unix testing Disaster Recovery

  10. 2003 Applications Tested/Not Tested Disaster Recovery

  11. Where We really Are Disaster Recovery

  12. Challenges • Need to create and maintain Recovery Plans for Fatal and Critical applications • Agencies to plan with OIR “unmet needs” for non-mainframe Fatal and Critical systems • Encourage Agencies to test more mainframe systems Disaster Recovery

  13. OIR DR Contacts Larry.K Peck Information Systems Disaster Recovery Consultant 532-0920 Van Moffatt Director MTS and Disaster Recovery 741-1436 Disaster Recovery

More Related