vSphere 5 was released (GA) on 24 August, 2011. Immediately after the release customers started asking us if we supported vSphere 5 with Veeam Backup & Replication. Some other vendors claimed vSphere 5 support even before it was released, so what took us so long?
We released our hotfix on 20 October, 2011, that means it took us a full 57 days to release a hotfix for Veeam Backup & Replication to FULLY support vSphere 5. One of the main issues with Veeam Backup & Replication 5.0.2 was that it didn’t work for all processing modes with VMSF5 (just like every other vendor at the time of this writing). A processing mode popular with our customers is direct SAN access utilizing the vStorage API for Data Protection (VADP). In order to support direct SAN access for VMFS 5, we had to move to the latest version of the VDDK API which was only made available the same day as the GA release of vSphere 5.
- 57 days to incorporate a new version of a low-level API
- 1368 hours to fully test
- 82,080 minutes to fix things that worked previously
So, rather than trying to shout from the rooftops that we supported vSphere 5 the day it was released (or even weeks before), we wanted to make sure everything worked. We make backup and DR software after all, and we don’t want our customers getting into a mess with their production data based on claims by marketing. I think Anton did a good job of explaining our position in the forums, please take a moment to read his post.
Before you go checking our downloads page for the hotfix, please be advised that it’s only available through Veeam support. Since this isn’t a full release, and not all of our customers will need it, we are only making it available via support. Of course, Veeam Backup & Replication v6 will have full support of vSphere 5 when it’s released later this year, and that will be our official release vehicle for vSphere 5.