VMware Datastore Full: Snapshot, Swap and Capacity Recovery Runbook

Identify the largest consumers

Check datastore usage and compare VM folders, snapshots, ISO files, logs and orphaned files. Do not delete files simply because they appear large.

Check snapshots first

Snapshots create delta disks and can grow rapidly with write-heavy workloads. Review the Snapshot Manager and investigate backup jobs that may have left snapshots behind.

Understand swap and metadata pressure

A critically full datastore can prevent required VM swap files or metadata updates. Leave operational headroom rather than trying to run a datastore at 100 percent capacity.

Check consolidation tasks

If consolidation is required, confirm that enough free space exists for the merge. A failed consolidation can require additional temporary capacity.

Remove only confirmed orphaned files

Before deleting anything from a datastore, map the file to a registered VM and verify that it is not part of an active disk or snapshot chain.

Add capacity or migrate workloads

When growth is structural, Storage vMotion or datastore expansion is safer than repeatedly deleting files. Plan capacity based on growth, snapshot behavior and recovery operations.

Validate the recovery

After freeing space, confirm VM power operations, snapshot tasks and application performance. Record the remaining free-space threshold for monitoring.

esxcli storage filesystem list
vim-cmd vmsvc/getallvms
du -h /vmfs/volumes/<datastore>/<VM>

Quick checklist

• Identify the largest consumers
• Check snapshots first
• Understand swap and metadata pressure
• Check consolidation tasks
• Remove only confirmed orphaned files
• Add capacity or migrate workloads
• Validate the recovery

Primary reference

This TechRunbook guide is independently written and cross-checked against Broadcom VMware documentation. View the reference →