Vmware 6.0 client chrome update#
If our internal devs were to do that - just slam out an update without thoroughly testing the changes, that could have major implications and cause bigger issues down the road - which is exactly what we don't want.īackups are, what I consider to be, a critical part of an infrastructure - especially production infrastructure. One of the reasons for this is because of their QA process - they don't just release patches for the sake of making a few people happy. It's not my / our only backup product, but at the end of the day its the only one I use probably 49 times out of 50. I've been a long time Veeam user - I find it to be my "go to guy" for VM restores when they are needed. Does this sound like something Symantec would do to you?įirst off, first post, and I registered specifically to comment on this thread. Somehow, I have a feeling that they do not actually support majority of the new vSphere 6 features around data protection - only whatever comes "for free" by swapping the VDDK to a newer version. I am planning to take a look at the depth of their vSphere 6 support soon. I have covered this bug in more details in the weekly forum digest 2 days I actually liked the previous version of your post (where you talked about innovations), you've made a very good point there. It was us who found and reported this bug to VMware - ALL other vendors have missed it in their testing, and just released their vSphere 6 support with it. This bug did not exist in the previous VDDK versions, and can severely impact production environments. Especially when this testing has already resulted in us finding a major VDDK 6.0 bug with SAN transport. What would your customers prefer? Should we cancel it, and release the RC build tomorrow? Either we do this few weeks long stress test, or we released without it. Thing is, long term backup reliability stress testing that we perform before releasing a new platform support simply cannot be accelerated - it can only be cancelled. Why would we do anything different with this particular release? Can you tell me a single good reason why should we be cutting down our standard testing cycles? For many, many years now, we have been very consistent with the time frame of releasing support for the new vSphere releases: about 6 weeks from GA on average.
Vmware 6.0 client chrome software#
We don't believe data protection software should be rushed, and we are also not in any sort of a racing game here. Honestly, your question is best directed to Symantec - may be they can share why on their forums? I cannot know what did they sacrifice to achieve that: quality, features, platform support or (most likely) all of the above? HoFFy wrote:why Symantec has been faster?
0 kommentar(er)
