🖼️Snapshotting

NEW

Captures a point-in-time copy of application or dataset state for recovery, migration, or analysis.

DESCRIPTION

Snapshotting records the exact state of data or systems at a specific moment. Storage systems often implement snapshots via copy-on-write to minimize overhead. Snapshots support backups, rollbacks, testing, and reproducible analytics. They differ from checkpoints by being user-initiated or operationally broader and not necessarily tied to streaming consistency protocols. Databases and filesystems expose snapshot features for point-in-time recovery. Retention policies and incremental chaining reduce storage costs while preserving restore points.

ALTERNATIVE DEFINITIONS

Wikipedia

In computer systems, a snapshot is the state of a system at a particular point in time.

General, system-agnostic definition focusing on point-in-time state.

Source

OpenZFS

A snapshot is a read-only copy of a dataset or volume at a given point in time.

Highlights read-only nature for storage systems like ZFS.

Source

AWS

An Amazon EBS snapshot is a point-in-time copy of an Amazon EBS volume.

Vendor-specific example illustrating point-in-time volume copies.

Source

RELATED TERMS

Savepoint Backup Point-in-Time Recovery Copy-on-Write Replication Versioning Filesystem Snapshot

COMPETING TERMS

Checkpointing Incremental Backup

KNOWLEDGE AREAS

Data Storage & Operations Data Management Data Architecture

TARGET AUDIENCE

Data Engineer DevOps Engineer Cloud Architect Data Architect

EXTERNAL SOURCES

• Wikipedia - Snapshot (computer science)
• OpenZFS - Storage snapshots explained in OpenZFS
• AWS - AWS EBS snapshots documentation
• PostgreSQL - Logical snapshot-like base backups

TOP QUESTIONS

How is Snapshotting different from Checkpointing?

Snapshots are general point-in-time copies for recovery or cloning; checkpoints are coordinated, periodic states for streaming fault tolerance.

Category: Concepts

What are common Snapshotting techniques in storage systems?

Copy-on-write and redirect-on-write are common, minimizing data duplication while preserving point-in-time views.

Category: Implementation

How often should I perform Snapshotting?

Align frequency with recovery point objectives and change rates. Use incremental snapshots to control cost.

Category: Best Practices

What is the risk of relying only on Snapshotting?

Snapshots on the same storage array may not protect against array failure or ransomware. Keep offsite backups.

Category: Risk

Can snapshots be writable?

Base snapshots are typically read-only, but clones can create writable copies derived from snapshots.

Category: Concepts

How does Snapshotting support analytics reproducibility?

Snapshots freeze datasets for consistent re-runs and audits, ensuring results are traceable to exact input states.

Category: Benefits

Do databases support Snapshotting?

Yes, via MVCC, backup snapshots, or storage-integrated snapshots to achieve point-in-time recovery.

Category: Tooling

How should I manage Snapshot retention?

Use policies for rotation, deduplication, and lifecycle rules to balance cost and recovery coverage.

Category: Management

What is a Savepoint in relation to Snapshotting?

A savepoint is a user-triggered snapshot-like state, often used for planned upgrades or migrations.

Category: Concepts