Please see instruction below.
jimpop1998
W12_DisasterRecoveryTemplate.docx
DISASTER RECOVERY PLAN
USE IN CASE OF DATA LOSS
|
Application Description |
||||||
|
Recovery Priority: |
|
|||||
|
Application Name: |
|
|||||
|
Application Description: |
|
|||||
|
Software Modules/Current Version: |
|
|||||
|
Vendor Name: |
|
|||||
|
User Location & Departments: |
|
|||||
|
Technical Support Information |
||||||
|
Vendor Support phone #’s & Web Site |
|
|||||
|
Vendor Account and/or Technical Contact Name & Number: |
|
|||||
|
Server(s) name: Server type: Server OS: Server Location: IP Address: |
|
|||||
|
Vendor access method: |
|
|||||
|
Modem Numbers: |
|
|||||
|
System Notes |
||||||
|
Interface Engine: |
|
|||||
|
Interfaces – Inbound: |
|
|||||
|
Interfaces – Outbound: |
|
|||||
|
Other Comments: |
|
|||||
Maintenance and Recovery Procedures |
||||||
|
Maintenance |
|
|||||
|
Backup Method/Schedule |
|
|||||
Support Personnel |
||||||
|
Name |
Site |
System |
Office |
Pager |
Home |
Cell |
|
Systems Administrator: |
|
|
|
|
|
|
|
Other Administrator: (PHNS or Customer) |
|
|
|
|
|
|
|
Last Updated: |
|
Recovery Procedures
This section describes the recovery strategies identified for equipment and services. Include notation for the following: Criticality Priority ; Other System Dependencies; SLA System (Y/N); Estimated Time to Restoration.
Assumptions
These recovery procedures rely on the following critical assumptions. If any of these assumptions are not true at the time of the disaster then the user facility must remain in downtime procedure mode until all such assumptions are true.
System Architecture
Software & Hardware:
Back-Up Schedules:
Insert information concerning backup strategy: Such as backed up by PHNS Operations & Systems staff according to the following schedule. All tapes are stored in a secure vault off site, etc.
Procedures
Disaster Recovery Procedures Page 1 of 2
