anpa wrote:I noticed previously in the thread a question regarding if there was any issues with running vCenter 6.7, but still having the hosts on 6.0U3 or 6.5U1 - if that was a supported solution? Same with vCenter 6.5U2, but having hosts on 6.5U1 - does that also break stuff?
For those questioning the time frame for Veeam, keep in mind that Veeam gets the GA code from VMware the same time as everyone else - this could be improved on by VMware to simple release the GA bits to integration partners some time before making it GA, that way they could have 3rd party support for their products when they go GA. The code many partners have tried with have been the beta bits, and VMware seems to change stuff between last beta and final GA bits.
ONE IT Service wrote:Following this post suggestion : https://ollis.blog/workaround-vmware-es ... mmenspiel/
There is a workaround that worked in my case. It's in German but it says to change the transport mode of your backup proxies to "Virtual Appliance" and to disable the option of failing back to network.
Restart your backup server and run your jobs again.
Seems to work for 2 days now.
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????
cambiumphil wrote:Yes, from VMware's perspective having downlevel hosts is a supported situation.
Users browsing this forum: Bing [Bot], Google [Bot] and 40 guests