office for information resources 03/04/2004disaster recovery1
TRANSCRIPT
03/04/2004 Disaster Recovery 1
Office for Information Resources
Disaster Recovery
03/04/2004 Disaster Recovery 2
Office for Information Resources
Disaster Recovery Program
Knowing what to do when systems “go down” so that disruption is minimizedHaving a documented plan and practice
Moving beyond mainframe systems to focus on the growing number of Unix and Intel server applications
03/04/2004 Disaster Recovery 3
Office for Information Resources
Systems / Applications
797 Systems / Applications
Mainframe, 123
Other, 31
Unix, 72
Intel, 504Vendor, 67
03/04/2004 Disaster Recovery 4
Office for Information Resources
DR Objectives Q/A existing data
Add new applicationsDrop applications that have been sunsetCheck data for completeness and accuracy
Y=Yes, N=NoDate of Most Recent Recovery Test
Ensure Operating System (L) and Data Base (M) version are up-to-date.
03/04/2004 Disaster Recovery 5
Office for Information Resources
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.
03/04/2004 Disaster Recovery 6
Office for Information Resources
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.
03/04/2004 Disaster Recovery 7
Office for Information Resources
System / Application Categories
797 Systems / Applications
Critical, 253Manageable, 275
Marginal, 115
Other , 20 Fatal, 134
03/04/2004 Disaster Recovery 8
Office for Information Resources
Agency Documented Recovery Plans
797 Systems / Applications
No Written Plans, 287
Vendor, 67
N/A, 31
Written Plans, 412
03/04/2004 Disaster Recovery 9
Office for Information Resources
Last Disaster Recovery Test
Very successful mainframe test
Increased Agency participation
Limited Unix testing
03/04/2004 Disaster Recovery 10
Office for Information Resources
2003 Applications Tested/Not Tested
40
94
34
219
0
40
80
120
160
200
240
"Fatal" Tested / Not Tested "Critical" Tested / Not Tested
03/04/2004 Disaster Recovery 11
Office for Information Resources
Where We really Are
03/04/2004 Disaster Recovery 12
Office for Information Resources
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
03/04/2004 Disaster Recovery 13
Office for Information Resources
OIR DR Contacts
Larry.K Peck Information Systems Disaster Recovery Consultant532-0920
Van Moffatt Director MTS and Disaster Recovery741-1436