What's the difference between RTO and RPO?

RTO (Recovery Time Objective) is the time it takes to restore systems after an outage. RPO (Recovery Point Objective) is the maximum acceptable data loss: how old the last backup may be. Both values should be defined in writing and tested regularly.

Are our backups safe in a ransomware attack?

Only if they're stored offline or air-gapped. Cloud backup (Backblaze B2) stays safe during a ransomware attack because attackers on the local network have no access to it. PBS also adds WORM-like data protection through deduplication trees.

How often are backups run?

That depends on your RPO. For most businesses, hourly incremental backups plus daily full backups are enough. Critical databases can be replicated continuously (WAL shipping for PostgreSQL).

Can we use Hetzner for GDPR-compliant backups?

Yes. Hetzner operates data centers in Germany and Finland, is ISO 27001 certified and signs a data processing agreement (DPA). That meets the GDPR requirements for processors.

Infrastructure from 1 week 1 point of contact

Cloud Migration & Backup — RTO under 45 minutes

Many companies don't have a real backup, just a single backup script that nobody tests regularly. We implement the 3-2-1 strategy and test it monthly.

Proxmox PBS · Restic · Hetzner · Backblaze B2

Get your backup strategy reviewed All services

RTO (Recovery Time Objective) typically < 45 minutes

RPO (Recovery Point Objective) typically < 1 hour

Automated monthly restore tests

Encryption of all backups (AES-256)

The 3-2-1 backup strategy

The rule of thumb for data security: 3 copies of your data, on 2 different types of media, with 1 copy at a different physical location. In practice, that means: a local backup on a NAS, a replicated backup on Hetzner StorageBox, and an encrypted offsite backup in Backblaze B2.

Copy 1: Proxmox Backup Server (PBS) on-site — fastest recovery
Copy 2: Restic on Hetzner Storage Box — GDPR-compliant EU cloud
Copy 3: Restic on Backblaze B2 — geo-redundant offsite backup
All backups AES-256 encrypted, keys stay with you

Hybrid cloud: on-premises + cloud

Not every workload belongs in the cloud, and not every workload should stay on-premises. We analyze your systems by latency requirements, data volume, compliance, and cost, and document a concrete hybrid architecture: critical databases on-premises, a scalable application layer in the cloud.

Disaster recovery plan

A DR plan is only as good as its last test. We don't just write the technical documentation — at handover, we run a full restore test, stopwatch in hand. After that, the test runs automatically every month and you get an email with the result.

FAQ

Ready for the next step?

30-minute initial call — assessment, concrete recommendations, fixed-price quote as a PDF.

Get your backup strategy reviewed