vim-cmd vmsvc/getallvms vim-cmd vmsvc/power.off 48 vmware-cmd -l (list the vm's)
ps aux | grep vmfs vmware-cmd /vmfs/volumes/datastore1/foldername/vmname.vmx stop trysoft hard
VMware Snapshots creates a "difference in time" reference file - perhaps a close analogy is a Windows Restore Point. Taking and restoring from a snapshot can as little as a minute (if the VM's new state is powered off) or very long (large complex VM powered on). Normally VMware creates a tree of snapshots (But VMware Server only allows you to create a single snapshot & revert back to it)
VMware Snapshots are not exactly backups of the virtual machine image, but rather like a log files. As the VM runs, it is adding data to the last difference file, related to the difference between the current live state and the one previous to it.
One alternative to taking snapshots that can be used in VMware Server is to shutdown the virtual machine and copy the vmdk, vmem, vmx, and nvram files. Later you could replace these files and your virtual machine would be back at the point of when that copy was made.
When a snapshot is created a number of files are created in the directory for that virtual machine.
COMMAND LINE MANIPULATION
vim-cmd vmsvc/snapshot.get vmid ROOT CHILD CHILD
deleted the first snapshot (the ROOT) now the two children both become two roots
vim-cmd vmsvc/snapshot.get vmid ROOT ROOT
HOW TO REVERT TO THE SECOND ROOT
vim-cmd vmsvc/snapshot.revert vmid 1 0 1
vim-cmd vmsvc/power.on vmid
UNFORTUNATELY THE ID'S FOR A SNAPSHOT DON'T QUITE CORRELATE TO REVERTS YET vim-cmd vmsvc/get.snapshotinfo vmid