Cloud, on-premise or hybrid backup: which suits an Australian small business?

Hybrid suits most Australian small businesses: a local copy for fast everyday restores, plus a cloud copy offsite and out of reach for the genuine disasters. Cloud-only makes sense for businesses already fully in the cloud with modest data. On-premise alone is the weakest choice, because it keeps every copy in the building.

The three options are usually presented as a philosophical choice, and they are not. They are three answers to a practical trade-off between how fast you can get data back and how well the copies survive something bad happening to your building or your network. Once you look at it that way, the decision is mostly arithmetic about your data volume, your internet connection and your recovery targets.

On-premise backup is fast and cheap to restore from. The data is metres away, a full server restore runs at local network speed, and there are no egress fees. Its weakness is concentration: fire, flood, theft or ransomware that reaches the network can take the original and the backup together. As the only strategy it fails the offsite half of the 3-2-1 rule and, more importantly, it fails the scenario that most often ends businesses, which is not a dead disk but an event that takes the whole site or the whole network.

Cloud backup inverts the profile. Geographic separation is inherent, capacity grows without buying hardware, and immutable retention is straightforward to configure so an attacker with your administrator password still cannot delete the copies. The costs are speed and dependence: a full restore is limited by your internet connection, some providers charge egress fees that only appear on the worst day, and you are relying on someone else's platform, which makes their data residency and their exit terms your business.

Hybrid is the default recommendation because it puts each copy where its weakness is covered. The local copy handles the everyday, which is where nearly all real restores live: the deleted folder, the corrupted database, the ransomware caught early. The cloud copy handles the day the building or the network is gone. Sizing them differently is the trick, since the local copy needs only enough retention to cover recent incidents, while the cloud copy carries the long tail. That split is also what keeps hybrid affordable, because you are not paying twice for the same retention.

Australian specifics change the maths in two ways worth naming. Connectivity is the first: cloud backup assumes an upload path that can carry your daily change and a download path that can carry a restore, and outside metropolitan fibre that assumption deserves testing before it is designed in. Data residency is the second: government-connected work and some contracts require Australian residency, and for health and financial records it is the safer default regardless. Both are questions to settle before architecture, not after.

Where the workload already lives matters too, and it is the fastest way to a decision. A business running Microsoft 365 with no server has little to back up locally and should think cloud-first, with the caveat that the tenant still needs an independent backup. A business with a line-of-business database on a server in the office needs the local copy for restore speed and the cloud copy for survival. And a business mid-migration, which is a great many, needs both anyway during the transition. Adelaide City General Practice moved its clinical systems to AWS precisely because a single on-site server was the whole risk, and the resilience came from the architecture rather than from buying a bigger backup drive.

Whichever shape you choose, one Essential Eight requirement cuts across all three and is worth checking directly: backups must be protected from the network they are backing up. That is a harder test than offsite, and it is the one on-premise arrangements most often fail, because a backup appliance joined to the same domain with the same administrator credentials is reachable by anyone who compromises that domain. Cloud copies with immutable retention pass it comfortably, which is a large part of why hybrid has become the sensible default rather than merely the cautious one.

The honest caveat is that the architecture matters less than two things it cannot fix: whether the copies are genuinely out of reach of a compromised network, and whether anyone has tested a restore recently. A beautifully designed hybrid system with an untested cloud copy is worse than a modest local one that gets restored every quarter, because it buys confidence it has not earned. Decide the shape, then prove it works. If you want it sized against your actual connection, data and obligations, call 1800 456 567.