The server doesn't come back up Tuesday morning. Somebody calls the IT number. Somebody else says the backups are fine. By afternoon most of the office is working off laptops and a phone hotspot. Annoying, but survivable.
Then Wednesday happens.
The backup did its job. The files are there. What isn't there is the thing that actually pays the bills. The invoice run. The quote for the job starting Monday. The dispatch board. The login for the supply house. Everyone is at work. Nobody is producing anything.
That is the part most owners have not priced out.
The outage you picture is not the one that happens
When a business owner hears "disaster recovery," they picture a fire, a flood, or a ransom note on a screen.
In a survey of more than 3,000 IT professionals published in early 2025, natural disasters caused 12% of on-premises outages. Ransomware caused 18%.
The single biggest cause was server hardware failure, at more than 20%. Internet provider outages accounted for 19%. Plain human error, somebody deleting the wrong thing, another 18%. Only 10% of the organizations surveyed said they had no outages at all in the previous year.
Read that list again. Almost none of it is dramatic. A failed drive. A cut fiber line. A folder that isn't where it was yesterday. That is what a bad year actually looks like.
Worth noting: these were mostly midsized companies, the kind with an actual IT department. If they are missing their recovery targets, a five person shop with no IT department is not in a better position.
You have probably already quoted a recovery time
Ask an owner how long they would be down. Most answer without pausing. A few hours. Maybe a day.
In the same survey, 60% of respondents believed they could recover from downtime in under a day. Only 35% actually did. More than 20% were down for two to three days.
Nobody was lying. They had simply never timed it. A recovery time you have never measured is not a plan. It is an assumption, and it is the one you will repeat to a customer on the worst morning of your year.
Two days is a business problem, not a technical one
A backup gets your data back. That is necessary, and it is narrow.
It does not tell you who invoices the customers on Wednesday. It does not tell you where the blank work orders are, or whether the person who orders parts can do it from a phone. It does not decide who may approve an emergency purchase while you are standing in a parking lot waiting on a truck.
The industry calls that gap business continuity. The plain version is: what does the business do while the computers are down.
Most small shops have never answered it, because answering it does not involve buying anything. There is no invoice attached to the answer, so it does not get done.
The federal advice is almost insultingly boring
CISA, the agency that handles this, tells small businesses to plan for running essential functions without access to their systems or even the internet. Their example is to shift to paper.
That is it. Not a second data center. Paper.
For a five to fifty person business in the Upper Peninsula, that is also the realistic version. You are not going to fail over to a backup site in Green Bay. You are going to write things down and drive to the bank.
Four questions and one sheet of paper
Sit down with the person who actually runs the office. Not the IT person. The one who knows how payroll gets done.
1. What two or three things have to happen every working day for money to come in? 2. Which of those could be done on paper, and do the blank forms exist somewhere you could reach them? 3. Who can make a spending decision at 8am when you are not reachable, and up to what amount? 4. Who calls the customers, and what does that person say?
Write the answers on one page. Keep a copy somewhere that is not on the server, which is the whole point.
If the first question stops you, that is not a failure. That is the finding, and it is worth more than the rest of the exercise.
Then test it for an hour
Pick a slow afternoon. Take away access to the shared drive for one hour and try to produce one real invoice or one real quote by hand.
You will learn in about twenty minutes which of your answers were true. Do not do it during payroll week, and tell your staff what you are doing or you will spend the hour explaining yourself.
The goal is not drama. It is finding out that the invoice template lives in a folder only one person can open, while it is still a hypothetical and not a Thursday.
What this is worth
You may read all of this and decide you need nothing from us. That is a real outcome, and it is worth saying plainly: if you can answer those four questions and your backups have been restored at least once, you are ahead of most.
If you cannot, the fix is usually smaller than people expect, and it starts with a conversation rather than a purchase.
The server coming back is the easy part. The week after is the one worth planning.