Snapshot
DevOps & AdminSnapshot is a point-in-time copy of a server, virtual machine, or storage volume that preserves data and often configuration so it can be restored later. In hosting and cloud environments, snapshots are typically created quickly by tracking changed blocks rather than duplicating everything immediately. They support rollback after updates, testing, and disaster recovery, but they are not always a complete backup strategy by themselves.
How It Works
A snapshot captures the state of a resource at a specific moment. Depending on the platform, it may include a disk volume only, or it may also include VM metadata such as attached disks, boot settings, and sometimes memory state. Most hosting platforms implement snapshots using copy-on-write or incremental techniques: the snapshot records a baseline, and subsequent writes are stored as changes while the snapshot continues to reference the original blocks. This makes creation fast and reduces initial storage overhead.
Restoring from a snapshot typically means reverting the volume or VM to that recorded state, or creating a new clone from the snapshot. Because snapshots depend on the underlying storage system, they can be sensitive to where they are stored (same node vs separate storage), retention limits, and performance impacts when many snapshots exist. Application consistency also matters: a snapshot taken while databases are writing may be crash-consistent rather than application-consistent unless the system quiesces I/O or uses filesystem and database hooks.
Why It Matters for Web Hosting
When comparing hosting plans, snapshot features affect how safely you can deploy changes and how quickly you can recover from mistakes. Look for whether snapshots are self-service, how many you can keep, where they are stored, and whether restores are instant or require support. Also verify what is included (full VM vs disk only) and whether snapshots complement, rather than replace, offsite backups and file-level restores.
Common Use Cases
- Rolling back after OS, control panel, or application updates
- Creating a safe checkpoint before configuration changes (firewall, PHP version, Nginx/Apache settings)
- Cloning a staging environment from production for testing
- Recovering quickly from accidental deletions or corrupted files
- Capturing a baseline image for repeatable server builds and migrations
Snapshot vs Backup
A snapshot is usually a fast, storage-level checkpoint designed for quick rollback on the same platform, while a backup is typically a separate copy intended for longer retention and recovery from broader failures. Snapshots may be stored on the same storage system and can be affected by the same outage, and they are often less flexible for granular restores. Backups are commonly exported or stored offsite and can support file-level recovery and compliance retention policies.