adrianych's Accepted Solutions

You will need to use viClient to enable SSH via configuration > Security profile. SSH & ESXi shell are off by default, you will need to start these Daemon services. At putty, use the root cre... See more...
You will need to use viClient to enable SSH via configuration > Security profile. SSH & ESXi shell are off by default, you will need to start these Daemon services. At putty, use the root credentials or admin
So what's the difference between "Consolidate" and "Delete All"?? I think you may have misconception of the snapshot.... I would use Windows update + service pack installation as an example... See more...
So what's the difference between "Consolidate" and "Delete All"?? I think you may have misconception of the snapshot.... I would use Windows update + service pack installation as an example. VM with MS svr 2003 running....you may want to install SP1, then test, then install the Windows updates, then test. - snapshot 1 (sn1) : Win2003 without updates & SP - Installation of  Win2003 SP1 (with reboot etc) - snapshot 2 (sn2) : Win 2003 SP1 - Install Windows updates on Win2003 SP1 - snapshot 3 (sn3) : Win 2003 SP1 with updates - svr testing for 5 days (eg. install Acrobat reader, Microsoft office) So u shd have 3 snapshots.....which all will "grow" as you test ur svr. But ur VM will have 4 main file types (with regards to this context) 1. Base VM files (vmdk, vmx, VM's memory, swp files etc) 2. VM's snapshot file 3. VM's snapshot swp files (swap may not be correct name....but I cannot think of the proper name) In logical terms.... - "sn1" is the base snapshot - "sn2" is "sn1" + "data1" - "sn3" is "sn1" + "data1" + data2" - VM1 is sn1" + "data1" + data2" + un-named swap data On the 5th day of testing....the VM will have files for - "base VM", "sn1", " sn2", "sn3", "data1",  data2" and un-named swap data that is generated during the 5 days testing. Then by right "consolidation" will convert the un-name swap into "data3" so that - "sn1" is the base snapshot + "data3" - "sn2" is "sn1" + "data1" + "data3" - "sn3" is "sn1" + "data1" + data2" + "data3" - VM1 is sn1" + "data1" + data2" + "data3" In a layman way....VMs with snapshot are VMs that have have been split into many files. When you delete snapshots (please do not try delete all), what you are doing is to merge sn1" + "data1" + data2" + un-named swap data or "data3" into a VM. Sorry....I forgot to add...please do not house or keep VMware snapshots for extended periods of time. Snapshots are not backups. They might snap then u have yourself shot......cheers....
I actually found the culprit after a few tries. There are several issues/causes for this but it leads any (one) of the following : 1. Dell EQL smart copy : the smart copy job is stuck. The iss... See more...
I actually found the culprit after a few tries. There are several issues/causes for this but it leads any (one) of the following : 1. Dell EQL smart copy : the smart copy job is stuck. The issue is fixed in the Dell EQL VSM 3.5.2 where unsuccessful snapshots are removed and re-queued. 2. Trend Micro Deep Security : Just re-sync the vCenter and clear/reset the error warnings for all computers 3. Acronis Backup job stuck or failure which causes the VM "aware" snapshot "services" to start and then stop. All I did was to stop the backup job as Acronis does not have a easy to understand error log. Please kindly update if it helps.