Category Archives: VMware Other

Veeam Backup Error: Out of the Vector Bound

When running a backup job using Veeam Backup & Replication v8 or v9 the job fails with Error: Out of the vector bound. Record index: [0]. Vector Size: [1] Job finished with error. Running an active full produces the same result. In our case this issue was caused by corruption to the metadata file. This can occur when the metadata file is not properly closed and breaks the chain, potentially down to a file system filling up, or server failure.

To resolve we start a new chain to re-create both full data and metadata. This is done by cleanly deleting records about the backup job from the Veeam Backup & Replication console and configuration database, and deleting backup files themselves from the destination storage. The job itself remains so does not need recreating.

  • First disable the job; open the Veeam Backup & Replication client. Ensure Backup & Replication is selected on the task pane on the left hand side and select Jobs. Right click the failed job and click Disable.


  • Next we need to remove the corrupted files.  Still in the Backup & Replication task pane select Backups. Right click the failed job and click Delete from disk to remove the backup files and records.


  • Now go back to the Jobs page and enable the job. Run an Active Full to create new data and metadata files.


Physical to Virtual Machine Conversion Guide

VMware vCenter Converter enables physical and virtual machines to be converted into VMware virtual machines. The source can be a physical server, or a virtual machine using another platform such as Hyper-V. The client can also be used to convert a VMware Workstation or Fusion virtual machine to a vCenter infrastructure VM or vice-versa. This post will walk through the physical to virtual (P2V) process; using VMware vCenter Converter to migrate the operating system, applications, and data over the network to the virtualisation platform.



  • There will be down time during the switch-over, best practises indicate any databases or applications should be stopped during the conversion, as well as Anti-Virus.
  • Most Windows and Linux operating systems are supported, you can view a full list of supported operating systems on page 19 of the vCenter Server Converter White Paper.
  • Communication across ports 22, 443, and 902 is required. If you are connecting the Converter client to a remote machine then ports 139, 445, and 9089 are also required.
  • If the source machine is Windows then ensure Windows Firewall does not block File and Printer Sharing.
  • Make sure the virtual infrastructure has the variables required to run the physical machine as virtual, such as the correct VLAN configuration if you intend on keeping the same IP address, as well as Backup, DR, monitoring, and any other third party application compatibility.
  • The vCenter Converter itself does not require a license, you will need a (free) VMware account to download.

Client Install

First we install the vCenter Converter client on the physical server to be virtualised. This is straight forward installer and can be done any time, a reboot is not required. Click any of the thumbnails below to enlarge.

  • Download the latest version of the vCenter Converter from VMware Downloads and run the application.
  • Click Next to start the wizard.
  • Click Next to accept the patent agreement.
  • Agree to the license terms and click Next.
  • Accept the default installation directory and click Next.
  • Select Local Installation and click Next.
  • Review the customer experience program option and click Next.
  • Click Install to start the installation.
  • Once complete click Finish.

P2V Process

With the vCenter Converter client installed the next step is to actually run the physical to virtual conversion. To ensure a clean conversion it is recommended to stop any databases or applications during this process, even if you cannot afford the downtime it is likely there will be a performance degradation while the conversion is running. You should also consider disabling any AV program during the conversion.

Open the VMware vCenter Converter Standalone Client. Click Convert machine.


Change the source type to This local machine and click Next. You can also convert a remote Windows or Linux machine using the appropriate option.


Change the destination type to VMware Infrastructure virtual machine, this allows us to connect to a vCenter Server. Enter the vCenter name and credentials, click Next.


Enter a unique name for the virtual machine and the organisational folder where it will be stored, click Next.


Select the host or cluster for the virtual machine and the storage to use, click Next.

Review the options page, there are a number of useful settings here. For example you can set the physical machine to shut down once complete and the virtual machine to power on, for automatic switch over. You can also set the correct VLAN for the vNIC to use, exclude drives from the P2V task, or change virtual hardware settings; such as increasing resources. Change any desired settings and click Next.


On the summary page click Finish to begin the P2V conversion. The P2V job will be added to the tasks list with an estimated completion time, this varies depending on the amount of data to migrate and the speed of the network.

Post P2V

Once complete the virtual machine will be powered off by default, unless you specified otherwise in the options page. If required, manually shut down the physical machine and power on the new virtual machine. If you power on the virtual machine while the physical server is still connected to the network make sure you have disconnected the vNIC from the virtual machine to avoid an IP address or host name conflict.

There are a number of ‘tidy up’ jobs we need to carry out on the new VM after the P2v process.

  • Install VMware Tools.
  • From the Edit Settings option of the virtual machine remove any unnecessary virtual hardware that may have been added as a hardware equiviliant was detected, but not used.
  • Remove any physical server, or hardware, management software such as RAID management, drivers, etc.
  • Remove any ghosted entries from device manager, to see non-present devices open command prompt as administrator and run set devmgr_show_nonpresent+devices=1. In Device Manager click View, Show Hidden Devices. Uninstall any greyed out devices.
  • Remove any system restore points from before the conversion.
  • Remove the VMware vCenter Converter client.

Resources – for additional information or troubleshooting steps see the VMware vCenter Converter User Guide. Calculate cost savings for converting physical servers to virtual using the VMware ROI TCO Calculator.

Custom Alerts for vSphere Events

Alarms in vSphere are notifications that are generated when selected events occur, or conditions and states are met. There are a number of predefined alarms within vCenter Server that monitor datacentres, clusters, hosts, virtual machines, datastores, and networks. When an alarm is triggered an action can be configured to automatically respond, this could be something such as sending an email alert, or running a script.

Alarms are automatically inherited from objects higher up in the vSphere hierarchy, for example alarms configured at datacentre level apply to all clusters, hosts, virtual machines within that datacentre. The top level is the vCenter Server, alarms configured here monitor all applicable objects in the vCenter.

In this post we will quickly go over how to setup an alert for an event logged by vSphere for which a predefined alert does not already exist. This is done by creating a custom alert using the EventTypeId as the trigger event.

The first thing we need to do is get the EventTypeId, this differs from the fully formatted message you see in vSphere. Open a PowerCLI window and type Connect-VIServer where is the name of the vCenter Server to connect. Use the Get-VIEvent Cmdlet to view events with the syntax below to narrow the results.

  • -Entity where is the virtual machine, host, resource pool, etc. you want to view events for.
  • -Start where is the start date to retrieve events from, this should be in dd/mm/yyyy format (or mm/dd/yyyy if using US regional settings).
  • -Finish where is the end date to retrieve events from, this should be in dd/mm/yyyy format (or mm/dd/yyyy if using US regional settings).
  • -MaxSamples where is the number of events to retrieve. The default value is 100.
  • -Types where is the type of event to list, valid values are error, info, and warning.
  • -Username where is the user that has initiated the events you want to retrieve.
  • You don’t have to use all of the above. The example below will list the last 10 events on Host1 that were initiated by administrator@vsphere.local.

    Get-VIEvent -Entity Host1 -Username administrator@vsphere.local -MaxSamples 10

    The output for each event should look something like this. Locate the EventTypeId and make a note of it.


    Log into the vSphere web client and browse to the level for which you want to apply the alarm, for example vCenter, host, virtual machine, etc. Click the Manage tab and select Alarm Definitions.


    Click the green plus symbol to add a new alarm. Enter a name and description for the alarm, select the type of object to monitor and change the Monitor for option to specific events occurring on this object and click Next.


    Click the green plus symbol to add an event. In the Event field enter the EventTypeId to monitor for, that we recorded earlier. The status of the new event is set to Alert by default, click Next.


    On the Actions page select how to act upon the alert when the event is generated. This could be by sending an email, automatically running a script, etc.


    The alarm has now been created and the configured action will be applied when the event is logged.