12 Cloud Backup Practices DevOps Can't Ignore

12 cloud backup practices: RTO and RPO tiers, automated plans, cross-account copies, Vault Lock and S3 Object Lock, Velero and scheduled restore tests.

Dec 30, 2025 - 12:28
Nov 12, 2026 - 05:57
 0  50
12 Cloud Backup Practices DevOps Can't Ignore

Cloud backups protect you only if they are automated, stored away from the systems they protect, locked against deletion, and restored regularly to prove they work. The 12 practices below cover what to back up, how often, where to keep copies, how to stop ransomware or a mistaken admin from deleting them, and how to test recovery against your RTO and RPO targets.

Examples use AWS because its backup features are clearly documented, and every command and default here was checked against AWS and Velero documentation in November 2026. For Kubernetes specifics, see our Kubernetes backup strategies; this post covers the cloud account level. It belongs to our cloud tools cluster.

Key takeaways

  • Set RTO and RPO per workload first; they decide backup frequency, method and cost.
  • The AWS Well-Architected reliability guidance groups backup into four practices: identify and back up data, secure and encrypt backups, automate backups, and periodically test recovery.
  • AWS Backup Vault Lock in compliance mode becomes immutable once its grace time (at least 3 days) ends. Not even AWS or the root user can delete recovery points before their retention ends.
  • S3 Object Lock adds write-once-read-many protection to objects and only works on buckets with versioning enabled.
  • Keep at least one copy in a separate account and Region from production.
  • A backup you have never restored is unproven. Schedule restore tests and measure the time they take.

The 12 practices at a glance

#PracticeRisk it reduces
1Inventory and classify dataCritical data with no backup at all
2Set RTO and RPO per workloadBackups that cannot meet business needs
3Automate backups with policiesMissed or forgotten manual backups
4Copy to another account and RegionOne account or Region failure taking all copies
5Encrypt backups and control keysExposure of backup data
6Make backups immutableRansomware or insiders deleting backups
7Separate backup permissionsOne compromised role destroying everything
8Use application-consistent and point-in-time backupsCorrupt or unusable database restores
9Back up Kubernetes objects and volumesLost cluster state and configuration
10Keep infrastructure reproducible as codeLong rebuilds after a disaster
11Test restores on a scheduleDiscovering broken backups during an incident
12Monitor jobs, retention and costSilent failures and runaway storage bills

1. Inventory and classify data

The first Well-Architected backup practice (REL09-BP01) is to identify all data that needs to be backed up, or decide how to reproduce it from sources. List every data store: databases, block volumes, file systems, object buckets, message queues with durable state, secrets and configuration. For each one, note its owner, its sensitivity and whether it can be rebuilt from another source. A cache or a build artifact store may not need backup; a customer database always does.

Tag resources with their backup tier so automation can select them. A tag such as backup-tier=gold lets a backup policy pick up new resources automatically, which closes the gap where a new database runs for weeks without protection.

2. Set RTO and RPO per workload

Recovery time objective (RTO) is how long a service can be down. Recovery point objective (RPO) is how much data, measured in time, you can afford to lose. A payments database might need an RPO of minutes and an RTO under an hour; an internal reporting store might accept a day for both.

TierExample RPOExample RTOTypical method
GoldMinutesUnder 1 hourContinuous backup or replication with point-in-time recovery
SilverHoursSeveral hoursFrequent scheduled snapshots
Bronze1 day1 day or moreDaily backups

The numbers above are examples; agree real ones with the business owner for each service. Without them, nobody can say whether a backup plan is good enough.

3. Automate backups with policies

REL09-BP03 is to perform data backup automatically. Use a central service such as AWS Backup, with backup plans that set frequency, retention, lifecycle and copy rules, and assign resources by tag. Define those plans in infrastructure as code so they are reviewed and reproducible. Avoid scripts on individual servers that someone wrote years ago and nobody monitors.

4. Copy to another account and Region

A backup stored in the same account and Region as production shares its failure modes. A compromised administrator account, a mistaken bulk delete or a Regional event can affect both. Copy important backups to a separate account dedicated to backups, and to a second Region for workloads that must survive a Regional outage. AWS Backup copy rules can do both as part of a plan.

The 3-2-1 backup strategy expresses the same idea: three copies of data, on two kinds of storage, with one copy away from the main site. In the cloud, "away" usually means another account and Region.

5. Encrypt backups and control keys

REL09-BP02 is to secure and encrypt backups. Encrypt recovery points with keys you control, restrict who can use those keys, and log key usage. Be careful when copying across accounts: the destination must be able to use a key for the copy, and losing access to a key means losing access to the backups it protects. Document key ownership as part of your disaster recovery plan.

6. Make backups immutable

Ransomware operators and malicious insiders often try to delete backups before they encrypt or destroy production data. Immutable storage stops that. AWS documents two main controls.

AWS Backup Vault Lock adds write-once-read-many protection to a backup vault. In governance mode, users with sufficient IAM permissions can remove the lock. In compliance mode, you set a grace time of at least 3 days, during which the lock can still be changed or removed. After the grace time ends, the vault and lock are immutable: no user, including the root user, and not AWS itself can change the lock or delete recovery points before their retention ends.

aws backup put-backup-vault-lock-configuration \
    --backup-vault-name prod-backups-locked \
    --changeable-for-days 3 \
    --min-retention-days 7 \
    --max-retention-days 35

Including --changeable-for-days creates a compliance-mode lock; leaving it out creates governance mode. AWS warns that backups in a locked vault cannot be deleted until their lifecycle ends, so a mistake in retention settings becomes a long-term storage cost. Test in governance mode first.

S3 Object Lock protects individual object versions with retention periods or legal holds, again in governance or compliance mode. It works only on buckets with S3 Versioning enabled. In compliance mode, no user, including the root user, can overwrite or delete a protected version until its retention period ends. See how immutable backups support ransomware-resistant architectures for design patterns.

7. Separate backup permissions

The role that runs production should not be able to delete backups. Use a dedicated backup account with its own administrators, restrict delete actions with vault access policies and organization-level policies, and require extra approval for any change to retention. AWS also notes that some actions outside AWS Backup still apply to EBS snapshot recovery points, such as sharing them or changing their storage tier, and suggests denying those EC2 actions with IAM policies or service control policies while exempting the backup roles that need them.

8. Use application-consistent and point-in-time backups

A snapshot of a disk under a busy database may capture a half-written state. For databases, use engine-aware backups: managed database snapshots and continuous backups that support point-in-time recovery, or native database tools that coordinate with the engine. Point-in-time recovery lets you restore to just before a bad migration or accidental delete, which a daily snapshot cannot do. Our post on how RDS snapshots and automated backups work explains the RDS options.

9. Back up Kubernetes objects and volumes

Kubernetes clusters hold state in two places: the API objects (Deployments, ConfigMaps, Secrets, custom resources) and persistent volumes. Velero backs up and restores both, and can also migrate resources to another cluster. Its disaster recovery guide shows a daily schedule and a restore:

velero schedule create daily-cluster --schedule "0 7 * * *"
# during recovery, set the backup storage location to read-only first, then:
velero restore create --from-backup daily-cluster-<TIMESTAMP>

Velero's guide recommends switching the backup storage location to read-only during a restore so backups are not created or deleted mid-recovery, and back to read-write afterwards. Compare tools in our list of Kubernetes backup tools for enterprise data.

10. Keep infrastructure reproducible as code

Data is only half of recovery. You also need networks, IAM roles, clusters, load balancers and DNS. If these are defined in Terraform, CloudFormation or a similar tool, with state stored safely and versioned, you can rebuild the environment in a new account or Region and then restore data into it. If they were built by hand in a console, rebuilding is guesswork. Back up the IaC state store itself, and keep the code in a version control system that does not depend on the environment you are recovering.

11. Test restores on a schedule

REL09-BP04 is to periodically recover data to verify backup integrity and the recovery process. Automate it where you can: restore the latest backup of a database into an isolated environment every week, run a validation query (row counts, a checksum, a known recent record), record how long it took and tear it down. Compare the measured time with the RTO. Do a fuller disaster recovery exercise, rebuilding a whole service in another Region, at least a few times a year.

Write down what you learned each time. Restore tests often find missing permissions, expired keys or undocumented manual steps, and it is far better to find them on a Tuesday afternoon than during an outage.

12. Monitor jobs, retention and cost

Alert on failed or missed backup jobs, copy jobs and restore tests, and send those alerts to the team that owns the service, not to an unread mailbox. Use compliance reporting, such as AWS Backup Audit Manager controls, to check that resources tagged for backup are actually in a plan and that locked vaults are in use where required. Review storage growth and lifecycle rules regularly; move older recovery points to cold storage where the service supports it, and make sure retention matches your actual legal and business requirements rather than "keep forever".

Quick checklist

  • Every data store listed, tagged and assigned a tier.
  • RTO and RPO agreed per workload.
  • Backup plans defined as code and applied by tag.
  • Copies in a separate backup account and a second Region.
  • Vault Lock or Object Lock on critical backups, tested in governance mode first.
  • Production roles cannot delete backups.
  • Databases use point-in-time capable backups.
  • Velero or an equivalent covers Kubernetes clusters.
  • Restore tests run on a schedule with recorded times.
  • Alerts for failed jobs reach the owning team.

To build and test these setups on AWS, see our AWS Solutions Architect Associate training, available in Kharadi, Pune and live online across India. Our Kubernetes disaster recovery tools guide covers cluster-level recovery further.

Official references

FAQs

What is the difference between RTO and RPO?

RTO is how long a service can be unavailable before recovery must be complete. RPO is how much data loss, measured in time, is acceptable. Both are set per workload and drive backup frequency and method.

What is AWS Backup Vault Lock compliance mode?

A vault lock that becomes immutable after a grace time of at least 3 days. After that, no user, including the root user, and not AWS can remove the lock or delete recovery points before their retention period ends.

Does S3 Object Lock need versioning?

Yes. Object Lock works only in buckets with S3 Versioning enabled, and it protects specific object versions with retention periods, legal holds or both.

How often should backups be restore-tested?

Automate a small restore test weekly for critical databases and run a fuller disaster recovery exercise a few times a year. Record how long each restore takes and compare it with the RTO.

Are snapshots enough to back up a database?

Not always. A disk snapshot of a busy database may not be consistent. Use engine-aware backups or managed database backups with point-in-time recovery, and test that restores work.

Why keep backups in a separate account?

If production credentials are compromised or misused, an attacker or a mistake can delete backups in the same account. A separate backup account with its own administrators keeps at least one copy out of reach.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.