<div>
I wonder what you mean by &quot;Veeam is having backup issues with it when running it in a VM&quot;<br />
since at the veeam forum, I only find this, which tells quite the opposite: <a href="https://forums.veeam.com/microsoft-hyper-v-f25/9-5-hyper-v-known-issues-t38927.html" rel="ugc">https://forums.veeam.com/microsoft-hyper-v-f25/9-5-hyper-v-known-issues-t38927.html</a><br />
--<br />
• Application-aware processing of VMs <i>with guest OS other than Windows Server 2016 </i>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.<br />
• Application-aware processing of Active Directory domain controllers running <i>on guest OS other than Windows Server 2016</i> 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.<br />
• Backing up VMs from Hyper-V cluster in rolling upgrade is supported, however RCT will not be leveraged <i>until the upgrade is completed for all nodes and cluster functional level is upgraded to Windows Server 2016</i>. Keep in mind that VMs virtual hardware version must be upgraded to version 8.0 before RCT can be leveraged on the VM.
</div>


<div>
Here is what I received as of Sunday from Veeam support - it looks as if it is resolved, <br />
<br />
&quot;Here is what I found. So this would only apply if the Windows 2016 has ReFS enabled.<br />
<br />
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.&quot;<br />
<br />
THanks!!
</div>


<div>
&quot;...just installing the update is not enough – you must also create the registry value to enable more aggressive memory unmapping...&quot;<br />
What registry value is that, could you link it?
</div>


<div>
That would be one of these three<br />
<a href="https://support.microsoft.com/en-us/help/4016173/fix-heavy-memory-usage-in-refs-on-windows-server-2016-and-windows-10" rel="ugc">https://support.microsoft.com/en-us/help/4016173/fix-heavy-memory-usage-in-refs-on-windows-server-2016-and-windows-10</a>
</div>


<div>
Thanks. I also wonder, how to recognize this &quot;memory pressure&quot; as Microsoft calls it. What process would consume much RAM? <br />
Cold you also link the original Veeam article, please?
</div>


<div>
<div class="content wysiwyg-content">
Hi all<br />
<br />
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. &nbsp;Anyone running it in Prod, if so for how long? &nbsp;Based on EOL of 2012. &nbsp;What do you guys think?<br />
<br />
Have a good day!
</div>
</div>


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!

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

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Veeam® has pioneered a new market of Availability for the Always-On Enterprise™ by helping organizations meet recovery time and point objectives (RTPO™) of less than 15 minutes for all applications and data. Veeam develops backup, disaster recovery and virtualization management software for VMware and Hyper-V virtual environments. The company focuses on products that help with virtualized workloads, reduce downtime, and ensure the system Availability required by service-level agreements.

Veeam

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.