After VMware released vSphere 6.7 Update 1 all want to install it. But many of them didn’t check the interoperatibility with, for example, the backup software. So… Veeam Backup and Replication 9.5 U3 not supports vSphere 6.7 Update 1.
The problem is in a small API change with big impact. There is a workaround for all of the early updaters to get your broken backups work again.
Last weekend the final version of Veeam Backup and Replication Update 1 was released.
VMware vSphere 6.5 is now fully supported.
The vSphere 6.5 support adds the following features:
- Encrypted VMs support.
- VMFS6 support.
- Virtual hardware version 13 support.
- NBD compression. VDDK 6.5 adds ability to enable native NBD traffic compression.
- New guest interaction API support.
- New VM tag API support. vSphere 6.5 introduces new APIs for programmatic access and management of vSphere tags.
To get the full list of changes go to https://www.veeam.com/download_add_packs/vmware-esx-backup/kb2222/
I’ve wrote down the few steps to install the update.
At the beginning of the new year Veeam has built the Release Candidate for Veeam Backup and Replication 9.5 Update 1.
With this update it is possible to backup VMs running on vSphere 6.5. You have to open a case at Veeam to get the Release Candidate. Remeber: Those updates are only for testing. Productive support will come with the official update!
After upgrade to the new version of Veeam Backup and Replication (9.5) you could get a failure within your Microsoft Exchange Backups.
The Backup runs even normal and ends apparently successful. But the logs are not being truncated and the event logs might shows an event ID 2034.
With the latest update to vCSA 6.0 Update 1 I’ve got an undefined error when I use the WebClient (Update vCSA 6.0 to vCSA 6.0 Update 1). The VMware Support said that a certificate mismatch in “User Experience Program” caused that error, but could not solve it.
My first thought was, ok, then I install a new vCSA. But every one of you know that there are many things to consider and a lot of work to transfer all data, permissions, roles, rules etc… *not funny*