Backup discipline that actually survives a real incident — not just nightly snapshots in the same data centre. Off-site copies, immutable storage where it matters, documented restore procedures and tested recovery time. The goal: when the bad day comes, you have already practiced.
Backup discipline that actually survives a real incident — off-site copies, immutable storage where it matters, documented restore procedures and tested recovery time.
A transparent engagement model with clear milestones.
List every system, identify which are critical, define RPO/RTO per system, choose backup destination accordingly.
Backup schedule, immutable storage for ransomware-relevant data, monitoring of backup success and failure alerts.
Quarterly restore tests with results documented. Annual disaster-recovery tabletop exercise included for retainers.
Practical, honest expectations — no exaggerated promises.
Backups survive the bad day, not just the audit checklist.
Immutable copies for the data that would hurt to lose.
Anyone qualified can perform the restore — not just one heroic person.
You know how long recovery actually takes.
Specialist pages strengthen the Graham Miranda ecosystem and route visitors to the right service.
Concise answers for visitors comparing Graham Miranda service areas.
For Linux servers: borg / restic / rsync.net. For Microsoft 365: third-party backup specialist (Datto/Veeam/AvePoint) since native M365 backup is insufficient. For databases: native tooling + WAL archiving for Postgres.
EU-region by default. Specific data residency (e.g. Germany-only) documented per engagement.
Immutable backups (S3 Object Lock or storage-level WORM) for critical data. Plus offline / air-gapped copies for the most-critical assets.
At minimum quarterly. Each test documents what was restored, in what time, and any issues found.
Yes — third-party backup is included for any serious M365 / Workspace setup. Native vendor backup is insufficient for real recovery scenarios.
Per system, per contract. Typical: critical systems 4 hours, important 1 business day, lower priority 3 business days. RTO is part of the written engagement.
Backup discipline that actually survives a real incident — off-site copies, immutable storage where it matters, documented restore procedures and tested recovery time.
