AWS Learning Journey

Backups You've Never Restored Aren't Backups: EBS, EFS, FSx, and AWS Backup

Volume types, snapshots, shared file systems, backup plans, vaults, cross-Region and cross-account copies — and the restore test most teams never run.

7 min read · 1382 words
AWSBackupDisaster RecoveryCloud StorageDevOps
Backups You've Never Restored Aren't Backups: EBS, EFS, FSx, and AWS Backup cover image

AWS from Zero to Production — Phase 5, Part 2 of 5 · See the full series roadmap


A team I know had backups. Nightly snapshots, retained for 30 days. Green checkmarks everywhere.

Then a bad migration corrupted their data, and they tried to restore. The snapshots were from the wrong volume. The ones that were right took hours to come back. And nobody had written down how to do it.

Backups you’ve never restored aren’t backups. They’re hopes.

This article covers the storage that servers and containers mount — EBS, EFS, and FSx — and how to protect all of it with AWS Backup, including the part that actually matters: proving you can get your data back.

What you’ll walk away with


Three kinds of storage


Amazon Elastic Block Store (EBS)

An EBS volume is a network-attached disk for an EC2 instance.

Volume types

SSD-backed:

HDD-backed:

HDD volumes can’t be boot volumes.

Quick win: Still on gp2? Switching to gp3 is an online change, and usually lowers cost at the same or better baseline performance.


EBS snapshots

A snapshot is a point-in-time backup of a volume, stored durably by AWS.

aws ec2 create-snapshot \
  --volume-id vol-0abc123 \
  --description "before schema migration" \
  --tag-specifications 'ResourceType=snapshot,Tags=[{Key=purpose,Value=pre-migration}]'

Restoring isn’t instant

A volume restored from a snapshot loads data lazily from storage. The first read of each block is slower. For volumes that must be fast immediately, use Fast Snapshot Restore (at extra cost) or pre-warm the volume.

Snapshot lifecycle policies

Amazon Data Lifecycle Manager creates and deletes snapshots on a schedule, based on tags:

Target:     volumes tagged backup=daily
Schedule:   every 24 hours at 03:00 UTC
Retain:     14 snapshots
Copy:       to us-west-2, retain 7

For organization-wide policy across services, AWS Backup is usually the better choice.

Cost tip: Old snapshots are a classic silent cost. Use the Archive tier for snapshots you must keep long term but rarely restore.


Amazon Elastic File System (EFS)

EFS is a managed NFS file system for Linux:

Use it for shared content, home directories, and containers that need shared persistent storage.

Engineer’s note: EFS isn’t a database. Lots of small random writes from many clients can be slow, and file locking across clients needs care.


Amazon FSx

When you need a specific file system, FSx provides fully managed ones:


AWS Backup: one place for all backups

Every service has its own backup feature. AWS Backup centralizes them:

Backup plans

A backup plan defines when to back up, how long to keep backups, and where to copy them:

Plan: production-daily
  Rule: daily
    Schedule:     every day at 05:00 UTC
    Retention:    35 days
    Move to cold storage after: 30 days (supported resources)
    Copy to:      vault in us-west-2, retain 35 days
  Resource assignment: all resources tagged backup=production

Tag-based assignment is the key. New resources tagged backup=production are protected automatically — no one has to remember.

Backup vaults

A backup vault stores recovery points, encrypted with a KMS key.


Cross-Region and cross-account backups

A backup in the same account and Region as the original doesn’t protect you from:

So copy backups:

Production account (us-east-1)
   -> backup vault
       -> copy to: backup account vault (us-east-1), Vault Lock
       -> copy to: backup account vault (us-west-2), Vault Lock

Restore testing

Here’s the step that separates real backups from hopes.

AWS Backup restore testing runs scheduled, automatic restores:

  1. Pick recovery points by resource type and selection criteria.
  2. AWS Backup restores them on a schedule.
  3. Optionally, run your own validation — for example, a Lambda function that queries the restored database.
  4. The restored resources are deleted after the test.
  5. You get a report: did it work, and how long did it take?

That duration is your real recovery time. Compare it to your Recovery Time Objective (Phase 8).

Engineer’s note: Also practice restores by hand, at least occasionally, with a written runbook. The middle of an incident is a terrible time to learn the restore process.


Common mistakes


Key takeaways


Quick self-check

Test yourself before moving on:

  1. Which EBS volume type should most workloads start with?
  2. Why might a freshly restored volume be slow?
  3. How do you protect backups from someone with admin access to the production account?
  4. What does restore testing tell you that backup success doesn’t?

Answers

  1. gp3.
  2. Data is loaded lazily from the snapshot on first read.
  3. Copy them to a separate backup account, with Vault Lock.
  4. Whether the backup actually restores — and how long it takes.

What’s next

In Part 3, we move to relational databases: Amazon RDS and Aurora — subnet groups, parameter groups, Multi-AZ, read replicas, backups, RDS Proxy, and Aurora Serverless.

When did your team last test a restore? Be honest in the comments.


Share this article

LinkedIn post draft