Web
Analytics Made Easy - StatCounter

Veeam backup fails after installing vSphere 6.7 Update 1

veeam-backup-fails-vsphere-67-update1-01

After installing VMware vSphere 6.7 Update 1, Veeam backup fails due to a change in the vSphere API 6.7 introduced by VMware.

The processed backup jobs fail with the error "Object reference not set to an instance of an object".

veeam-backup-fails-vsphere-67-update1-02

If you use Veeam as your backup solution, avoid updating your infrastructure with vSphere 6.7 Update 1 until the issue has been fixed.

 

Workaround for Veeam Backup

Currently there is not a fix for this problem but Veeam provided a temporary workaround to allow the jobs to be completed successfully.

In Veeam Backup and Replication Server you need to create a registry key in the HKLM\SOFTWARE\Veeam\Veeam Backup and Replication section.

Open the Registry Editor, right click the Veeam Backup and Replication item and select New > Multi-String Value.

veeam-backup-fails-vsphere-67-update1-03

Create the key VMwareOverrideApiVersion and assign the value 6.7.1=6.7. Click OK to confirm.

veeam-backup-fails-vsphere-67-update1-04

The created new registry key.

veeam-backup-fails-vsphere-67-update1-05

After creating this registry key, reboot the server and re-run the failed backup jobs. This time the backup job completes successfully.

veeam-backup-fails-vsphere-67-update1-06

As stated by Veeam in the KB2784, this is just a workaround since overriding the API version may affect other Veeam functionalities.

The official support for vSphere 6.7 Update 1 will be included in the upcoming Veeam Backup and Replication 9.5 Update 4.

signature

6 Comments

  1. Gaston 06/11/2018
  2. Jens 14/11/2018
  3. Georg 19/11/2018
    • Paolo Valsecchi 19/11/2018
      • Georgi 19/11/2018
        • Anonymous 06/12/2018

Leave a Reply