Will
Your Business Survive?
A
disruption in the technology infrastructure
can cause a serious threat to the
stability of any business. Click
here to review Disaster Recovery
Planning & Prevention - Part
3.
An important aspect of
disaster recovery is the availability
of original operating system and application
CDs, key codes, and other items necessary
to bring a file server or other critical
systems back into operation. Often
when systems are down, these items
are discovered missing. This translates
into increased downtime and replacement
costs.
One recommendation is to purchase two
three-ring binders, CD inserts, and
organizer tabs. Duplicate and insert
the master CDs for the operating systems,
applications, and backup software into
the binders. Also document key codes
needed for installation as well as
notes of any other items required to
restore the system, and store those
items in the binder. Keep one binder
on-site and the other off-site.
When a server or critical system must
be rebuilt due to fire, viruses, corruption,
or other means, a backup of current
data should exist both on-site and
off-site. If required, new equipment
can be ordered. But, if the operating
system and applications master CDs
were lost in the disaster, the programs
and data may not be easily restored.
So, you call the software manufacturers
for new copies to be shipped overnight.
Unfortunately, you may discover that
your systems were running older versions
of software that are no longer available
for purchase. In addition, since the
data was created using older versions
of applications and operating system
software, a conversion may need to
be performed to enable proper operation.
This will most likely consume time,
money, and create training issues that
are not appropriate or affordable.
Following are some suggestions on
what the binders should contain:
- Copies of the file server operating
system, backup software and
any major applications.
- Key codes or registration numbers
needed to reinstall the
software.
- Documentation of contacts
including emergency numbers
of staff
and vendors.
- Documentation of where
the backup tapes are
and how to
retrieve them.
- Special logins and
passwords needed for
proper system
operation. The master
login should not be
documented for security
reasons.
Have
that login information
put into the company
safe and somewhere
secure off-site.
- Any special instructions
needed to install
the operating system
or backup
software.
- Documentation of
the servers,
including hard drive layout.
- Documentation
of the
Internet
connection,
including
login,
passwords,
support
numbers,
and special
information
needed
including
firewalls
and routers.
- Documentation
of
the disaster
recovery
procedures
for
specialty applications
such
as
Microsoft’s
SQL
or Exchange
server.
Programs
like
these
have
very
special
needs
for
proper recovery.
Investigate
those
procedures
and
document
the
results in the
binder.
- Disaster
recovery
plans.
Include
what has
to
be done
and who
does it.
Plan it
out ahead
of time
and insert
those
instructions
in the
binder.
- Documentation
for maintenance
contracts,
phone numbers,
and expiration
dates.
The last four newsletters offer recommendations
on basic disaster recovery planning
and prevention. If interested in learning
more or obtaining assistance, contact
Micro Visions at 616-776-0400.
