Backup & restore strategy template

A 3-2-1 backup plan for cloud data: what gets backed up, how often, where the copies live, and a monthly restore drill.

Use this templateFree, opens in your browser. No sign-up.

Backup & restore strategy template
Sources
Backup jobs
Copies (3-2-1 rule)
Monthly restore drill
RDS Postgres (orders)
S3: user uploads
EBS volumes (build servers)
Kubernetes manifests + volumes
Continuous PITR (WAL archiving, 5 min)
AWS Backup plan: nightly 02:00 UTC
Velero: daily cluster backup
Copy 1: backup vault, same region (35 days)
Copy 2: vault in us-west-2 (90 days)
Copy 3: immutable vault, separate account, object lock 1 year
Data
Method
Frequency
Retention
RPO
RTO
Orders DB
PITR + snapshot
Continuous + nightly
35 days / 1 year
5 min
1 hour
User uploads
Versioning + replication
Continuous
90 days
15 min
4 hours
Build servers
EBS snapshot
Nightly
14 days
24 hours
8 hours
Cluster state
Velero
Daily
30 days
24 hours
2 hours
Pick a random backup
Restore into an isolated account
Verify row counts + checksums
Time it against the RTO
Log the result, fix gaps
Backup & restore strategy
versioning + replication
cross-region copy
cross-account copy
The backup & restore strategy template as it opens in Kelvo: 15 boxes, 1 table and 14 links, in 4 sections.

What's on the board

Sources
RDS Postgres (orders) · S3: user uploads · EBS volumes (build servers) · Kubernetes manifests + volumes
Backup jobs
Continuous PITR (WAL archiving, 5 min) · AWS Backup plan: nightly 02:00 UTC · Velero: daily cluster backup
Copies (3-2-1 rule)
Copy 1: backup vault, same region (35 days) · Copy 2: vault in us-west-2 (90 days) · Copy 3: immutable vault, separate account, object lock 1 year
Monthly restore drill
Pick a random backup · Restore into an isolated account · Verify row counts + checksums · Time it against the RTO · Log the result, fix gaps

Table columns: Data, Method, Frequency, Retention, RPO, RTO.

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Link by dragging. Hover a box and drag one of its dots onto another box. The whole box is the target, and links stay attached when you move things.
  4. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  5. Group by environment or region. Draw a frame (F) around a group of services; moving the frame moves everything inside it.

Good for

  • backup
  • disaster recovery
  • aws
  • rto rpo
  • cloud
  • Design reviews and architecture decision meetings
  • Runbooks and onboarding for on-call engineers
  • Planning a migration or a cost-cutting pass

Related templates

  • Multi-region disaster recovery template previewMulti-region disaster recovery

    Warm-standby DR across two regions with DNS failover and replicated data, RTO/RPO options and a failover runbook.

  • AWS three-tier web app template previewAWS three-tier web app

    A highly available web app on AWS: DNS and CDN, load balancer, auto-scaled app servers and Multi-AZ database in a VPC.

  • Serverless event-driven app template previewServerless event-driven app

    An AWS serverless order system: API Gateway and Lambda, DynamoDB streams into EventBridge, SQS with a dead-letter queue.

  • Cloud cost optimization board template previewCloud cost optimization board

    FinOps actions sorted from quick wins to governance: clean up, right-size, commit, re-architect and keep costs visible.

  • AWS VPC network layout template previewAWS VPC network layout

    A two-AZ AWS VPC with public, private and data subnets, internet and NAT gateways, route tables and security groups.

  • Kubernetes cluster overview template previewKubernetes cluster overview

    Ingress, services, deployments and pods in a namespace, with config, storage, control plane and add-ons around them.

All cloud and devops diagram templates · All templates

Use the backup & restore strategy template