Software · Cloud and infrastructure
Backup and recovery
Encrypted, off-site backups and rehearsed recovery plans that bring systems back after a failure or attack.
A backup only counts once it has been restored. We design backup and recovery around how much data you can afford to lose and how long you can be down, then build it: encrypted, immutable copies kept off-site and in a separate account, coverage for servers, databases and SaaS data, and scheduled restore drills that prove the plan works.
What we build
- Backup policies set by recovery point and recovery time for each system
- Encrypted, deduplicated backups with restic, BorgBackup or Veeam
- Immutable copies with object lock in a separate cloud account
- Database backups with point-in-time recovery for PostgreSQL and MySQL
- Microsoft 365 and Google Workspace backup for mail, files and sites
- Automated restore tests that boot, check and report on recovered systems
- Disaster recovery run-books and failover to a second region or site
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
- Schedule fires at 01:00 for 18 protected systems
- Snapshot
- Encrypt and dedupe
- Copy off-site
- Lock copies
- Restore test
- Report
What it does well
3-2-1 by default
Three copies, on two kinds of storage, with one off-site and out of easy reach.
Ransomware resistant
Immutable, separately owned copies cannot be deleted with stolen admin passwords.
Tested restores
Restores run on a schedule and report the time taken and any files that failed.
Encrypted at source
Data is encrypted before it leaves the machine, with keys that you control.
Clear targets
Each system has a written recovery point and time goal the design is checked against.
One protection view
A single report shows what is protected, when it last backed up and last restored.
Questions
We already have backups. Why would we need more?
Many backups have never been restored, sit on the same network as the systems they protect, or can be deleted by the same admin account. We check yours against your recovery goals, test a real restore, and fix only the gaps we find.
What are RPO and RTO?
Recovery point objective is how much recent data you can afford to lose, such as one hour. Recovery time objective is how long a system may be down. They differ by system, and they decide backup frequency, storage choice and whether you need a standby copy running.
Is Microsoft 365 data not already backed up?
Microsoft keeps the service running and offers limited retention, but deleted or overwritten data, compromised accounts and long-term retention are your responsibility. A separate backup gives you independent copies you can restore by user, mailbox, site or file.