Back at work in hours, not weeks
Your servers and data backed up locally and in Azure, checked every day, tested every month, and ready to run in Azure to the recovery targets you set.
Every protected server and its data backed up where it runs, then copied over a secure link to Azure, so a lost file is back in minutes and nothing depends on a single copy.
Recent recovery points close at hand, so a deleted or overwritten file is back in minutes.
Backups run on their own and land in Azure, with nothing to swap, carry or store.
The backup does the heavy lifting itself, so your servers keep working at full speed while it runs.
Only what's changed is sent, so storage and data links cost less.
Copies held in Microsoft's Azure datacentres in Australia, in a separate region from your own systems.
Email, files and Teams can join the same design through our Microsoft 365 backup service.
Your servers replicated to Azure in near real time, ready to run there to the recovery targets you've agreed, so your people are working again in hours, not weeks.
How quickly each server must be back, and how much recent work could be lost, agreed server by server and written into your policy.
Your backup and DR policy changes as your business does, and our engineers work from it day to day.
Recovery runs in Azure, away from your production systems, so one site's trouble never takes both.
A full recovery test each year, worked through your recovery checklist.
Step-by-step recovery and test procedures, and checklists to confirm everything works afterwards.
Recovery servers are specified to mirror your production servers.
A person reviews every backup each weekday and fixes anything that needs it, so you can trust that a restore will work when you need one.
Every month we restore a random sample of your data, to prove backups can be recovered.
Once a year we recover your servers in Azure, confirm they work, then remove the test servers to keep costs down.
We look after the backup and replication policies, and make routine changes as your needs shift.
The backup software is part of the service, kept up to date by us.
Your backup configuration, recovery process and diagrams kept current alongside the rest of your IT documentation.
We're accountable for restoring to the recovery targets in your policy.
On premises, in the cloud or both, the design follows your servers and brings recovery together in Azure.
Servers running in the cloud are backed up where they run, then replicated over a secure link to Azure in a geographically separate region.
Backups land on a local storage device first, for the fastest restores, then replicate over a secure link to Azure.
Servers on premises back up locally first; servers in the cloud back up to a separate region. Everything comes together in Azure.
Every backup checked, every month restored, every year recovered in full.
Daily
human checks of every backup, with anything that fails fixed
12
restore tests a year, on a random sample of your data
1
full disaster recovery test a year, through your checklist
Hours
to have your people working again, not weeks
A short project puts everything in place and proves it works before the managed service begins.
Step 1
We agree a recovery time and a recovery point for each server, and write them into your backup and DR policy for sign-off.
Step 2
We set up the backup platform, storage in Azure, a local storage device if you need one, and the policies to meet your targets.
Step 3
We restore files and whole servers, start every protected server in Azure, and write up the recovery process and checklist.
Step 4
You review the results and sign off, and the managed service begins.
Services that round out backup and disaster recovery.
Email, files and Teams, backed up and easy to restore.
See how your environment lines up with the ACSC Essential Eight.
Internet and links between your sites, managed with the carrier.
Anything else? Ask us directly.
A one-off setup project, then a fixed monthly fee for the managed service, which includes the backup software. Azure storage and recovery resources are billed each month on what you use, so that part grows with your data. If you keep servers on premises, you'll also buy a local storage device for the first copy.
Recovery time is how quickly a server must be running again. Recovery point is how much recent work you could afford to lose, measured in time. We agree both for each server and write them into your backup and DR policy.
We restore your servers and data in Azure to the targets in your policy, following your written recovery process. The recovery work itself is charged as time and materials unless we've agreed otherwise.
Microsoft 365 can be part of the same design, through our Microsoft 365 backup service, which is a separate agreement.
It gets your servers and data running in Azure. Business continuity goes further: where your people work from, how they connect, how regional sites and vendors reach the recovered systems, and how everyone stays in touch. We'll point those out as we plan, but they sit outside this service.
Managed IT Services checks backups and tests restores wherever a backup solution is in place. This service provides that backup, plus disaster recovery: the recovery targets, the replication to Azure and the annual recovery test.
