The command to run is (from "c:\program files\VMware\VMware Consolidated Backup Framework" by default):
# vcbmounter -h <vsphere host> -u <username> -a name:<VM Machine Name> -r <Local backup directory> -t fullvm -m nbd -M1The command above will prompt for your password on the command line, you can include it in the command if you want to leave your password in the logs in plain text.
-a name: - This uses the VM name shown in VSphere (case sensitive) and will allow you to backup VM's which are powered off. Other options allow you to use the network name or IP of the Virtual Machine, but these require the VM to be on.
-t fullvm - the other option is to mount the VM so you can acces the files in the filesystems. Full VM gives you a VMWare image you can import elsewhere.
-M 1 - This sets the monolithic flag giving one big file for the filsystem. Otherwise it would split the filesystem into 2GB chunks
Earlier I mentioned that this backup would only be crash consistent. You can reduce potential problems by installing VMWare Tools to the guest VM, and by setting up scripts which the backup process can run before the snapshot to unmount databases etc. For example you could turn off any databases, do the snapshot then turn the databases back on - databases would only be off for a couple of minutes and the backup would not risk corrupted database tables.
mountvm gives access to the guest file system remotely so you can backup specific files
vcbvmname lists details of all VM's on a server