Recover quickly when it matters
Resilient backup and disaster recovery that protects your business from data loss and downtime, designed around what you can afford to lose and tested so restores are routine.
Backup and disaster recovery you have actually tested
Every cloud provider offers backup. Very few businesses have checked that theirs works. The common failures are quiet: the backup job that has been failing for a month, the database that was never included, the backup stored in the same account as the ransomware, and the restore that takes three days when the business assumed three hours.
Orbit3's cloud backup service starts with two numbers: how much data you can afford to lose and how long you can afford to be down. From those we design the backup and recovery approach, automate it, isolate it from the environment it protects, and rehearse the restore until it is routine. Under managed services, the backups are monitored and test-restored on a schedule.
- Recovery objectivesRPO and RTO agreed per system, so protection matches business impact.
- Automated, isolated backupsImmutable copies in a separate account or region, out of reach of a compromised environment.
- Disaster recovery planA written strategy and runbook for losing a region, an account or a system.
- Tested restoresScheduled recovery tests, with the results recorded.
For any business that would struggle to explain a lost week
The question is not whether you have backups. It is whether you have restored from them, and how long it took.
Businesses facing ransomware risk
Which is all of them. You need copies an attacker with your credentials cannot reach, and a plan for rebuilding from them.
Companies with contractual uptime obligations
Your customers or insurer want a documented, tested recovery plan with defined recovery times.
Teams relying on default cloud snapshots
Snapshots exist, in the same account, with no retention policy and no restore ever attempted. You would like more certainty than that.
Protection that has actually been restored from
Backup is a process, not a product. We design it around what your business can afford to lose and how long it can afford to be down, then prove it works.
- Recovery objectives workshopRecovery point and recovery time objectives agreed per system with the people who depend on them, and written down.
- Backup inventory and gap analysisWhat is protected today, what is not, and where existing backups would fail a real restore.
- Backup design and automationPolicies for databases, file storage, virtual machines, containers and configuration, using native services where they fit.
- Immutable and isolated copiesBackups that cannot be altered or deleted for a retention period, stored in a separate account or region from production.
- Retention and cost controlRetention schedules that meet your legal and business needs without paying to keep everything forever.
- Disaster recovery strategyBackup-and-restore, pilot-light, warm standby or active-active, chosen per system by its recovery objectives and budget.
- Recovery runbooksStep-by-step procedures for restoring each system, written so someone other than the author can follow them at 3am.
- Restore testingScheduled recovery tests, from single-file restores to full environment rebuilds, with timings and results recorded.
- Monitoring and reportingBackup job monitoring, alerts on failure, and a periodic report showing coverage, test results and any gaps.
Protect, plan, verify
A backup you have never restored from is a hope, not a plan. Every engagement ends with a rehearsed recovery and a written runbook.
Protect
We agree recovery objectives, close the gaps in what is backed up, and automate resilient, isolated backups of every critical system.
Plan
We design the disaster recovery strategy per system and write the runbooks, so recovery is a procedure rather than an improvisation.
Verify
We rehearse restores on a schedule and record the results, so you know your recovery times are real and your backups are usable.
AWS, Azure and Google Cloud
Each cloud has native backup services that are excellent for some workloads and inadequate for others. We use them where they fit and add cross-region or cross-cloud protection where they don't.
Amazon Web Services
AWS Backup with vault lock for immutability, cross-account and cross-region copies, RDS and Aurora point-in-time recovery, S3 versioning and Object Lock, and Elastic Disaster Recovery for warm standby.
Microsoft Azure
Azure Backup with Recovery Services vaults and immutability, Azure Site Recovery for replication and failover, SQL point-in-time restore, and storage soft delete and versioning.
Google Cloud
Backup and DR Service, persistent disk snapshot schedules, Cloud SQL automated backups with point-in-time recovery, and Cloud Storage retention policies and object versioning.
Frequently asked questions
What are RPO and RTO?
Recovery point objective is how much data you can afford to lose, measured in time since the last backup. Recovery time objective is how long you can afford to be down. Every system gets its own pair, and they drive every design decision, because protecting everything to the highest standard is unaffordable and unnecessary.
Are cloud provider snapshots enough?
Rarely on their own. Default snapshots usually live in the same account as production, have no retention policy, and have never been restored. They are a starting point, not a plan.
How do backups protect against ransomware?
By being immutable and isolated. Immutable backups cannot be altered or deleted during their retention period, even by an administrator. Isolated backups live in a separate account or region with separate credentials, so an attacker who compromises production cannot reach them.
How often do you test restores?
On a schedule agreed for each system, typically monthly for single-system restores and at least annually for a full disaster recovery rehearsal. Every test is timed and recorded so you can show the evidence.
What does disaster recovery cost?
It scales with the recovery time you need. Backup-and-restore is inexpensive but slow; a warm standby costs more to run but recovers in minutes. The recovery objectives workshop is where we match each system to the cheapest option that meets its needs.
Can you take over backups for an environment we run ourselves?
Yes. Backup and recovery can be delivered as a standalone engagement, with your team running the rest of the environment, or as part of our managed service.
Often combined with this
Recovery planning sits alongside security and day-to-day operations. These services close the loop.
CloudOps Managed Services
24/7 monitoring, patching, security and cost control for your AWS, Azure or Google Cloud environment, run by us.
Learn moreCloud Security
Security reviews, risk assessments and hardened target-state controls mapped to the standards you need to meet.
Learn moreCloud Optimisation
FinOps analysis, right-sizing and governance that cut cloud spend and keep it down.
Learn moreConfident you could recover from data loss?
Book a free 30-minute call and we'll pressure-test your backup and recovery strategy.