Hi,
Indeed I use esXpress for backuping up all my VMs. All but my fileserver (which is no more than a standard W2K3 server+FTP+print which I keep as a template). I upload my VMDK backups through esXpress to the same fileserver (using FTP). After that, I backup the entire fileserver using an agent on the fileserver for Backup Exec to tape. Including the images of my VMs.
Almost forgot, in order to be done with all these problems around quiescing which simply fails occasionally, I simply ask esXpress to take some of my VMs down (soft shutdown), then make the snapshot, power them back on, and stream the VM to the FTP server. This is a sure way to quiesce your backups, and is acceptable in my environment (Exchange for instance goes down for 5 minutes every day around 3:00AM using this setup). The upside is off course, that the backup is ALWAYS restorable without any problems of an unclean shutdown.
Apart from that, I now run esXpress 3.1-RC3 to test what the people at esXpress call "simple replication". The most important VMs (Exchange, Domain controller, SQL etc) get restored during the day automagically using the auto mass-restore feature. Basically every VM marked for replication which has a new backup image (delta or full), gets restored automatically to the DR site each day (or more frequent if you choose to).
In case of severe problems at the primary site, I can just directly fire up the VMs which are restored daily to the DR site (without having to set LUNs to primary, reregister VMs or any of that), rollout a template of the fileserver there and stream the file-level backup from tape. Solid!