EA Disaster Recovery Orientation

1
(No Transcript)
2
Agenda
Introduction
1
Disaster Recovery Defined
2
Disaster Recovery Priority
3
Roles and Responsibilities
4
DR Plan Stages
5
6
EADR Timeline and Scope
DR Impact on SDLC
7
8
Q A
3
Introduction- What is DR?

• Provides EA with a standardized process for
  creating, testing, and auditing Disaster Recovery
  Plans
• Resides within TTS and is administered by the
  Disaster Recovery Core Team
• The Disaster Recovery Core Team is responsible
  for
• leading the DR program
• ownership of DR processes and procedures, and
• working with the multiple technology groups
• The DR program is designed to manage the risk of
  disruptions to Turners business

4
The Disaster Recovery Team Mission Statement

• We will lead a program in partnership with
  Turners IT organizations to promote
  recoverability of systems and applications by
  implementing processes and procedures for
  effective disaster recovery planning.

5
Defining a Disaster

• Significant physical damage or loss, up to the
  complete loss, disablement, or loss of access to
  a single production location (i.e. CNNC, TWD)
• A single production location may consist of one
  to many data centers

6
Defining a Disaster

• Disaster scenarios do not include
• Loss of Turner facilities not housing production
  systems
• System failures resulting from unplanned outages
  that impact a limited number of systems.

7
Recovery Priority

• What is Recovery Priority (RP)?
• The level assigned to each of Turners systems
  and applications ranking its criticality to the
  business and designating the order of recovery
• IT systems are grouped into specific recovery
  priorities

8
Recovery Priorities Defined

• Recovery Time Objective (RTO) A recovery
  parameter measured in time for the defined
  recovery requirement of a system.
• Recovery Point Objective (RPO) A systems data
  recovery parameter measured by data lost within a
  specified time period in the event the system is
  impacted by a disaster.

RP 1 RP 2 RP 3 RP 4
RTO 0 8 hour recovery 8 48 hour recovery 2 7 day recovery 7 30 day recovery
RPO no or slight data loss within 24 hours prior to disaster 24 to 36 hours prior to disaster 24 to 36 hours prior to disaster
9
Business Impact Analysis
RP Level
AIA

• How are IT systems assigned a Recovery Priority?
• An Application Impact Analysis (AIA) survey will
  be completed by the business for each system
• A systems Recovery Priority is determined by the
  score calculated from the AIA

10
Initiating DR for a Project
11
Enterprise Disaster Recovery

• The Disaster Recovery Management (DRM) Module of
  the DR Program defines the strategy for recovery
  of systems from an enterprise perspective
  including
• Emergency Operations Procedures
• Disaster scenario (Type of disaster and location)
• Playbooks (Recovery Plans by location, by
  priority)
• Roles and Responsibilities
• Communications
• DR Plans are the foundation for executing the DRM
  process at the time of an incident

12
Roles and Responsibilities

• The TTS DR Core Team members support DR Planners
• DR Planners are assigned by TTS to manage
  multiple DR Planning efforts

13
Roles and Responsibilities

• The EA DR team consists of a Team Lead and the
  component authors. The Team Lead is responsible
  for the completion of the DR Plan and DR testing.
  
• The component owners are individual contributors
  to the plan documentation.
• The EA DR team is responsible for
• documenting the recovery procedure
• performing the formal exercise of Pre-Validation
• scheduling, documenting, executing, and
  evaluating a systems Disaster Recovery Test

14
Roles and Responsibilities

• The EA Validation Team serves in an audit
  capacity, walking through the DR Plans detailed
  recovery steps to ensure that the DR Plan is
  thorough and executable
• Validation team members are the peers of those
  who wrote the DR plan

15
Disaster Recovery Plan Stages

• The four stages of the DR Planning process are
  defined as
• Kickoff and Assessment
• Development
• Validation
• Testing

16
Kickoff and Assessment

• Team Leader Meeting
• The DR Planner familiarizes the Team Leader with
  the DR Planning process, the completed DR
  Questionnaire is reviewed, and the Recovery
  Components associated SMEs are identified to
  participate in the process
• Kickoff Meeting
• The system is reviewed, responsibilities are
  assigned, a timeline is established, and time
  reporting is reviewed

17
Development

• Develop the DR Plan
• SMEs
• Team Lead
• Perform Pre-Validation

18
Validation

• Perform Validation
• A formal exercise where the DR Plan is validated
  by the authors peers, any gaps are identified,
  and updates are made to the plan where necessary.
• DR Test scope/type is defined for the official
  test
• Turnover of the validated plan
• A PDF version of the plan is generated by the DR
  Core Team to be hosted on the DR Sharepoint site.

19
Types of Testing

• Live Test (most optimal)
• Production environment is completely powered
  down or disabled
• DR Recovery component chapters are used to
  recover the system to run in the DR environment
• If live testing is not possible, the DR Plan
  authors are to determine the most robust test
  possible with acceptable risk by the business
• DR Site Test (most common)
• Executing Recovery Steps at the DR site without
  affecting the production environment
• Lab Test
• Executing Recovery Steps in a Lab environment
  other than the DR site
• Walkthrough
• The Validation step of the DR Plan writing
  process serves as a table top test for systems
  that cannot be tested in any other way

20
Testing

• Test Team Meeting
• Discuss the type of test, test plan document and
  environment
• Test Execution
• Follow-up
• Updates are made to the DR Plan and Test Plan if
  necessary
• Next Steps are identified if a test is not
  successful

21
How does DR affect me in EA?

• All participants in the development life cycle
  will likely be affected in some way
• Developers, Infrastructure/Administrators, DBAs,
  BAs, PMs will all contribute to the development
  and maintenance of a plan
• The DR process has been integrated into the EA
  SDLC so that it is defined as part of the
  development process

22
Development Methodologies

• The DR deliverables have been defined in the EA
  SDLC which is what the majority of EA projects
  follow
• Projects following Agile or other development
  methodologies that do not follow the EA SDLC are
  responsible for the same DR deliverables
• The EA DR Team will be working on defining the DR
  deliverables within the project life cycle for
  these types of projects

23
SDLC updated for DR
24
Discovery Planning

• Engage the DR team by submitting a Remedy service
  request

25
Discovery Planning

1. An AIA Survey will be sent to the sponsor of the
   project
2. The DR Core Team will calculate the results of
   the BIA and inform the Remedy ticket submitter of
   the RP level for the project
3. The Remedy ticket submitter will communicate the
   RP level to all team members including the
   extended team
4. A DR Planner will be assigned to your project to
   familiarize you with the process and facilitate
   the development of the DR Plan

26
Discovery Planning

• The projects forecasting should include
  additional cost and resource parameters for
  Disaster Recovery activities

SMEs include Application, Architects,
Management, or any other contributor to the DR
Plan.
27
Analysis Design

• Use the RP level established in the Discovery
  Planning phase to drive the architecture and
  design of the system.

• The architecture team and DBAs need to ensure
  that the architectural proposal satisfies DR
  requirements
• The RP level is one of many non-functional
  requirements that act as input to the
  Infrastructure Specification

28
Development

• Development of the DR Plan is performed by
  following the key steps included in the project
  plan

29
Development

• The DR Planner will schedule and facilitate the
  Team Leader and Kickoff meetings, and coordinate
  and define all deliverables with the Team Lead
• The Team Lead manages plan writing amongst
  component authors, facilitates issue resolution,
  and reports status
• The component authors document detailed component
  recovery procedures

30
Testing

1. Certification of the DR Plan by conducting at
   least one of the four levels of testing available
2. Turnover of the DR Plan to the DR Core Team for
   PDF and storage by submitting a Remedy ticket

31
Implementation

• There are no DR related activities in this phase.
  All DR deliverables should be completed at this
  time.
• It is possible that the DR testing of the system
  has not been completed and is scheduled to be
  completed soon after implementation.
• There is a 45 day window from when the system is
  implemented and the testing needs to be completed.

32
Production Support

• Maintain the DR Plan
• The DR Plan must be periodically reviewed and
  updated

33
DR Checklist

• Remedy ticket sent to SAO Disaster Recovery team
  to notify the DR Core team of a new System
• BIA completed
• RP Level assigned
• DR Planner assigned
• Proposed Architecture design satisfies the
  Recovery Priority
• Detailed recovery procedure documented in the DR
  Plan
• DR Plan Validated
• DR Plan Tested
• DR Plan Maintained

34
PM Templates

• All templates on the PM website
  (http//eapm/default.aspx) have been updated with
  DR tasks/descriptions
• A customer handout has been developed to assist
  in explaining Disaster Recovery to your customers

35
DR Contacts

• Plan contributors/authors, contact your Team Lead
• Team Leaders, contact your DR Planner
• DR Planners, contact the DR Core Team
• The EADR sharepoint site is available for more
  information
• http//eainfo/sites/eadr/default.aspx

36
DR Contacts

• The TTS DR Core Team
• Brian Solomon, Disaster Recovery Analyst 7 -
  1459
• Scott Eisert, Disaster Recovery Analyst 7 -
  0723
• Gail Grimes, Disaster Recovery Analyst 7 - 1472

37
QA