-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Apr 05, 2018 8:34 pm
- Full Name: Ryan Mortier
- Contact:
Is v9.5 u3a an alpha build or is it stable for production use?
I plan to upgrade vSphere to 6.7 and before that I was wondering if this is a stable build first.
-
- Veteran
- Posts: 487
- Liked: 106 times
- Joined: Dec 08, 2014 2:58 pm
- Full Name: Steve Krause
- Contact:
Re: Is v9.5 u3a an alpha build or is it stable for production use?
Yes it is a stable release.
Veeam does not typically put updates out for general download that are not considered stable and fully supported. The only people who are in their alpha/beta channels are specific targeted customers and partners.
Veeam does not typically put updates out for general download that are not considered stable and fully supported. The only people who are in their alpha/beta channels are specific targeted customers and partners.
Steve Krause
Veeam Certified Architect
Veeam Certified Architect
-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Apr 05, 2018 8:34 pm
- Full Name: Ryan Mortier
- Contact:
Re: Is v9.5 u3a an alpha build or is it stable for production use?
Thanks, I was just confused about the "a" in the version. Not sure what it stands for.
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Is v9.5 u3a an alpha build or is it stable for production use?
Smaller updates that are mostly focused on platform support typically get a character prefix, while major releases increment digit Update 1/2/3/4, etc.
It's stable release that can be safely used in production.
Thanks.
It's stable release that can be safely used in production.
Thanks.
-
- Chief Product Officer
- Posts: 31816
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Is v9.5 u3a an alpha build or is it stable for production use?
This was adopted from how VMware labels the new builds each time they reissue one, so that people could distinguish between builds more easily than with 6-digit build numbers. For example, in the past few months we've seen vSphere 6.7, vSphere 6.7a, vSphere 6.7b and so on. They are actually at vSphere 6.7d already, as of today
Update 3a is a significant update though, so it should not have used "a" to start with. And at some point, the intention was to call it Update 4. There's a whole story behind that, but basically we were forced to call it Update 3a
Who is online
Users browsing this forum: Bing [Bot] and 95 guests