drr1 kick off meeting
TRANSCRIPT
1
DRR 1 KICK OFF MEETINGCristiane Ramos
2
AGENDA
▶ Disaster Recovery(DR) Overview ▶ DRR1 Dates▶ DRR1 Schedule▶ DRR SLA▶ DRR1 Dashboard▶ DRR1 Expectations▶ Post DRR1
3
OVERVIEW
▶What is a Disaster??
Disasters are unplanned events, often causing physical loss, but always causing intolerable or unacceptable impacts, loss of critical systems, or loss of services to key customers
Examples: Fire, flood, earthquake, sabotage, Terrorist act, or facility access denial, etc.
4
OVERVIEW
▶Disaster Recovery Plan (DRP)
5
OVERVIEW
▶Disaster Recovery Plan (DRP) A Disaster Recovery Plan (DRP) is a comprehensive
statement of consistent actions to be taken before, during and after a disaster. Invocation procedures, organization roles and responsibilities must also be detailed in the plan
The plan is designed to recover from the “worst case” scenario (destruction of the main or primary facility)
6
OVERVIEW
▶ Disaster Recovery Rehearsal
Prepare all system and the TOC support team members for possibilities of disaster
Ensure the Disaster Recovery Plan and main failover procedures can be executed smoothly during Pre-Games and Games period in case of a disaster declaration
7
DISASTER RECOVERY REHARSAL DATES
DRR1 / Disaster Recovery Rehearsal One: 21 – 23 March 2016
DRR2 / Disaster Recovery Rehearsal Two: 02 – 04 May 2016 (TOC to ATC and PDC to SDC)
8
DISASTER RECOVERY REHARSAL OBJETIVES
Test the readiness of the alternative site(SDC)
Verify main failover checklists (PDC to SDC)
Test related PnPs
Identify missed PnPs for the critical services
Train and educate TOC Support Staff
9
DRR1 SCHEDULE
▶ March 16th – Pre-Test: 09:00 – 18:00 ▶ March 21th- DRR1 Preparation: 09:00 – 18:00
▶ March 22th- DRR1 Exercise: 08:00 – 18:00
▶ March 23th – DRR1 Exercise: 09 – 18:00**Will be needed if something goes wrong on the day before, or if there won´t be enough time for the Failback
10
DRR SLA
▶RPO (Recovery Point Objective)From what time in the processing cycle the data is going to be
recovered (how much data we are prepared to lose or re-enter from an alternate source)
RPO is two hours
11
DRR 1 DASHBOARD
▶ Scope – Monitoring removed from
DRR1 Scope, as it will be available by late April only
▶ PnP Status
▶ SDC Readness– IDS Services ->TO BE 100% TODAY
– Tech and IT Security Sevs ->100%
– OSS Services – 100%
▶ Shifts Status– 100% complete
▶ Risks and Issues– Not having all services running
on SDC
– Have Bump in and Bump out shifts during DRR1 shifts
12
DRR1 EXPECTATIONS
▶What we already know:We won´t meet the SLA for this DRR because of SWD Procedure – restore of the backup copy is taking at least two hours.▶ The Outcome Expected: Configuration that needs to be fixed PnPs to be corrected Measurement of the time required for each service
recovery
13
POST DRR1
▶AFTER ACTION REVIEWS OBJECTIVES
Fix all gaps preventing to reach SLA
Fix and adapt PnPs for DRR2
01/05/2023
Thank you
Atos, the Atos logo, Atos Consulting, Atos Worldline, Atos Sphere, Atos Cloud and Atos WorldGridare registered trademarks of Atos SA. June 2011
© 2011 Atos. Confidential information owned by Atos, to be used by the recipient only. This document, or any part of it, may not be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos.