Advanced IT Support • Backup and Recovery • Jacksonville, FL

Disaster Recovery Plan: What It Is and Why You Need It

Backups protect your data. A recovery plan decides how fast you are working again.

Quick AnswerA disaster recovery plan is a written, tested plan for getting the business working again after something takes your systems down: ransomware, a failed server, a hurricane, or an office you cannot get into. It covers what gets restored first, how long each system can be down, where the backups are and who can restore them, how staff keep working in the meantime, and who calls whom. Having backups is not the same thing. The plan is what turns backups into an actual recovery.
Most small businesses have some kind of backup. Far fewer know how long it would actually take to get back to work if the server died tonight, or which system they would need first, or who has the password to the backup account. Those questions get answered either ahead of time, calmly, or in the middle of an outage, under pressure. A disaster recovery plan is just answering them ahead of time.

The plan does not need to be long. For most small businesses, a few clear pages that the right people can find and follow is far more useful than a binder nobody has opened.


Backups vs. a Recovery Plan

Backups answer
  • Is a copy of our data stored somewhere?
  • How often is it copied?
  • Is a copy kept off site?
A recovery plan answers
  • What do we restore first, and how long does it take?
  • Who does the restoring, and how do they get in?
  • How do we keep working while it happens?
  • Who tells clients, staff, and the insurance carrier?

A business can have excellent backups and still be down for a week because nobody knew how long a full restore would take, or the only person with the backup login was on vacation.


The Disasters That Actually Happen

For small businesses in Northeast Florida and Southeast Georgia, the realistic list is not dramatic. It is the stuff that happens every year to someone:

  • Ransomware that encrypts files and servers, and sometimes the backups connected to them
  • A server or storage device that fails without warning
  • Hurricanes and tropical storms that close the office or knock out power for days
  • Extended internet or power outages at the building
  • Someone deleting or overwriting important files by accident
  • Water damage, fire, or a break-in at the office

Two Numbers Every Plan Needs

How long can each system be down?

Some systems can be out for a day without much harm. Others stop the business within an hour. Email, your practice or line-of-business software, and shared files usually top the list. Ranking them tells you what to restore first and how fast the recovery has to be.

How much work can you afford to lose?

If backups run once a night and the server fails at 4 PM, a day's work is gone. For some businesses that is acceptable. For others, like an accounting firm in tax season, it is not. The answer decides how often backups need to run.

IT people call these the recovery time objective and recovery point objective. The names do not matter. What matters is that the business has decided on them, and that the backup setup can actually meet them.


What a Small Business Plan Should Cover

  • A list of your critical systems and data, and where each one lives
  • The order systems get restored in, and how long each takes
  • Where backups are stored, including at least one copy that ransomware cannot reach
  • Who can start a restore, and how they get access if the office is closed
  • How staff keep working: from home, on laptops, or with a paper process
  • A contact list: IT provider, internet provider, insurance carrier, key vendors
  • Who tells clients and staff what is happening, and what they say
  • When the plan was last tested, and what was learned
An untested plan is a guess

The first time you find out a backup does not restore should not be during a real outage. Test restores on a schedule, and walk through the plan with the people involved at least once a year. Every test turns up something: a missing password, a step that takes longer than expected, a system nobody remembered.


Testing Without Disrupting the Business

Testing does not mean shutting the office down. A good test restores a sample of files and at least one full system to a separate location, times how long it takes, and checks that everything works. A tabletop walkthrough, where the people in the plan talk through what they would do in a specific scenario, catches gaps in the process side without touching any systems at all.


When the Disaster Is a Cyberattack

Ransomware needs one extra step in the plan: making sure systems are clean before restoring onto them, and that the attacker is out of the network. Restoring too quickly onto compromised machines can mean doing it all twice. Your plan should name who to call first, including your IT provider and your cyber insurance carrier, since many policies have requirements about how an incident is handled.


Start Small, Then Test

If you do not have a plan today, start with three things: list your critical systems, confirm where your backups are and that someone other than one person can restore them, and test one restore. That alone puts most small businesses in a far better position. Our backup and recovery page covers how we build and test plans for clients.