EXCHANGE 2003 DISASTER RECOVERY - Home … TO GIVE OUT.doc · Web viewServer Host Name: DC1 and DC2...

WISCONSIN MUNICIPAL MUTUAL INSURANCE COMPANYBUSINESS IMPACT ANALYSIS

WMMIC maintains a small office with a local area network (LAN) that supports about 75 users. The office relies on the LAN and its components for standard automated processes, such as developing and using spreadsheets, word processing and electronic mail (e-mail). The office also maintains a customized database application that supports claim information management, reporting, and transaction processing, a key resource management process. The LAN includes the following components:

Two Domain Controllers – DC1 and DC2 (authentication/logon information) Web server – RMX - (supports customized database RMIS, reporting application) File Server – EX1 – (file server for all user documents, including all attachments for claims

in the RMIS) Exchange server – EX2 – (email server, outlook web access and mailboxes) Two networked printers, one with scanner 7 desktop computers, 3 laptop computers Citrix Server - CITRIX1 – (runs Terminal Services for remote access to Riskmaster) Firewall server ISA1 (runs Microsoft Information Security and Acceleration Server)

CRITICAL IT RESOURCES

The following resources are critical, meaning that they support critical business processes:

Authentication/network operating system server (required for users to have LAN access)

Database server (required to process the Riskmaster system) Terminal server E-mail server and application Eight desktop computers (to support eight of nine WMMIC staff) Network cabling Electric power Heating, ventilation and air conditioning (HVAC) Physical security Facility

Critical Business Process Critical Resource

1. Provide Riskmaster access to remote users Riskmaster (Web Server)2. Provide claims admin, payments, reports Laptop or Desktop Computers3. Provide Financial and Loss Information Business Objects (Web Server)4. Communicate with members, others Email (Exchange Server, OWA Server)

/tt/file_convert/5aa5c7707f8b9ab4788da078/document.doc1

5.6.

DISRUPTION IMPACTS AND ALLOWABLE OUTAGE TIMES

Critical Resource Max Allowable ImpactOutage

1. Domain Controller12 hours Users cannot authenticate/log on2. Network Cabling 12 hours LAN inoperable3. SQL Server 24 hours Users cannot access Riskmaster data4. Business Objects Svr 48 hours Delay in providing reports5. Exchange Server 48 hours Inability to communicate electronically but

users may utilize their personal email addresses6. Desktop/Laptops 72 hours Staff may use their own personal computers7. Printers 1 week Cannot print supporting document for vendors8. Scanners 1 week Paper cannot be attached electronically9. Terminal Server 1 week Occasionally used by TPA (HRH), remote users

RECOVERY PRIORITIES

Resource Recovery Priority

1. Web Server High2. Domain Controller/Authentication Server High3. Exchange Server Medium-High4. Business Objects Server Medium4. Desktop or Laptop Computers High5. Network Cabling High6. Printers/Scanners Low7. Terminal Server Low

IDENTIFICATION OF RISKS AND PREVENTATIVE CONTROLS

Preventive measures are in place that may mitigate or eliminate outage impacts.

- Deadbolt lock on server room door within locked office, keyless alarmed entry to building.

- Quick Ship agreements through vendors for hardware. - Appropriately sized uninterruptible power supply to provide short-term backup power

to system components.- Self-contained air conditioning unit to control network hardware environment.- Offsite storage of backup software and critical business data.- Frequent, scheduled backups.- Servers are all on racks that eliminate contact with the floor.

Other measures could be plastic tarps that may be unrolled over IT equipment to protect from water damage. Fire and smoke alarms and/or water sensors, heat-resistant and waterproof containers for backup media and vital non-electronic records, fire extinguisher in the server room, network management card for the UPS to automatically shut down the network in event of power failure.


Preliminary System InformationSystem Manager Point of Contact

Server Host Name: DC1 and DC2System Description: DC1 is WMMIC’s primary domain controller, DC2 is backup domain controller.

Individuals within WMMIC that depend on or support the system: Jan Clingman – Systems Coordinator, Kimberly Weihert – Workers Comp Adjuster, Nicole Baus – Claims Assistant, Jennifer Ott – WC Claims Supervisor, Kevin Murphy – Executive Director, Stephanie Drescher – Claims Assistant, Brenda Schelman – Liability Claims Adjuster, Dean Boes –Operations Manager

Individuals outside the organization that depend on or support the system: WMMIC Members – remote users of the system, HRH Insurance Services – work comp TPA for WMMIC members who are remote users of the system, Berbee engineers who obtain and set up network hardware.

Hardware: DC1 and DC2 servers are IBM x346 Xeon Dual Core 2.8GHz/800MHz, 4MB L2, 2x1GB, O/Bay U320 with 40GB Hot Swap SCSI HDD. Three-year Onsite 24x7 4-hour response repair warranty.

Software: Software – Windows Server 2003 SP2, Backup Exec 10, Internet Explorer 6

Critical Roles for Critical Resources:

Authentication/Logon Server Hardware Berbee Information NetworksAuthentication/Logon Server Software Berbee Information NetworksWeb Server Berbee, CSC, WMMIC Systems Coordinator Firewall Engineers (Berbee or others)CSC Installers

Server Host Name: RMXSystem Description: The RMX server runs Riskmaster Xr3 SP 5a, Microsoft SQL Server, Business Objects. Riskmaster Xr3 is the claims management information system being accessed by WMMIC members remotely, up to 75 total users. Business Objects is the reporting tool which utilizes the Riskmaster database. The database is SQL Server.

Individuals within WMMIC that depend on or support the system: Jan Clingman – Systems Coordinator, acts as liaison with CSC development and support and also a user of the system.Kimberly Weihert – Workers Comp Adjuster, secondary liaison with CSC development and support, also a user of the system.Nicole Baus – Claims Assistant, Jennifer Ott – WC Claims Supervisor, Kevin Murphy – Executive Director, Stephanie Drescher – Claims Assistant, Brenda Schelman – Liability Claims Adjuster, Kimmer Price – Liability Claims Adjuster, Dean Boes – Operations Manager

Individuals outside the organization that depend on or support the system: CSC RISKMASTER, development and support of Riskmaster and other applications running on this server. WMMIC Members – remote users of the system, HRH Insurance Services – work comp TPA for WMMIC members who are remote users of the system, Berbee engineers who obtain and set up network hardware.

Hardware: RMX server is an IBM x346 Xeon Dual Core 2.8GHz/800MHz, 4MB L2, 2x1GB, O/Bay U320 with 36GB Hot Swap and 73GB Hot Swap SCSI HDD. Three-year Onsite 24x7 4-hour


response repair warranty from July 2006.

Software: Software – Windows Server 2003 SP2, Apache Tomcat 5.0, CSC Media Content Manager, CSC Riskmaster Xr3, Acrosoft Server, Acrosoft, Java, Adobe Reader 7.0, Microsoft Word, Microsoft Excel, Business Objects XIr2, Microsoft SQL Server 2000, WinZip 10, Account Ability

Critical Roles for Critical Resources:

Authentication/Logon Server Hardware Berbee Information NetworksAuthentication/Logon Server Software Berbee Information NetworksWeb Server Berbee, CSC, WMMIC Systems Coordinator Firewall Engineers (Berbee or others)

CSC Installers


WISCONSIN MUNICIPAL MUTUAL INSURANCE COMPANYCONTINGENCY PLAN

1. INTRODUCTION

1.1 PURPOSE AND PLANWMMIC’s Contingency Plan establishes procedures to recover the network operations in the event of a disruption extending beyond 72 hours. There shall be a plan for each major application or general support system to meet the needs of critical IT operations. The Contingency Plan shall be reviewed annually and updated as necessary. The procedures must account for full nightly backups to be conducted and sent to the designated off-site facilities. Specific responsibilities are assigned to designated staff or positions to facilitate the recovery and/or continuity of essential IT functions. Resources necessary to ensure viability of the procedures shall be acquired and maintained. Personnel responsible for target systems shall be trained to execute contingency procedures. The plan and recovery capabilities shall be tested annually to identify weaknesses.The following objectives have been established for this plan:

Maximize the effectiveness of contingency operations through an established plan that consists of the following phases:- Notification/Activation phase to detect and assess damage and to activate the plan- Recovery phase to restore temporary IT operations and recover damage done to

the original system- Reconstitution phase to restore IT system processing capabilities to

normal operations. Identify the activities, resources, and procedures needed to carry out WMMIC’s

processing requirements during prolonged interruptions to normal operations.- Assign responsibilities to designated personnel and provide guidance for

recovering the network operations during prolonged periods of interruption to normal operations.

- Ensure coordination with other WMMIC staff who will participate in the contingency planning strategies. Ensure coordination with external points of contact and vendors who will participate in the contingency planning strategies.

1.2 APPLICABILITYWMMIC’s Contingency Plan applies to the functions, operations, and resources necessary to restore and resume their operations as it is installed at 4785 Hayes Road, Madison, Wisconsin. This Contingency Plan applies to WMMIC and all other persons associated with RiskMaster as identified under Section 2.3, Responsibilities.

1.3 SCOPE1.3.1 Planning PrinciplesVarious scenarios were considered to form a basis for the plan, and multiple assumptions were made. The applicability of the plan is predicated on two key principles.

WMMIC’s facility in Madison, Wisconsin, is inaccessible; therefore, WMMIC is unable to perform processing for its members.


A business relationship exists with Berbee Information Networks Corporation.

- Berbee will provided its IT resources to assist in recovering data and functionality during an emergency situation that prevents access to WMMIC’s original facility.

- Berbee will be used to continue recovery and processing throughout the period of disruption, until the return to normal operations.

1.3.2 AssumptionsBased on these principles, the following assumptions were used when developing the IT Contingency Plan.

- The network is inoperable at WMMIC and cannot be recovered within 48 hours.- Key personnel have been identified and trained in their emergency response and

recovery roles; they are available to activate WMMIC’s Contingency Plan.- Preventive controls (e.g., environmental controls, waterproof tarps, sprinkler systems,

fire extinguishers, and fire department assistance) are fully operational at the time of the disaster.

- Computer center equipment and components are connected to an uninterruptible power supply (UPS) that provides 20 minutes of electricity during a power failure.

- Hardware and software at WMMIC are unavailable for at least 48 hours.- Current backups of the application software and data are intact and available at Berbee’s

offsite storage facility, and offsite on magnetic tape or removable hard drive or ftp site.- The equipment, connections, and capabilities required to operate WMMIC’s network

are available at Berbee, Madison, Wisconsin. - Service agreements are maintained with CSC for Riskmaster software, Berbee

for quick ship agreements through vendors for hardware, and communications providers to support the emergency system recovery.

2. CONCEPT OF OPERATIONS

2.1 SYSTEM DESCRIPTION AND ARCHITECTURE

Provide a general description of system architecture and functionality. Indicate the operating environment, physical location, general location of users, and partnerships with external organizations/systems. Include information regarding any other technical considerations that are important for recovery purposes, such as backup procedures. Provide a diagram of the architecture, including security controls and telecommunications connections.

DOMAIN CONTROLLERS

WMMIC is an organization using a single local area network (LAN) with only one domain and two domain controllers (DC1 and DC2) which improves the availability and reliability of network services, provides fault tolerance, balances the load, and provides additional infrastructure support. Maintaining these two domain controllers makes it possible for the domain to continue to function if one domain controller fails or must be disconnected. It also improves performance by making it easier for clients to connect domain controller when logging on to the network. Separate servers host WMMIC’s email, risk management information system, firewall, terminal services and web server. All of WMMIC’s network hardware is located in a secured room with limited public access.


WMMIC’s domain controllers run the Windows Server 2003 SP2 operating system with Active Directory, which stores directory data and manages user and domain interactions, including user logon processes, authentication, and directory searches.

WMMIC uses the backup tool on the domain controller to automatically back up all of the system components and all of the distributed services upon which Active Directory is dependent. This dependent data, which includes Active Directory, is known collectively as the System State data.

FIREWALL

WMMIC’s firewall server (ISA1) runs Microsoft® Internet Security and Acceleration (ISA) Server 2003. It is an extensible platform that integrates firewall and cache features, and routes requests and responses between the Internet and client computers. ISA Server provides filtering to block access to specific sites, and uses network address translation (NAT) and other methods to enable secure access between an intranet and the Internet. The ISA server settings are backed up to removable media tape and stored off-site.

ROUTER

WMMIC currently utilizes a Cisco router.

RISK MANAGEMENT INFORMATION SYSTEM

A dedicated server (RMX) is used for maintaining the business-critical data required for the Claims Management Information System. The Operating System is Windows Server 2003 SP2. The main applications running on RMX are SQL Server, Riskmaster X and Business Objects. The databases for Riskmaster X claims management and Web Intelligence report templates are maintained on SQL Server, along with the security database containing logon information for these applications.

The RMX System State is backed up to removable media (tape). All databases are backed up automatically each night to a separate server (EX1) Tivoli System Management runs nightly on the EX1 server and transfers all of this data to Berbee’s offsite backup facility and is stored on a 30-day rotation basis. The EX1 server saves a current week of data. A daily status report is generated and emailed to WMMIC Systems Coordinator.

WMMIC WEBSITE

The WMMIC website is hosted by Berbee, and all files are on their server. Accessibility to the website would not be affected by a WMMIC disaster. Backup files for WMMIC website are stored on EX1 server and saved to removable media (tape) nightly.

EMPLOYEE PC’s

PC’s in the office are protected by Symantec Multi-Tier Antivirus 10. The antivirus client is pushed to new PC’s by the server, and updates are maintained daily by the server through Live Update.

Software running on PC’s in the office includes:

Windows XP Professional Operating System (all PC’s)Riskmaster World 7.0.7 with PDF Forms (all PC’s)Microsoft Office 2003 or 2007 with Outlook (all PC’s)Internet Explorer 6 or 7 (all PC’s)Adobe Acrobat Reader 7 (all PC’s)Adobe Acrobat Standard or Professional 7.0 (some PC’s)WS_FTP (some PC’s)Macromedia Dreamweaver (some PC’s)Yahoo Messenger (all PC’s)WinZip 10 Registered (all PC’s)Adagio Checks and Ledger (some PC’s)

All software is located in the secured room with limited public access, along with the network hardware. Copies of all business-critical software are stored off-site at:

All document files are served to each PC through a user folder maintained by a user account in Active Directory, and these folders are stored on the EX1 server. These files are backed up nightly to removable media (tape).

PRINTERS


Some PC’s have printers directly connected and share with others. All PC’s connect to two printers on the network through TCP/IP, the Ricoh 350e (IP address=192.168.1.50) and the Ricoh C3500 (IP address=192.168.1.52).

EMAIL

The email server (EX2) runs Windows Server 2008 which runs Exchange Server 2007. Much of the Exchange Server 2007 configuration information (specifically related to Internet protocols and routing) is stored in the metabase on the local computer. Symantec Mail Security for Exchange provides antivirus and spam protection on WMMIC’s network, as well as Berbee’s Antivirus Filtering on the servers before email passes through to WMMIC’s network.

BACKUPS AND MITIGATION

Hotfixes and security updates are uploaded and installed on a regular basis, at least monthly, or immediately if the update is of a critical nature.

DC1 and DC2 system state data is backed up to removable media (tape) using Backup Exec 10.0 and is copied nightly on a two-week rotation.

EX2 stores all Exchange database storage groups, and they are backed up nightly by Backup Exec 10.0 to removable media (tape). The backups are typically stored at C:\WINDOWS\system32\inetsrv\MetaBack. They are also stored at D:\Exchsrvr\mdbdata.


Following is information for all of WMMIC’s data being backed up to tape or TSM.

Backup Exec Incremental Backups Daily to Tape using HP SureStore device.


Data backed up to tape using Backup Exec are System States for DC1, DC2, RMX, EX1, EX2 files stored in a Public folder that are used by staff, and user folders (My Documents for each user).

TSM Tivoli Storage Manager BackupsThe following dsm.opt file is located on EX1 in C:\Program Files\Tivoli\TSM\baclient. This file contains the backup scripting that tells TSM what to back up.

** Berbee TSM Client Option File (dsm.opt) for Windows 2003 Servers** v1.0 08/08/2002 - Started documenting change history* v1.1 09/13/2002 - Added exclude for MOM Agent temporary files* v1.2 12/18/2002 - Changed COMPRESSION default to YES* v1.3 01/27/2002 - Excluded the \dhcp folder (not \dhcp\backup)* Changed log path to D:\Logs\TSM*

LARGECOMMBUFFERS YESTCPNODELAY YESCOMPRESSION YESCOMMMETHOD TCPIPTCPSERVERADDRESS adsm2.binc.netTCPPORT 1500PASSWORDACCESS GENERATESCHEDLOGRETENTION 7 DDOMAINC:DOMAIND:PRESCHEDULECMD BerbeePreSchedScript.vbs (stored on EX1\ C:\tsmfiles)

NODENAME WMMIC

EXCLUDE "*:\...\*" INCLUDE "*:\...\dsmsched.log" LOGINCLUDE "*:\...\dsmerror.log" LOGINCLUDE "*:\...\DSM.OPT" INCLUDE "D:\sql_backups\...\*" *All Riskmaster and Business Objects dataINCLUDE "D:\public\Accounting\...\*" *All Accounting data, financials, banking infoINCLUDE "D:\dorn\...\*" *All Riskmaster user data, Sortmaster rptsINCLUDE "D:\public\qrasp\...\*" *All NAIC, AM Best, etc. data

EXCLUDE.DIR "D:\dorn\autoupdate" EXCLUDE.DIR "D:\dorn\tools" EXCLUDE.DIR "D:\dorn\rmwin_old" EXCLUDE.DIR "D:\dorn\rmworldpgm" EXCLUDE.DIR "D:\dorn\rmworld" EXCLUDE.DIR "D:\dorn\ftp" EXCLUDE.DIR "D:\dorn\docs_trng" EXCLUDE.DIR "D:\dorn\ntsrv" EXCLUDE.DIR "D:\exchsrvr\mdbdata" Exclude.Dir "D:\public\Jan Clingman"Exclude.Dir "D:\public\Backups"


2.2 LINE OF SUCCESSION

WMMIC sets forth an order of succession to ensure that decision-making authority for the WMMIC’s Contingency Plan is uninterrupted. The Executive Director (ED) is responsible for ensuring the safety of personnel and the execution of procedures documented within this Contingency Plan. If the ED is unable to function as the overall authority or chooses to delegate this responsibility to a successor, the Systems Coordinator shall function as that authority.

2.3 RESPONSIBILITIESThe following team has been developed and trained to respond to a contingency event affecting the IT system.The Contingency Plan establishes a team assigned to participate in recovering WMMIC’s operations. The team is responsible for recovery of WMMIC’s computer environment and all applications. Members of this team include personnel who are responsible for the daily operations and maintenance. The team consists of the Systems Coordinator and the person that acts as their backup when the Systems Coordinator is unavailable.


6. PLAN APPENDICES

Vendor Contact List WMMIC Emergency Action Plan Service Level Agreements


TABLE OF CONTENTS

SECTION PAGE

Emergency ContactsA. On-site Emergency Contacts 2B. Organizational Contacts 3C. Off-site Emergency Telephone Numbers 4

1. General Description of Facility 6

2. Arrangements with Local Agencies 7

1. Types of Emergencies and Emergency Coordinator’s Actions and Responsibilities 7

a. Fire, Explosion 7b. Minor Fire Response 8c. Tornado 8d. Telephone Bomb Threat 9

4. Notification and Evacuation Procedures 9


This plan is designed to inform WMMIC employees and emergency personnel about what to do in the event of a reasonably foreseeable emergency. Examples of foreseeable emergencies include fire, tornado, etc. Elements of plan

The following elements, at a minimum, shall be included in the plan: (i) Emergency escape procedures and emergency escape route assignments; (ii) Procedures to be followed by employees who remain to operate critical plant operations before they evacuate; (iii) Procedures to account for all employees after emergency evacuation has been completed; (iv) Rescue and medical duties for those employees who are to perform them; (v) The preferred means of reporting fires and other emergencies; and (vi) Names or regular job titles of persons or departments who can be contacted for further information or explanation of duties under the plan.

SECTION 1 – General Description of Facility

Wisconsin Mutual Insurance Company performs primarily office work, at no time in their operations do they permanently store chemicals or other hazardous materials. WMMIC is located on the east-side of Madison on the second floor of a two-story office building that houses four other businesses. The building is frame construction, unsprinklered. It is situated in a small office park with similar buildings on two sides. Hayes Rd is a frontage Road off of East Washington. The WMMIC building is on the corner of exit 135A on I-90 and Hwy 151 (East Washington). WMMIC is on the SE side of Hayes Rd. next to the Motel 6 (formerly the Fairfield Inn). The exposure presented by the hotel and expressway exit ramp is considered minimal due to the greater distances involved. The proximity to the Interstate highway and to U.S. Route 151, major truck thoroughfares, presents an exposure to WMMIC’s office being inaccessible. E.g. An overturned truck spills hazardous chemicals, resulting in declaration of an emergency and evacuation of the surrounding area for safety and to clean up and assess damage.

Within one mile of the facility there is a large shopping mall, many restaurants and hotels, apartment complexes, a variety of specialty shopping centers and a day care. There are no large bodies of water within one mile of the office.Attached are figures detailing the location of the building along with office escape routes and evacuation meeting points.


SECTION 2 – Arrangements with Local Agencies

In the event of a fire or other emergency the police and fire department will receive primary control of the situation, once on-site. In addition to their other responsibilities they will also be responsible for:

1. The possible need for evacuating other buildings in the area (particularly downwind from the site) in the event of a major fire or explosion.

2. Crowd control and isolation of the area.

3. Keeping vehicular traffic lanes open for emergency vehicles.

SECTION 3 – Types of Emergencies and Primary Coordinator's Actions and Responsibilities

Categories of emergencies and appropriate facility personnel response procedures are outlined below. A minor fire is defined as a fire capable of being readily extinguished with a portable fire extinguisher, is non-explosive, and non-threatening to human health. If the assessment indicates that the facility has had a release, fire or explosion which could threaten human health or the environment outside the facility, the Emergency Coordinator must follow the procedure below:

Types of Emergencies

Fire or Explosion

1. Activate the Employee Emergency Plan, and immediately activate internal facility communications to notify all personnel of an imminent hazard and existing emergency. Evacuate building if the situation calls for this.

2. Notify management personnel.

3. Contact fire department and police department if necessary. Give them the name and location of the incident and briefly describe the nature of the problem.

4. Fight the fire only if it can be done safely and easily extinguished. Otherwise evacuate to an upwind position.

5. Assess possible hazards to human health or the environment that may result from the incident.

Minor Fire Response


1. Notify the Executive Director or Emergency Coordinator.

2. Remain upwind from the fire.

3. If properly trained , initiate fire fighting procedures to control or extinguish the minor fire using portable fire extinguishers. There is an all-purpose ABC fire extinguisher located outside the office door in the hallway on the second floor.

4. Fight the fire only if it can be done safely and easily extinguished. Otherwise evacuate to an upwind position.

5. If the fire progresses beyond the incipient fire stage (beyond the capabilities of portable extinguishers), activate the fire alarm. Evacuate the facility.

Tornado

Tornado Watch: A watch indicates that weather conditions are favorable for the development of tornadoes.1. Emergency Coordinator shall monitor weather news by radio.2. Weather forecast will be relayed to employees.

Tornado Warning: Warnings are issued when a tornado is probable or one has been sighted.1. Discontinue outside work.2. Relocate indoors.3. Stand by to shutdown operations.

Tornado Approaching: An approaching tornado is heard or sighted from the facility.1. Shutdown facility operations.2. Seek shelter in a secure room or under heavy objects such as metal tables that

are bolted down.3. Stay away from windows.

Following a Tornado:1. Administer medical aid to injured personnel.2. Initiate needed cleanup which calls for activation of Response Plan.

Telephone Bomb Threat:

1. Treat the threat as real. Do not assume it is a joke.

2. Record the message word-for-word, if possible.


3. Obtain the time and location of threatened detonation, if possible.

4. Note any background noise or speech peculiarities.

5. After the call, notify proper personnel.

6. Evacuate the facility as directed.

SECTION 4 – Notification and Evacuation Procedures

Evacuation

Evacuation is a difficult decision, but a decision that must be made without delay. For planning procedures, assume a full scale evacuation (downwind for 3/4 of a mile) will be necessary. Evacuation takes time, therefore, if the fire cannot be extinguished within a very short period of time and the fire is intensifying, then full evacuation may be necessary. Close proximity evacuation should begin within the first 30 minutes as a precautionary measure.

Employee Alarm System Employees must communicate alarms by voice or by telephone. Outside Emergency Response teams must be notified by telephone.

In the event of a fire or other emergency that starts in our office, the Emergency Coordinator is responsible for altering the other tenants in the building. The company and telephone numbers are located in the Emergency Contact List. Emergencies which may affect other persons in different areas of the building (e.g.: a fire) requires alerting everyone in the facility as quickly as possible.

Evacuation Routes and Safe Areas

Employees must know what their assignments are in emergency situations. Each person must know the proper escape route to use and help direct traffic, if necessary. They should advise other employees to move away from exit doorways and congregate in pre-assigned areas, away from the building or other areas where they may hamper emergency operations.

Normal escape routes are through doorways closest to the area occupied, unless the emergency is at or adjacent to that site. Then, the next nearest exit is to be used. Diagrams at the end of this plan describe the exit routes for WMMIC.

In the event that an evacuation is required all WMMIC employees and guests will evacuate the building and congregate in the Motel 6 parking lot, adjacent to the office building. At that time all employees should be accounted for.


Evacuation, if needed beyond this point, depends on the wind direction. The best place to congregate will be upwind of the emergency area, depending on the direction of the wind will determine the final location. A good rule of thumb is to move into the wind or at least at right angles to that direction; stay out of areas downwind from the site. If it is necessary to evacuate further, do so as a group to remain accounted for.

Accounting for Employees - Post Evacuation

All employees at the facility at the time of an emergency evacuation must be accounted for after evacuation. Employees will be accounted for in the safe area after the evacuation. If anyone is missing, the person accounting for employees should make responders aware that there may be an employee in the building with a brief description of the missing individual.

If it is necessary for any individual to remain in the evacuated building, every effort should be made to pass that information on to the person responsible for accounting for evacuated employees. Visitors to WMMIC’s office are the responsibility of the person (employee) being visited as far as evacuation and accounting for them at the meeting site.

Rescue and Medical Duties

Any emergency first aid required is to be rendered by the person or persons most qualified to do so. Medical treatment or first aid measures should only be handled by trained responders. It is the responsibility of fellow employees to alert responders to the need for first aid or other medical treatment.

Post-Fire Clean-up

The fire scene should be secured to keep unauthorized personnel out until clean-up and decontamination is completed. All clean-up procedures will be conducted by the Munz Corporation, the property management company that owns the building. At the same time WMMIC will begin to retrieve files and recover information from the system backup.


EXCHANGE 2003 DISASTER RECOVERY - Home … TO GIVE OUT.doc · Web viewServer Host Name: DC1 and DC2...

Documents

Transcript of EXCHANGE 2003 DISASTER RECOVERY - Home … TO GIVE OUT.doc · Web viewServer Host Name: DC1 and DC2...