Snapshots (State Snapshots)

Snapshots are saved states of a system, dataset, or virtual environment at a specific point in time. They “freeze” the current state of an object so it can later be restored, rolled back, or used as a base for cloning and backup deployment.

In IT infrastructure, snapshots are widely used in virtualization, cloud platforms, data storage systems, and databases. Their main purpose is to provide a fast backup and recovery mechanism without requiring a full copy of all data.

How Snapshots Work

A snapshot captures the state of a system at the level of a file system, disk, or virtual machine. Instead of creating a full copy of the data, the system typically stores only changes made after the snapshot is created.

The process works as follows:

• A point-in-time state of the system is created
• Data is marked as snapshot-protected (immutable at that point)
• All new changes are stored separately (copy-on-write or redirect-on-write)
• During recovery, the system is restored to the saved state

For example, in a virtual machine, a snapshot can capture the state of a server before an update. If the update causes issues, the system can quickly roll back to the previous state.

Types of Snapshots

Depending on the infrastructure layer, snapshots can vary:

• Block-level (disk) snapshots
• File system-level snapshots
• Virtual machine snapshots
• Database snapshots

Each type is used for different purposes, from backup creation to testing and deployment validation.

Where Snapshots Are Used

Snapshots are widely used in many IT scenarios:

• Virtualization (VMware, KVM, Hyper-V)
• Cloud platforms (AWS, Azure, OpenStack)
• Storage systems (SAN, NAS)
• Databases and analytics systems
• DevOps and testing environments

For example, DevOps teams often create snapshots before deployments to enable fast rollback in case of failure.

Key Characteristics

Snapshots have several important properties:

• Fast creation without full data duplication
• Minimal performance impact during creation
• Support for snapshot chains (multiple restore points)
• Storage efficiency by saving only changes
• Dependence on underlying storage system

However, maintaining many snapshots can increase storage load and reduce performance over time.

Limitations and Risks

Despite their usefulness, snapshots have limitations:

• Not a full backup (they depend on the underlying storage)
• Can consume significant space over time
• Performance may degrade with many changes or snapshots
• Do not protect against physical storage failure

Therefore, snapshots are usually used alongside full backup systems.

FAQ

🠔 Back to glossary