We backup a 1TB VMWare File Server using VMWares VCB with Symantec Backup Exec 12.0, everything is connected with 4Gb fibre

Over the last few months our job rate has slowly dropped from around 1600Mb/s to a disappointing 650Mb/s.

For some reason after tring everything imaginable the problem was solved by simply defragmenting the drive being backed up.

I finally tried this after finding a similar story on vmware forum

If you have forgotten to enter the VLAN ID during the VMWare ESX or VSphere installed or you have entered the wrong VLAN ID you will find you will be unable to manage the VMWare host remotely, the only way to resolve this is to change the VLAN ID via the command line shell.

First you will need to log on locally to the server, the username will be root and you will have had to enter a password as part of hte install.

You will then need a couple of bits of information

If you get the below message when tring to use the Console in the Virtual Infrastructure Client it is because the permissions have been lost on the configuration file (.vmx) for that Virtual machine

Restarting the VMware management service can resolve lots of problems mainly problem where the VMware Host cannot be contacted correctly by the Virtual Infrastructure Client, or Virtual machine will not start or vmotion

Restarting the service does the same things as restarting the host but done properly it leaves the Virtual Servers running!

I recently started using the VMWares Consolidated Backup product to backup the virtual servers on our VMWare ESX hosts. Dues to our VCB proxy server only having a 40Gb Hard Drive we where having problems with the pre-command script that comes with the Backup Exec integration module for VCB.