This question blurs the lines a bit between a V13 and V12 question.
I understand Veeam generally wants customers on the latest version and I think there's a lot of merit to this, but this is putting a bit of a pinch on customers/administrators. Alleviating the pressure on us specifically around the nature of security patches/updates would be much appreciated.
The all versions sticky says that the V13 is the GA/RTM "from September 3, 2023" [sic - I'm interpreting as 2025-09-03].
The Veeam Product Lifecycle webpage says that V12 versions reach the "end of fix" date at the next GA date. I take this to mean that (per the letter of the policy) that V12's end of fix date is end of September 2025.
Is this an unintended consequence? Or is this a typo and V13 is not yet a GA until Q4 (that would be implied by the V13 FAQ Sticky)? Or is Veeam really going to push customers to V13 when the 13.0.1 patch drops in Q4?
What happens if there's a security vulnerability impacting V12 versions? Are customers going to be pressured to upgrade to V13 to remediate vulnerabilities? Is Veeam going to support V12 for security vulnerabilities ("(exceptions may be made on a case-by-case basis)" as noted on the Lifecycle page)?
-
- Enthusiast
- Posts: 28
- Liked: 9 times
- Joined: Oct 09, 2024 6:17 pm
- Contact:
-
- Chief Product Officer
- Posts: 32546
- Liked: 7864 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [V13] [V12] Veeam Product Lifecycle Question
We're patching all security vulnerabilities until End of Support (and sometimes slightly beyond) and have been doing so for all previous versions.
The exceptions mentioned in the Support Policy are for non-security related fixes.
The exceptions mentioned in the Support Policy are for non-security related fixes.
-
- Enthusiast
- Posts: 28
- Liked: 9 times
- Joined: Oct 09, 2024 6:17 pm
- Contact:
Re: [V13] [V12] Veeam Product Lifecycle Question
Noted - that gives a lot of reassurance. Maybe the lifecycle policy I linked could use a review on the terminology it uses to carve out security vulnerabilities into the end of support definition. I think the delineation of quality/bug fixes and security fixes is an important one.
-
- Chief Product Officer
- Posts: 32546
- Liked: 7864 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [V13] [V12] Veeam Product Lifecycle Question
Agree, @m_zolkin FYI
-
- Veeam Software
- Posts: 38
- Liked: 17 times
- Joined: Aug 26, 2009 1:13 pm
- Full Name: Mike Zolkin
- Location: St. Petersburg, Florida
- Contact:
Re: [V13] [V12] Veeam Product Lifecycle Question
Good idea, thanks for the heads up. We will update the wording soon.
VP, WW Customer Technical Support
Who is online
Users browsing this forum: Amazon [Bot], Google [Bot] and 39 guests