Backup as a Service: Stop Gambling on Recovery

It is Tuesday morning and a server has failed. Your team reaches for the backups, confident they have been running for years. An hour later the picture is clear: the last clean copy is months old, the recent jobs failed silently, and no one can say whose job it was to notice. Quotes are not going out, staff are standing around, and you are learning the hard way that having backups is not the same as being able to recover. This is the exact gap backup as a service is built to close.

Most businesses do not lack backup software. What they lack is anyone who is contractually on the hook when a restore fails, and that is a very different thing to buy.

Backup as a service, often shortened to BaaS, moves the work, the risk, and the responsibility onto a provider for a predictable monthly fee. It is less a piece of technology than a way of buying one.

This guide is about that buying decision, not the mechanics. If you want the underlying method, our data backup strategy guide covers how backups should be designed. Here we look at what backup as a service includes, who carries the risk, what it should cost, and the questions that separate a real service from rebranded storage.

What are you really buying with backup as a service?

You are buying an outcome and an owner, not a product. With backup as a service, a provider takes contractual responsibility for protecting your data and recovering it on demand, for a fixed monthly fee. The deliverable is not software on a server; it is the assurance that your data comes back, and someone whose job is on the line if it does not.

That distinction matters because backup is the classic task that belongs to everybody in theory and nobody in practice. A licence sitting on a server is not a service. Backup as a service draws a clear line: the provider configures coverage, watches it daily, proves it restores, and answers for the result. You are paying to turn backup from a quiet assumption into someone’s named job.

How is buying a service different from buying software?

Backup software gives you capability; backup as a service gives you accountability. When you buy software, your team still owns every task: installing it, watching it, fixing failed jobs, testing restores, and carrying the blame when something is missed. When you buy the service, those tasks and that liability move to the provider under an agreement, which is what managed backup really means in practice.

The practical effect is felt the day a backup fails. With software, that failure is your problem to notice, diagnose, and fix, usually mid-crisis. With backup as a service, it is the provider’s problem to have caught already, under terms you agreed in advance. With software you hope someone checked; with the service, someone is contracted to.

What is in scope, and what is not?

A clear scope is the heart of the deal. It should spell out exactly which systems are covered, how often they are backed up, how long copies are kept, and what recovery you are entitled to. Watch for gaps that look minor but bite hard, such as cloud mailboxes left out because people assume the platform handles its own protection. That assumption is a common and costly trap, which our Office 365 backup guide unpacks in detail. The rule when reviewing scope is simple: if it is not written down as covered, treat it as not covered.

Scope also has a habit of going stale. The accounting system you moved to the cloud last year, the second branch you opened, the new shared drive the projects team set up themselves: each can quietly fall outside a scope that was accurate on day one. A real backup as a service builds in periodic review so coverage keeps pace with the business, instead of freezing at whatever was true when the contract was signed. Ask how and how often scope is revisited, because an out-of-date scope fails in exactly the same way as no backup at all.

Who is accountable when a restore fails?

With backup as a service, the provider is. That single shift is the main thing you are paying for. In a typical in-house setup, responsibility is diffuse: IT set it up, someone was meant to check it, and when it fails the business absorbs the loss with no recourse. A managed service replaces that with a named owner and an agreement that defines exactly what they must deliver.

This is why the contract matters more than the brochure. A real backup as a service commits the provider to specified monitoring, testing, and recovery, and gives you something to hold them to if they fall short. A product licence with a support number does not. The question to keep asking a prospective provider is not what their tool can do, but what they are agreeing to be responsible for.

What does a service level agreement promise?

A backup as a service SLA should commit to two things in plain numbers: how recent a copy you can recover to, and how quickly recovery happens once you call. The first limits how much work you could lose; the second limits how long you are down. Vague language such as best effort or as soon as possible is a warning sign, because it commits the provider to nothing measurable. Get those two figures in writing and matched to how your business really runs, because a target that sounds fine on paper can still be too slow for the system your whole team depends on.

Should backups be independent of your other IT?

Ideally yes. A growing concern is that if your backups share credentials and systems with the environment they protect, a single breach can take out both at once. A well-designed service keeps recovery copies separated and isolated, so that even a compromise of your main systems or your IT provider does not take your backups with it. It is a fair and increasingly important question to put to any provider before you sign.

How much should backup as a service cost?

Pricing is normally a predictable monthly fee scaled to how much data you protect and the level of recovery you need. The figure on its own means little. The right comparison is not the fee against zero, but the fee against the full cost of carrying backup yourself, which is almost always higher than it looks.

Outsourced backup looks like a new line of spend, but doing it in-house carries hidden costs that never appear on an invoice: staff hours spent managing and checking jobs, the storage and infrastructure you still have to buy, the risk premium of silent failures, and the emergency day-rate when an untested backup lets you down. Backup as a service folds those into one operating line you can budget for, and converts an unpredictable crisis expense into a planned cost.

Is it cheaper than doing it ourselves?

For most small and mid-sized businesses, yes, once the true cost of DIY is counted honestly. A single failed recovery, or one day of downtime, frequently exceeds a year of service fees. Beyond the raw numbers, a predictable monthly cost is far easier to defend at board level than an unbudgeted recovery bill after an incident has already done the damage.

What pricing red flags should I watch for?

Be wary of pricing that looks cheap because recovery is billed separately. Some providers price the storage low and charge heavily at the moment you need to restore, which is exactly when you have least leverage. A genuine backup as a service makes recovery part of the deal, not a surprise invoice during a crisis. Always ask what a real restore would cost on top of the monthly fee.

How do you choose a backup as a service provider?

Judge each backup provider on what they will be accountable for, not on the technology they list. The strongest signal is a clear, written commitment to monitor daily, test restores regularly, keep an isolated off-site copy, report in plain language, and meet defined recovery targets. If those are not in the agreement, you are buying storage with a service label on it.

What questions separate a real service from storage?

Ask hard, specific questions and listen for specific answers. When did you last perform a real restore for a client? How fast can you recover a single file, and a full server? Are recovery copies isolated from our live systems? Do you test restores, and will you show me the reports? What does a full recovery cost beyond the monthly fee? A provider who answers these clearly is selling a service; one who deflects is selling a product.

How do we move from DIY to a managed service?

The switch usually starts with an audit of what you back up now, what is missing, and how recoverable it really is. From there the provider designs coverage, takes over monitoring and testing, and proves the first restore before handing you reporting. Exodesk delivers this as part of our managed IT services, so backup is owned alongside the rest of your IT instead of sitting as a separate worry. Where backup as a service ends and a wider response begins is set out in our disaster recovery plan guide.

When does backup as a service become the right call?

Backup as a service becomes the right call the moment backup stops being clearly owned. The trigger is rarely a disaster; it is usually an uneasy realisation that nobody can confidently answer basic questions about whether the data is safe.

A few signs make the decision for you. Nobody is certain the backups are running. No one has tested a restore in months. The person who set it all up has left. Your backups sit on the same network as the data they protect. Coverage has drifted as the business grew, so newer systems may not be included at all. Each of these is a gap in ownership, which is precisely what backup as a service is bought to supply.

How will I know the service is working?

Through reporting you can read without being technical. The whole point of paying for a managed service is that you should see, in plain language, that backups completed and restores were tested, and be told quickly if something needs attention. If a provider cannot show you that evidence on a regular basis, you have bought storage, not assurance. Backup as a service should also dovetail with your wider resilience planning, so it is worth confirming how it connects to your business continuity plan instead of sitting in isolation.

Does the size of my business change the answer?

It changes the shape, not the principle. A very small, stable setup may be manageable in-house for a while, but the case for backup as a service strengthens fast as you add servers, cloud platforms, and people, because operating it well every day becomes its own discipline. For most South Island SMEs, the point where backup as a service pays for itself arrives sooner than expected, usually the first time a restore is needed and no one is sure it will work.

Exodesk takes contractual ownership of business backups for companies across Christchurch, Dunedin, and the wider South Island, monitoring, testing, and restoring so a recovery works on the day it matters. We have been keeping South Island businesses running since 1989.

Contact us today to discuss how we can help your business or connect with us on LinkedIn to stay updated with more insights.

Frequently Asked Questions

What is backup as a service?

It is a way of buying data protection as a guaranteed result instead of a tool. You hand the whole job to a specialist who is contractually answerable for keeping your information safe and getting it back when you ask, in exchange for a steady monthly charge. The point is to turn protection into a defined duty someone is on the hook for, not an in-house assumption.

How is backup as a service different from backup software?

Backup software gives you the capability to back up, while backup as a service gives you accountability for the outcome. With software, your team still owns installing, monitoring, fixing, and testing, and carries the blame if something is missed. With the service, those tasks and that liability move to the provider under an agreement, so a failure is theirs to have already caught.

Who is responsible if a restore fails?

With backup as a service, the provider is responsible under the terms you agreed. This is the core difference from an in-house setup, where responsibility is diffuse and the business absorbs the loss with no recourse. A genuine service names an owner and commits them to defined monitoring, testing, and recovery, which is why the contract matters more than the marketing.

What should a backup as a service SLA include?

A good service level agreement commits the provider in plain numbers to how recent a copy you can recover to and how quickly recovery happens once you call. The first limits how much work you could lose; the second limits how long you are down. Vague terms such as best effort are a warning sign, because they commit the provider to nothing you can hold them to.

How much does backup as a service cost?

Pricing is usually a predictable monthly fee scaled to how much data you protect and the recovery level you need. The fair comparison is not the fee against zero, but against the full in-house cost: staff time, storage, the risk of silent failures, and emergency recovery rates. For most small and mid-sized businesses, a single failed recovery or day of downtime exceeds a year of service fees.

What pricing red flags should I watch for?

Be cautious of low headline pricing where recovery is billed separately, because you have least leverage at the moment you need to restore. A real backup as a service includes recovery in the deal rather than charging heavily for it during a crisis. Always ask what a full restore would cost on top of the monthly fee before you sign.

Should backups be kept separate from our main systems?

Ideally yes. If backups share credentials and systems with the environment they protect, a single breach can take out both at once. A well-designed service keeps recovery copies isolated, so a compromise of your main systems, or even your IT provider, does not take your backups with it. It is a fair question to put to any provider before committing.

What questions tell me a provider is selling a real service?

Ask when they last performed a real restore for a client, how fast they can recover a single file and a full server, whether recovery copies are isolated, and whether they will show you test reports. Specific, confident answers indicate a service; deflection indicates a product with a service label. The point is to test what they will be accountable for, not what their tool can do.

Do we still need this if we have an internal IT person?

Often yes, as a complement rather than a replacement. Backup as a service takes a repetitive, easy-to-neglect task off an internal person’s plate and adds external monitoring, tested recovery, and accountability that one busy individual cannot reliably maintain alone. It also adds independence, so your protection does not rest on a single person remembering to check.

How do we switch from managing backups ourselves?

It usually starts with an audit of what you back up now, what is missing, and how recoverable it genuinely is. The provider then designs coverage, takes over monitoring and testing, and proves the first restore works before handing over reporting. Exodesk manages this as part of a wider managed IT service across the South Island, so backup is owned alongside the rest of your IT.