![]() ![]() Gostev wrote:Not necessarily, as we have been working with VMware to deliver full support for vSphere 6 since the first vSphere 6 Technology Preview build, and we do have the code that works with RC. However, VMware has a history of implementing significant changes between RC and RTM, which once required us to rewrite the entire engine component - and when something like this happens, we can no longer rush the release due to long reliability stress testing being required.Īnd yes, on top of all the usual considerations, having the brand new storage technology in the picture most certainly adds significant risks and reduces predictability comparing to all previous vSphere releases. Not necessarily, as we have been working with VMware to deliver full support for vSphere 6 since the first vSphere 6 Technology Preview build, and we do have the code that works with RC. Should we read that to mean, you expect 2 to 3 months to be an "optimistic" timeline? Saying that's been the norm, but then "side noting" that this is "certainly been the most complex release in the history of vSphere release for us to support" kind of makes it sound like you expect this to be a while. ![]() I just recall chatting with a Veeam sales guy once back when you were getting close to supporting vSphere 5.5, and I remember him saying that you guys don't get started, at all, until the new version of vSphere goes RTM, which I thought was about the dumbest thing I had ever heard considering the release Betas and RCs months ahead of time. PS: Apologies in advance if the 2-3 month historical lag time already takes into account looking at Betas and RCs as soon as they come out (i.e., it's really 6 months worth of work, and you guys already do get started before RTM and just make tweaks when the final bits are released). While I'm certainly grateful that Veeam is faster to market than anyone else, wouldn't it make sense to make it a goal to continue to shorten that window? Increasing that delta between you and everyone else just gives Veeam that much more time to be the only backup vendor to support a new release, which should translate to better marketing and perhaps even better sales. I mean, isn't that kind of one of the big reasons VMware and other companies release Betas / RCs - so the development community can see what's coming and prepare for it? It would seem to me that if you just start looking a the Betas and RCs, you could at least have an idea of whats going on ahead of RTM so you can begin building in the code required in order to work with it, and be ahead of the game instead of playing catch up. You guys have access to the Betas and RCs that have been out for a while, right? If I can get onto the beta program, surely Veeam can too? #Veeam 8.0 vmware 6.0 PatchIf you have not already installed patch 3 I suggest you do that now.So. Looking at their KB article 1751 we now see “ Upgrading vCenter or ESX(i) hosts may result in duplicate hosts appearing under Managed Servers, causing jobs to fail with object not found errors“. Veeam has released patch 3 for Veeam Backup & Replication 6.5 which now solves this issue. You can manually go in and remove these, however make sure you make a database backup first and if you feel unsure then do not hesitate to call Veeam and ask for their help to resolve this. What seems to happen sometimes are that the ESXi host(s) upgraded from fx 4.1 to 5.1 will stay in the SQL database. #4 Add the standalone hosts in the backup job ![]() #2 Add each host as a standalone host with correct credentials #1 Remove the vCenter from Veeam (unfortunately this means deleting all jobs currently using it or as a minimum remove the VMs from the job). I am sure this is something that has been fixed in Veeam B&R 6.5 (soon to be released). After upgrading their VMware ESXi hosts and vCenter to 5.1 (unsupported) they could suddenly no longer backup VMs one of their two hosts using Veeam.įailed to login to “” by SOAP, port 443, user “”, proxy srv: port:0Ĭannot complete login due to an incorrect user name or password. ![]() Today one of our regular customers called with a wierd error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |