2,187
edits
(→Can't Remove Snapshot: Added "No Snapshots Exist in Snaphot Manager (but still exist)") |
(→Troubleshooting: Added "Snapshot Still Active?" and renamed "Can't Remove Snapshot" to "Can't Commit Snapshot") |
||
Line 235: | Line 235: | ||
'''ESXs can't communicate''' | '''ESXs can't communicate''' | ||
* ESXs need to be able to communicate via VMotion network. DNS problems and FQDN inaccuracies can also cause problems | * ESXs need to be able to communicate via VMotion network. DNS problems and [[Acronyms#F|FQDN]] inaccuracies can also cause problems | ||
'''VM is connect to CD-ROM/ISO''' | '''VM is connect to CD-ROM/ISO''' | ||
Line 250: | Line 250: | ||
** [http://kb.vmware.com/kb/1009073 VMware KB1009073 - Unable to take a quiesced VMware snapshot of a virtual machine] | ** [http://kb.vmware.com/kb/1009073 VMware KB1009073 - Unable to take a quiesced VMware snapshot of a virtual machine] | ||
=== Can't | === Can't Commit Snapshot === | ||
'''Operation timed-out''' | '''Operation timed-out''' | ||
* Not unusual for large redo files, the process continues and its just vCentre reporting it as a time-out | * Not unusual for large (>10GB) redo files, the process continues and its just vCentre reporting it as a time-out | ||
** Check the VM's files for any activity, | ** Check the VM's files for any activity (changes in disk sizes), very large redo files (eg 100 GB) could take 4hrs! | ||
** Also see [[Virtual_Machines#Snapshot Still Active?|Snapshot Still Active?]] | |||
'''No Snapshots Exist in Snaphot Manager (but still exist)''' | '''No Snapshots Exist in Snaphot Manager (but still exist)''' | ||
Line 259: | Line 260: | ||
*# Start a new snapshot | *# Start a new snapshot | ||
*# In snapshot manager use ''Delete All'' (not Delete!) | *# In snapshot manager use ''Delete All'' (not Delete!) | ||
=== Snapshot Still Active? === | |||
# Check ''Snapshot Manager'', if there's snapshots listed then there are still active snapshots | |||
# Open up ''Datastore Browser'' to the VM's folder, and see if any snapshot files exist, if not then there are no active snapshots | |||
# Check the VM's VMX file, the VMDK filename(s) will be either a snapshot or normal flat base disk file | |||
#* EG <code> scsi0:0.fileName = "MyVM-000001.vmdk" </code> ←←←←← Snapshot file ''(snapshot running)'' | |||
#* EG <code> scsi0:0.fileName = "MyVM-000001-delta.vmdk" </code> ← Snapshot file ''(snapshot running)'' | |||
#* EG <code> scsi0:0.fileName = "MyVM.vmdk" </code> ←←←←←←←←← Base disk file ''(no snapshot running)'' | |||
#* EG <code> scsi0:0.fileName = "MyVM-flat.vmdk" </code> ←←←←←← Base disk file ''(no snapshot running)'' | |||
# If there's no snapshots running, but snapshot files exist then the files can be deleted (if you're sure!) | |||
=== Can't Customise === | === Can't Customise === |