DRP Brief to Exec MgmnT - II 6-18-9

Disaster Recovery Briefing : 

Disaster Recovery Briefing IT Steering Committee June 18, 2009

Agenda : 

Agenda Purpose of Briefing Disaster Recovery Strategy Outline of Plan Testing

Purpose of Briefing : 

Purpose of Briefing Secure ITSC feedback & approval HIPAA regulations & two recent audits require a Plan to be in place

Disaster Recovery Strategy : 

Disaster Recovery Strategy Strategy will change after FY10 as Redundant Data Center comes online Current strategy Remote restoration in Philadelphia using backup tapes with 24-48 hours for Tier 1 resumption of service FY11 (and beyond) strategy Mirrored data at Redundant Data Center with <4 hours for resumption of service

Outline of Plan—Planning Methodology : 

Outline of Plan—Planning Methodology

Outline of Plan—BIA/BC Results : 

Outline of Plan—BIA/BC Results Surveyed 67 managers in Jan-Mar 2009 Responses received from 49 managers & incorporated into Plan Meet with all managers 1:1 over next 6 months to finalize BIA/BC components for incorporation into version 2 of Plan Update current department business continuity procedures to reflect Meditech & migration to Redundant Data Center

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 1: Initial Response Assess the details of the failure Director of Network Systems will physically visit the site of the event to assess damage In the event that a catastrophic disaster causes excessive damage to the Data Center, the Director of Network Systems will obtain clearance from administration or Law Enforcement Official(s) for the DR/Emergency Management Team to be allowed on the premises The Director of Network Systems will inform the contact at the alternate facility of the potential need to use the designated disaster recovery space.

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 2: Assess Physical Site Physically visit the site of the event Complete and return the Assessment of Physical Damage form to the Disaster Recovery Coordinator: Contact support vendors for software/hardware/telecommunications devices that have been damaged and inform them of the disaster/event. Contact critical software vendors to inform them of the disaster/event and to notify them that their services may be required in restoring the application(s).

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 3: Functional Restoration at Alternate Site Contact hardware vendors if necessary to inform them of the equipment requiring shipment. Work with facilities management Test "reprogrammed network" Install/restore operating systems on hardware Complete a Disaster Recovery Status Report

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 4: Application Restoration at Alternate Site The Software Recovery Team will contact critical applications vendors Load critical applications on the hardware Once installed, the Applications Recovery Leads will notify other team members as appropriate for assistance in restoring data. The Application Lead responsible for completing a software recovery will complete a Disaster Recovery Status Report and provide it to the Disaster Recovery Coordinator.

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 5: Test System Components The Emergency Management Team members will test application system functionality The Director of Network Systems will notify Administration to work with department directors and to make recommendations to hire temporary clerical/data entry staff if necessary The Application Recovery Leads will notify end users and/or any temporary data entry personnel contracted by individual departments that they will soon be entering and merging data created since the disaster back into the individual applications.

Outline of Plan—DR Procedures : 

Outline of Plan—DR Procedures Step 6: Restore/Repopulate Applications Data per predetermined RTO (Tier) Priority Levels Retrieve backup media and recovery procedures from their alternate, safe location Inventory backup tapes and determine if all necessary tapes are at the backup site. Estimate the amount of data lost between the last data backup tape and the loss of data processing capabilities. Populate applications with historical data from taped back ups. Complete Disaster Recovery Status Report

Recovery Time Objective (Tier) Levels : 

Recovery Time Objective (Tier) Levels Priority (Tier 1) Applications - Recovery Time Objective (RTO): 24-48 hours Infrastructure (Core servers for Applications) Meditech C&S – LSS eMail – Internet Priority (Tier 2) Applications – Recovery Time Objective: 49-72 hours ANSOS Home Health Radiology Medical Records Priority (Tier 3) Applications – Recovery Time Objective: 73+ hours Patient Accounting/HR/Accounting Pyxis All other applications

Disaster Recovery Teams : 

Disaster Recovery Teams

Testing : 

Testing “Table Top” exercise October 2009 based on current DR strategy Gloria Fluck to facilitate exercise NetSys to perform annual restore from tapes at SunGard in Philadelphia in October 09 Revise DR/BC Plan based on Table Top and change in DR strategy Complete exercise in FY11 based on Redundant Data Center strategy

Questions? : 

Questions?