Backups vs business continuity: what actually happens on the day everything stops

Having backups is not the same as being able to keep trading. Here is what a bad day really looks like, and the one-page plan that gets you through it.

Ask most business owners whether their data is backed up and they will say yes, with reasonable confidence. Ask what happens on the day everything stops, and the answer gets vaguer. That gap, between having backups and being able to keep trading, is what business continuity is about, and it is wider than most people think.

A realistic bad day, hour by hour

Picture a regional business with a dozen staff. At 7:40am the server in the back room dies, or ransomware has encrypted it overnight, or a burst pipe has flooded the office. The backups exist. Good. But here is what the day actually looks like.

Hour one: staff arrive to nothing working. Nobody is sure who to call, so three people call three different numbers. Hour two: it becomes clear the backups are on a drive sitting next to the dead server, in the same flooded room. Hour four: someone asks where the software licences and installer files are, and the answer is on the server. Hour six: customers are ringing, and nobody can see the booking system or the account balances, so the team is guessing. Hour eight: the owner is doing maths on how many days of this the business can absorb. Hour twelve: the evening is spent writing down everything anyone can remember about passwords, licences and supplier contacts, because it turns out the list was on the server too. The next morning: half the team comes in anyway and stands around, because nobody has worked out yet who can work from home and who cannot. The backups, technically, still exist. Getting from "backups exist" to "we are trading again" turns out to be the whole problem.

The two questions that matter

Continuity planning comes down to two questions. First: how much data can you afford to lose? If the backup runs once a night, a disaster at 5pm wipes a full day's work. If that thought hurts, you need backups running more often. Second: how long can you be down? An hour, a day, a week? Your honest answer decides how much preparation is worth doing, because faster recovery needs more groundwork laid in advance.

In the trade these are called the recovery point objective (RPO) and recovery time objective (RTO), but the plain-English versions are all you need to make good decisions: how much can we lose, and how long can we stop?

The 3-2-1 idea in plain words

The classic backup rule is called 3-2-1: keep three copies of your important data, on two different types of storage, with one of those copies offsite. The offsite part is what saves you when the office itself is the problem. A backup drive beside the server fails the test the day the server room floods, burns or gets stolen.

Cloud services still need backing up

A quick word on a common assumption: moving to Microsoft 365 or Google Workspace is not the same as being backed up. Microsoft keeps the lights on and the service running, but under its shared responsibility model, your data is your responsibility. Deleted emails, ransomware-encrypted files and departed-employee mailboxes can all become unrecoverable without a separate backup of your cloud data. We set this up for businesses every week, and it is simpler than people expect.

A word on ransomware specifically

Ransomware, where an attacker encrypts your files and demands payment, deserves its own paragraph because it changes the order of operations. If your server was encrypted overnight, restoring last night's backup onto the same system is pointless: the way the attacker got in is still open, and you will simply be encrypted again. The entry point, usually a phished email account, a weak remote access setup or an unpatched server, has to be found and closed first. Only then does the restore begin. This is why a continuity plan includes "who investigates how they got in" and not just "who restores the files".

Where staff work from tomorrow

Continuity is also about desks. If your team works on desktops wired to the office, a flooded office means nobody works, full stop. If they have laptops and cloud logins, tomorrow looks very different: some work from home, a couple hot-desk at another site or a quiet corner of the local library, and the phones get diverted to mobiles. None of that happens by accident on the day. It happens because someone decided in advance which roles can work remotely, checked that staff home internet and mobile coverage are up to it, and wrote down who answers the phones and from where. If your internet and phone lines are down with the office, a voice over internet protocol (VoIP) phone system can usually be diverted in minutes, but only if someone knows the login. Put that detail on the one-page plan.

Test it, then rehearse it

Two habits turn a plan on paper into a plan that works. First, actually restore things from backup, regularly, and time how long it takes. Second, once a year, run a tabletop drill: gather the key people for half an hour, describe a scenario ("the server died at 7:40am, walk me through what we do") and let everyone talk through their part. The gaps surface in the conversation, where they are cheap to fix, instead of on the day, where they are not.

The one-page continuity plan

You do not need a binder. One page, printed and pinned somewhere, covering:

• Who calls whom: the internal phone tree and the after-hours IT number.
• Where staff work from if the office is unusable, and how they log in from there.
• How customers are told: who posts it, who answers the phones, what the script is.
• Where the critical account details and licence information live, somewhere other than the server.

If you would like answers to those questions without the pauses, talk to our team. Backups that are monitored and restore-tested, plus a plain one-page continuity plan, are part of how we look after businesses across Victoria.

• backups
• business continuity
• managed it
• disaster recovery