Home/Data center & cloud/Backup & Disaster Recovery

Backups are not doneuntil a restore has run.

A 3-2-1 backup architecture with immutable copies, offsite replication, defined RPO and RTO per workload, and quarterly DR drills that produce a report — so when something goes wrong, recovery is a procedure, not a hope.

ProductionVMs · DBs · filesLocal backupPBS · dedup · fast restoreImmutable copylocked retentionOffsitesecond site / cloudDR drillquarterly · reportedRPO 15 min – 24 h · RTO 1 – 8 h, per workload, in writingSuzu Technology · Backup & Disaster Recovery · sheet 29not to scale
Fig. 29 — 3-2-1 designProduction → Local backup → Immutable copy → Offsite
Data center & cloud

What we do

We rolled out Proxmox Backup Server for production estates and we know where backups fail: untested restores, retention that silently stops, ransomware that encrypts the backup along with the data. Our design answers each: deduplicated local backups for fast restores, an immutable copy with locked retention, an offsite replica, and a drill every quarter.

Every workload gets an RPO and RTO in writing. The DR drill proves them, and the report goes to management.

Included
  • AssessmentWorkload inventory, current backup gaps, RPO/RTO targets
  • Architecture3-2-1 design, PBS or equivalent, immutability, offsite
  • ImplementationJobs, retention, encryption, monitoring, alerting
  • VerificationAutomated restore tests and quarterly DR drills
  • ReportingMonthly backup health, drill reports, capacity forecast
How it runs

The engagement, step by step

01

Audit

We inventory what you run — hardware, hypervisors, storage, backups, network — and document the risks.

02

Blueprint

HLD/LLD with architecture, bill of materials, migration plan, budget and timeline, within 48 hours of the audit.

03

Build

Change-controlled implementation with MOPs, rehearsed cutovers and as-built drawings.

04

Operate

Monitoring, AMC or managed operations with monthly reports and quarterly reviews.

Commitments

What we put in writing

Written into the blueprint before work starts. If a number is not here, ask for it — we put it in writing.

RPO / RTODefined per workload, written into the design
ImmutabilityLocked retention on at least one copy
DrillsQuarterly, documented, with management report
MonitoringFailed or missed job alerts within 15 minutes
FAQ

Questions we get asked

Do you back up Microsoft 365 and cloud workloads too?
Yes — SaaS and public-cloud workloads are included in the 3-2-1 design with their own tooling.
What happens during a ransomware incident?
The immutable copy cannot be altered; we restore from it to clean infrastructure following the DR runbook, with recovery times matching the agreed RTO.
Can you take over our existing backup software?
Yes. We audit it, fix retention and verification, and replace it only if it cannot meet the targets.

Send us your rack list or hypervisor inventory. The blueprint comes back in 48 hours.

Free audit call, written HLD, fixed-price proposal.