Sure enough, somebody HAD to post something like this sooner or later, without even reading the topic. It is almost inevitable, always just a matter of time
At first, your question was not removed. It has nothing to deal with vSphere 5.1, and has been moved to the existing corresponding discussion about this issue Veeam 6 and ESXi 5 - SSH Failed To Connect
. In future, kindly please search the forum before you post - this will save you a lot of time.
Also earlier in this topic, I have explained that all basic B&R 6.1 functionality (including all job types) work just fine on vSphere 5.1 based on our testing results. No official support, but the jobs should be running just fine (as many users have already indicated above too, anyway).
Now, regarding timely vSphere 5.1 support - as I've already explained on the first page, we would be more than happy to provide you with new vSphere version support right at GA - if VMware provided partners with RTM code at least 1-2 month in advance, like some other platform vendors do. However, instead VMware's standard practice is to provide RTM code to everyone on the same day. I am sure you understand that it is not realistic for us to implement and test new platform support in 1 day. So, think twice who you should be unhappy with. It's not like VMware does not realize that the ecosystem will not be ready, if they are given RTM code along with the actual customers?
Of course, we did have earlier access to beta and RC builds, however if you read this topic carefully, RTM code introduced new issues which did not exist in the final RC build, and we now have to work on addressing those. And, we also have to rollback code for workarounds around RC code issues that RTM build did resolve (to prevent unexpected effects). And after all that is done, we need to perform full regressive functionality testing against the RTM code. Untested code, you can use today if you want to (I am talking about using B&R 6.1 against vSphere 5.1) - but our commitment for official support requires certain procedures to be performed, and all product features supported (not just some of them).
As you can see, there is much work to be done for us after we get RTM code. And I must say, I have seen quite a few VMware releases in the past 5 years, but I've never seen THIS MANY changes between final RC and RTM build (where time difference between them was just a few weeks).
Finally, keep in mind that even VMware itself does not support vSphere 5.1 yet in some of their *most strategic* offerings, such as VMware View. And when even VMware does yet not provide vSphere 5.1 support (having direct access to all vSphere builds and plans), what do you expect from vendors receiving RTM code on the same day with yourself?