Recovery requirements
Identify critical services, acceptable data loss and restoration priorities.
Backup & Disaster Recovery
Backup and disaster recovery is the combination of protected copies of your data and a tested way to restore the services that depend on it after a failure, cyber incident or site outage. Umbrella Tech helps Australian organisations set recovery priorities, design backup and recovery arrangements, and prove them with restore tests, so you know what can be recovered and how quickly.
The problem
The challenge we help you address
A successful backup job does not prove an application can be restored when needed. Unclear recovery priorities, missing dependencies, backups reachable by the same accounts an attacker would use, and procedures that have never been tested can leave the business exposed.
The outcome
What the engagement should deliver
A clear view of your recovery capability and the work needed to meet business expectations. Recovery targets are agreed for critical services, protection is designed around them, and restores are tested within the agreed scope with the results recorded.
How we can help
Protection design
Review backup coverage, separation from production, retention and recovery dependencies.
Disaster recovery plan
Document the steps, people and systems needed to restore each critical service.
Recovery validation
Carry out agreed restore tests and record procedures, results and remediation actions.
Terms worth knowing
- Recovery point objective (RPO): how much data, measured in time, the business can afford to lose.
- Recovery time objective (RTO): how long a service can be unavailable before the impact is unacceptable.
- Immutable or offline backup: a copy that cannot be changed or deleted from the production environment, which protects against ransomware.
- Disaster recovery plan: the documented procedure for restoring services, including who does what and in what order.
Regular backups are one of the Essential Eight mitigation strategies published by ASD's Australian Cyber Security Centre, and its maturity model expects restoration from backups to be tested.
How we deliver
How a recovery project runs
01
Prioritise
Agree critical services and their RPO and RTO with the business owners.
02
Review
Check what is backed up today, where copies are held and who can reach them.
03
Design and implement
Close the gaps in coverage, separation and retention.
04
Test
Restore agreed systems and record how long it took and what was missing.
Frequently asked questions
Can't see your question? Ask us directly →
What is backup and disaster recovery?
Backup is keeping protected copies of data. Disaster recovery is the planned, tested process for bringing services back after a major failure. Business backup solutions need both to be useful.
When should a business review its disaster recovery solutions?
After a change of systems or providers, when moving to the cloud, after a security incident, or if restores have not been tested recently.
Can you verify existing backups?
Yes. We review coverage and configuration and perform agreed restore tests. The test scope determines which systems, data and recovery scenarios are validated.
How long does a backup and recovery project take?
It depends on the number of systems, data volumes, the state of existing documentation and how many restore tests are in scope. Scope and timing are confirmed in discovery.
What are the main security or governance considerations?
Keeping backups out of reach of compromised administrator accounts, encrypting them, controlling who can delete them, and testing restores on a schedule with an owner for the results. Our Cybersecurity services cover the controls around them.
Plan the next improvement
Tell us which systems matter most and how you back them up today. We will help define a practical starting point.