API version on the source server does not allow transfer operation error

Inline images 1

You receive the error when using Veeam Backup and FastSCP 3.0.2 and when you are attempting to transfer files between a client and an ESX/ESXi server.

Found this excellent post which recommended upgrading the Veeam software from 3.0.2 to 3.0.3 and voila it does indeed work:



Is it possible to rename a VMware vSphere or ESX datastore whilst it is live?

You can easily rename a Datastore via the vSphere client without any impact on running VM’s in that datastore.

The name that you see is a friendly name that Vcenter uses for the datastore. The actual UUID of the datastore is not being changed therefore there is no impact on the vSphere host, datastore or VM’s.

If you feel unsure then by all means migrate the VM’s from the datastore before you make the name change.

Error ‘HA agent has an error: cmd startagent failed: Internal AAM Error – agent could not start’ on a VMware ESX 3.5 cluster node

I received this error after the ESX cluster nodes had all restarted. It only affected one ESX server

C:\Documents and Settings\jonesmc\Desktop\Screen Captures\ScreenShot099.jpg

To resolve I simply right clicked on the ESX cluster node in the VMware Infrastructure Client and selected ‘Reconfigure for VMware HA’. After a short time the task completes, the error is cleared and High Availabilty is again available across all nodes.

I did this whilst a number of virtual machines were hosted by this particular node without any problems


Sometimes the ‘Reconfigure for VMware HA’ does not clear the error. Instead you may have to disable and re-enable HA across the whole cluster. To do this right click on the Cluster and select ‘Edit Settings’


Uncheck the ‘Enable VMware HA’ box and select OK. When it has completed return to the ‘Enable VMware HA’ feature and check the box. This will disable and reenable HA across all nodes in the cluster.

Again this can be done without shutting down your VM’s. Obviously the only issue would be if there is a failure whilst HA is disabled


When deleting a Snapshot in the VMware Infrastructure Client an ‘Operation timed out’ is displayed

Firstly, do not panic!! This has happened a couple of times to me and tends to be when a snapshot has been forgotten, has not been deleted and has grown to a large size.

As the content of the snapshot has to be written back to the original vmdk file before being deleted it can take a while to delete. A 21GB snapshot took around 5 hours to commit to the original vmdk file before being deleted.

There is an excellent article that explains all about Snapshots and Snapshot management which can be found here:


After installing and configuring a VMware virtual machine with Solaris 10 the VM turns off after a few seconds during the boot process

An error message is reported in the VMware Infrastructure Client

‘VMware ESX Server unrecoverable error: (vcpu-0). Could not reserve memory for vmm64. Are you sure your VM specifiEs a 64 bit guest 0S?’


This error is caused, in my case inadvertently when the 64-bit version of Solaris is installed into a 32-bit defined VMware Virtual Machine. By default the Solaris 10 installation iso comes with both 32-bit and 64-bit versions. During the installation process if it detects a 64-bit compatible platform it will install the 64-bit version unprompted. This may be a problem later if your ESX servers are not all 64-bit compatible and therefore would not be able to accept a 64-bit VM migration or if you intend to install a 32-bit version of an application such as Oracle into the OS.

If 64-bit is not a problem then edit the settings of the VM when it is powered down and select the 64-bit version as the Guest Operating System. This should now work when powered up.


To revert to the 32-bit version, first configure the Guest OS as (64-bit) see above. Power on the VM in 64-bit mode and you now need to force the Solaris OS to boot in 32-bit mode.

To do this run the following command with superuser privileges from a command line prompt within the guest Solaris VM:
eeprom boot-file=kernel/unix

Shut down the Solaris VM, edit the VM settings and then reconfigure the Guest OS as Sun Solaris 10 (32-bit). Power on the VM and both the VM and OS should be running as 32-bit regardless of the host hardware.

How to convert a VMware Server Image to ESX Server 3.5 (V2V) using the VMware Converter Enterprise utility

If you have a virtual image that is hosted on a VMware Server instance and you wish to transfer this to an existing Virtual Infrastructure consisting of a number of ESX servers then you need to run the VMware Converter Enterprise utility.

There are two versions of the Converter utility, Starter and Enterprise. The Starter version is available to everyone and is great in converting physical machines to virtual images (P2V) and for backing up and cloning images. The Enterprise utility is only available to those that have a Virtual Infrastructure Enterprise Edition licensing although there is no additional cost incurred. It also allows conversion to an ESX environment.

Installing the VMware Converter Enterprise plugin

The plugin is built into the Virtual Infrastructure Client and is the quickest and easiest way to run it. There is the advantage of being able to run the conversion tool from your own PC or any location that has a VMware Infrastructure Client installed.

You can also download a stand alone copy from the VMware site but for this process using the plugin in the VI client is easier.

Double click the ‘VMware Infrastructure Client’ shortcut


Select ‘Plugins’ and then ‘Manage Plugins’


In the ‘Available’ tab select the ‘Download and install..’ button. If it is not there you may already have it installed. This being the case check the ‘Installed’ tab


When prompted to select a language select ‘English (United States)’


Select ‘Next’ at the ‘Welcome’ screen


Select ‘Install’


The Converter utility is installed. Click ‘Finish’


The Plugin manager now shows the Converter Enterprise Client as installed


Select the ‘Installed’ tab and check the ‘Enabled’ box in the VMware Converter Enterprise Client. Click OK


At this point I would now recommend powering off the image that you wish to convert.

Right click on the ESX Server that you wish to host the converted image and select ‘Import Machine…’


The ‘Import Wizard’ opens. Click ‘Next’


Select ‘Other’ in the source drop down selection field. You could also select ‘Physical Computer’ here if you wanted to carry out a Physical to Virtual (P2V) conversion.


Select the Virtual Machine path and the add details of the relevant user account and password required to access the path.


At the ‘Source Data’ screen select ‘Import all disks and maintain size’


Select the ‘Destination’. This should be the ESX server that you initially right clicked to import the machine to


Give the Virtual Machine a name. This will probably be the same name as it already has


Select the Datastore to import the image to. If your ESX server has local storage this will also show as an option, in this instance it is ‘storage1’


Select the number of network interfaces that you require. This tends to be the same as is already configured within the image.

Also select whether you want them powered on or off. This would be useful if you want to test the server before allowing it to go live


Check the ‘Install VMware Tools’ and ‘Remove all System Restore checkpoints’ options


Run the task immediately unless you wish to schedule out of hours


Confirm that your settings are correct and also check the ‘Power on the new virtual machine after creation’ if you wish for the image to be automatically started up once imported


The conversion begins and you can follow progress in the ‘Recent Tasks’ area


Selecting the task also shows a more detailed progress report


Once created the imported virtual machine is started and operational!