{"id":7755,"date":"2016-07-05T09:00:43","date_gmt":"2016-07-05T16:00:43","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/windowsserver\/?p=7755"},"modified":"2024-03-11T09:19:28","modified_gmt":"2024-03-11T16:19:28","slug":"whats-new-in-failover-clustering-05-resilient-private-cloud","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/windows-server\/blog\/2016\/07\/05\/whats-new-in-failover-clustering-05-resilient-private-cloud\/","title":{"rendered":"What\u2019s new in failover clustering: #05 Resilient private cloud"},"content":{"rendered":"

This post was authored by Subhasish Bhattacharya, Program Manager, Windows Server.<\/em><\/p>\n

Introduction<\/h2>\n

In the past, in a world of reliable but expensive SANs, an aggressive high-availability strategy designed to fail fast was most optimal. The health of the system would be closely monitored to detect issues and react quickly and swiftly. This minimized downtime when catastrophic failures occurred.<\/p>\n

In today\u2019s cloud-scale environments, commonly comprising of commodity hardware, transient failures have become more common than hard failures. These transient compute and storage failures in commodity hardware are triggered by common events such as switch reset, packet loss, latency, and spanning tree convergence. In this new world, reacting aggressively to handle transient failures can cause more downtime than it prevents.<\/p>\n

The storage and compute stack in Windows Server 2016 has been designed to optimize both high availability and resiliency. In a Software Defined Datacenter, we must assume infrastructure will break and it is imperative that software is resilient. At the same time, it is not acceptable to have degraded Virtual Machine (VM) availability.<\/p>\n

Resilient private clouds: Compute and storage virtual machine resiliency<\/h2>\n

Windows Server 2016 introduces increased VM resiliency features to address both:<\/p>\n