Cloud
Disaster recovery and cloud backups
RTO, RPO, and runbooks in plain language — how Melbourne businesses plan recovery when servers, sites, or Microsoft 365 fail.
Need help with this? Talk to our Cloud Systems team
RPO and RTO defined
Recovery Point Objective (RPO) is how much data you can afford to lose — measured in time since last good backup. Recovery Time Objective (RTO) is how fast systems must be back online. A four-hour RTO with 24-hour RPO is common for SMEs; tighten targets for finance or operations-critical systems.
Scenarios to plan for
Ransomware, fire or theft of a server, Microsoft 365 admin mistakes, domain hijacking, and extended ISP outages. Each scenario needs a named owner, communication list, and technical steps — not a binder nobody has opened since 2019.
Cloud-specific considerations
Know how to restore mailboxes, SharePoint libraries, and Azure VMs from backup consoles — not only from recycle bins. Keep offline admin credentials and document which vendor holds DNS registration.
Exercise the plan
Tabletop walkthroughs take an hour; live restore tests take longer but expose gaps. Update the runbook when you add a site, change accounting software, or move files to a new SharePoint library.
Related service
This is part of our Cloud Systems service for Melbourne businesses.
Try it now
Run the related tools
Need a hand?
Run the tools. Then talk to us.
Use our free diagnostics to see what is wrong, then get Melbourne IT support for the fix.
Keep reading
More guides
What is Microsoft Intune for small business?
A plain-English guide to Microsoft Intune for Australian SMBs — what it manages, when you need it, and how it fits with Microsoft 365.
- Intune in one sentence
- Why small businesses look at Intune
Microsoft 365 onboarding checklist
The setup steps most small businesses miss — identity, email, devices and security in the right order.
- Identity first
- Email and DNS