Electronic Data Recovery

1
Electronic Data Recovery

• L. Dean Glatt,
• Director, ITD Computer Systems Division
• Larry Lee
• ITD Contingency Planner

2
Data Recovery

• Electronic Data RecoveryWhen a disaster occurs,
  people and businesses look to the government to
  provide for their safety and welfare.  That
  dependency requires the availability of agency IT
  systems.  IT recovery priority must be based on
  sound business analysis. 
• This session will provide an example at a
  high-level design as to what it takes to ensure
  that something as simple as email is available
  during a disaster and will help emphasize why
  agency business leaders should direct IT recovery
  determination and be involved in its service
  level delivery. 

This session will explain IT DR Planning
terminology and requirements.
3
Elements of a DR PlanNon-I.T. specific

• Provide for the safety and well being of people
  on the premises at the time of a disaster
• Continue critical business operations
• Minimize the duration of a disruption to
  operations and resources (both information
  processing and other resources)
• Minimize damage and losses
• Establish management succession and emergency
  powers
• Facilitate effective coordination of recovery
  tasks
• Reduce the complexity of the recovery effort
• Identify critical lines of business and
  supporting functions

4
DR Expectations of I.T.
Steps weve taken in the past few years

• Background
• The State has a central data repository that
  supports several state agencies. While that data
  repository is acceptable, the state is concerned
  that the existence of only one data repository
  places them at risk. At a minimum, a duplicate
  repository, while within the same physical
  proximity, would move them to a more secure
  position and at the same time, is a step in the
  right direction for a more secure means planned
  in the future. An assessment is the first step
  in realizing this duplicate center.

5
Business Impact Analysis / Contingency Planning

• Business issue, not technical issue
• Business expectations drive technical solutions
• Long term outages have catastrophic impact on
  public, economy, business, government and
  environment

6
E-Mail Case Study
7
Email case study (cont)
8
Rationalization of the States Solution

• The rationale for the States Solution is based
  upon regulations, mostly Federal mandates, that
  require a point in time recovery system.
• What has been done.
• Benefits associated with implementation of the
  solution
• Risks associated with not implementing the
  solution
• Impact to each supported agency.

9
(No Transcript)
10

11
Decision Responsibility

• Should your employees be making these business
  decisions?
• How old can your data be (RPO)?
• How quickly must you be back in business (RTO)?

12
Redundancy

• Data Network
• Firewalls, Proxy, VPN
• Server Systems
• Mirrored, Clustered, HA configurations
• Staff
• Knowledge backup, Outsource arrangements

13
Summary

• When a disaster occurs, the public and businesses
  look to the government for support in providing
  for their safety and welfare.
• In public sector, every mission is critical. If a
  specific task isnt, does it ultimately support a
  critical responsibility?
• A single department cannot operate without other
  departments systems.