There’s good news for those of you who didn’t make it to VeeamON 2019 in Miami, FL. Veeam published recap videos, keynotes and technical session for you to watch online.
Next VeeamON will be in Las Vegas May 4-6 2020.
Next major release of Veeam Backup & Replication will no longer support several Windows versions. That was announced by Anton Gostev in his weekly forum digest on Feb. 25th 2019.
Veeam Backup & Replication components will no longer support being installed on Windows Server 2008 SP2, Windows 8.0 and Windows 10 1507/1511. However, Windows Server 2008 R2 SP1, Windows 8.1 and Windows 10 (1607 or later) will continue to be supported. Also, Microsoft Windows 7 SP1 continues to be supported as before.
Application-aware processing and guest file system indexing will no longer support Windows Server 2003 and Windows XP virtual machines. However, crash-consistent backup of such VMs will of course still be supported – as generally speaking, we don’t care what’s inside those images we’re backing up (and whether there is any OS at all).
VMware vSphere 5.0 and 5.1 will no longer be supported. However, vSphere 5.5 will continue to be supported. Importantly, the new VeeamCDP functionality specifically will require vSphere 6.5 or later due to its platform dependencies.
The long announced and postponed feature VeeamCDP will require vSphere 6.5 and later versions.
On December 5th you can join VeeamOnVirtual 2018 right from your desktop. Between 10 AM an 3 PM (CET) there will be several sessions in three main tracks: Business Track, Technical Track and Cloud Track. You’ll find details about speakers and sessions in the agenda.
Don’t hesitate and register for free.
On October 16th 2018 vSphere 6.7 Update 1 became available. An update we’ve been desperately waiting for. Finally vSphere-Client (HTML5) has become fully functional. Until that some tasks had to be done with the infamous flash client.
Unfortunately problems emerged soon after users updated their clusters to vSphere 6.7 U1 in combination with Veeam Backup jobs.
VMware and Veeam worked hard to identify the root cause of the problem. It turned out that there was a change in the vSphere API which caused communication issues with Veeam Backup.
Latest API version is 6.7.1, but this one seems to be incompatible with Veeam Backup 9.5 U3a. According to Veeam sources, the issue will be settled with the soon to come Veeam Backup Update 4.
For all of those who have already updated their clusters to vSphere 6.7 U1 there’s a workaround. You need to enter a registry key to force Veeam Backup using the older API 6.7.
Warning! This solution is not recommended by Veeam Support. 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. Do not upgrade. Read this passage again!
The workaround outlined below has to be reverted as soon as Veeam 9.5 Update 4 is available.
HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
You need to add a multi-string-value (REG_MULTI_SZ). Enter the Value below:
6.7.1 = 6.7
This registry key forces Veeam Backup to use API 6.7, but might lead to other yet unknown problems. But it enables to run your Veeam Backup jobs again.