-
What is VMware Snapshot?
-
How VMware Snapshots Work
-
How to Create a Snapshot in vCenter or ESXi
-
How to Revert, Delete and Consolidate Snapshots
-
VMware Snapshot Best Practices
-
How to Monitor Snapshots with Alarms and PowerCLI
-
Snapshot vs. Backup
-
Something you need to know about VMware snapshot
-
Make real backup with Vinchin Backup & Recovery
-
VMware Snapshot FAQs
-
Sum Up
Before installing a patch or upgrading an application, most VMware administrators take a snapshot so they can roll back if something breaks. Snapshots are fast and convenient, but they’re also one of the most common causes of slow VMs and full datastores in vSphere environments.
Quick answer: A VMware snapshot preserves a VM’s disk state (and optionally its memory) at a point in time, so you can revert to it later. Best practices: use snapshots only for short-term changes such as patching, keep them no longer than 24–72 hours, keep no more than 2–3 snapshots per VM, delete them as soon as the change is verified, monitor snapshot age and size with alarms or PowerCLI, and never use snapshots instead of backups.
What is VMware Snapshot?
A VMware snapshot captures the state of a virtual machine at a specific moment: its virtual disks, its settings, and optionally its memory and power state. Reverting to the snapshot returns the VM to exactly that point.
Taking a snapshot usually takes only seconds, which makes it ideal for quick rollback before risky changes. But a snapshot isn’t a copy of the VM; it depends on the original disks, which is why snapshots can’t replace backups.
Types of VMware Snapshots
| Type | Option in the Take Snapshot dialog | What it captures | Typical use |
|---|---|---|---|
| Disk-only (crash-consistent) | Neither option selected | Disk state, as if the power was cut | Quick rollback where the VM can be restarted |
| Memory snapshot | Include virtual machine’s memory | Disks plus memory and power state; revert returns to a running VM | Before patches and upgrades on a running VM |
| Quiesced snapshot | Quiesce guest file system (needs VMware Tools) | Disks after VMware Tools flushes file system writes (and VSS writers on Windows) | Backups and application-consistent copies |
Memory and quiesce can’t be selected together. Memory snapshots take longer and briefly pause the VM while memory is written to disk.
How VMware Snapshots Work
When you take a snapshot, ESXi stops writing to the VM’s original disk and creates a delta disk (for example vmname-000001.vmdk). All new writes go to the delta disk; the original disk becomes read-only. Each further snapshot adds another delta disk to the chain.
Other files include:
.vmsd: the snapshot list and relationships.vmsn: VM configuration and memory state for each snapshot (if memory is included)
Because every read may have to check the chain of delta disks, and delta disks keep growing as data changes, long or large snapshot chains slow the VM down and consume datastore space.
How to Create a Snapshot in vCenter or ESXi
In the vSphere Client (vCenter):
1. Right-click the VM and select Snapshots > Take Snapshot.
2. Enter a name and a description, for example the change you’re about to make and your name.
3. Select Include virtual machine’s memory or Quiesce guest file system, or neither (see the table above).
4. Click Create.
In the ESXi Host Client: right-click the VM, select Snapshots > Take snapshot, and choose the same options.
With PowerCLI:
New-Snapshot -VM "VM01" -Name "Before-Patch-2026-11" -Description "KB updates, by admin" -Memory
How to Revert, Delete and Consolidate Snapshots
Open the snapshot manager: right-click the VM and select Snapshots > Manage Snapshots.
Revert: select a snapshot and click Revert to return the VM to that state. Changes made after the snapshot are lost.
Edit: change a snapshot’s name or description.
Delete: removes the snapshot from the list and merges its changes into the parent disk, so the VM keeps its current state. It does not undo changes.
Delete All: merges all snapshots into the base disk.
Deleting a large snapshot can take a long time and adds I/O load, so do it outside peak hours.
Consolidate: if a snapshot deletion fails, delta disks can remain even though the snapshot manager shows nothing, and vCenter shows “Virtual machine disks consolidation is needed”. Right-click the VM and select Snapshots > Consolidate to merge them.
With PowerCLI:
# Delete all snapshots older than 3 days
Get-VM | Get-Snapshot | Where-Object { $_.Created -lt (Get-Date).AddDays(-3) } | Remove-Snapshot -Confirm:$falseVMware Snapshot Best Practices
1. Use snapshots for short-term rollback only, such as patching, upgrades and configuration changes.
2. Keep them for no more than 24–72 hours. VMware recommends not keeping a single snapshot for more than 72 hours.
3. Keep chains short. vSphere supports up to 32 snapshots per VM, but 2–3 is a practical maximum for performance.
4. Delete the snapshot as soon as the change is verified, and check that the delete actually completed.
5. Name and describe every snapshot with the reason, date and owner, so others know whether it can be deleted.
6. Avoid snapshots on busy VMs during peak hours. Creating and deleting snapshots on VMs with heavy I/O can stun the VM or fail to quiesce.
7. Leave space on the datastore. Delta disks can grow up to the size of the original disk.
8. Be careful with memory snapshots on VMs with large memory; they take longer and pause the VM.
9. Don’t resize disks with snapshots present; delete them first.
10. Monitor snapshot age and size with alarms and regular reports (below).
11. Never treat a snapshot as a backup.
How to Monitor Snapshots with Alarms and PowerCLI
Create a snapshot size alarm in vCenter:
1. Select the vCenter, datacenter or cluster, go to Configure > Alarm Definitions, and click Add.
2. Enter a name such as “VM snapshot too large”, choose Virtual Machines as the target type, and click Next.
3. Under Alarm Rule, select the trigger VM Snapshot Size (GB), set the condition (for example above 50 GB), and choose the severity and any email or SNMP notification.
4. Add a reset rule if needed, review, and click Create.
vCenter also includes a built-in alarm for Virtual machine consolidation needed status; make sure it’s enabled.
Report snapshot age with PowerCLI (vCenter alarms don’t track age directly):
Get-VM | Get-Snapshot |
Select-Object VM, Name, Created, @{N="SizeGB";E={[math]::Round($_.SizeGB,1)}} |
Sort-Object Created | Format-Table -AutoSizeSchedule this weekly and send the output to the team.
Snapshot vs. Backup
| VMware snapshot | VM backup | |
|---|---|---|
| Stored where | On the same datastore, depending on the original disks | On separate storage, independent of the VM |
| Survives datastore loss or corruption | No | Yes |
| Retention | Hours to days | Days to years |
| Performance impact over time | Grows with size and age | None on the VM after the job |
| Use | Quick rollback during changes | Recovery from failures, deletion, ransomware and disasters |
For more detail, see VM snapshot vs. backup.
Something you need to know about VMware snapshot
Snapshot is easy to create, but you still need to know more about it to use it correctly.
How long does it take to create a snapshot in VMware? This depends on how much data there is. Usually, it will take just a couple of seconds to complete the process.
Does VMware snapshot affect performance? Yes, it will cause some performance issues but its advantages are over its disadvantages. Remember to delete old snapshots.
How long should you keep VMware snapshots? It is suggested by VMware that don't use a single snapshot for more than 72 hours because the size of snapshot file will grow as time goes by and take more and more storage on datastore. That's also why you should manually delete snapshot. If VM snapshot is not properly deleted, you might see the error message that virtual machine disk consolidation is needed in vSphere.
How many snapshots you can create on a VM? The maximum number is 32 but it is suggested to use only 2 to 3 snapshot to cause less performance influence on VM.
Try creating VM snapshot when it is not busy. If there is a large amount of ongoing I/O to virtual machine, you might fail to create snapshot.
Last but not least, do not use snapshot as backup. Snapshot is convenient for short-term data protection but IT environment is still vulnerable without backup system. The snapshot file is only a change log of the original virtual disk. If severe disaster happens to the VM, snapshots can't recover VM. Making backup takes more time, but it is worth for data security.
Make real backup with Vinchin Backup & Recovery
Backup is essential for data security. Vinchin Backup & Recovery can bring you professional protection for your vSphere environment. Vinchin is the official partner of VMware and has helped thousands of companies build backup systems.
Vinchin Backup & Recovery deployment is easy and fast. Just install the package in virtual environment, and then you can add the hosts and backup any VMs via a user-friendly web console agentlessly. There are a lot of useful features like forever incremental backup, backup data verification, Lan-free backup, data compression, etc.
In its intuitive web console, it is easy to backup the virtual machine in 4 steps.
Step 1. Select the VMware VM
Step 2. Select the backup storage
Step 3. Select the backup strategies
Step 4. Submit the job
You can have a 60-day full-featured free trial to deploy this excellent backup software in your virtual environment. Just click the button to download it. There are many other brilliant features for you.
VMware Snapshot FAQs
Q1: How long should I keep a VMware snapshot?
As short as possible, ideally less than 24 hours and no more than 72 hours. Delete it as soon as you’ve confirmed the change worked.
Q2: Does deleting a snapshot delete my data?
No. Deleting a snapshot merges its changes into the parent disk, so the VM keeps its current state. Only Revert discards changes.
Q3: Can I migrate a VM that has snapshots?
Yes. vMotion and Storage vMotion both support VMs with snapshots in current vSphere versions. Still, it’s good practice to delete unneeded snapshots first, because they make migration slower.
Q4: Why does my VM still show “consolidation needed” after deleting snapshots?
A deletion didn’t finish, often because a backup job still had the disks locked. Make sure no backup is running, then select Snapshots > Consolidate.
Q5: Do snapshots slow down a VM?
Yes. Every snapshot adds a delta disk that reads may have to go through, and large or old snapshots also slow down deletion. Keep chains short and delete snapshots promptly.
Q6: How do I find all VMs with snapshots?
Run Get-VM | Get-Snapshot in PowerCLI, or in the vSphere Client add a Snapshots filter in the VMs list view.
Sum Up
VMware snapshots are the fastest way to roll back a change, as long as they stay short-lived. Create them with clear names, keep only a few for no more than a few days, delete or consolidate them promptly, and monitor size and age with alarms and PowerCLI. For real protection, combine snapshots with regular backups stored outside the datastore.
Try Vinchin Backup & Recovery free for 60 days.
Share on: