But it enables to run your Veeam Backup jobs again. Veeam 9.5 U2 2017 : Installing: Backup & Replication for Todays Always ON Business (Veeam Backup & Replication Book 1) eBook : Networkers. This registry key forces Veeam Backup to use API 6.7, but might lead to other yet unknown problems. You need to add a multi-string-value (REG_MULTI_SZ).
HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
#VEEAM 9.5 UPDATE#
The workaround outlined below has to be reverted as soon as Veeam 9.5 Update 4 is available. If you’re not yet on vSphere 6.7 U1 and you’re using Veeam Backup, you better wait until release of Veeam Backup 9.5 Update 4. Warning! This solution is not recommended by Veeam Support. You need to enter a registry key to force Veeam Backup using the older API 6.7. According to Veeam sources, the issue will be settled with the soon to come Veeam Backup Update 4.įor all of those who have already updated their clusters to vSphere 6.7 U1 there’s a workaround. Latest API version is 6.7.1, but this one seems to be incompatible with Veeam Backup 9.5 U3a. It turned out that there was a change in the vSphere API which caused communication issues with Veeam Backup. VMware and Veeam worked hard to identify the root cause of the problem. Unfortunately problems emerged soon after users updated their clusters to vSphere 6.7 U1 in combination with Veeam Backup jobs. Until that some tasks had to be done with the infamous flash client.
Finally vSphere-Client (HTML5) has become fully functional. An update we’ve been desperately waiting for. On October 16th 2018 vSphere 6.7 Update 1 became available. Failed Backup Jobs after Update to vSphere 6.7 U1
0 kommentar(er)
