Back online in hours, not days.
Disaster recovery and business continuity services for Melbourne and Sydney business.
Tiered recovery targets, tested failover, and a plan your team can actually run at two in the morning when the person who wrote it is on a plane. Backups are not a recovery plan. The difference only becomes obvious on the day you need one.
The difference
Backup is not disaster recovery.
A backup is a copy. Disaster recovery is getting your whole business running again. You need both, but do not confuse them.
Backup
Copies of your data
- Point-in-time copies of your data
- Restore individual files or mailboxes
- Protects against accidental deletion
- Does not bring systems back on its own
Disaster recovery
Your whole business back online
- Whole systems and apps recovered
- Defined RTO and RPO targets per tier
- Tested failover, not just a copy
- A runbook your team can follow under pressure
What is the difference between backup and disaster recovery?
A backup is a copy of your data. Disaster recovery is the ability to get your whole business running again, to an agreed timeframe, with a documented process and proof that it works. A backup with no tested restore is a file, not a plan.
What are RTO and RPO?
Recovery Time Objective is how long you can be down. Recovery Point Objective is how much data you can afford to lose. Every system gets both, and they are not the same for every system.
How often should we test a restore?
We test real restores quarterly and run a full failover exercise annually. Anything less frequent and you are relying on hope.
How quickly can you get us back?
It depends on the tier. Our mission-critical tier targets 15 minutes recovery time and 5 minutes recovery point. Standard systems target 24 hours. The table is below.
Do we need this if we are on Microsoft 365?
Yes. Microsoft guarantees the service, not your data. A deleted mailbox, a deleted SharePoint site or a departed employee’s OneDrive are all your problem to recover.
Proof
Recovery you can hold us to.
Targets we commit to and exercises we actually run, not a borrowed industry average.
Targets
RTO & RPO by tier.
Recovery time and acceptable data loss, set per tier so the most critical systems come back first.
| Tier | Recovery time (RTO) | Data loss window (RPO) | Suits |
|---|---|---|---|
| Tier 1 • Mission critical | 15 min | 5 min | Trading, clinical and live operations |
| Tier 2 • Core systems | 4 hrs | 1 hr | Line-of-business apps and email |
| Tier 3 • Standard | 24 hrs | 12 hrs | File shares, archives and reporting |
Confidence
Tested, not assumed.
A recovery plan you have never run is a guess. We test on a schedule and report the results to you.
Quarterly test restores
We restore real data every quarter, so recovery is proven and not assumed.
Annual full failover
A full failover exercise each year confirms the whole environment comes back.
Runbook reviews
The recovery runbook is reviewed and kept current as your systems change.
Report to you
You get a clear report on every test, with any gaps and the fix in plain terms.
Cost of inaction
What an outage actually costs an Australian business.
You will see a cost-per-hour-of-downtime figure quoted on most disaster recovery pages. We have left it off, because there is no Australian source for it. What there is:
Australian businesses adversely affected by a cyber incident, 2024-25
ABS Characteristics of Australian Business 2024-25. The ASD reports ransomware was present in 11% of the incidents it responded to over the same period.
The honest answer is that the cost is specific to you, and it is a number your finance team can produce in an afternoon: revenue per trading hour, plus the wages of everyone who cannot work, plus whatever the contractual consequences are. We do that exercise with you as part of the tiering, because a business case beats a statistic.
Proof
A real recovery, anonymised
One recovery story, told against the same RTO and RPO targets you set with us up front.
A food manufacturer restored operations in under four hours after a major outage.
“We hit the tier targets we agreed. The line was running again before the day was lost.”
Anonymised • sector label only.
Start here
Not sure where to start?
A no-obligation conversation about your infrastructure, security posture and operational risk. No lock-in, and a response within one business day.