Too many snapshots - Virtual machine server (VMS) not enough free space
Environment
Content
Because the workstation that is for backing up VMs had hardware question, it affected the VMS had too many snapshots, going not enough free space.
How did identify snapshots that were locked
At the beginning, following VMware KB 1002310 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002310) that didn't work.
To unlock them, restarted management agent services and host agent service.
How did restart its management agent services and host agent service
SSH to the VMS, then restart services
Reference
Update
- VMware ESX 4.x
- VMware vCenter 4.x
Content
Because the workstation that is for backing up VMs had hardware question, it affected the VMS had too many snapshots, going not enough free space.
How did identify snapshots that were locked
At the beginning, following VMware KB 1002310 (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002310) that didn't work.
1 - Take a snapshotvCenter showed that error message "Remove all snapshots. Unable to access file <unspecified filename> since it is locked." Those snapshots were locked.
2 - Delete all snapshots
To unlock them, restarted management agent services and host agent service.
How did restart its management agent services and host agent service
SSH to the VMS, then restart services
#service mgmt-vmware restartThen, consolidated the snapshots for clearing datastore space.
Stopping VMware ESX Server Management services:
VMware ESX Server Host Agent Watchdog [ OK ]
VMware ESX Server Host Agent [ OK ]
Starting VMware ESX Server Management services:
VMware ESX Server Host Agent (background) [ OK ]
Availability report startup (background) [ OK ]
#service vmware-vpxa restart
Stopping vmware-vpxa: [ OK ]
Starting vmware-vpxa: [ OK ]
Reference
- VMware KB 1002310 - Committing snapshots when there are no snapshot entries in the Snapshot Manager (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002310)
- VMware KB 1003490 - Restarting the Management agents on an ESXi or ESX host (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003490)
- Veeam KB 1213 - Unable to access file [unspecified filename] since it is locked (http://www.veeam.com/kb1213)
Update