This document is intended to provide operational procedures and serve as a reference for the Information Technology Personnel at Community Care College, Oklahoma Technical College, and Clary Sage College Disaster Recovery Community Care College Clary Sage college Oklahoma Technical College
Disaster Recovery Committee Teresa Knox Ivan Acosta John Sullivan Lynn Long Josue Panecatl Vang Chang Rebecca Banuelos Brigitte Kurr Douglas Shokes Name CEO Property Manager Facility Manager IT Consultant IT Specialist IT Specialist Marketing Director Registrar Software Developer Title
Revision History *Disaster and Recovery plan was developed since January 2004 REVISION DATE NAME DESCRIPTION Original 1.0 March 11, 2013 Vang Chang IT Specialist
Table of Contents Information Technology Statement of Intent... 5 Policy Statement... 5 Objectives... 5 Key Personnel Contact Info... 6 External Contacts... 7-8 1 Plan Overview... 9 1.1 Plan Documentation Storage... 9 1.2 Backup Strategy... 9 1.3 Risk Management... 9 1.4 Emergency Power Overview... 10 2 Emergency Response... 11 2.1 Emergency Alert... 11 Appendix A Technology Disaster Recovery Plan Templates... 12 Disaster Recovery Plan for <Loki>... 12 Disaster Recovery Plan for <Vulcan>... 13 Disaster Recovery Plan for <Zeus>... 14 Disaster Recovery Plan for <Thor2>... 15 Disaster Recovery Plan for Remote Connectivity... 16 Appendix B Suggested Forms... 17 Disaster Recovery Event Recording Form... 17 Communications Form... 17
Information Technology Statement of Intent Our mission is to ensure information system uptime, data integrity and availability, and business continuity. Policy Statement The company shall develop a comprehensive IT disaster recovery plan. A formal risk assessment shall be undertaken to determine the requirements for the disaster recovery plan. The disaster recovery plan should cover all essential and critical infrastructure elements, systems and networks, in accordance with key business activities. The disaster recovery plan should be periodically tested in a simulated environment to ensure that it can be implemented in emergency. All staff must be made aware of the disaster recovery plan and their own respective roles. The disaster recovery plan is to be kept up to date to take into account changing circumstances. Objectives The principal objective of the disaster recovery is to develop, test and document a wellstructured and easily understood plan which will help the company recover as quickly and effectively as possible from an unforeseen disaster or emergency which interrupts business operations.
Key Personnel Contact Info Name, Title Contact Option Contact Number Vang Chang Work: 918-610-0027 X2021 Alternate 918-845-0453 vchang@communitycarecollege.edu Alternate Email Josue Panecatl Work 918-610-0027 X2028 Alternate 918-409-2761 jpanecatl@communitycarecollege.edu Alternate Email Work Alternate Alternate Email Work Alternate Alternate Email Work Alternate Alternate Email Work Alternate Alternate Email
External Contacts Name, Title Contact Option Contact Number Property Manager Ivan Acosta Work 918-610-0027 X2009 918-521-4679 iacosta@communitycarecollege.edu Advance Alarms Shannon Morrison Work 918-251-0644 918-830-2850 Work 918-858-8888 Fax Barracuda Model #: BAR=YF-312360 Work 888-268-4772 408-342-5400 Cisco Joe Hewitt Work 919-349-9400 919-329-6351 Emergency Reporting EasyTel Phone company Work 918-523-8090 Cherie Wheeler-Territory Namager Fax cwheeler@easytel.com EasyTel Cory Baker-Technician Work 918-523-8211 Google Email accounts Work 877-355-5787 Customer Pin: 135173857 855-733-8319 Support Pin: 97501
Name, Title Contact Option Contact Number HP Server Support Natasha S. Matsumura Work 800-334-5144 natasha.s.matsumura@hp.com JD Young Bobbie Work 918-925-3303 JD Young Justin Work 918-855-7914 Cisco Tech Support Mario User ID 212-257-6253 Password Cisco ASA Firewall Work 800-553-2447 Work Work
1 Plan Overview 1.1 Plan Documentation Storage Copies of this Plan, CD, and hard copies will be stored in secure locations to be defined by the company. Each member of senior management will be issued a CD and hard copy of this plan. 1.2 Backup Strategy Key business processes and the agreed backup strategy for each are listed below. The strategy chosen is for a fully mirrored recovery site at location. This strategy entails the maintenance of a fully mirrored duplicate site which will enable instantaneous switching between the live site (Campuses) and the backup site. KEY BUSINESS PROCESS IT Operations Tech Support - Hardware Tech Support - Software Facilities Management Email Purchasing Disaster Recovery Finance Human Resources Web Site BACKUP STRATEGY Fully mirrored recovery site Fully mirrored recovery site Fully mirrored recovery site Fully mirrored recovery site Cloud base Google apps. Fully mirrored recovery site Fully mirrored recovery site Fully mirrored recovery site Fully mirrored recovery site Cloud base 1.3 Risk Management There are many potential disruptive threats which can occur at any time and affect the normal business process. We have considered a wide range of potential threats and the results of our deliberations are included in this section. Each potential environmental disaster or emergency situation has been examined. The focus here is on the level of business disruption which could arise from each type of disaster. Potential disasters have been assessed as follows: Potential Disaster Flood Electrical power failure Loss of communications network services Brief Description Of Potential Consequences & Remedial Actions All critical equipment is located on 1st Floor Redundant UPS array together with auto standby generator that is tested weekly & remotely monitored 24/7. Two diversely routed T1 trunks into building. WAN redundancy,
PRIMARY EMERGENCY POWER COMMUNITY CARE COLLEGE EMERGENCY POWER OVERVIEW 1. Power supplied by Public Service Company is disrupted. The disruption of power is sensed by the UPS (Uninterruptable Power System) in the Computer Room and in the Second Floor Air Handler Room. Electric power is supplied by each UPS from a bank of batteries to all circuits connected to the UPS. 2. The disruption of power is also sensed by the automatic transfer switch in the Central Plant and in the Computer Room Electrical Closet. After 15 seconds, a signal is sent to the Emergency Generator to start. Once power from the Emergency Generator is established, the transfer switch in the Computer Room and in the Central Plant engage. 3. The UPS in the Computer Room and in the Second Floor Air Handler Room sense the power originating from the Emergency Generator. The UPS are not able to differentiate whether power is supplied by PSO or the Emergency Generator as power is always routed through the UPS batteries. 4. Power will be supplied by the Emergency Generator until both transfer switches sense that PSO has restored electric service. At that time, the transfer switches disengage. Any disruption that occurs in the transfer of power is picked up by each UPS. SECONDARY EMERGENCY POWER 1. In the event of the failure of the primary emergency power systems, a portable generator can be connected to the exterior connection box (West of the building). The portable generator will only supply power to the Computer Room. 2. The power from the portable generator is fed through a breaker panel in the Computer Room Electrical Closet. There are two circuit breakers in the panel that provides power for Computer Room equipment and Computer Room lighting. The circuit breakers must be moved to the ON position to allow power to enter the Computer Room circuits. 3. There are five wire leads in the exterior connection box: orange, yellow and brown are for 480 volts; gray is for 277 volts (lighting); green is for ground.
2 Emergency Response 2.1 Emergency Alert The person discovering the incident calls a member of the Emergency Response Team in the order listed: Emergency Response Team Vang Chang Josue Panecatl Ivan Acosta John Sullivan
Appendix A Technology Disaster Recovery Plan Templates Disaster Recovery Plan for Loki Accounting System (QuickBooks), Active Directory, DNS, and DHCP SYSTEM Loki OVERVIEW PRODUCTION SERVER Applications KEY CONTACTS Hardware Vendor System Owners Database Owner Application Owners Software Vendors Offsite Storage BACKUP STRATEGY FOR SYSTEM ONE Daily Weekly Location: Community Care College Server Model: HP Proliant Operating System: Windows Server 2008 R2 Enterprise CPUs: 2.90 Gigahertz AMD Athlon II X4 635 Memory: 7672 Megabites usable installed memory Total Disk: 999.89 Gigabytes usable hard drive capacity DNS Entry: 192.168.x.x IP Address: 192.168.x.x Other: Accounting System (QuickBooks) Active Directory DNS DHCP HP corp. Community Care College Community Care College Community Care College Backup Schedule 12 am 12 am DISASTER RECOVERY PROCEDURE Scenario 1 Contact Aktec for data backup Total Loss of Data Scenario 2 Contact HP Corp. for hardware replacement. Total Loss of HW A backup for all applications and data in Loki, including the Accounting System (QuickBooks) is scheduled to run at 12am.
Disaster Recovery Plan for Vulcan Millennium, Active Directory, DNS, and DHCP SYSTEM Vulcan OVERVIEW PRODUCTION SERVER Applications KEY CONTACTS Hardware Vendor System Owners Database Owner Application Owners Software Vendors Offsite Storage BACKUP STRATEGY for SYSTEM TWO Daily Weekly Location: Oklahoma Technical College Server Model: HP Proliant Operating System: Windows Server 2003 R2 CPUs: 2.80 Gigahertz Intel Core i7 860 Memory: 8188 Megabytes usable installed memory Total Disk: 634.64 Gigabytes usable hard drive capacity DNS Entry: 192.168.x.x IP Address: 192.168.x.x Other: Active Directory Millennium (Harns) DNS DHCP HP Corp. Community Care College and Oklahoma Technical College Community Care College and Oklahoma Technical College Community Care College and Oklahoma Technical College Backup Schedule 12 am 12 am DISASTER RECOVERY PROCEDURE Scenario 1 Contact Aktec for data backup and Harms for Millennium Total Loss of Data Scenario 2 Contact HP corp. for hardware replacement Total Loss of HW
Disaster Recovery Plan for Zeus Millennium, Active Directory, DNS, and DHCP SYSTEM Zeus OVERVIEW PRODUCTION SERVER Application KEY CONTACTS Hardware Vendor System Owners Database Owner Application Owners Software Vendors Offsite Storage BACKUP STRATEGY for SYSTEM THREE Daily Weekly Location: Oklahoma Technical College Server Model: HP Proliant Operating System: Windows Server 2007 R2 CPUs: 3.0 Gigahertz (2x processors) Memory: 64 Gigabytes usable installed memory Total Disk: 634.64 Gigabytes usable hard drive capacity DNS Entry: 192.168.x.x IP Address: 192.168.x.x Other: Active Directory Millennium (Harms) DNS DHCP HP Corp. Community Care College and Clary Sage College Community Care College and Clary Sage College Community Care College and Clary Sage College Backup Schedule 12 am 12 am DISASTER RECOVERY PROCEDURE Scenario 1 Contact Aktec for data backup and Harms for Millennium Total Loss of Data Scenario 2 Contact HP corp. for hardware replacement Total Loss of HW
Disaster Recovery Plan for Thor2 Student Information Management System (Transcript), SYSTEM Zeus OVERVIEW PRODUCTION SERVER Applications Location: Oklahoma Technical College Server Model: HP Proliant Operating System: Windows Server 2007 R2 CPUs: 3.0 Gigahertz (2x processors) Memory: 64 Gigabytes usable installed memory Total Disk: 634.64 Gigabytes usable hard drive capacity DNS Entry: 192.168.x.x IP Address: 192.168.x.x Other: Student Information Management System (Transcript), KEY CONTACTS Hardware Vendor System Owners Database Owner Application Owners Software Vendors Offsite Storage BACKUP STRATEGY for SYSTEM FOUR Daily Weekly HP Corp. Community Care College and Clary Sage College Community Care College and Clary Sage College Community Care College and Clary Sage College Backup Schedule 12 am 12 am SYSTEM TWO DISASTER RECOVERY PROCEDURE Scenario 1 Contact Aktec for data backup and Harms for Millennium Total Loss of Data Scenario 2 Contact HP corp. for hardware replacement Total Loss of HW A backup for all applications and data in Thor2, including the Student Information Management System (Transcript), is scheduled to run at 12am.
Disaster Recovery Plan for Remote Connectivity SYSTEM OVERVIEW EQUIPMENT Location: Community Care College Device Type: ASA Cisco Router Model No.: ASA SSM-10 Network Interfaces: 1Gigabit interface Power Requirements: 115V System Serial #: DNS Entry: 192.168.x.x IP Address: 192.168.x.x Other: KEY CONTACTS Hardware Vendor System Owners Network Services SageNet Community Care College 1 Gigabyte interface DISASTER RECOVERY PROCEDURE Scenario 1 Contact SageNet for network support Total Loss of Network Scenario 2 Contact SageNet for hardware replacement Total Loss of HW
Appendix B Required Forms Disaster Recovery Event Recording Form All key events that occur during the disaster recovery phase must be recorded. An event log shall be maintained by the disaster recovery team leader. 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. Description of Disaster: Commencement Date: Date/Time DR Team Mobilized: Activities Undertaken by DR Team Date and Time Outcome Follow-On Action Required Disaster Recovery Team's Work Completed: <Date> Event Log Passed to Business Recovery Team: <Date> Communications Form It is very important during the disaster recovery and business recovery activities that all affected persons and organizations are kept properly informed. The information given to all parties must be accurate and timely. In particular, any estimate of the timing to return to normal working operations should be announced with care. Groups of Persons or Organizations Affected by Disruption Customers Management & Staff Suppliers Media Stakeholders Others Persons Selected To Coordinate Communications to Affected Persons / Organizations Name Position Contact Details