State Of Tennessee Mainframe Systems

1
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

3
Systems / Applications
4
DR Objectives

• Q/A existing data
• Add new applications
• Drop applications that have been sunset
• Check data for completeness and accuracy
• YYes, NNo
• Date of Most Recent Recovery Test
• Ensure Operating System (L) and Data Base (M)
  version are up-to-date.

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 MMainframe, UUnix, IIntel,
  OOther
• (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.

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.

7
System / Application Categories
8
Agency Documented Recovery Plans
9
Last Disaster Recovery Test

• Very successful mainframe test
• Increased Agency participation
• Limited Unix testing

10
2003 Applications Tested/Not Tested
11
Where We really Are
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

13
OIR DR Contacts

• Larry.K Peck
• Information Systems
• Disaster Recovery Consultant
• 532-0920
• Van Moffatt
• Director MTS and Disaster Recovery
• 741-1436