disaster recovery plan template () - Safe Computing

advertisement
UNIVERSITY OF MICHIGAN
DISASTER RECOVERY PLAN
RECOVERY TEAM
RECOVERY TEAM LEADER:
ALTERNATE TEAM LEADER:
PLAN ACTIVATION
The following personnel are authorized to activate this plan:
Name
Title
Contact Information
1
2
3
Review this document annually.
Last reviewed on:
Next review due by:
mm/dd/yyyy
03/07/16
mm/dd/yyyy
Disaster Recovery Plan
Recovery Team: _______________________
TABLE OF CONTENTS
INTRODUCTION .................................................................................................. 4
Preface ..................................................................................................................................................... 4
Assumptions........................................................................................................................................... 4
RECOVERY TEAM CONTACT INFORMATION .................................................. 5
Recovery Team Contact Procedures/Team Preparation ............................................................. 5
Recovery Team Contact List .............................................................................................................. 6
Production Data Centers and Recovery Sites................................................................................ 7
Recovery Team Leader Responsibilities ......................................................................................... 8
General ..................................................................................................................................................... 8
Developing the Disaster Recovery Plan .......................................................................................... 8
Response................................................................................................................................................. 9
Resumption and Recovery.................................................................................................................. 9
Assumption/Scope .............................................................................................................................. 9
Critical Functions ................................................................................................................................ 9
Dependencies ..................................................................................................................................... 9
Restoration: .......................................................................................................................................... 10
Response Tasks Table: ..................................................................................................................... 11
Assumptions/Scope Table ................................................................................................................ 12
Resumption/Recovery Critical Function Table ............................................................................ 13
Restoration Tasks Table: .................................................................................................................. 14
RECOVERY TEAM RESPONSIBILITIES........................................................... 15
General ................................................................................................................................................... 15
Critical Function Task List(s) ........................................................................................................... 15
Critical Function Task List ................................................................................................................ 16
Vendor Notification ............................................................................................................................. 17
Stakeholder Notification .................................................................................................................... 18
Off Site Stored Materials ................................................................................................................... 19
Salvage: Critical Resource Retrieval .............................................................................................. 20
03/07/16
Page 2 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Data Center Salvage List ................................................................................................................... 21
Spare Parts Inventory List................................................................................................................. 22
APPENDIX: TELEPHONE SCRIPT ................................................................... 23
APPENDIX: TERMS ........................................................................................... 24
APPENDIX: EMERGENCY OPERATIONS CENTER INFORMATION .............. 26
APPENDIX: UM STANDARD PRACTICE GUIDE POLICIES ............................ 28
APPENDIX: CONFERENCE ROOMS ................................................................ 29
REVISION / DISTRIBUTION / ACKNOWLEDGEMENT OF REVIEW: .............. 30
Revision History .................................................................................................................................. 30
Document Distribution: ..................................................................................................................... 30
Acknowledgement of Review:.......................................................................................................... 30
03/07/16
Page 3 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Introduction
Preface
The objective of a Disaster Recovery Plan (DRP) is to establish a written set of procedures to recover a
business IT infrastructure in the event of a disaster. The purpose of this document is twofold:
 The document provides guidelines and forms to establish and document a Disaster Recovery Plan
 The completed document will serve as a functional Disaster Recovery Plan.
Advance planning allows the Disaster Recovery Team to gather critical information, analyze requirements,
assign roles and responsibilities, and develop streamlined processes to expedite the recovery process.
Additionally, pre-planning can ensure reduced recovery time, the resumption of the “right” functionality, and
reduced recovery costs without the complex demands of an immediate disaster situation.
Assumptions
In order to facilitate the implementation of this Disaster Recovery Plan (DRP), certain assumptions have been
made to:
1. Keep the DRP manageable at the Disaster Recovery Team level
2. Limit the scope of the initial DRP
3. Build a solid foundation for further enhancements to the DRP
General Assumptions
1. Individual Disaster Recovery Plans will be developed based on the architecture currently in place.
2. A single production data center has been disabled by a disaster; one remaining production data center
is undamaged and available to support the Disaster Recovery effort.
3. The Executive Crisis Management Team Leader will activate the Disaster Recovery Plan as soon as
possible after a major disaster has disabled a production data center.
4. The recovery site data centers, equipment and information are intact and accessible.
5. At least 60% of qualified personnel are available to execute the Disaster Recovery Plan.
6. Organizations external to ITS, such as the central offices, vendors, government agencies, and others,
will be reasonably cooperative during the recovery period, e.g., parking restrictions will not be enforced.
03/07/16
Page 4 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Recovery Team Contact Information
Recovery Team Contact Procedures/Team Preparation
Recovery Team Contact Procedures Checklist
1. Disaster Recovery Team Leader receives Plan
Activation notification
2. Disaster Recovery Team Leader updates Telephone
Script
3. Disaster Recovery Team Leader notifies Alternate
Recovery Team Leader
4. Disaster Recovery Team Leaders notify assigned
Recovery Team Members
5. Instruct each Recovery Team member where to
report.
6. Record the results of each telephone call on the
Recovery Team Contact List in the Contact Status
box.
7. Disaster Recovery Team Leader and Recovery Team
Members should bring:
8. Do not talk to the Media
9. In some instances, recovery tasks mat be initiated
remotely by a Disaster Recovery Team member
before he/she reports to the Recovery Site
Fill in Description, Location, and phone number
based on the designated Disaster Recovery
Operations Center
Refer to Recovery Team Contact List and
Telephone Script
Refer to Recovery Team Contact List and
Telephone Script
Meeting location, time, additional contact
information
Note date/time of contact or last attempt made;
Note if a call back is required
1.
2.
3.
4.
ITS Disaster Recovery Plan
Laptop computer and charger
Cell phone and charger
ID Badge(s), parking pass
Discuss any tasks that may be initiated remotely
with the Disaster Recovery Team Leader; obtain
approval; record all steps and results for
subsequent on-site briefings
10.
Additional Tasks (optional)
1. If directed, meet the Executive Crisis Management
Team at the Emergency Operations Center
2. Document Information provided at ECMT briefing
3. Contact vendors and/or stakeholders, if appropriate
4. Report status of critical functions and potential
concerns to the Executive Crisis Management Team
during the briefing
5. Brief Recovery Team on the situation
6. Begin Disaster Recovery Team operations
7.
8.
9.
10.
03/07/16
Location, Time, Phone Number
Page 5 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Recovery Team Contact List
Disaster Recovery Team Name (replace with team name)
Team
Name
Title
Cont uniqname Work Phone Cell Phone Home Phone Contact Status
by:
Team Leaders
1.
ECMT
2.
T/L
Team Members
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
03/07/16
Page 6 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Production Data Centers and Recovery Sites
Primary Production Data Center (insert name) - DISABLED
Designated Recovery Site Data Center (insert name) – Recovery Site
Primary Disaster Recovery Operations Center
Facility Name:
Street Address:
City/State/Zip:
Primary Contact:
Alternate Contact:
Floor:
Phone No:
24 Hour No:
FAX No:
Other No.:
Security Considerations:
Parking & Transportation Considerations:
Alternate Disaster Recovery Operations Center
Facility Name:
Street Address:
City/State/Zip:
Primary Contact:
Alternate Contact:
Floor:
Phone No:
24 Hour No:
FAX No:
Other No.:
Security Considerations:
Parking & Transportation Considerations:
03/07/16
Page 7 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Recovery Team Leader Responsibilities
General
The primary responsibility of the Disaster Recovery Team Leader is to provide direction for his/her team during
the execution of the Disaster Recovery Plan.
At the initiation of the Disaster Recovery Plan, the Disaster Recovery Team Leader’s primary responsibility is
to contact and assemble his/her Disaster Recovery Team according to the procedures outlined in the
Recovery Team Contact Procedures
1. Contact the Disaster Recovery Team
2. Meet Disaster recovery Team at Disaster Recovery Data Center or designated meeting location.
3. Identify/assign Disaster Recovery Team members responsible for responding to the initial disaster
declaration (based on availability).
4. Critical Function Assessment: Assign sub-teams or individuals to Critical Function resumption.
During the execution of the Disaster Recovery Plan, the Disaster Recovery Team Leader:
1. Participates in meetings with the Executive Crisis Management Team.
2. Directs the disaster recovery efforts of the Disaster Recovery Team.
3. Oversees communication activities of the Disaster Recovery Team.
4. Coordinates with the Executive Crisis Management Team and other Disaster Recovery Teams in
administrative and recovery issues.
Developing the Disaster Recovery Plan
1. Document the Disaster Recovery Team Contact List
2. Assign an Alternate Recovery Team Leader to act as Disaster Recovery Team Leader if or when the
Recovery Team Leader is not available
3. Identify the functional team members responsible for responding to the initial disaster declaration and
for planning, testing, implementing and maintaining the Disaster Recovery Plan for each critical
system.
4. Consider staffing levels over prolonged periods; recovery efforts may exceed the “normal” work day.
5. Determine recovery goals, objectives and timeframes to be addressed in the Disaster Recovery Plan;
identify critical functions and/or systems, Recovery Time Objectives, Recovery Point Objectives,
dependencies, and expect cost of recovery.
6. Identify and prioritize the Critical Functions that must be restored in order to resume business
processes.
7. Determine and document the basic assumptions and scope of the Disaster Recovery Plan.
8. Identify any internal and external dependencies for the successful execution of the Disaster Recovery
Plan
9. Develop a list of vendors and contractors whose services will be required for recovery.
10. Develop a list of stakeholders that will require notification.
11. Test and maintain the Disaster Recovery Plan for the Disaster Recovery Team.
03/07/16
Page 8 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Response
The Response phase is comprised of two key components: Staff notification and damage assessment. Once
the staff has been notified of the disaster recovery scenario, it is important to assess the extent of the damage
to the data center. As part of the damage assessment in the response phase, list the steps and/or processes
required to:
1. Assess the extent of the damage including equipment damage and services affected
2. Identify salvageable equipment, if possible
3. Identify the processes and systems that may still be functioning
4. Formulate a basic resumption/recovery strategy
5. Begin the initial resumption steps to address critical functions
Resumption and Recovery
Assumption/Scope
Basic assumptions regarding the extent of a data center disaster, the availability of resources and personnel,
and the acceptance criteria for resumption of basic services will determine the overall scope of the Disaster
Recovery Plan. Assumptions should identify services or systems that will be restored in an emergency as well
as the resources required to restore those services. Clearly document any capabilities that will not be
immediately addressed by the Disaster Recovery Plan.
1. Determine the minimum acceptable level of operations that is required for this function or
process.
2. Determine the Recovery Time Objective (RTO) for each supported function or process. Provide a
realistic estimate of the time it will take to restore the service to the minimum acceptable level of
operation utilizing existing recovery options.
3. Recovery Point Objective (RPO). Estimate the work effort, in hours, of data that will need to be reentered following resumption of the service.
Critical Functions
The determination and restoration of critical functions may depend on the data center site that has been
disabled by a disaster. In some instances, all critical functions may reside at a single site; in other instances,
only a portion of a system’s critical functions may reside at the disabled site.
Identify Critical Functions for each production data center in the table below.
Critical functions may be categorized as:
 Resumption – Time-sensitive, critical operations – Address these critical Functions first
 Recovery - all other operations, ancillary Functionality
Dependencies
Identify the dependencies associated with the resumption of each Critical Function.
1. Identify dependencies between critical functions and support functions.
2. Document internal and external dependencies required to achieve the recovery objectives, including:
 Hardware and software infrastructure
 LAN, WAN and Telecommunications
 Vendor and 3rd party products or services
 Products and services produced internally
03/07/16
Page 9 of 30
Disaster Recovery Plan
Recovery Team: _______________________
 Personnel and facilities
3. Include dependencies on other departments internal to the organization as well as those that are
external.
Restoration:
After the resumption and recovery phases have been completed and all systems and processes have been
determined to be stable, management may begin to consider data center restoration.
Restoration is the process of repairing and restoring the damaged data center to its original capabilities. In the
case of total destruction, restoration requires the establishment of an entirely new site which supports
business operations in totality.
03/07/16
Page 10 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Response Tasks Table:
Disaster Recovery Team Name (replace with team name)
Response Tasks:
Task Required Steps
Comments
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
03/07/16
Page 11 of 30
Assigned To: Cmpl
Disaster Recovery Plan
Recovery Team: _______________________
Assumptions/Scope Table
Disaster Recovery Team Name (replace with team name)
Production Data Center:
Assumptions:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
03/07/16
Recovery Site:
Impact/Comments:
Page 12 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Resumption/Recovery Critical Function Table
List Critical Functions in priority order
Disaster Recovery Team Name (replace with team name)
Production Data Center:
Priority Critical Function:
Dependencies:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
03/07/16
Page 13 of 30
Res / Rec
RTO
Disaster Recovery Plan
Recovery Team: _______________________
Restoration Tasks Table:
Disaster Recovery Team Name (replace with team name)
Restoration Tasks:
Task Task
Comments
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
03/07/16
Page 14 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Recovery Team Responsibilities
General
When the Executive Crisis Management Team Leader notifies the Disaster Recovery Team Leader that the
Disaster Recovery Plan (DRP) has been activated, the primary responsibility of the Disaster Recovery Team is
to activate their Disaster Recovery Plan in order to support the university’s recovery effort.
After the disabled data center has been identified and the Disaster Recovery Team has reported to the
Disaster Recovery Operations site, The Disaster Recovery Team leader, with the assistance of key team
personnel, will assess and prioritize the recovery process for site-specific critical functions.
The Disaster Recovery Team Leader will assign the recovery of critical functions to team members.
The Disaster recovery Team Leader may also assign team members to:
1. Notify critical vendors (refer to table)
2. Notify critical stakeholders/customers (refer to table)
3. Initiate the retrieval of off-site resources.
Critical Function Task List(s)
Create a Critical Function Task List for each Critical Function listed above. The Task List required steps and
dependencies may vary depending on the designated Recovery Site. When these variations are significant, a
separate, Recovery Site specific Critical Function Task List should be created for each Critical
Function/Recovery Site combination.
1. Copy and insert Task Lists for additional Critical Functions
2. A Task List may depend on:
 Production Data Center and
 Recovery Site
3. Create individual Task Lists for all Production Data Center/Recovery Site combinations
03/07/16
Page 15 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Critical Function Task List
Disaster Recovery Team Name (replace with team name)
Critical Function:
Production Data Center:
Task Required Steps
Recovery Site:
Dependencies/Expected Results
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
03/07/16
Page 16 of 30
Assigned To:
Cmpl
Disaster Recovery Plan
Recovery Team: _______________________
Vendor Notification
Identify and itemize vendors that are critical to the organization’s mission, core business processes and/or functions.
Enter all contact information including any 24 hour support hot-line and email addresses.
Enter contract numbers or support identification numbers that may be required for service from a vendor.
List all UM personnel that are authorized to request service from a vendor.
Notes: Use the Notes section to record any contact with the Vendor during the disaster recovery process.
Disaster Recovery Team Name (replace with team name)
Vendor Name:
Address 1:
Address 2:
City/State/Zip:
Primary Phone:
After-Hours Phone:
Escalation/Hot-Line Phone:
Business Fax:
Contact Name/Phone/Ext.
Contact email:
Notes:
Product/Service:
Contract Nbr./Support ID:
UM Authorized Contacts: (name, uniqname, phone)
1.
2.
3.
4.
5.
*copy/insert table for additional vendors
03/07/16
Page 17 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Stakeholder Notification
Stakeholders may be internal ITS groups or departments as well as external entities such as banks, retirement companies, health service
providers, etc. who share data with the University.
Identify upstream ITS stakeholders and dependencies.
Identify key ITS stakeholders who will require notification when the Disaster Recovery Plan is activated.
Identify downstream ITS stakeholders when recovery efforts are complete.
Notes: Use the Notes section to record any contact with the Stakeholder during the disaster recovery process..
Disaster Recovery Team Name (replace with team name)
Stakeholder Department:
Name:
Work Phone:
Cell Phone:
Other Phone:
email:
ITS Service/Application:
Service Dependencies:
1.
2.
3.
4..
5..
Notes:
*copy/insert table for additional stakeholders
03/07/16
Page 18 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Off Site Stored Materials
Copies of critical documents, system backups, critical supplies, etc. may be available from a number of
sources:
 Commercial storage facilities used by the university.
 Other university facilities may have similar resources or copies of critical documents.
 Clients or contractors may have copies of critical documents.
Key considerations in the retrieval of any off-site materials should include:
 Time to access
 Proximity to data centers,
 Importance of off-site stored material
Recovery Box
Create a “Recovery Box” for your business unit. This Recovery Box could contain items that your business
unit would need if your building were not accessible. Some items that could be contained in this box include:
 Copies of software keys or system disks
 Copies of procedure manuals.
This box must be stored at an off-site location. The box and an inventory listing of its contents are both critical
records and should be documented as such.
1.
2.
3.
4.
Storage location refers to the name of the off-site storage facility.
Contact name refers to the person who coordinates retrieval of recovery boxes.
Box Identifier refers to the identifying code on the outside of the box.
Contents/Comments identify the items stored in the box and special concerns such as update /
maintenance or shelf life.
The creation and maintenance of a Recovery Box is optional. If a Recovery Box is not part of your Disaster
Recovery Plan, make a note on the form below.
Disaster Recovery Team Name (replace with team name)
Recovery Box
Recovery Team:
Storage Location:
Contact Name:
Box Identifier:
Contents
03/07/16
Comments
Page 19 of 30
Disaster Recovery Plan
Recovery Team: _______________________
Salvage: Critical Resource Retrieval
A disaster may not completely destroy the contents of a data center. Depending on the circumstances, it may
be possible to retrieve and re-use certain equipment. Be sure to contact your technical support area and/or
facilities staff for assistance prior to any salvage effort.
Following a disaster, local authorities and the facilities staff may determine that the disaster site is safe to
enter. Site access may be permitted for a short time. This could be for as little as 15 minutes or one half-hour.
Use the table below to create a list of critical items that would be useful in the recovery effort.
Assume that the items are salvageable; if not, note the condition.
List the items in order of importance.
(a full salvage operation may be conducted a a later time)
Include: computer DVDs, computers, selected paper files and work in process.
Do not include: unimportant files and information that is duplicated elsewhere.
03/07/16
Page 20 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Data Center Salvage List
Disaster Recovery Team Name (replace with team name)
Production Data Center:
Floor/Locn. Details:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
03/07/16
System/Component/Model/Config.
Comments
Page 21 of 30
Condition
Vendor
ITS Disaster Recovery Plan
Recovery Team: _______________________
Spare Parts Inventory List
Departments may maintain an inventory of critical spare parts or devices to be used in the event of an emergency or disaster.
Use this table to track and maintain spare parts inventory.
If the inventory is stored in a location with limited or controlled access, record the location contact information in the Stakeholder
table.
Disaster Recovery Team Name (replace with team name)
UM Part Number
03/07/16
Mfg. Part Number
Description
Location
Page 22 of 30
Stockroom
Bin/Shelf
Qty
ITS Disaster Recovery Plan
Recovery Team: _______________________
Appendix: Telephone Script
If contact is made, say "MAY I SPEAK WITH (Recovery Team member)?” ;then provide
the following information:
1. Brief description of the situation.
________________________________________
2. Location of the Disaster Recovery Operations Center:
________________________________________
3. Phone number at the Disaster Recovery Operations Center: _____________
4. Action required, as noted by the Recovery Team Leader
5. Inform the Recovery Team member to make no public statement regarding the situation.
6. Inform Recovery Team member that no calls are to be made to other employees.
(This will avoid premature notification to families of employees working at the time of the
disaster.)
If the telephone is answered by an answering machine/service:
1. Leave message requesting person call you at (telephone number).
2. Record the call and pertinent details on the Recovery Team Contact List status box
3. Try one of the alternate number
If the Recovery Team member is not available, say "WHERE MAY I REACH (Recovery
Team member)?"
1. If the Recovery Team member is at any location other than work, obtain a phone
number, make a call and provide the above information to the Recovery Team member.
2. If the Recovery Team member is at work, indicate that you will reach the individual at
work.
(DO NOT DISCUSS THE DISASTER SITUATION WITH THE PERSON ANSWERING
THE PHONE.)
If there is no answer at any contact number:
1. Record the time attempted contacts were made on the Recovery Team Contact List
2. Periodically call again, until contact is made.
If contact information is invalid (e.g., wrong number, person moved):
1. If Recovery Team member has moved, try to obtain a new telephone number and
contact the Recovery Team member
3. Make a note in the Contact Status Box - Incorrect Contact Information.
03/07/16
Page 23 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Appendix: Terms
Disaster Recovery (DR):
Disaster Recovery involves a set of policies and procedures to enable the recovery or
continuation of vital technology infrastructure and systems following a natural or human-induced
disaster. Disaster recovery focuses on the IT or technology systems supporting critical business
functions.
Disaster Recovery Plan (DRP)
A Disaster Recovery Plan (DRP) is a documented process or set of procedures to recover and
protect a business IT infrastructure in the event of a disaster.[1] Such plan, ordinarily
documented in written form, specifies procedures an organization is to follow in the event of a
disaster.
Disaster Recovery Team Leader
The Disaster Recovery Team Leader is typically a functional manager responsible for creating
the Disaster Recovery Plan and providing leadership to the Disaster Recovery Team during
plan execution.
Disaster Recovery Team
The Disaster Recovery Team is generally the functional team responsible for day to day
support of the critical functions identified in the Disaster recovery Plan.
AVPLT (UM ITS)
Associate Vice President Leadership Team
Executive Crisis Management Team
The ITS Executive Management Team comprised of the CIO, the AVPLT, and key members of
management required to oversee the entire disaster recovery effort.
Recovery Time Objective (RTO)
The Recovery Time Objective (RTO) is the targeted duration of time and a service level within
which a business process must be restored after a disaster (or disruption) in order to avoid
unacceptable consequences associated with a break in business continuity.
Recovery Point Objective (RPO)
A Recovery Point Objective (RPO) is the maximum tolerable period in which data might be lost
from an IT service due to a major incident. .
03/07/16
Page 24 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Four phases of Disaster Recovery
1. Response
Respond to a disaster during and immediately after it has occurred
2. Resumption
Resume time-sensitive operations quickly after a disaster has occurred
Critical Functionality
3. Recovery
Recover all other operations that may have been delayed
Ancillary Functionality
4. Restoration
Restore the damage/disable site or find another production location
03/07/16
Page 25 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Appendix: Emergency Operations Center Information
Management should identify at least three(3) Emergency Operations Centers including one (1)
off-campus site
Emergency Operations Center (EOC - NORTH)
Facility Name:
Street Address:
City/State/Zip:
Primary Phone:
Secondary Phone:
FAX No.
Conference (Bridge)Phone:
Conference (Bridge)Phone:
EOC email:
EOC Web Site
EOC (ECMT) Team Lead:
ECMT Alternate Lead:
Disaster Recovery Coordinator:
Facilities Coordinator/Phone:
Security Considerations:
Parking/Transportation:
Emergency Operations Center (EOC - SOUTH)
Facility Name:
Street Address:
City/State/Zip:
Primary Phone:
Secondary Phone:
FAX No.
Conference (Bridge)Phone:
Conference (Bridge)Phone:
EOC email:
EOC Web Site
EOC (ECMT) Team Lead:
ECMT Alternate Lead:
Disaster Recovery Coordinator:
Facilities Coordinator/Phone:
Security Considerations:
Parking/Transportation:
03/07/16
Page 26 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Emergency Operations Center (EOC – OFF CAMPUS)
Facility Name:
Street Address:
City/State/Zip:
Primary Phone:
Secondary Phone:
FAX No.
Conference (Bridge)Phone:
Conference (Bridge)Phone:
EOC email:
EOC Web Site
EOC (ECMT) Team Lead:
ECMT Alternate Lead:
Disaster Recovery Coordinator:
Facilities Coordinator/Phone:
Security Considerations:
Parking/Transportation:
03/07/16
Page 27 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Appendix: UM Standard Practice Guide Policies
Responsibility for Maintaining Information Technology Backup and Recovery
Procedures
http://spg.umich.edu/policy/601.07-1
Emergency Closure and Emergency Operations Reduction
http://spg.umich.edu/policy/201.27
03/07/16
Page 28 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Appendix: Conference Rooms
1. Identify and record Conference Room information for building that may be available during disaster recovery
2. Use one sheet per building
1.
Bldg./Flr
Room
Calendar Room Name
Phone
Seats
Map
Equipment
ASB –
1st Floor
1010
ITS ASB 1010
734-763-4986
33–36
https://backstage.its.umich.edu/conferencerooms/
ASB-1010.pdf
Wireless Access, Speakerphone,
52" Monitor, Cable TV
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
03/07/16
Page 29 of 30
ITS Disaster Recovery Plan
Recovery Team: _______________________
Revision / Distribution / Acknowledgement of Review:
Revision History
Revision
Date
Author Name
Description Of Changes
1.0 (Original)
09/12/2014
rebaron
Draft Template
Document Distribution:
Copy Issued To
Position
1.
2.
3.
4.
5.
6.
7.
8.
Storage location
Storage location
Hardcopy / Flash
drive / Other
Date
(mm/dd/yyyy)
Acknowledgement of Review:
Name
03/07/16
Role
Signature
Page 30 of 30
Download