ghettoVCB.sh - Free alternative for backing up VM's for ESX(i) 3.5, 4.x, 5.x, 6.x & 7.x

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

XavierE · ‎10-28-2009

I downloaded it to a windows PC. I then used vSphere client to upload it to a datastore.

I ssh to the esx server and edited the file via VI.

I did open it using notepad to see the text but did not save anything I simply closed it.

I will try again. Thanks

jberne74 · ‎10-28-2009

I suggest uploading the file with WinSCP as text and editing in using the vi editor in Putty.

stighenning · ‎10-29-2009

To remove the ^M from the file, do this;

sed 's/.$//' ghettoVBC.sh > NewghettoVCB.sh

..it will work

XavierE · ‎10-29-2009

Thank you guys for your suggestions, they were very helpful.

The script now runs and works great however I get this message below. Is this something that I can fix?

DiskLib_Check() failed for source disk The system cannot find the file specified (25).

cwkoh · ‎10-29-2009

Hi S3BAST13N. I am also looking to exclude backup od "independent" disk. Can you share with us how to modify the script to do so. Thanks.

lamw · ‎10-29-2009

FYI - Independent disk logic will be added to the next release of ghettoVCB

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

cwkoh · ‎10-29-2009

Great. Is this also in the beta. Can I have a copy to test. Thx.

lamw · ‎10-29-2009

Yea that'll be in the next release and sorry the BETA is closed. I should have a new release of the script soon enough

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

cwkoh · ‎10-29-2009

OK I'll wait for the release then

lukechip · ‎10-30-2009

Hi,

How is ghettoVCB supposed to handle VMs that are in a suspended state ? I'm just starting to play around with ghettoVCB now, and I'm finding that when ghettoVCB hits a machine which:

1/ is suspended, and

2/ has no snapshots

It takes snapshot, backs it up, but DOES NOT delete the snapshot it took as part of the backup.

Consequently, next time I try to backup the machine, when it is in a powered on state, the backup fails since there is a pre-existing snapshot (called vcb_snap).

Am I missing something ?

lamw · ‎10-30-2009

Yep, the logic when taking the snapshot is correct, but upon removal it only checks for "Powered On" VMs only, this has been fixed and will be ported to the next release of the script. In the meantime, if you would like to update the script just search for the section where the snapshot is removed and add and "OR" statement that says:

 \[\[ "${ORGINAL_VM_POWER_STATE}" == "Suspended" \]\]

This will solve the problem.

Thanks for the comments

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

XavierE · ‎10-30-2009

I have been testing the script for a couple days, and it seems to work fine. I have a couple questions:

1) Should the nvram and log files be also backed up? I only see the .vmx and .vmdk files

2) In some VMs I get this message but the backup still works

DiskLib_Check() failed for source disk The system cannot find the file specified (25).

Thanks

lamw · ‎10-30-2009

1) No, these files are not explicitly required (nvram will be generated upon boot up if not there) The logs may or may not be useful, depends on what you'll use them for and you could have quit a few logs. This can easily be added as a additional files but won't be part of this script

2) Can you provide more information about the environment, the VMDK(s) you're trying to backup? There's probably something going on with the disk it's trying to clone either at the source or destination. Would be helpful to provide some output from your run, as your error is vague in general. Remember to wrap all output in tags

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

lukechip · ‎10-31-2009

My backups only contain the .vmdk and .vmx files. Consequently, when I restore the machine using vmkfstools, the resultant machine is in a powered off state. This took me a little by surprise, since the machine was powered on when the backup was taken, and I'd expected it to be restored in exactly the same state.

As a result, my questions are:

1/ is this the intended behaviour

2/ is there any risk of memory resident or cached data that has not been written to the VMs disk being lost ? For example, an unsaved file that is open when the backup is taken, or data that has been saved but is in the VMs operating system cache, and not actually written to the VMs disk ?

Thanks.

lamw · ‎10-31-2009

1) Yes that is the intended behavior as stated in the previous reply

2) Using the quiesce option would solve this problem, take a look here for more details: http://virtualizationreview.com/Blogs/Everyday-Virtualization/2009/08/Quiesced-Snapshots.aspx

As of today, this is disabled by default but in the next release of the script, a user can configure both the quiesce and memory option of a VM when specifying a backup snapshot prior to backup. You can manually change the value in the script but it'll be a manual process.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

lukechip · ‎10-31-2009

Regarding "If you find this information useful, please award points for "correct" or "helpful"."...

How do I do this ?

I'd like to, but can't see where to do it !

XavierE · ‎11-02-2009

Will,

1) Thanks for your responses. Agreed. nvram and log files may not be useful. If I wanted to copy the log files and nvram I could only add 2 lines in your script after line 266 correct?

 cp "${VMX_PATH}" "${VM_BACKUP_DIR}"

to something like

cp ${VMX_DIR}/*.log ${VM_BACKUP_DIR}

cp ${VMX_DIR}/*.nvram ${VM_BACKUP_DIR}

2) I could not replicate the error "DiskLib_Check() failed for source disk The system cannot find the file specified (25)" anymore, I do not know what I did different with the test VM I have. I will post what I can if it happens again.

3) I noted that in your script, line 227 you have a check for existing snapshots and if found the backup is not performed. Do you do that for a special reason? wouldn't the script take a new snapshot (vcb_snap) below the other ones and remove it at the end? is this supported?

lamw · ‎11-02-2009

1) That should work, you'll want to test and verify.

3) Snapshots are not meant to be kept for long durations of time, there is a miss-conceptions on what snapashots are used for. They should be short lived and hence I will ignore any VMs with prior snapshots, you're more than welcome to modify the script to support this, but I will provide 0 support on this type of configuration.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

XavierE · ‎11-03-2009

1) After line 266

cp "${VMX_PATH}" "${VM_BACKUP_DIR}"

I added these 2 lines to also copy the nvram and log files

cp ${VMX_DIR}/*.log ${VM_BACKUP_DIR}

cp ${VMX_DIR}/*.nvram ${VM_BACKUP_DIR}

3) Agreed. VMware snapshots should be short lived, however on testing/prestaging VMs sometimes you need to keep a snapshot for 24 hours or so.

I tested the script with more than 1 snapshot and I think I understand why it won't support more than 1 snapshot because it will only remove 1 snapshot, the vcb_snap snapshot taken for the backup. If I’m not wrong this is in line 384

${VMWARE_CMD} vmsvc/snapshot.remove ${VM_ID} > /dev/null 2>&1

It's very tricky trying to remove a specific snapshot due to the levels and indexes for snapshots. If VMware could have a way to delete a snapshot based on the name of the snapshot that would eliminate many caveats.

I'm adapting the script to our environment. So I am doing these other changes/additions:

a) Allow the backup to proceed if snapshots are found and remove all snapshots (I chose I prefer a backup over a previous snapshot). So I commented out the snapshot check and modified the script in line 384 to this:

${VMWARE_CMD} vmsvc/snapshot.removeall ${VM_ID} > /dev/null 2>&1

b) A boolean (true/false) variable/parameter to also snap the memory when creating the snapshot. Example below

${VMWARE_CMD} vmsvc/snapshot.create ${VM_ID} vcb_snap VCB_BACKUP_${VM_NAME}_`date +%F` ${SNAP_MEMORY} > /dev/null 2>&1

c) I added a line at the end of the script to add permissions at my backup dir specified (openfiler SMB/NFS share)in the VM_BACKUP_VOLUME parameter.

chmod -R +rw ${VM_BACKUP_VOLUME}

I noticed that the files/folder created by the script had root permissions only so when the backup software tried to access the files to back them up it failed.

d) I also added a notification procedure at the end of the script to email the log created

I tested the script with my modifications/additions and works fine in our environment

Thanks Will for providing this script as it's a great contribution and useful tool and other people can also contribute to your work.

Can't wait to see the next release that will contain the independent disk logic and quiesce memory option of a VM (and more perharps?)

lamw · ‎11-03-2009

There are actually 2 reasons why I don't support backup of VMs w/snapshots

1) Reason from previous reply

2) It's not easy using vimsh ... having said that, it's stupid simple using the official VI/vSphere API's which allows you to remove a snapshot based on a name. This can be seen with if you take a look at the code, but again even with this version I do not support backups of a VMs with snapshots (going back to reason #1)

Having said all that, it's definitely possible with vimsh but you just have to figure out the index/child values which I thought I had figured out but it's really not worth it and again goes back to my reason #1

Glad the script is working out for you and the customization you're implementing for your specific environment.

Definitely keep an eye out in next few weeks for the next release, it'll be introducing some nice features

--William

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

kerozen · ‎11-05-2009

Hi,

thanks a lot for this script.

It's working fine in our environnment but it take so long to backup.

In fact, i backup vms to an nfs share on a little nas (iomega storcenter pro ix4-100) which is very slow for read and write (even in ftp or smb mode).

so i realize that ghettoVCB.sh does the backup directly to this share and then compress the vm on the share (when i enable compress of course).

Is it possible to do the snapshot locally, compress the backup and then send it to share (then delete the local compressed backup). In this order, i will gain some time to backup vms.

The only thing i need is enough space for locally backing up the biggest vm.

thanks by advance.

ben

voro · ‎11-05-2009

I've used a Iom200rl in the past and their NFS performance is not great. You should check how fast it transfers from the esx console (without using the script). Also you can tweak nas' exports config (async, no_wdelay, etc, but be careful with this, use at you own risk!) or try using jumbo frames, if your hardware supports it. I've experienced a huge increase of transfer rate with these.

kerozen · ‎11-05-2009

Hi,

the transfer rate is not really a problem. The real problem of the iomega is the I/O of the disks.

The best solution will be to compress before send the backup to the nas. (if space is available of course)

with this, less data to send to the nas, less time to send it.

i will look for jumbo frame too (the esxi nic, the switch and the nas have to support it)

voro · ‎11-05-2009

When I said transfer rate I didn't mean "network bandwidth". Jumbo frames can improve the situation if its related to network. Poor NFS performance can be related to network and to storage I/O; async and no_wdelay can improve the NFS performance when saving data.

To see which one you have to tweak you could do some testing with cat or dd with /dev/zero and /dev/null with ssh without compression and nfs. If it's fast (well, fast enough for a storcenter) then the bottleneck it's the NFS saving data and then those params I said above can make things a little better.

I think your proposal would require a major overhaul of the script. Meanwhile, if you have enough local space, you can set a local dir as VM_BACKUP_VOLUME, and after the script has ended, move the backups to the storcenter with a different script (quite easy to code because you can copy the rotation procedure from the original script).

kerozen · ‎11-05-2009

thanks.

i will look deep in this jumbo frame. easy on the iomega (just one click to activate jumbo frame support), i've read that i need to create a new virtual switch on esxi and define the mtu size for frame. sounds a bit more complex.

i've just ended trying to backup four vms to the little nas, compressing each one.

i got a big vmdk that was not stored in the gzipped file, the script return this error: tar: cannot store file 'XXXXXXX/xxxx-flat.vmdk' of size 107374182400, aborting.

so i ended with a gzipped file of 104 Bytes.

i will look into the script to see how i can do a local save then copy over the nfs share, as you suggest.

CBrienen · ‎11-10-2009

Hi William,

I have the exact same problem as Davidpyper described in his post from 28 Sep 2009. I have been using your script for a while now and never had any problems. Since a couple of weeks the script sometimes "hangs" while removing a snapshot. If I look in VC I see a snapshot in the snapshot manager of that particulary date. If I remove the snapshot the script continues and starts snapshotting the upcoming VM's. Before the script starts there are NO snapshot present in VC. It is not consistent so I don't know where to look. Any idea where to look?

Thanks for the script.

Christian

lamw · ‎11-11-2009

I've not seen this issue from others and haven't been able to reproduce. Are there anything specific with this VM in particular or set of VMs? Have you tried to backup other VMs except for this one to see if it's only this VM?

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

banthorpe · ‎11-12-2009

Hmm - OK looking into this again. It always fails on the 3rd VM regardless of size of that VM or the preceeding VM.

cwhitmore · ‎11-16-2009

I'm trying to backup one VM with two vmdk files. I've installed the latest GhettoVCB, but when I try to run "./GhettoVCB.sh serverlist" I get the following error:

/vmfs/volumes/48f62e13-c6958ca2-6bc2-0022198dec59 # ./ghettoVCB.sh serverlist

Skipping invalid VM '368'

Skipping invalid VM '384'

Skipping invalid VM '400'

Segmentation fault

Taking backup snapshot for Sharepoint2008x64 ... ################

Start time: Tue Nov 17 03:38:42 UTC 2009

Destination disk format: VMFS thick

Failed to open '/vmfs/volumes/BackupsStore/Sharepoint2008x64/Sharepoint2008x64_1.vmdk': Device or resource busy (1048585).

Destination disk format: VMFS thick

Failed to open '/vmfs/volumes/BackupsStore/Sharepoint2008x64/Sharepoint2008x64.vmdk': Device or resource busy (1048585).

Compressing VM backup "/vmfs/volumes/NFS/Sharepoint2008x64/Sharepoint2008x64-2009-11-17.gz"...

ash: /vmfs/volumes/NFS/Sharepoint2008x64/Sharepoint2008x64-2009-11-16: bad number

./ghettoVCB.sh: ./ghettoVCB.sh: 462: Syntax error: /vmfs/volumes/NFS/Sharepoint2008x64/Sharepoint2008x64-2009-11-16+1

/vmfs/volumes/48f62e13-c6958ca2-6bc2-0022198dec59 #

lamw · ‎11-16-2009

1) Please wrap any output you have in code tags, makes it much more readable on the forums. Please refer to this document if you have any questions: http://communities.vmware.com/markuphelpfull.jspa

2) How many VMs do you have on this host?

3) Is this ESX(i) and what build/version?

4) Can you please run the following command and paste the results:

ESX

vmware-vim-cmd vmsvc/getallvms

ESXi

vim-cmd vmsvc/getallvms

It looks like when it's querying for certain VMs, they're considered 'invalid' for some reason and probably why you're getting the initial dump.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

cwhitmore · ‎11-17-2009

Hopefully this paste works better:

/vmfs/volumes/48f62e13-c6958ca2-6bc2-0022198dec59 # ./ghettoVCB.sh serverlist
Skipping invalid VM '368'
Skipping invalid VM '384'
Skipping invalid VM '400'
Segmentation fault
Taking backup snapshot for Sharepoint2008x64 ... ################
Start time: Tue Nov 17 13:41:20 UTC 2009
Destination disk format: VMFS thick
Failed to open '/vmfs/volumes/BackupsStore/Sharepoint2008x64/Sharepoint2008x64_1.vmdk': Device or resource busy (1048585).
Destination disk format: VMFS thick
Failed to open '/vmfs/volumes/BackupsStore/Sharepoint2008x64/Sharepoint2008x64.vmdk': Device or resource busy (1048585).
Compressing VM backup "/vmfs/volumes/NFS/Sharepoint2008x64/Sharepoint2008x64-2009-11-17.gz"...
End time: Tue Nov 17 13:41:20 UTC 2009
Completed backup for Sharepoint2008x64! ####################
Start time: Tue Nov 17 13:41:10 UTC 2009
End time: Tue Nov 17 13:41:20 UTC 2009
Duration : 10 Seconds
Completed backing up specified Virtual Machines!
/vmfs/volumes/48f62e13-c6958ca2-6bc2-0022198dec59 #

I have six guests installed, ESXi version is 3.5.0

~ # vim-cmd vmsvc/getallvms
Vmid Name File Guest OS Version Annotation
112 vmXP vmXP/vmXP.vmx winXPProGuest vmx-04
208 FreeBSD71 vmFreeBSDx64/vmFreeBSDx64.vmx otherLinuxGuest vmx-04
416 ArchiveManager2003 ArchiveManager2003/ArchiveManager2003.vmx winNetEnterpriseGuest vmx-04
432 Sharepoint2008x64 Sharepoint2008x64/Sharepoint2008x64.vmx winLonghorn64Guest vmx-04
448 LegalFiles LegalFiles/LegalFiles.vmx winLonghorn64Guest vmx-04
96 vmBackup2003x64 vmBackup2003x64/vmBackup2003x64.vmx winNetStandard64Guest vmx-04
~ #

I'm only trying to backup one of the VM's (Sharepoint2008x64). It runs with errors if I shutdown the VM.

goppi · ‎11-17-2009

Great that policy based backup has been added.

The only thing still missing IMHO is the possibility to take a snapshort in powerdown state before backup. Depending on guest OS and running apps this is the only way to get a reliable backup. How about an additional setting TAKE_SNAPSHOT_ON_POWER_DOWN=1. Then the sequence would be as follows:

Power machine down,

Take snapshot,

Power up,

Take backup,

Remove snapshot

Taking a backup only with the setting POWER_VM_DOWN_BEFORE_BACKUP=1 can be quite time consuming and is not always an option.

IIRC this feature has been requested by two others. So how about?

Thanks again for that great software.

lamw · ‎11-17-2009

I've just released a new version of the script, please download this version and go over the documentation as there have been some changes on using the script. There were some issues that may have been fixed which might help resolve the issue you're running.

If you're still seeing the issue, please provide an execution run on the vm that is failing with both dryrun and debug mode.

Thanks

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

lamw · ‎11-17-2009

Sorry this feature will not be supported as mentioned in the past, there are no significant advantages to this and I'm not exactly sure what you're deeming "reliable backup". You're more than welcome to look at other Enterprise ready solutions if you need something more reliable ... and of course you're more than welcome to edit the script to fit your environment.

Thanks

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

goppi · ‎11-17-2009

I did not realize that it was mentioned in the past that it will not be supported, so I'm sorry for missing that. With "reliable backup" I don't want to say that ghettoVCB is not reliable, so don't feel offended. However depending on the apps and the os you are running you cannot always be sure that you have a consitent state on disk when taking a snapshot while the machine is running.

This is a similar thing like with VSS on MS Windows. Without apropriate VSS writer for certain apps you are running you cannot be sure that a consitent state is written on disk when you take a snapshot. As this mechanism (IPC between app, os and vmware) is missing on VMware (or at least I'm not aware of it) with certain apps (e.g. dbms) a snapshot will have a good chance to be corrupt on application level (on filesystem level it will be intact of course).

If I'm missing anything obvious please let me know.

Regards

lamw · ‎11-17-2009

I agree, but that's where enabling the quiesce of the snapshot comes into play and of course this is also OS dependent and if you have VMware Tools installed. You'll either use the default filesystem sync driver or VSS if you're on a Windows OS. Even with using other solutions like Veeam or vDR, you're still using a snapshot like solution and they also rely on quiescing the filesystem to ensure that you have a consistent backup.

Hope this helps

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

goppi · ‎11-17-2009

Ok not sure how exactly quiesce works with VMware. From what I found so far it seems that it triggers all VSS writers and so tries to ensure all data is written to disk before taking the snapshot. So if you have a system with VSS writers for all apps properly set up this should work. I will make some tests with that option to see if it works reliable. However I thik I will modify the scripts to support taking snapshots on power down state just to be on the safe side. Seems to be possible without big changes. IMHO this is still a good option as it ensures integrity and dramatically reduces downtime compared to taking a backup in power down state.

Thanks again for developing ghettoVCB and sharing it with the community.

Regards,

goppi.

cwhitmore · ‎11-18-2009

That did it. I'm backing it up now. Thanks for your help on this and the new features.

I haven't tried the snapshot quiesce or snapshot memory, but if I'm running MS-SQL on this server is there a reason why I wouldn't use it? ( I already have VSS turned on)

Oh, one minor typo I found in the ghettVCB.sh file. You have "VMDK_FILES_TO_BACKUP=" inside the area that says not to edit below this line. No big deal, just thought you might want to know.

I work for a non-profit so we have little funds for IT. Your script has allowed us to evaluate Vmware and virtualization options. Thanks again.

lamw · ‎11-18-2009

Glad to hear the new release fixed the issues.

I would definitely do some research on backing up any database systems, but there shouldn't be any reason why it won't work and I'm sure others have done it. If you already have VMware Tools installed and have VSS enabled, then yes you should be using snapshot quiesce option, the memory really is more for testing purposes and since the .vmsd and .vmss is not backed up as it only pertains to the snaspshot created.

For a deep dive on how VMware snapshots works, take a look at this VMware KB: http://kb.vmware.com/kb/1015180

Regarding the variable, I meant to put it there

The reason is by default if you don't use individual VM backup policy, it'll backup all "valid" VMDK(s) ... there is no concept of an exclusion/inclusion list as that is only supported with backup policy for each VM.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators

If you find this information useful, please award points for "correct" or "helpful".

scowse · ‎11-18-2009

The new script is very slick - thanks very much.

Just curious about these two lines from std out:

sleep: Interrupted system call

wc: standard input: Interrupted system call

Edit: I also note that the cron faq has not been updated to the new syntax e.g. "ghettoVCB.sh -f vmlist"

lamw · ‎11-18-2009

Glad to hear you're enjoying the new features of the script!

Regarding the output, I'm not sure where thats coming from ... sounds like something might have interrupted the syscall and hence the output. Could you provide more details about your environment, ESX(i) host, version, etc...? Are you able to consistently reproduce, without reproducibility, it'll be very hard for me to help troubleshoot.

Thanks for the doc info, I'll get that updated as soon as I get a chance.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

VMware Code Central - Scripts/Sample code for Developers and Administrators