Any tips on how to restore the base VMDK?

Perhaps reduce the NTFS partition to 10GB, then use vmkfstools to shrink the VMDK? Sounds easy in theory, but I don't know exactly where to start.

That's the rub.. BackupExec wasn't catching an embedded MySQL database in a piece of software on that server. The vendor's documentation didn't mention any special backup instructions or considerations, and now I'm screwed. I guess I have some bad news to give Monday morning!

On a related note: Would ESXRanger or VCB been able to properly backup the MySQL database while the VM was running and the database in use?

This only worked because I did not modify the disk in ANY way other than stated above!

Solution:

Boot GPartEd ISO in new VM with plain (wwcs-read180.vmdk) drive attached
Shrink partition back to 10GB

Create blank 10GB drive to hold 10GB partition:
vmkfstools -c 10G -d thick wwcs-read180-10g.vmdk

Copy drive contents using DD, bs and count are set for 10GB drive
dd if=wwcs-read180-flat.vmdk of=wwcs-read180-10g-flat.vmdk bs=1048576 count=10240

Move broken drive out of the way, name new drive to old name:
vmkfstools -E wwcs-read180.vmdk wwcs-read180-30gbad.vmdk
vmkfstools -E wwcs-read180-10g.vmdk wwcs-read180.vmdk

Open snapshot depending on broken VMDK, note parentCID variable:
nano wwcs-read180-000001.vmdk
Example: parentCID=b7c9e128

Open fixed VMDK, set CID to value from parentCID.
nano wwcs-read180.vmdk
Example: CID=b7c9e128

Boot Up

Change SCSI type? No

Hooray!

I'll be doing a FULL backup and reinstalling this application soon on a fresh VM, I don't trust it after all the hackery I've put it though.

Helpful for how to shink a VMDK: http://www.vmware.com/community/message.jspa?messageID=423911

I have posted a more official writeup on my blog about this thread.

http://www.gorillapond.com/2006/11/26/foot-wounds/