1/4
Case Study: Snapshot Wasn't the Backup — A Costly Lesson for Every Virtualization Administrator
  

rizzuan Lv3  Posted 2026-Jul-16 10:20

One of the most common misconceptions in virtual environments is treating snapshots as backups.

Recently, I came across a discussion where an administrator believed that keeping multiple VM snapshots was sufficient for data protection. Everything seemed fine—until storage usage increased dramatically and VM performance began to degrade.

Fortunately, no data was lost, but it served as an important reminder that snapshots and backups serve very different purposes.

Initial Symptoms
Storage usage increased much faster than expected.
Several virtual machines became noticeably slower.
Snapshot chains had grown over several weeks.
Backup jobs were still completing successfully.

At first, storage capacity appeared to be the only issue. However, a deeper investigation revealed something more important.

Investigation

The following checks were performed:

Reviewed datastore utilization.
Checked the number and age of VM snapshots.
Verified backup job status.
Examined storage latency during peak hours.

It was discovered that several virtual machines still had snapshots that had never been consolidated after maintenance and testing activities.

Root Cause

The root cause was long-lived snapshots.

Snapshots are designed as temporary recovery points, not long-term backup solutions.

As snapshots continue to grow, they consume additional storage and can negatively impact VM performance.

Resolution

The following actions were taken:

✅ Consolidated and removed unnecessary snapshots.

✅ Verified successful VM backups.

✅ Implemented a policy to review snapshots regularly.

✅ Added snapshot age monitoring to routine health checks.

✅ Reminded administrators to remove snapshots immediately after maintenance or upgrades.

Lessons Learned

Snapshots are incredibly useful during:

System upgrades
Software patching
Configuration changes
Short-term rollback scenarios

However, they should never replace a proper backup strategy.

A reliable backup protects your data.

A snapshot only provides a temporary rollback point.

Understanding the difference can prevent storage problems and improve the overall stability of your virtualization environment.

Discussion

How does your organization manage VM snapshots?

Do you automatically remove old snapshots?
Do you have a maximum snapshot retention policy?
Have you ever experienced storage issues caused by forgotten snapshots?

I'd love to hear your best practices.

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go

Syed Majid Lv2  Posted 2026-Oct-21 12:21
  
You're 100% right - this is still the #1 mistake I see in almost every health check.Everyone learns it the hard way: A snapshot is not a backup, it's a change log.Backup = Independent, crash-consistent copy of your data on different storage.
Snapshot = Delta file that says "keep the old blocks, write new changes here". If the base disk is lost, all snapshots are useless.That case you described is classic. I've seen the exact same chain:Admin takes snapshot before patching -> Patch works -> Forgets to delete -> Next week another snapshot -> 3 weeks later datastore at 90% -> VM is running on 4 delta disks -> Read performance drops 30-50% -> Backup software using CBT breaks because chain is too long.
John R Lv1  Posted 2026-Oct-21 10:56
  
Last edited by John R 2026-Oct-21 11:25.

Last edited by John R 2026-Oct-21 11:09.

There are 2 types of snapshots for sangfor HCI.
1. virtual storage base (2 nodes cluster only allow to perform this type of snapshots. Ofcourse 3 nodes and above cluster able to perform this as well.
2. Storage base (Able to execute only 3 nodes cluster & above)
** at least 1.5 times the total differential data of all snapshots to be merged**

Drawback for virtual storage base snapshots is after you remove the snapshots the previous concur disk space won't be removed. It will only be removed if you perform the clone for that particular machine.
How to allow storage base snapshot for 2 node cluster?
you need to buy or deploy witness node & newer firmware.
Two-host + one witness node scenario, HCI 6.9.0 and later (applicable range: HCI 6.9.0–6.11.3)
Prosi Lv4  Posted 2026-Jul-16 23:17
  
Hi,
VM snapshots are an excellent tool for short-term protection before upgrades, patching, or configuration changes.
I've seen environments where snapshots are left for weeks or even months, simply forgotten. Over time, these snapshots become larger, consuming valuable storage capacity and increasing disk I/O overhead. Ultimately, this leads to VM performance degradation, storage warnings, and in some cases, backup job failures.
However, snapshots are not a substitute for a proper backup strategy.
Muhammad Shiraz Lv3  Posted 2026-Jul-16 15:10
  
Yes.. we usually keep snapshots only for short term use. After maintenance or testing, we remove them quickly. We did face storage issues once because of old snapshots, so now we keep a closer check.
ND Lv4  Posted 2026-Jul-16 14:13
  
True, each snapshot creates a delta disk. a small snapshot taken during a patch window can grow to the size of the base disk if left alone for weeks.

Keep using snapshots for their real purpose — short-term rollback during patching/upgrades — but pair that with the policy you already implemented: age monitoring and mandatory removal after the maintenance window closes.
Sheikh_Shani Lv3  Posted 2026-Jul-16 13:53
  
Thanks for Sharing
Humayun Ahmed Lv4  Posted 2026-Jul-16 12:15
  
Thanks to share!