Cloud Backups and Snapshots: The Differences That Matter

A snapshot can be part of a backup strategy. Check what it captures, where it is stored and how it is restored. The words “snapshot” and “backup” alone do not tell you whether the copy survives losing the original account.

What a snapshot captures#

A snapshot records storage at a point in time. Implementation varies by platform. Amazon EBS, for example, describes its snapshots as incremental backups: changed blocks are saved, and each retained snapshot contains the information needed to restore a volume. Deleting an earlier snapshot does not automatically invalidate every later one.

Check how your provider stores and protects snapshots, whether cross-account or cross-region copies are available, and which credentials can delete them. Do not assume all snapshots remain on the original physical disk.

What must be recoverable#

A usable backup needs the data and configuration required to restore the application. For a database-backed website, that commonly includes files, uploads, configuration and a consistent database copy. A provider-native snapshot may be convenient for restoring on that platform, while an application export may be easier to move elsewhere. Test the restore process you intend to use.

Check application consistency#

A disk snapshot taken during writes may be only crash-consistent. Follow the database and provider documentation for coordinating writes or taking a database-aware backup. A successful snapshot job is not proof that your application will restore correctly.

Separate the failure domains#

Keep a recovery copy that a compromise of the production account cannot easily destroy. Review storage location, access permissions, retention and deletion protection. A copy in another region may help with a regional failure but still share administrative credentials with production.

Test both recovery paths#

Before an update, a snapshot may provide a convenient rollback. For losing access to the provider, test an independent recovery path. Record the time required to restore, the data you would lose since the last copy and any credentials or tools needed. Use those results to set your backup schedule.