Hi, i've been trawling a number of posts on here regarding using ReFs repositories, early issues with 2016 and issues with 2019. Im currently using Veeam / ReFs in a smaller environment with Server 2016 1607 with good results and no major issues
We're building a new, much larger environment reusing some HPE Apollo Gen 9 servers which only Support server 2016 (at this time, we have applied for an exception from HPE support for 2019).
So my question is.. if you were deploying a Veeam Refs environment today on Server 2016 would you stick with LTSC / 1607 or go Semi-Annual? Are there any stability and improvements improvements in Semi-annual which arn't in a fully patched 1607 OS?
Many thanks!
-
- Enthusiast
- Posts: 81
- Liked: never
- Joined: Nov 06, 2013 3:15 pm
- Full Name: J Cook
- Contact:
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Veeam with ReFs and 2016
I recommend you stick to Server 2016 LTSC for guaranteed absence of surprises
-
- Enthusiast
- Posts: 81
- Liked: never
- Joined: Nov 06, 2013 3:15 pm
- Full Name: J Cook
- Contact:
Re: Veeam with ReFs and 2016
Thanks for the response that's what I was thinking! Out of interest... is 2019 generally ok now with Veeam & RefS or still throwing in a few curve balls?
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Veeam with ReFs and 2016
Only 2019 SAC releases are OK at this time (1903 and 1909).
For LTSC, they only just now finally found the issue that was causing all the problems. So it's a question of waiting for an official update to be released. Which can potentially take months, based on the history. There's a big thread about this on the main VBR forum with updates from people testing the private fix.
For LTSC, they only just now finally found the issue that was causing all the problems. So it's a question of waiting for an official update to be released. Which can potentially take months, based on the history. There's a big thread about this on the main VBR forum with updates from people testing the private fix.
Who is online
Users browsing this forum: No registered users and 11 guests