<COMPANY

NAME>

BUSINESS
CONTINUITY
PLAN
VERSION 1
<CREATION DATE>

CREATED BY
(COMPANY NAME OR LOGO HERE)
This page intentionally left blank
Introduction............................................................................................... 2

Business Continuity Plan Testing and Review.............................................2

Recovery Time Objective...........................................................................3

Recover Point Objective.............................................................................3

Technology Components address in this manual........................................3

Notification of problems..............................................................................3

Operational Procedures.............................................................................4

Procedures Status...............................................................................4

Error Detection for main file server........................................................6

Contact information....................................................................................7

Appendix................................................................................................... 8

Sample back up log sheet....................................................................8

Blank backup log sheet........................................................................1

BUSINESS CONTINUITY PLAN PAGE 2

Introduction

Purpose. The purpose of this document is to provide information regarding the business
continuity plan for ITL Lab. This booklet will contain a list of operational procedures to
ensure preparedness for a technology failure as well as procedures to execute in the
event of a failure.

Background. All business should have a plan of action if an important part of their
technology install base should fail. A plan that will tell them what they need to do to get
back a predetermine level of by a predetermined point in time. This manual is aid at
documenting the plan for ITL Labto obtain operational plans as well as emergency plan to
reach their RPO in the RTO.

Business Continuity Plan Testing and Review

This plan should be tested and reviewed at least twice a year with at least one of those
tested being a test of the ability to recover software and data from tape.

Testing may result in a need to update this plan. Those updates should be incorporated
into a revision of this plan. Revisions to this document should be recorded below.

Document Revision History

CREATED/MODIFIE REVIEWED BY CHANGES MADE
VERSION

DATE

D BY

1 19/11/2018 Tomy George Initial Document

BUSINESS CONTINUITY PLAN PAGE 3

Recovery Time Objective

The follow table describes recovery time objectives and their relative impact to ITL Lab

Down Time Effect include ($) Acceptance

1 week

1 business day

1 business hour

Recover Point Objective

The follow table describes recovery point objectives and their relative impact to ITL Lab

Roll Back time Effect ($)

1 week

1 business day

1 business hour

Technology Components address in this manual

As of this revision of the Business Continuity Plan ITL Lab has addressed the following components in
this manual:

1. Main File Server –

Notification of problems

This manual contains certain procedures aimed at providing protection from outages of
the technology components addressed. In the event there are problems detected while
executing any of these procedures notification of the problem should be done in the
following way.

1) Notes should be made in any logs that are being kept as a result of the process’
execution - AND –
BUSINESS CONTINUITY PLAN PAGE 4

2) Notification must be passed to the next level of the escalation path by telephone.

3) Escalation path:

a. The principle should note the problem in the log

b. <Operations Managers Name> must be notified via telephone. If the work

phone is busy, leave a voice mail and call cell phone contact as well

c. Follow any additional escalations listed in the procedure itself.

Operational Procedures

The remainder of this document is a list of procedures, their status and contact information for any
key personnel or vendors needed to achieve the RPO in the RTO window. and their status.

Procedures Status

The following table describes the procedures needed and their status.

Procedure to address Status

Daily Back up procedure for main file server Yellow

Restore procedure for software and data on the main file server Red

Error detection on the main file server or any of its subsystems Red

A reaction plan for errors detected on the main file server or any of its Red
subsystems

Description of Status:
Green = For a procedure to be considered green the follow must be true:
1) The procedure is created and documented
2) The procedure is a part of some one’s job, This would be called the principal person
3) There is a back up person that knows how to execute the procedure and will do so in the absence of the principal
4) The procedure has been tested in the last 6 months by a some one other than the principal or the back up person
Yellow = Yellow indicates:
1) The procedure is created and documented
2) The procedure is a part of someone’s job, This would be called the principal person
Red = Red indicates:
1) The procedure is identified as needed.
2) There is no documented procedure
BUSINESS CONTINUITY PLAN PAGE 5

Restore Procedure for main file server

Purpose of this procedure. It is the policy of ITL Labto perform a backup procedure for the main file
server daily. The backup tape will be taken off site and kept in a safe place.

The backup will be used to recover from any failure on the main file server. This procedure is the
steps to complete a restore of software and data to make the file server operational after an event.

Principal executer of the is procedure: <Name>

Back up executer of this procedure: <Name>

Timing of this procedure: This procedure should take about

Time of day to start:

Length of time to complete:

How often: Each business day

Steps to complete this procedure:

1) Go to the server and

2) Put the tape in the drive (how do you know it is in right)

3) Enter something in the log (what does a proper entry look like?)

4) The Restore is complete when (what message is on the screen)

5) If the Restore fails (how will you know) do this (what do you want them to do)

Questions regarding this procedure should be referred to <Operations Manager> via email. Note that
problems with the backup should be logged and escalation followed from Step 5 above.
BUSINESS CONTINUITY PLAN PAGE 6

Error Detection for main file server

Purpose of this procedure. It is the policy of ITL Labto perform a backup procedure for the main file
server daily. The backup tape will be taken off site and kept in a safe place.

The backup will be used to recover from any failure on the main file server. This procedure is the
steps to complete a restore of software and data to make the file server operational after an event.

Principal executer of the is procedure: <Name>

Back up executer of this procedure: <Name>

Timing of this procedure: This procedure should take about

Time of day to start:

Length of time to complete:

How often: Each business day

Steps to complete this procedure:

1) Go to the server and

2) Open a certain program and look for??? (what are we looking for)

3) Enter something in the log that says you looked and what you saw (what does a proper entry
look like??)

4) If there are errors what do you do? (what do you want them to do or who should they call)

Questions regarding this procedure should be referred to <Operations Manager> via email. Note that
problems with the backup should be logged and escalation followed from Step 5 above.
BUSINESS CONTINUITY PLAN PAGE 7

Contact information

Name Company Phone Responsibility of the contact

<Operations <Operations Work: <Operations Manager> – overall responsibility for

Manager> Company> this manual, the procedures in it and principle
Cell escalation point for problems related to
procedures and their execution.

Chris Broughton Chris Broughton 812-528-2596 Consultant – assisted with the creation of the
& Associates business continuity plan this manual

<Software <Software 555-555-1234 Software Vendor – responsible for the operation of

Vendor Name> Vendor Name> the software. Escalation point for failed backups
on the main file server

<Hardware <Hardware 555-555-1234 Hardware vendor– responsible for installation and

Vendor Name> Vendor Name> operation of computer hardware. Escalation point
for computer hardware related problems.

<Network Vendor <Network Vendor 555-555-1234 Network support vendor– responsible for
Name> Name> installation and operation of the network
components. Escalation point for network
component related problems.

<Telephone <Telephone 555-555-1234 Telephone support vendor – responsible for

Vendor Name> Vendor Name> installation and operation of the telephone system.
Escalation point for telephone related problems.
BUSINESS CONTINUITY PLAN PAGE 8

Appendix

Sample back up log sheet

Date Time Tape Initial Comments

Numbe s
r

10/1/06 9:00AM 1 CSB The back up was successful. Detected no errors

10/2/06 9:00AM 2 CSB Back successful – no errors

10/3/06 9:00AM 3 CSB Back up seemed successful but error that some files

Were not back up appeared on the screen.

Notified office managers by phone. She said to let her

know if it happens again

10/4/06 9:00AM 4 CSB Successful back up no errors – let the office manager

Know by phone there were no errors today

10/5/06 10:00A 1 TLB Successful back up no errors

M

 Date: The date the backup was taken

 Time: The time the back up completed
 Tape Number: The number of the tape the back up was written to
Comments: backup successful, failed, any errors detected and who was notified. If additional space
is needed use additional lines as needed.
Blank backup log sheet

Date Time Tape Initial Comments

Numbe s
r

 Date: The date the backup was taken

 Time: The time the back up completed
 Tape Number: The number of the tape the back up was written to
Comments: backup successful, failed, any errors detected and who was notified. If additional space
is needed use additional lines as needed.