IT recovery planning for Brisbane small businesses

Brisbane colleagues mapping recovery responsibilities

An IT recovery plan is a short document that says which systems your business needs first after something breaks, who brings them back, and how. It also says where the clean copies of your data live. For a business of 5 to 100 people, it usually runs to a few pages, not a binder. The plan only counts once someone has restored a real file from a real backup and timed it.

We are a Brisbane Managed IT team and we look after Microsoft 365, security, backups and networking for businesses across the Sunshine Coast to the Gold Coast. This guide is the routine we would walk you through ourselves.

IT Start
Build a Recovery Plan That Works
IT Start supports Brisbane businesses with managed IT, backups and cybersecurity, helping you plan for system recovery and data protection.
Contact Us

Key Takeaways

  • Start with a list of what the business cannot work without, ranked by how many hours you could cope without each item. Do not start with technology.
  • Set two numbers per system: how long you can be down and how much recent data you can afford to lose.
  • Keep at least one backup copy that your everyday accounts cannot delete, and back up Microsoft 365 as well.
  • Test a restore when you set backups up, once a year and whenever your setup changes. An untested backup is a guess.
  • Write the plan so a non-technical person can follow it on a bad morning, with phone numbers that do not depend on your own email.

Table of Contents

What an IT recovery plan covers

Business Queensland says a recovery plan helps cut recovery time and limit losses when an IT incident hits. It suggests the plan includes ways to get operating quickly, a list of key resources and equipment, and recovery time objectives. That last term simply means how long you are prepared to wait for a system to come back.

The terms get muddled, so here is how they fit together:

  • A disaster recovery plan covers getting IT systems and data back.
  • A business continuity plan covers keeping the business serving customers, with or without IT. The Queensland Government’s guideline treats IT as one element of continuity and notes a service can sometimes carry on through a manual process while systems are down.
  • A cyber incident response plan covers what you do in the first hours of an attack. Ours is covered in our guide to incident response plans for SMBs.

For a 20-person business, you do not need three separate documents. One recovery plan with a front page for “what to do in the first hour” does the job.

What most businesses get wrong

We see this a lot: a business has a backup tick on a dashboard and considers recovery handled. A tick means a job ran. It does not mean the files can be restored, that they are complete, or that anyone knows how long it takes.

The regulator’s findings point the same way. APRA reviewed backup practices in 2024 and named two recurring weaknesses: backups not properly separated from the production environment, and testing that was too narrow or not rigorous enough. APRA regulates banks and insurers, so this is about large entities. Small businesses make the same mistakes with fewer resources to absorb them.

Three other gaps turn up again and again in our work:

  1. The plan assumes the office is available. Nobody has written down what happens if the server room or the whole building is not.
  2. Only one person knows the admin passwords, and they are on leave or have left.
  3. Microsoft 365 is assumed to be “in the cloud, so safe”. Email, SharePoint and OneDrive are hosted, but deleted or overwritten data is still your problem to recover.

Step 1: list what the business runs on

Before you pick any backup product, list what you depend on. The Queensland Government’s business continuity and ICT recovery fact sheet suggests identifying critical and non-priority services, the dependencies they share and the impact of each failing over time. NAB’s guidance adds staff, suppliers, premises, and vital records such as customer data, and points out that one event can hit several of these at once.

In practice, a one-page table is enough. Here is a hypothetical example for a 15-person accounting practice (not a real client):

System Who needs it Tolerable downtime Tolerable data loss
Email and calendar (Microsoft 365) Everyone Half a day An hour or two
Accounting and tax software Accountants One working day Same day
Client files on SharePoint or a file server Everyone One working day Same day
Phone system Reception Half a day Not applicable
Staff intranet and templates Admin A few days A week

The numbers belong to you, not to us. Ask the people who run each area how long they could manage with pen and paper or a workaround. You will often find the answer is longer than the IT person assumed, and that one system nobody mentioned (the phone line, the payroll portal, the door access system) is the one that stops everything.

List the dependencies on people too. If your internet connection, your Microsoft 365 sign-in and your accounting software all depend on one admin account, write that down. That single account is a risk to fix.

Step 2: set recovery time and data loss targets

Two terms matter here, and both are plain once explained:

  • Recovery time objective (RTO): the longest you can be without a system.
  • Recovery point objective (RPO): the most recent data you can afford to lose, measured in time. If your RPO is four hours, backups must run at least that often.

APRA’s guidance frames this for regulated entities as the maximum disruption time, the maximum data loss and the minimum service level for each critical operation. You are not regulated by it, but it is a good way to think. The AICD small business handbook says to set backup frequency from the data loss you can accept.

Here is our honest opinion on cost. Tighter targets cost more, and most small businesses do not need minute-level recovery for everything. Paying for instant failover to a second site makes sense for a system that earns money by the minute. For a staff intranet or an archive of old projects, it is money wasted. Put your spend on the three or four systems at the top of your table and give the rest a cheaper, slower recovery.

If you are an APRA-regulated entity, this article is not enough for you. CPS 230 sets formal requirements for business continuity and critical information assets, and you need to work to it directly.

Step 3: design backups that survive an attack

The ACSC says that without reliable backups, recovering information after a cyber incident may be difficult or impossible. Its handbook recommends backing up regularly or automatically as part of normal operations.

The design detail that matters most is isolation. The ACSC’s mitigation strategies explain that ransomware and malicious insiders can encrypt, corrupt or delete backups that are easily reachable, so copies should be stored offline or disconnected. It also advises keeping them for at least three months, so that when an incident is finally noticed there is still an undamaged copy to go back to. That retention point is the one we see skipped most. A business that keeps only 14 days of history can find that the bad files have already replaced every good version.

APRA adds a rule that works well at any size: no single account should be able to modify or delete both your live data and your backups. For a small business, that means the admin account you use every day should not hold the keys to the backup storage.

A checklist we work through:

  • At least one backup copy in a separate location, such as protected off-site storage or a separate cloud environment, as the AICD handbook suggests.
  • Separate sign-in for the backup system, with multi-factor sign-in turned on for every account that can reach it.
  • Backups of Microsoft 365 mailboxes, SharePoint and OneDrive, which the AICD handbook names as platforms to cover.
  • Retention of at least three months.
  • Backup failure alerts that go to a person, not to a mailbox nobody reads.

If you want this set up and watched for you, that is what our backup and disaster recovery service in Brisbane is for. For the Microsoft 365 side, our Microsoft 365 support and management covers the tenant settings your recovery depends on.

Step 4: cover the boring failures too

Plans written after a news story about ransomware tend to cover only ransomware. Proton’s 2026 guidance is not our source for this, so we will say it from experience: the most common recovery jobs we see are dull. A laptop dies. Someone deletes a shared folder. A staff member leaves with the only copy of a password. A supplier’s cloud tool goes down for an afternoon.

Give each of these a line in the plan: what to do, who does it, where the backup is. A deleted folder should be a ten-minute restore from a known place, and writing that down is what makes it so.

Queensland adds weather. Business Queensland notes that IT incidents can come from a wider crisis such as a bushfire or flood, and that the safety of staff and the public comes first. Your IT plan should sit under any emergency plan you already have. For a Brisbane business near the river or a creek, that means asking one practical question: if the office is closed for a week, can staff reach email, files and the phone system from home? With Microsoft 365 set up properly, the answer is usually yes. With a file server in a back room, it is no.

Step 5: write down who does what

The ACSC handbook says an incident plan should define staff roles, escalation paths and communication paths, with step-by-step procedures for detection, containment, response and recovery. The business.gov.au checklist adds how to report an incident, how to tell employees and customers, and how to run the business during and after.

One page of contacts goes a long way:

  • Who makes the call to declare an incident (usually the owner or general manager).
  • Who talks to staff and who talks to customers.
  • Your IT provider’s contact details and your cyber insurer’s claim line, if you hold a policy.
  • The Australian Cyber Security Hotline: 1300 292 371, listed in the business.gov.au checklist.
  • Admin credentials held in two places, one of them a sealed copy off the network.

Print it. If your email and your network are the things that failed, a plan stored only in your email is no use. Our cyber security incident response plan example shows how this page can look.

On ransom payments, the AICD’s 2024 publication says paying does not guarantee you get your information back or stop it being sold or leaked, and you may be targeted again. The point of good backups is that this decision is not forced on you.

Where the data and reality do not match

The guidance is clear that backups should be tested. In practice, testing is the first thing dropped when a business is busy. The ACSC says to test restoration when backups are first set up, once a year and whenever IT infrastructure changes. The Information Security Manual goes further and says restores of data, applications and settings should be tested together to a common point in time, as part of recovery exercises.

YouTube Video

The “common point in time” idea matters more than it sounds. Restoring a database from Tuesday and the files it points to from Thursday can leave you with software that starts but shows the wrong data. Test the pieces together.

A restore test we would run for a small business takes about an hour:

  1. Pick a real folder with files that changed last month.
  2. Restore it to a different location, not over the original.
  3. Open five files and check they are the right version.
  4. Restore one mailbox item and one SharePoint file from the Microsoft 365 backup.
  5. Note how long it took and compare it with your recovery time target.
  6. Write the result and date at the bottom of the plan.

Then run a larger exercise now and then. The ACSC handbook suggests simple drills, checking decision-making and fixing the gaps they reveal. A drill can be a 30-minute conversation: “It is Monday 8am, the file server is encrypted, what do we do?” The gaps show up quickly. Usually it is a missing phone number or a password nobody can find.

APRA’s testing guidance says to confirm backups are effective and protected from unauthorised changes, and that coverage is enough to recover critical operations within tolerance. Put that as two questions on your annual review: did the restore work, and could it have been tampered with.

What is not worth doing

Some honest limits, since we would rather you spend well:

  • A recovery plan template downloaded and left with blanks filled in generically is not worth the paper. It has to name your systems and your people.
  • Full replication of every system to a second site is not worth paying for in a business of 10 or 20 people. Tier your systems and protect the top ones hardest.
  • A plan nobody has read. If staff cannot say where the one-page version lives, it will not be used.
  • A single drill, never repeated. Review the plan after any change to staff, software or suppliers.

This guide is also not for a one-person business with a single laptop and a cloud drive. A simple automatic backup and a written list of passwords will do for you.

How we approach recovery planning

Our Business IT Support is charged at $145 an hour ex GST, which suits a one-off project like building and testing a recovery plan. Managed IT plans cover support, devices, Microsoft 365, backup and security on an ongoing basis, so the plan is kept current as your staff and software change. If you want a second set of eyes on your backups or want us to run the restore test with you, our backup and disaster recovery page describes what we do. We offer a free consultation or project assessment to start, with no hard sell. If cyber risk is the main worry, our Cyber Security page is the place to begin.

Our view on recovery planning

We think most recovery plans fail for one reason: they are written once and filed. The businesses that recover well are the ones that treat the plan as a routine, like servicing a car.

Our recommendation is simple. Keep the plan to a few pages. Rank your systems honestly. Keep one backup copy that your daily admin account cannot touch. Back up Microsoft 365 as well. Run a restore test each year and after every big change.

That routine is what we build into Managed IT for businesses of 5 to 100 people from Brisbane through to the Sunshine Coast and Gold Coast. Good routine care means the first time you restore a file is not the day you urgently need it.

IT Start

FAQ

What is the difference between a disaster recovery plan and a business continuity plan?

A disaster recovery plan is about restoring IT systems and data. A business continuity plan is wider and covers keeping the business serving customers, including manual workarounds. The Queensland Government treats the IT plan as one supporting part of the continuity plan. A small business can combine both into one short document.

How often should we test our IT recovery plan?

The ACSC says to test restoring backups when they are first set up, once a year and whenever your IT infrastructure changes. Run a short discussion drill as well, and update the plan when staff, suppliers or software change.

Is there free help if we have already been hit by a cyber incident?

Yes. The Small Business Cyber Resilience Service, delivered by IDCARE for the Australian Government, offers free one-on-one support to small businesses to build a tailored plan and recover from an incident. You can also call the Australian Cyber Security Hotline on 1300 292 371.

Do we need to back up Microsoft 365?

We recommend it. The AICD handbook says to back up all platforms integral to your operations, including cloud services such as Microsoft 365. Cloud hosting does not protect you from accidental deletion or a compromised account. We can check how yours is set up through a free consultation.

IT Start
Discuss Your IT Recovery Plan
Contact IT Start to discuss your business’s IT support, backups and cybersecurity needs with a Brisbane-based team.

Sources

Related Posts