Documents I used:

PDF:

VMware Symantec PDF

Symantec VMware PDF

Overview: (From VMware Tech Support)

VMware Tech Support PDF

Note:

This solution (work around) is for small business. In my opinion I would not do this method, but it can be done.

Restore Using NTBackup VI3 Images.pdf

Daemons:
Samba has to be installed
NFS has to be installed.

Some pictures are distorted and or whited out text to cover names of servers.

Diskpart

This was taken from the Microsoft website.  A customer asked how this command would work in VMWare.  I tried it and it worked just like usual.

VIM 2.0  (yes I skip the upgrade to 2.1)
Server that was running 2.0 remain at VIM 2.0.  I created another server for VIM 2.5.  Then as I upgraded ESX 3.02 to ESX 3.5 I moved them over to the VIM 2.5.  (No Real no choice, the VIM 2.0 will not allow ESX 3.5 to connect.)

My notes:

VIM 2.5 and ESX 3.5 Migrations

Clean up from the command line (CLI)

Clean up for the CLI may show a difference between real storage.

After deleting old images from the MD 1000.  I went to the VI3 VC and it showed this much drive space.

The “Linux Console” showed

after 15 mins the VI3 VC corrected itself showing the same as the CLI.

df -h works but does not show the vmfs file system.  Use vdf -h to show the file system.

ESX Command Line

PDF of ESX.

Helps if no VMC to server.