vSphere 6.0 U1

[stanthewizzard]

Hello

Is Veeam compatible with those two ?

Thanks

[flakpyro]

Patched to vCenter and ESXi 6.0 Update 1 today and was unable to run any Veeam jobs until i re-enabled SSLv3 on port 902 on my ESXi hosts as per

http://kb.vmware.com/selfservice/micros ... Id=2121021

Veeam logs contained

Code: Select all

[11.09.2015 14:32:55] <  3016>      ERR |SSL error, code: [336151568].error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure
[11.09.2015 14:32:55] <  3016>      >>  |SSL_connect() function call has failed.
[11.09.2015 14:32:55] <  3016>      >>  |Failed to establish connection with the SSL server.
[11.09.2015 14:32:55] <  3016>      >>  |Cannot initialize new SSL connection.
[11.09.2015 14:32:55] <  3016>      >>  |Authd handshake has failed.

and the console showed

Code: Select all

NFC storage connection is unavailable. Storage: [stg:datastore-636373,nfchost:host-329656
Failed to create NFC download stream. NFC path: [nfc://path].

After enabling SSLv3 on the esxi hosts backups run as they did before the update to 6.0 Update 1.

[jamerson]

didn't want to update the host yet.
people who did, is VEEAM working fine with the new 6.0U1 ?

[albatorsk]

I has the same problem after upgrading to 6.0u1 as flakypro, but the issue was resolved by enabling SSLv3 again.

[Gostev]

people who did, is VEEAM working fine with the new 6.0U1 ?

I know we have also updated our QC labs with vSphere 6.0 U1 on Friday as well, but I did not hear anything bad from QC yet. However, it's possible that they have upgraded, armed the auto-tests to run over the weekend, and left home (or to the bar). In any case, I will know this for sure on Monday.

[stanthewizzard]

The issue was resolved for me too by enabling SSLv3

Thanks flakypro

[chrmol]

I also got the "Failed to create NFC download stream" after upgrading one of my lab hosts to Update 1.

[ACrispiels]

I also got the "Failed to create NFC download stream" after upgrading one of my lab hosts to Update 1.
The issue was resolved for me too by enabling SSLv3
Thanks flakpyro and VBu

[gerdesj]

It's a shame that Veeam don't support proper encryption by default. SSLv3 has been deprecated for some time now. TLS 1.1+ should be the default by now for all software, it's been around for a long time. PCI DSS (current) mandates TLS and will be required this next June.

On the other hand perhaps VMware could have notified their third party providers of software that they would be doing this first.

Veeam: Pull your finger out. The various SSL related issues have been news for months if not years.

[Gostev]

Jon, I don't know if you had a chance to read this thread before posting - but according to the KB article above, this issue affects even VMware's own products...

In any case, there is really no need to be so harsh in your very first post on these forums... let's be constructive. I know that we do use TLS in our product, because I was checking on this myself a few months ago (had many questions regarding this and our Cloud Connect functionality). So, this issue is as unexpected to me, as it is to you.

I don't want to be guessing, but judging on the error above, this error could be caused by certain VMware NFC API function not supporting TLS. We will know for sure once our devs get a chance to investigate this issue more closely.

[joergr]

@All please also keep an eye on this one - it is a bad one and it concerns esxi 6.0.x and 6.0u1.
http://kb.vmware.com/selfservice/search ... Id=2124669

Best,
Joerg

[agregersen]

It seems our installation is doing the backup slower after U1 and the SSLv3 workaround - what's your experience?

[lightsout]

As I would understand it, this effects ESXi 6.0 U1 and not vCenter 6.0 U1? As it seems to be ESXi which is the source of issue.

I'll agree I was surprised that Veeam was still using SSL too, so I'll be curious to see what the devs find out.

[wreedps]

I am having the same issue after updating to U1, how do I fix this?

[rseabrooke]

Yep, that effected us and we cannot go back to 5.5 because we are running Horizon on top of it:(

@All please also keep an eye on this one - it is a bad one and it concerns esxi 6.0 and 6.0u1.
http://kb.vmware.com/selfservice/search ... Id=2124669

[Gostev]

@All please also keep an eye on this one - it is a bad one and it concerns esxi 6.0.x and 6.0u1.
http://kb.vmware.com/selfservice/search ... Id=2124669

Wow! This one sounds like vSphere 6.0 Update 1a is due soon!

[Gostev]

As far as the original issue that created this topic, the research has now been completed.

SSL usage seems to be isolated to NFC API, and is caused by a bug in parsing the list of supported SSL/TLS protocol versions on our side. Despite TLS was added at some point, this bug went unnoticed, as things continued to work normally over SSL - until now.

The good news is that this will be very easy for us to fix - so, we are planning to provide the hotfix for v8 Update 2 soon, and also include this fix into v8 Update 3 scheduled to be released late September (with the main feature being Windows 10 support). Thanks!

[mdmd]

As someone how doesn't use VI, are there any step by step instructions, or anyway to enable this in the Vsphere client.

[mdmd]

Its ok, didn't take much to learn, must have needed that coffee Thanks.

[Ben Milligan]

Hi Everyone!

We have a KB now. =)

http://www.veeam.com/kb2063

Cheers!

[Liberty4All]

If I am just upgrading vCenter are there any issues? Thank you.
Paul

[Ben Milligan]

Not this one - but are you upgrading in place or replacing vCenter? Changing ref-id's in a new vCenter is something different but important to understand.

[Liberty4All]

I am doing an in place upgrade.

[Ben Milligan]

Ref-id's should then stay intact, and you should be good to go. =)

(For edification on the other scenario, we track by ref-id, so we would not be able to 'find' a VM in a job referenced by the former ref-id. This would happen to all VM's that are inventoried by the vCenter being replaced, however my support team has a script that can help with this situation prior to the vCenter change.)

[wreedps]

When will the update for Veeam be released?

[foggy]

As it is stated above,

...v8 Update 3 scheduled to be released late September

However, hotfix for the current v8 Update 2 will be available sooner, so please contact technical support to be notified immediately.

[kjstech]

I just came here to check Veeam compatibility with the latest vSphere and I'm surprised to see this. Were still on 5.0. Never liked the single sign on in 5.1, the flash based web client in 5.5, and now were just exploring 6.0 releases to see if its worth updating. I'm really glad to see Veeam is on top of this. Though I think we will be holding off upgrading our 5.0 yet again because VMWare KB 2124669 looks too risky of an issue to have in a production environment where jobs are on the line.

[Gostev]

The hot fix has been sent to support - you can reference issue ID 56246 to speed up the conversation

[pad343848]

Where can I download hotfix?
It's realy important for me to fix VEEAM asap!

[foggy]

Sergey, please contact our technical support to get it. Thanks.