We help IT Professionals succeed at work.

Windows server 2016 vs 2012 - What is the consensus....

1,553 Views
Last Modified: 2017-04-12
Hi all

We have to do a few server installs and not hearing really good things about 2016 at this point, inclusive of that Veeam is having backup issues with it when running it in a VM.  Anyone running it in Prod, if so for how long?  Based on EOL of 2012.  What do you guys think?

Have a good day!
Comment
Watch Question

Datacenter platform engineer Lindows
CERTIFIED EXPERT
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
I wonder what you mean by "Veeam is having backup issues with it when running it in a VM"
since at the veeam forum, I only find this, which tells quite the opposite: https://forums.veeam.com/microsoft-hyper-v-f25/9-5-hyper-v-known-issues-t38927.html
--
• Application-aware processing of VMs with guest OS other than Windows Server 2016 fails with the “Failed to take in-guest VSS snapshot COM error: Code: 0x80042308” error. This issue is fixed in the recent Windows Updates for the corresponding operating systems.
• Application-aware processing of Active Directory domain controllers running on guest OS other than Windows Server 2016 fails with the “Failed to create VM recovery checkpoint” error (32770). This is a Hyper-V 2016 issue that Microsoft is planning to address in the future update.
• Backing up VMs from Hyper-V cluster in rolling upgrade is supported, however RCT will not be leveraged until the upgrade is completed for all nodes and cluster functional level is upgraded to Windows Server 2016. Keep in mind that VMs virtual hardware version must be upgraded to version 8.0 before RCT can be leveraged on the VM.

Author

Commented:
Here is what I received as of Sunday from Veeam support - it looks as if it is resolved,

"Here is what I found. So this would only apply if the Windows 2016 has ReFS enabled.

Great news that some ReFS users have been waiting for! The March 2017 cumulative update for Windows Server 2016 includes the fix for infamous ReFS issue with 4KB clusters (technically speaking, it affects volumes with 64KB clusters as well, but having 16x less clusters makes it much harder to run into). Please note that just installing the update is not enough – you must also create the registry value to enable more aggressive memory unmapping, and remember to reboot the server after doing so."

THanks!!

Author

Commented:
Thanks for the input!
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
"...just installing the update is not enough – you must also create the registry value to enable more aggressive memory unmapping..."
What registry value is that, could you link it?
Patrick BogersDatacenter platform engineer Lindows
CERTIFIED EXPERT

Commented:
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Thanks. I also wonder, how to recognize this "memory pressure" as Microsoft calls it. What process would consume much RAM?
Cold you also link the original Veeam article, please?
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.