Snapshot
Also known as: Point-in-time snapshot
A snapshot is a saved point-in-time state of a system that lets you briefly roll back to exactly that moment.
A snapshot captures the state of a system or virtual machine at a specific point in time so you can roll back to exactly that state shortly afterward. It exists mainly to provide a safety net around risky changes - an update, a configuration change - before they are actually made.
In practice a snapshot is usually taken manually or automatically right before a planned change and kept around for a few hours or days afterward. Technically, a snapshot only records the differences from the original state, not a full, independent copy of the data.
The most expensive and most common mistake in practice is treating a snapshot as a backup. A snapshot typically sits on the very same storage device as the original data and depends on that device being available - if the storage fails or gets encrypted, the snapshot disappears right along with the original. Snapshots are also usually meant to be short-lived and get deleted automatically on a schedule, which makes them useless for restoring something from weeks or months ago.
What it means in practice
For a business this means: a snapshot before an update is a good idea, but it does not replace a real, off-site backup following the 3-2-1 rule. NDVDL keeps a strict distinction in every setup between snapshots for short-term safety and backups for actual data protection.
Is this handled properly at your site?
We look at how it actually stands with you — and say honestly whether anything needs doing.
Related terms
All termsA term from your quote missing here?
Send us the passage you do not follow. We will explain it — with no obligation to order anything.