vSphere 5 Support

[gerdawg]

It is not:

Here is a good technet thread on it:
http://social.technet.microsoft.com/For ... e33fe0511c

I believe you are limited to some form of iSCSI/FC or samba setup for Hyper-V to be supported.

[Gostev]

OK, back to the main topic. As promised, here is an update on vSphere 5 RTM code compatibility for Veeam Backup & Replication 5.0.2

Our QC has found the following incompatibilities:
• Incremental replication passes to ESXi 5 target fail (initial pass works normally).
• Backup in direct SAN access mode will fail for VM disks on VMFS5 volumes.
• SureBackup is not functional when ESXi 5 is used to host the virtual lab.
• Multi-OS FLR is not functional when ESXi 5 is used to run the FLR helper virtual appliance.
• vCenter Server 5.0 causes job to fails with the "Inactive datastore" error. Jobs on standalone ESXi 5 hosts do not seem to be affected by the issue, but all jobs configured through the vCenter Server 5.0 connection are.

At a first sight, all issues are easy to fix. We plan to make the hotfix addressing all of the issues above available through support in about 2 weeks. I will update this topic once the hotfix is available.

Thanks!

[digitlman]

This is why we always wait a month or three after a new version of software for the kinks to get worked out.

Will this delay v6? Is it still looking at a Q42011 release?

[DAPBENJAMIN]

Hi,

I am seeing exactly the same problems as Gostev! I hope they are fixed soon!

Regards,

Darren

[Gostev]

This is why we always wait a month or three after a new version of software for the kinks to get worked out.

Yep, always a good thing to wait until dust settles with the new major release when talking about core platform. In fact, I know that most of our larger customers typically validate the new hypervisor code in test lab for months (!) before going ahead with production use. Remember that earlier VMware service pack release when VMs would not start up after being shut down? This caused "production down" all over the world for customers who had jumped the gun... no guarantees something like this will never happens again.

First ESXi 5 patch was announced on the same day when vSphere 5 went GA... enough said. And it is not some issue with VMware, it's in the nature of software development. Microsoft "SP1 rule" is there as well most people prefer not do deploy major releases until SP1 is out.

Will this delay v6? Is it still looking at a Q42011 release?

Only slightly (some extra R&D and QC time is needed, but not much since we need to fix these issues in v6 anyway). Definitely still Q4 2011 release for v6, and more like the middle of Q4, than the end.

[flakpyro]

OK, back to the main topic. As promised, here is an update on vSphere 5 RTM code compatibility for Veeam Backup & Replication 5.0.2

Our QC has found the following incompatibilities:
• Incremental replication passes to ESXi 5 target fail (initial pass works normally).
• Backup in direct SAN access mode will fail for VM disks on VMFS5 volumes.
• SureBackup is not functional when ESXi 5 is used to host the virtual lab.
• Multi-OS FLR is not functional when ESXi 5 is used to run the FLR helper virtual appliance.
• vCenter Server 5.0 causes job to fails with the "Inactive datastore" error. Jobs on standalone ESXi 5 hosts do not seem to be affected by the issue, but all jobs configured through the vCenter Server 5.0 connection are.

At a first sight, all issues are easy to fix. We plan to make the hotfix addressing all of the issues above available through support in about 2 weeks. I will update this topic once the hotfix is available.

Thanks!

Very strange, in our testing here we have been able to backup via vCenter 5.0 as long as the volume is VMFS3, VMFS5 volumes fail. (This is via SAN mode.)

In Hot Add mode backing up via the ESXi host directly fails but backing up via vCenter 5.0 works as expected, once again as long as the Volume is VMFS3.

VMware tools quince is disabled as well.

[ThomasMc]

Bit OT here but since this is the first major release that VMware has done since we have been virtualizing is it normal to just upgrade as they release it? I would have thought people would want to test for a good couple of months before deploying 5.

[AlexWhit]

is there an update when the hotfix will be out? i am wanting to upgrade to ESXi 5 for the USB3 option.

thanks

[Gostev]

Reading through my post above, hotfix development should take about 2 weeks. I will provide an update at the end of the next week. Thanks!

[nicko82]

Any update on the hotfix, I would like to start testing this ASAP?

[dionrowney]

Reading through my post above, hotfix development should take about 2 weeks. I will provide an update at the end of the next week. Thanks!

My calendaring math skills say "end of the next week" = Sept 23.

[RHofland]

Waiting for this hotfix, my test environment wants to be backup'd.

[nicko82]

Waiting for this hotfix, my test environment wants to be backup'd.

Actually the backup component works fine with vSphere 5, its only replication that doesn't work for me.

[agentduke]

I see a lot of criticism floating about upgrading to vSphere5 from vSphere 4.1. It should be noted that many people are forced to do this by VMWare themselves. For products under support, they provide a limited window in which to upgrade the product for free. However, they stipulate that you must immediately discontinue use of your previous key in conjunction with the upgrade.

So while many see fit to 'fault' their peers for early adoption, not all of this is their fault. A great many are being forced to do this by VMWare themselves. VMWare is interested in adoption....they really don't care that Veeam doesn't work yet. Just thought I'd point that out so we can get past some of that criticism and onto a fix. Those of us in the middle-ground, who are testing this in a lab, have the luxury of testing without such pressure.

[chrmol]

Could we be lucky to see any hotfix today?
(It would be nice to spend the weekend on my home lab env.)