stagnant wrote:["brian.mathis"]I can confirm.....vCenter 6.7 (haven't upgraded my hosts yet) does NOT work with Veeam 9.5 Update 3. (Error: Object reference not set to an instance of an object)
Let's hope Update 3a becomes available soon."
Tested in our lab and same result here. Have not found any workaround yet other than adding 6.5 ESXi hosts directly.
As far VMware vSphere 6.7 support in Veeam products, it is important to realize that as an ISV, we get the GA code at the same time with everyone else, so it will take us some time to test all of our products against it now that it's available. However, we already know that the most current Veeam Backup & Replication 9.5 Update 3 does NOT support vSphere 6.7 and as I mentioned here before, our release vehicle for adding this support will be Update 3a. Of course, we've already done a lot of work based on the pre-release code drops (for example, migrating our vSphere Web Client plug-in to HTML5 alone took us a few months). But it is only now that we can see the actual GA code (and notably, we're already finding some differences with the RC code) . Finally, since everyone will have the question about expected Update 3a timelines anyway: historically, we've been shipping new vSphere release support on average within 2 months from GA (with the official commitment for new platform support being 90 days from GA date). In this particular case however, there are additional unknowns in the equation: Windows Server 2016 RS4 and Windows 10 Spring Creators Update releases, support for which needs to catch the same release train. Although presumably, these should be shipped any day now – and testing the RC code has not revealed any major issues so far.
For those who did jump the gun and upgraded to vSphere 6.7 despite lack of official support, but unwilling to downgrade back to a supported vSphere version – remember that you can also use our agents to backup your VMs until Update 3a is shipped. We've actually just launched the 3 month production license program for Veeam Agents for Microsoft Windows and Linux, as well as Veeam Backup for Microst Office 365 - available to ALL customers and prospects without any restrictions. So if you have a need to protect your Windows and Linux workstation and servers whether they are physical or virtual, on-prem or in the cloud - or want a local backup of your corporate data hosted in Microsoft Office 365, you can now give our corresponding solutions a try. The license can be obtained directly from the download pages of Veeam Agents for Windows and Linux and Veeam Backup for Office 365.
DaStivi wrote:i did some research… i got one vm with the "object reference not set error"... this vm got back'd-up with NBD Mode... i need some time to realize that there was a snapshot open... looks like because of that the vm didn't got saved with my storage integration… but basically it looks like that with storage integration (backup from storage snapshot, or NFS Direct backup) the backup of vms on 6.7 does work, but not with NBD mode for example!
cgrossman wrote:DaStivi, you are awesome! Under Backup Infrastructure\Backup Proxies, I selected my proxy, went to Properties, and Transport mode was set to Automatic selection. I changed that to Virtual Appliance, and unchecked the box for Failover to network mode if primary mode fails. Now my backup WORKS! And, it's much faster. I was topping out around 120Mb throughput before, but now I'm seeing over 400Mb. Veeam Forums FTW!
Cragdoo wrote:direct quote from Gostev, in this weeks "The Word from Gostev" ...you do subscribe to this don't you??? if not ...shame on you
Cragdoo wrote:for those who have upgraded, are we talking your lab/test/dev environments? Surely no-one was stu... brave enough to upgrade to 6.7 on release day in production????
thirst things first, vSphere was released even bevor Gostev sent his newsletter… and some users want's to update as soon as possible because knowing whats gooing is their daily business…
i didn't read someone to really flame about Veeam not support vSphere 6.7 from day-0, also everybody can see that when VMware changes things not vendor can instantly support such things, but this is exactly what these forums are for... to find people and share the knowledge and possibly, like we did, find workarounds!
leeg123 wrote:i doubt this is useful info, but we upgraded our LAB to 6.7
We also can't backup, and this is totally fine. However as a test, we initiated an instant VM restore into the ESX 6.7 and it did successfully restore and boot
Again, not useful, but hopefully helpful to those out there who feel the need to test things that probably shouldn't even be bother with.
Eagerly awaiting update 3!!!
Users browsing this forum: Bing [Bot], Google [Bot] and 17 guests