vCenter 5.5 Update 2

[lightsout]

Hey all,

As vCenter 5.5 Update 2 is out:

https://www.vmware.com/support/vsphere5 ... notes.html

Has this been tested with Veeam by anyone yet? Any reason not to upgrade?

Thanks!

[Gostev]

Hi

My standard recommendation is to wait for at least 2 weeks before jumping a new release of any software, with one and only one exception: if your is production down due to a big, and the fix is included in this new release Just because you cannot make it worse than it already is!

Let someone else run into any possible issue that may have got by QC.

Thanks!

[lightsout]

Well I see a reason for ESXi 5.5 Update 2 at least:

https://www.vmware.com/support/vsphere5 ... notes.html

ESXi hosts might be disconnected from vCenter Server after Veeam backup is performed
After you perform Veeam backup, the ESXi hosts might be disconnected from the vCenter Server.
This issue occurs when Veaam tries to create a snapshot of the virtual machine.
Error messages similar to the following are written to the hostd.log file:

--> Crash Report build=1312873
--> Signal 11 received, si_code -128, si_errno 0
--> Bad access at 735F6572

This issue is resolved in this release.

[Gostev]

Just like I said, it would indeed be a reason if you actually experienced this issue in production right now. But from what I know, the issue is extremely uncommon.

[Gostev]

So, I've checked with our support, and apparently it's not just "extremely uncommon", as I originally thought based on not seeing this in the top support cases report. Basically, we've never had a single support case open for this one by our customers. But, since this update changes some behavior around Veeam B&R, I don't advise that you apply it until we perform a short testing cycle against it. I will update once the testing has been completed.

[ChrisRoad]

We were one of the victims of this problem.
We had at least 2-3 disconnects of random ESXi hosts every week. (our environment consists of ~20 ESXi hosts)

Glad to see this problem addressed, though we would much rather see a fix/workaround in Veeam than in ESXi, as the later is much more cumbersome to apply.

[Daveyd]

So, I've checked with our support, and apparently it's not just "extremely uncommon", as I originally thought based on not seeing this in the top support cases report. Basically, we've never had a single support case open for this one by our customers. But, since this update changes some behavior around Veeam B&R, I don't advise that you apply it until we perform a short testing cycle against it. I will update once the testing has been completed.

Thanks for keeping us informed. I am waiting to apply this to fix another issue but will hold off.

[bleblanc]

I'm about to upgrade vCenter from v5.0U1 to v5.5U2 and I currently have Veeam v6.5 patch 3.

Once vCenter is done upgrading I'm going to upgrade Veeam to v7 patch 4 so we will see how that goes!

[veremin]

It still might be worth waiting till QA confirms that the latest VMWare update works well in conjunction with our software. As to upgrading procedure, I'd recommend disabling existing jobs, until backup server also gets updated, since the 6.5 doesn't support VMware 5.5. Thanks.

[Gostev]

We've been running U2 in QC since Monday, and have not encountered any issues.

[Tarqy]

Any idea when we will get the 'official' thumbs up for compatibility from you guys?

[MarkKoester]

To second what Tarqy said, I have a prospect who is looking for an 'official' thumbs up as well - ideally in the form of release notes or minimally a blog or forum post. Looking forward to hearing more on that soon. TIA

[Gostev]

Hi, all. Here is the official thumbs up! All looks good, no issues observed. Thanks.

[tinto1970]

Thank to you Anton and all guys at Veeam for having tested it so quickly: your help is always useful

[lando_uk]

Reviving this thread.

Are we ok to install the latest shellshock security patch update on VCA? (5.5.0.20100, Build 2170515) ?

[foggy]

We do not perform full testing against every minor update, but we've already installed this one in our QC lab and have not encountered any issues so far.