ESXi 6.5 and vCenter 6.5 support

[veremin]

It does not matter, as neither VB&R 9.0 nor VB&R 9.5 supports vSphere 6.5. Thanks.

[ailar]

Any news about update 1?

[foggy]

Hi Ailar, have you read this topic carefully? If you're asking about ETA for Update 1, then this was already answered a couple of times above.

[bodgeup]

It does not matter, as neither VB&R 9.0 nor VB&R 9.5 supports vSphere 6.5. Thanks.

I have Veeam 9 update 0 running with Vcenter 6.5 and its working fine which surprised me.

JK

[foggy]

Hi John, as it is mentioned above, even if basic functionality may work, this combination is not officially supported.

[Zew]

As Alex already mentioned "Not Supported" This is a key thing to remember, IF something were to happen /go wrong. Veeam support may not be able to help you as that version of ESXi/vCenter is NOT SUPPORTED! Make sure everyone in your IT environment is aware of this, if you are using Veeam and the latest VMware builds.

[raphael@schitz.net]

Hi folks, i'd need to clone a vm on a standalone ESXi 6.5 (non production) but got this message when trying to connect.



Anything workaround i can use even if vSphere 6.5 is not supported yet?

Thx

[benbour]

I'm looking for a solution to a similar issue as well. Updated production VCSA to 6.5 and found it broke backup with:

Task failed Error: Support for vSphere 6.5 requires Veeam Backup & Replication 9.5 Update 1 or later.

Called Veeam and was told I can't get update 1 until the new year, so why does the error message say I must update? Why not just say I have to rollback until an update is actually available?

In the past, I was given an early release in beta to test, was hoping for something similar in this case.

[Gostev]

Called Veeam and was told I can't get update 1 until the new year, so why does the error message say I must update? Why not just say I have to rollback until an update is actually available?

If you look carefully, the error message does not say you must update now. Why I worded the message this way: remember that the same exact GA B&R code you have used will still be downloaded and installed by customers 3, 6, 12 months from now. So, the wording had to be both "technically correct" today and yet "future proof" for the next year. And I think I have succeeded in meeting both requirements with the current wording

In the past, I was given an early release in beta to test, was hoping for something similar in this case.

We will have something similar again, I will notify here in this topic when we start the Update 1 pilot and then you will be able to obtain one from support. The current plan is to start the pilot around the end of December.

[benbour]

We will have something similar again, I will notify here in this topic when we start the Update 1 pilot and then you will be able to obtain one from support. The current plan is to start the pilot around the end of December.

Thanks for that. Since I've always used appliance, VMware wisely upgrades to 6.5 and essentially just "turns off" vcsa 6 and then turns on 6.5. Rolling back is as simple as turning off the new one, updating your network for old one and turning it back on. I will wait until U1 is available and then switch back over to 6.5

[heelsonwheels]

Any update on when ESX 6.5 would be supported ?

[Vitaliy S.]

Please take a look at the first page of this thread for the answer.

[infused]

Hmm thought this was a minor release

[Gostev]

Not really, as I explained in the second post of this topic

[mikeely]

Cripes. Right in the middle of our test deployment vSphere got updated, now it looks like we're dead in the water on the test.

Can we please get a better ETA than "generally about two months after GA?" It's been long enough to have a better sense of how Update 1 development is going.

[Gostev]

Can we please get a better ETA than "generally about two months after GA?" It's been long enough to have a better sense of how Update 1 development is going

Well, this is probably not going to be what you wanted to hear, so don't shoot the messenger!

Long story short, we had to do a major rewrite of our VDDK 6.5 support code, because VMware dropped one new VDDK feature that we have already integrated with. This change happened last minute, between the last RC and RTM builds - and we only found out from testing the RTM build. They told us about the new functionality back in February, and while it did require significant amount of code changes to support, we had plenty of time to implement and test. In hindsight, we were better off not jumping the gun, but honestly this functionality was just too juicy to pass on...

Anyway, this fact will certainly delay our vSphere 6.5 support somewhat. We thought we were sitting on the "ready to go" code, and did not really expect that the "holy grail" of the backup engine will need such a major surgery. That said, unless stress testing uncovers any surprises, I expect us to still be able to meet our historical "2 months after vSphere RTM" timeline with mid-January release.

[mikeely]

Thanks for the detailed and prompt response. From curiosity (and since VMWare's RCs aren't totally NDA material) what feature did they drop at the last minute?

[Gostev]

Since we've got this information under NDA and the feature was never announced publicly, I have to assume it remains under NDA... but I can say it is performance related. Part of this new functionality actually survived in the RTM build, but not the one that really makes difference unfortunately.

[mikeely]

Datastores running WinFS, right?

[orb]

Is it safe to run the vCenter in 6.5 and leave all host in 6.0U2 to avoid comparability problems ?

Oli

[foggy]

Olivier, such configuration is also not supported.

[jamerson]

Does anyone knows when the the update will be available ?

[Gostev]

Just about everyone who read my post at the top of this page knows this

[jamerson]

I know its two konten after the release.
We are already 2 months behind.
We are busy with a new infrastructuur and want to apply the new esxi 6.5
That ehy the rush

[tsightler]

We are already 2 months behind.

GA for vSphere 6.5 was Nov 15th so we are not even one full month from that yet.

[pirx]

Not if they are running on beta.... *duck and cover*

[dbhagen]

Anxious to get my hands on the new web interface for vSphere (mostly Mac shop here), but can't leave backups behind.

[WinstonWolf]

Hello ,

Yesterday we updated our Vcenter Server to Version 6.5 and now Veeam B&R tells me to Update to Version 9.5 Update 1 .
Release Date Vsphere was the 15.11.2016

Whats going on Veeam ?

[ACC]

The current Veeam 9.5 version doesnt have official support for VMware vCenter 6.5 or ESXi 6.5, the official support comes with Veeam 9.5 update 1. There no official release date for this update.

[homerjnick]

Anxious to get my hands on the new web interface for vSphere (mostly Mac shop here), but can't leave backups behind.

You can install the fling on an ESXi box and use it, its pretty good...I have been using it for a while...I suspect what they offer as download n the fling is the same as ESXi 6.5.