disaster recovery drill report sample

ホーム
ames wheelbarrow 4 wheel
mario sports games, ranked
disaster recovery drill report sample

2022.07.31
why does my kitten chew on everything

disaster recovery drill report sample

The report will also contain an assessment of the impact to normal business operations. disaster recovery template software templates profile chapter applications profiles drill fire forms form evaluation emergency pdffiller eval printable Our mission is to ensure information system uptime, data integrity and availability, and business continuity. The disaster recovery plan should cover all essential and critical infrastructure elements, systems and networks, in accordance with key business activities. fillable pdffiller The report should contain information on the emergency, who was notified and when, action taken by members of the DRT together with outcomes arising from those actions. Suppliers of critical goods and services will continue to support recovery of business operations as the company returns to normal operating mode. Description of Emergency:Date Occurred:Date Work of Disaster Recovery Team Completed: Name of Team MemberContact DetailsContacted On (Time / Date)By WhomResponseStart Date RequiredRelevant Comments (e.g., Specific Instructions Issued) ___________ Mobilizing the Business Recovery Team Form Following an emergency requiring activation of the disaster recovery team, the business recovery team should be notified of the situation and placed on standby.

Tornado5Electrical storms5Act of terrorism5Act of sabotage5Electrical power failure34Redundant UPS array together with auto standby generator that is tested weekly & remotely monitored 24/7. 2.3.7 Alternate Recovery Facilities / Hot Site If necessary, the hot site at SunGard will be activated and notification will be given via recorded messages or through communications with managers. Each potential environmental disaster or emergency situation has been examined. ___________ Preparing the Business Recovery Report Form On completion of business recovery activities the BRT leader should prepare a report on the activities undertaken and completed. ?BM( 3.3 Media Team ____________________________________________ ____________________________________________ ____________________________________________ 3.4 Rules for Dealing with Media Only the media team is permitted direct contact with the media; anyone else contacted should refer callers or in-person media representatives to the media team. earthquake fillable The report should contain information on the disruptive event, who was notified and when, action taken by members of the BRT together with outcomes arising from those actions. ; Decide which elements of the DR Plan should be activated; Establish and manage disaster recovery team to maintain vital services and return to normal operation; Ensure employees are notified and allocate responsibilities and activities as required. It is also very important that only authorized personnel deal with media queries. A separate form should be used for each recovered business process. The disaster recovery plan should be periodically tested in a simulated environment to ensure that it can be implemented in emergency situations and that the management and staff understand how it is to be executed. An event log shall be maintained by the disaster recovery team leader.

The report should be distributed to senior management, as appropriate. Policy Statement Corporate management has approved the following policy statement: The company shall develop a comprehensive IT disaster recovery plan.

1.3 Backup Strategy Key business processes and the agreed backup strategy for each are listed below. I confirm that above business process is now acceptable for normal working conditions. 1.2 Plan Documentation Storage Copies of this Plan, CD, and hard copies will be stored in secure locations to be defined by the company. Whenever changes are made to the plan they are to be fully tested and appropriate amendments should be made to the training materials. WAN redundancy, voice network resilience Probability: 1=Very High, 5=Very Low Impact: 1=Total destruction, 5=Minor annoyance 2 Emergency Response 2.1 Alert, escalation and plan invocation 2.1.1 Plan Triggering Events Key trigger issues at headquarters that would lead to activation of the DRP are: Total loss of all communications Total loss of power Flooding of the premises Loss of the building 2.1.2 Assembly Points Where the premises need to be evacuated, the DRP invocation plan identifies two evacuation assembly points: Primary Far end of main parking lot; Alternate Parking lot of company across the street 2.1.3 Activation of Emergency Response Team When an incident occurs the Emergency Response Team (ERT) must be activated. 3.2 Media Strategies Avoiding adverse publicity Take advantage of opportunities for useful publicity Have answers to the following basic questions: What happened? Name: ___________________________________________________________________ Title: ____________________________________________________________________ Signature: ________________________________________________________________ Date: __________________________ All Rights Reserved, 2009, TechTarget PAGE \* MERGEFORMAT 34 Person Identifying Incident E F m n v w tm`m`m`mtSSHh CJ OJ QJ \h 5OJ QJ \^J h hi CJ OJ QJ h hi h hi OJ QJ h hi 5OJ QJ hy 5OJ QJ \^J h 5CJ OJ QJ ^J h h # h 6CJ OJ QJ ^J h # h # 6CJ, OJ QJ h # CJ, OJ QJ h CJ, OJ QJ h CJ0 OJ QJ \hy CJ0 OJ QJ \ h)d 5CJ h 5CJ Recovery Tasks (Order of Priority)Person(s) ResponsibleCompletion DateMilestones IdentifiedOther Relevant InformationEstimatedActual1.2.3.4.5.6.7. It is assumed that business unit management will be fully involved throughout the recovery, but in order for the recovery process to be fully effective, overall responsibility during the recovery period should probably be with a business recovery process team. The notification will request DRT members to assemble at the site of the problem and will involve sufficient information to have this request effectively communicated. If insurance-related assistance is required following an emergency out of normal business hours, please contact: ____________________________________________ Policy NameCoverage TypeCoverage PeriodAmount Of CoveragePerson Responsible For CoverageNext Renewal Date 5 Financial and Legal Issues 5.1 Financial Assessment The emergency response team shall prepare an initial assessment of the impact of the incident on the financial affairs of the company.

The following event log should be completed by the disaster recovery team leader to record all key events during disaster recovery, until such time as responsibility is handed over to the business recovery team. Included in messages will be data on the nature of the disaster, assembly sites, and updates on work resumption. 2.3.2 DR Procedures for Management Members of the management team will keep a hard copy of the names and contact numbers of each employee in their departments. 2.3.4 Backup Staff If a manager or staff member designated to contact other staff members is unavailable or incapacitated, the designated backup staff member will perform notification duties. > T V M N O P Q R S bjbj[[ 9 9 ; [ J Z Z Z n n n 8 2" d n Q 0 8 8 8 8 TU B [ b] $ ! Z J^ M U @ J^ J^ 8 8 j_ j_ j_ J^ t 8 Z 8 j_ J^ j_ j_ 0 f 4 8 fLQ ^ R $ ! 0 Q @ *_ @ H 4 Z 4 J^ J^ j_ J^ J^ J^ J^ J^ j_ J^ J^ J^ Q J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ J^ : IT Disaster Recovery Plan Template By Paul Kirvan, CISA, CISSP, FBCI, CBCP Revision History revisiondatenamedescriptionOriginal 1.0 Table of Contents TOC \o "1-4" \h \z HYPERLINK \l "_Toc241554706"Information Technology Statement of Intent PAGEREF _Toc241554706 \h 5 HYPERLINK \l "_Toc241554707"Policy Statement PAGEREF _Toc241554707 \h 5 HYPERLINK \l "_Toc241554708"Objectives PAGEREF _Toc241554708 \h 5 HYPERLINK \l "_Toc241554709"Key Personnel Contact Info PAGEREF _Toc241554709 \h 6 HYPERLINK \l "_Toc241554710"Notification Calling Tree PAGEREF _Toc241554710 \h 7 HYPERLINK \l "_Toc241554711"External Contacts PAGEREF _Toc241554711 \h 8 HYPERLINK \l "_Toc241554712"External Contacts Calling Tree PAGEREF _Toc241554712 \h 10 HYPERLINK \l "_Toc241554713"1 Plan Overview PAGEREF _Toc241554713 \h 11 HYPERLINK \l "_Toc241554714"1.1 Plan Updating PAGEREF _Toc241554714 \h 11 HYPERLINK \l "_Toc241554715"1.2 Plan Documentation Storage PAGEREF _Toc241554715 \h 11 HYPERLINK \l "_Toc241554716"1.3 Backup Strategy PAGEREF _Toc241554716 \h 11 HYPERLINK \l "_Toc241554717"1.4 Risk Management PAGEREF _Toc241554717 \h 11 HYPERLINK \l "_Toc241554718"2 Emergency Response PAGEREF _Toc241554718 \h 12 HYPERLINK \l "_Toc241554719"2.1 Alert, escalation and plan invocation PAGEREF _Toc241554719 \h 12 HYPERLINK \l "_Toc241554720"2.1.1 Plan Triggering Events PAGEREF _Toc241554720 \h 12 HYPERLINK \l "_Toc241554721"2.1.2 Assembly Points PAGEREF _Toc241554721 \h 12 HYPERLINK \l "_Toc241554722"2.1.3 Activation of Emergency Response Team PAGEREF _Toc241554722 \h 12 HYPERLINK \l "_Toc241554723"2.2 Disaster Recovery Team PAGEREF _Toc241554723 \h 13 HYPERLINK \l "_Toc241554724"2.3 Emergency Alert, Escalation and DRP Activation PAGEREF _Toc241554724 \h 13 HYPERLINK \l "_Toc241554725"2.3.1 Emergency Alert PAGEREF _Toc241554725 \h 13 HYPERLINK \l "_Toc241554726"2.3.2 DR Procedures for Management PAGEREF _Toc241554726 \h 14 HYPERLINK \l "_Toc241554727"2.3.3 Contact with Employees PAGEREF _Toc241554727 \h 14 HYPERLINK \l "_Toc241554728"2.3.4 Backup Staff PAGEREF _Toc241554728 \h 14 HYPERLINK \l "_Toc241554729"2.3.5 Recorded Messages / Updates PAGEREF _Toc241554729 \h 14 HYPERLINK \l "_Toc241554730"2.3.7 Alternate Recovery Facilities / Hot Site PAGEREF _Toc241554730 \h 14 HYPERLINK \l "_Toc241554731"2.3.8 Personnel and Family Notification PAGEREF _Toc241554731 \h 14 HYPERLINK \l "_Toc241554732"3 Media PAGEREF _Toc241554732 \h 15 HYPERLINK \l "_Toc241554733"3.1 Media Contact PAGEREF _Toc241554733 \h 15 HYPERLINK \l "_Toc241554734"3.2 Media Strategies PAGEREF _Toc241554734 \h 15 HYPERLINK \l "_Toc241554735"3.3 Media Team PAGEREF _Toc241554735 \h 15 HYPERLINK \l "_Toc241554736"3.4 Rules for Dealing with Media PAGEREF _Toc241554736 \h 15 HYPERLINK \l "_Toc241554737"4 Insurance PAGEREF _Toc241554737 \h 15 HYPERLINK \l "_Toc241554738"5 Financial and Legal Issues PAGEREF _Toc241554738 \h 16 HYPERLINK \l "_Toc241554739"5.1 Financial Assessment PAGEREF _Toc241554739 \h 16 HYPERLINK \l "_Toc241554740"5.2 Financial Requirements PAGEREF _Toc241554740 \h 16 HYPERLINK \l "_Toc241554741"5.3 Legal Actions PAGEREF _Toc241554741 \h 16 HYPERLINK \l "_Toc241554742"6 DRP Exercising PAGEREF _Toc241554742 \h 16 HYPERLINK \l "_Toc241554743"Appendix A Technology Disaster Recovery Plan Templates PAGEREF _Toc241554743 \h 17 HYPERLINK \l "_Toc241554744"Disaster Recovery Plan for PAGEREF _Toc241554744 \h 17 HYPERLINK \l "_Toc241554745"Disaster Recovery Plan for PAGEREF _Toc241554745 \h 19 HYPERLINK \l "_Toc241554746"Disaster Recovery Plan for Local Area Network (LAN) PAGEREF _Toc241554746 \h 21 HYPERLINK \l "_Toc241554747"Disaster Recovery Plan for Wide Area Network (WAN) PAGEREF _Toc241554747 \h 23 HYPERLINK \l "_Toc241554748"Disaster Recovery Plan for Remote Connectivity PAGEREF _Toc241554748 \h 25 HYPERLINK \l "_Toc241554749"Disaster Recovery Plan for Voice Communications PAGEREF _Toc241554749 \h 27 HYPERLINK \l "_Toc241554750"Appendix B Suggested Forms PAGEREF _Toc241554750 \h 29 HYPERLINK \l "_Toc241554751"Damage Assessment Form PAGEREF _Toc241554751 \h 29 HYPERLINK \l "_Toc241554752"Management of DR Activities Form PAGEREF _Toc241554752 \h 29 HYPERLINK \l "_Toc241554753"Disaster Recovery Event Recording Form PAGEREF _Toc241554753 \h 29 HYPERLINK \l "_Toc241554754"Disaster Recovery Activity Report Form PAGEREF _Toc241554754 \h 30 HYPERLINK \l "_Toc241554755"Mobilizing the Disaster Recovery Team Form PAGEREF _Toc241554755 \h 31 HYPERLINK \l "_Toc241554756"Mobilizing the Business Recovery Team Form PAGEREF _Toc241554756 \h 31 HYPERLINK \l "_Toc241554757"Monitoring Business Recovery Task Progress Form PAGEREF _Toc241554757 \h 32 HYPERLINK \l "_Toc241554758"Preparing the Business Recovery Report Form PAGEREF _Toc241554758 \h 32 HYPERLINK \l "_Toc241554759"Communications Form PAGEREF _Toc241554759 \h 33 HYPERLINK \l "_Toc241554760"Returning Recovered Business Operations to Business Unit Leadership PAGEREF _Toc241554760 \h 33 HYPERLINK \l "_Toc241554761"Business Process/Function Recovery Completion Form PAGEREF _Toc241554761 \h 33 Information Technology Statement of Intent This document delineates our policies and procedures for technology disaster recovery, as well as our process-level plans for recovering critical technology platforms and the telecommunications infrastructure. We have considered a wide range of potential threats and the results of our deliberations are included in this section.

The team's responsibilities include: Establish facilities for an emergency level of service within 2.0 business hours; Restore key services within 4.0 business hours of the incident; Recover to business as usual within 8.0 to 24.0 hours after the incident; Coordinate activities with disaster recovery team, first responders, etc. The assessment should include: Loss of financial documents Loss of revenue Theft of check books, credit cards, etc. Business Recovery Team Leader Name: ________________________________________ Signature: ________________________________________________________________ Date: __________________________ (Any relevant comments by the BRT leader in connection with the return of this business process should be made here.) hb```f Y ,`q`#LxRMPT+[^cuhq``? $En}p'.y- Plan exercising ensures that emergency teams are familiar with their assignments and, more importantly, are confident in their capabilities. : Technical Specifications: Network Interfaces: Power Requirements; System Serial #: DNS Entry: IP Address: Other:HOT SITE EQUIPMENTProvide detailsSPECIAL APPLICATIONSASSOCIATED DEVICES KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide detailsNetwork ServicesProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Switch Provide details Scenario 2 Total Loss of Network Provide details ADDENDUM CONTACTS Support Systems Support system Critical network assets Critical interfacesCritical files to restoreCritical network services to restoreOther services Appendix B Suggested Forms Damage Assessment Form Key Business Process AffectedDescription Of ProblemExtent Of Damage _____________ Management of DR Activities Form During the disaster recovery process all activities will be determined using a standard structure; Where practical, this plan will need to be updated on a regular basis throughout the disaster recovery period; All actions that occur during this phase will need to be recorded. In the event of an actual emergency situation, modifications to this document may be made to ensure physical safety of our people, our systems, and our data. Additional objectives include the following: The need to ensure that all employees fully understand their duties in implementing such a plan The need to ensure that operational policies are adhered to within all planned activities The need to ensure that proposed contingency arrangements are cost-effective The need to consider implications on other company sites Disaster recovery capabilities as applicable to key customers, vendors and others Key Personnel Contact Info Name, TitleContact OptionContact NumberWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate EmailWorkAlternateMobileHomeEmail AddressAlternate Email Notification Calling Tree External Contacts Name, TitleContact OptionContact NumberLandlord / Property Manager Account Number NoneWorkMobileHomeEmail AddressPower Company Account Number WorkMobileHomeEmail AddressTelecom Carrier 1 Account Number WorkMobileFaxHomeEmail AddressTelecom Carrier 2Account Number WorkMobileHomeEmail AddressHardware Supplier 1Account Number WorkMobileEmergency ReportingEmail AddressServer Supplier 1 Account Number.Work MobileFaxEmail Address Workstation Supplier 1 Account Number WorkMobileHomeEmail AddressOffice Supplies 1Account Number C3095783WorkMobileHomeEmail AddressInsurance Name Account Number WorkMobileHomeEmail AddressSite Security Account Number WorkMobileHomeEmail AddressOff-Site Storage 1Account NumberWorkMobileHomeEmail AddressOff-Site Storage 2 Account Number User IDPasswordHomeEmail AddressHVAC Account Number WorkMobileHomeEmail AddressPower Generator Account NumberWorkMobileHomeEmail AddressOther Account NumberWorkMobileHomeEmail Address External Contacts Calling Tree 1 Plan Overview 1.1 Plan Updating It is necessary for the DRP updating process to be properly structured and controlled. Employees who cannot reach staff on their call list are advised to call the staff members emergency contact to relay information on the disaster. Availability of company credit cards to pay for supplies and services required post-disaster 5.3 Legal Actions The company legal department and ERT will jointly review the aftermath of the incident and decide whether there may be legal actions resulting from the event; in particular, the possibility of claims by or against the company for regulatory violations, etc. DW8@GG+foao=^7;1 =+e&R *0:k"tidh` h``h`````b6$ Appendix A Technology Disaster Recovery Plan Templates Disaster Recovery Plan for SYSTEM OVERVIEW PRODUCTION SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY FOR SYSTEM ONEDailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM ONE DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for SYSTEM OVERVIEW PRODUCTION SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for Local Area Network (LAN) SYSTEM OVERVIEW SERVERLocation: Server Model: Operating System: CPUs: Memory: Total Disk: System Handle: System Serial #: DNS Entry: IP Address: Other:HOT SITE SERVERProvide detailsAPPLICATIONS (Use bold for Hot Site)ASSOCIATED SERVERS KEY CONTACTSHardware VendorProvide detailsSystem OwnersProvide detailsDatabase OwnerProvide detailsApplication OwnersProvide detailsSoftware VendorsProvide detailsOffsite StorageProvide details BACKUP STRATEGY for SYSTEM TWODailyProvide detailsMonthlyProvide detailsQuarterlyProvide details SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Total Loss of Data Provide details Scenario 2 Total Loss of HW Provide details ADDENDUM CONTACTS File Systems File System as of Minimal file systems to be created and restored from backup: Filesystem kbytes Used Avail %used Mounted on Other critical files to modifyNecessary directories to createCritical files to restoreSecondary files to restoreOther files to restore Disaster Recovery Plan for Wide Area Network (WAN) SYSTEM OVERVIEW EQUIPMENTLocation: Device Type: Model No. 4 Insurance As part of the companys disaster recovery and business continuity strategies a number of insurance policies have been put in place. Potential disasters have been assessed as follows: Potential DisasterProbability RatingImpact RatingBrief Description Of Potential Consequences & Remedial ActionsFlood34All critical equipment is located on 1st FloorFire34FM200 suppression system installed in main computer centers. Hmf_:lrk4b jV}-3K]y$RVT0}4VnZru,)8]mvT&'g1C6{) e0vYfxChUtqu@kE%8h=0|0k]]!n )". ____________ Business Process/Function Recovery Completion Form The following transition form should be completed and signed by the business recovery team leader and the responsible business unit leader, for each process recovered. This process should be formalized in order to ensure that all parties understand the change in overall responsibility, and the transition to business-as-usual. All staff must be made aware of the disaster recovery plan and their own respective roles. ! " [Content_Types].xml ( k0^1F>tZX{sV.mO3:Nx`NX7h=3VH,2#J@. The report should be given to business recovery team leader, with a copy to senior management, as appropriate. This will only happen if everyone with a role to play in the plan has rehearsed the role one or more times. KEY BUSINESS PROCESSBACKUP STRATEGYIT Operations Fully mirrored recovery siteTech Support - Hardware Fully mirrored recovery siteTech Support - Software Fully mirrored recovery siteFacilities ManagementFully mirrored recovery siteEmail Fully mirrored recovery sitePurchasing Fully mirrored recovery siteDisaster Recovery Fully mirrored recovery siteFinance Fully mirrored recovery siteContracts Admin Fully mirrored recovery siteWarehouse & Inventory Fully mirrored recovery siteProduct Sales Fully mirrored recovery siteMaintenance Sales Fully mirrored recovery siteHuman Resources Off-site data storage facility Testing Fully Mirrored Recovery site -Fully mirrored recovery siteWorkshop Fully Mirrored Recovery site -Fully mirrored recovery siteCall CenterFully mirrored recovery siteWeb Site Fully mirrored recovery site 1.4 Risk Management There are many potential disruptive threats which can occur at any time and affect the normal business process.