vSphere 5.5 tests done?

[emk23]

Is vSphere 5.5 supported?

What is or is not supported in the new features? 62TB virtual rdms?

[lohelle]

Hello

I was just wondering if you have tested Veeam 7 on vSphere 5.5 yet?
I undestand that official support is some time away, but have you done some testing?
Just curious!

[nmace]

Also curious! Is there an ETA on support for 5.5? And will 6.5 support the new version of vSphere or 7.0 only?

[foggy]

No ETA currently as vSphere 5.5 was just announced and is not generally available yet.

[Gostev]

We have been looking at vSphere 5.5 since beta, and currently have RC installed in our labs. While some things still may change in the RTM build, it is pretty clear already that vSphere 5.5 will not be supported out of box with the current B&R version - and just like all previous vSphere releases, this one will also require some works to be done from our side... looking back, we always needed from 2 to 3 months to implement and test new vSphere version support. There might be slight variations of this time range depending on how this overlaps with our release cycle (next minor release we've been working on).

While 64TB VMDK support is definitely not a problem for us to support (B&R engine supported 64TB virtual disks for almost a year now, thanks to 64TB VHDX support on Hyper-V side of things), some other technical changes in vSphere 5.5 will require fairly significant effort from our side, and we are already working on this.

[chrisdearden]

Just heard that the Powershell APi in 5.5 will expose the tags function - which could led to some great scripts to create jobs based on those tags ( be even better in the GUI , but thats for a different feature request )

[beovax]

As this article is posted after the release of version 7, I suspect this thread is saying that Vsphere 5.5 will not work with Veeam v7 is that correct? If this is the case we are looking at 3 months plus before its worth upgrading to Vsphere 5.5 when used with Veeam v7?

[foggy]

As this article is posted after the release of version 7, I suspect this thread is saying that Vsphere 5.5 will not work with Veeam v7 is that correct?

Correct, current product version (Veeam B&R v7.0.0.690) will not support vSphere 5.5.

If this is the case we are looking at 3 months plus before its worth upgrading to Vsphere 5.5 when used with Veeam v7?

Correct.

[Gostev]

I don't know where this "3 months plus" came from, I never said anything like this. What I said was that historically, it took us 2-3 months after RTM with previous vSphere releases. As for vSphere 5.5, we will only know when we test out the RTM code, and perform the release planning based on our findings.

We've already seen situations when there were so many changes between vSphere RC and RTM, that we had to re-write and subsequently retest big chunks of code required to support the new release. So, we won't be able to provide any estimations around vSphere 5.5 support until we're done with the RTM code testing.

[yolgezer]

Hi,
Vmware Esxi 5.5 released yesterday ,when it will be supported ?
62tb vmdk is interesting.

[foggy]

Ahmet, please review this topic for the detailed answer.

[Gostev]

Downloading.

[STGdb]

Does VEEAM B&R 7.0 fully support VMware ESXI and vCenter 5.5 or do we need to wait for B&R SP1?

[foggy]

You should wait for the next release, v7 does not support vSphere 5.5, nor it will be supported in the upcoming patch 1.

[STGdb]

Thanks. Downloaded 5.5 and was reviewing the Release Notes. Glad I didn't start to upgrade yet.

[RMullis]

BTW any ETA on patch 1?

[Gostev]

Any day now, however vSphere 5.5 support is not a part of Patch 1.

We have just prepared the vSphere 5.5 environment. We will need 2 weeks to complete the full testing cycle, and plan the release. Things are looking good so far, and we should be able to deliver vSphere 5.5 support in 2013.

[dellock6]

Anton, did you also downloaded vCloud 5.5 now that is out?

Luca.

[CaptainFred]

Any day now, however vSphere 5.5 support is not a part of Patch 1.

We have just prepared the vSphere 5.5 environment. We will need 2 weeks to complete the full testing cycle, and plan the release. Things are looking good so far, and we should be able to deliver vSphere 5.5 support in 2013.

Thats good news

[Gostev]

Anton, did you also downloaded vCloud 5.5 now that is out?

Yes. Some hefty changes there, so this one will probably take longer to fully support.

[LarsWulf]

I know that Veeam currently is not supporting vSphere 5.5 and that are working on it.
But on simple question: Will there only be an update for Veeam 7.0 or also for 6.5 ?

[Vitaliy S.]

Hi Lars,

The update will be available for Veeam B&R 7.0 only.

Thanks!

[Odarchuk]

You should wait for the next release, v7 does not support vSphere 5.5, nor it will be supported in the upcoming patch 1.

When will be available patch 1 ?

[dellock6]

Few hours ago in the weekly forum digest, received by mail:

"Patch #1 is currently in the limited release stage, and should become generally available later this week"

Luca.

[Odarchuk]

Thank you for good news!

[axelklos]

Hi,

we ordered 6 new ESX Hosts and plan to use latest version of Vsphere 5.5. Is the release of latest Veeam version (which supports ESX 5.5) confirmed? If not, is it possible to get a preview of that?

Regards

Axel

[foggy]

Axel, have you reviewed the topic above?

[axelklos]

Axel, have you reviewed the topic above?

Yes is this an "unoffical" confirmation ?

[foggy]

Here is an official information regarding vSphere 5.5 support:

Any day now, however vSphere 5.5 support is not a part of Patch 1.
We have just prepared the vSphere 5.5 environment. We will need 2 weeks to complete the full testing cycle, and plan the release. Things are looking good so far, and we should be able to deliver vSphere 5.5 support in 2013.

[Gostev]

From the same forum digest Luca referenced above:

vSphere 5.5 has also became generally available last week. We have it deployed in our labs, and are currently testing the prototype code built for vSphere 5.5 RC. If all goes as planned, we will release support for both new hypervisors before the year ends (more precise timelines in the next couple of weeks). In the meantime, you can start preparing your backup infrastructure for vSphere 5.5 by upgrading backup proxy servers OS to 64-bit. This is required because starting vSphere 5.5, VMware will ship 64-bit version of vStorage API for Data Protection (VDDK) modules only. Basically, we will continue to support all the same Windows OS versions, but they MUST be 64-bit now, whereas previously it did not matter. If for any reason you are not planning to upgrade to vSphere 5.5 any time soon, then no action is required on your part (you can continue using 32-bit OS for your backup proxies).