{"id":14512,"date":"2013-05-02T13:00:00","date_gmt":"2013-05-02T12:00:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=14512"},"modified":"2013-05-02T13:00:00","modified_gmt":"2013-05-02T12:00:00","slug":"maintenance-windows-for-patching-a-ws2012-hyper-v-cluster-make-no-sense-to-me","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=14512","title":{"rendered":"Maintenance Windows For Patching A WS2012 Hyper-V Cluster Make No Sense To Me"},"content":{"rendered":"
Here I am, working on a Sunday (when I wrote this post).\u00a0 It\u2019s not so bad, it\u2019s raining outside, so that rules out going for a walk or doing some photography.\u00a0 I jumped onto Twitter and saw someone moaning that they had to work on a Sunday to patch their Hyper-V cluster.\u00a0 To me that\u2019s a WTF! moment.<\/div>\n
\"image\"<\/a><\/div>\n
Windows Server 2012 Failover Clustering gives us Cluster Aware Updating (CAU).\u00a0 Using this you can patch a Hyper-V cluster without getting manually involved in \u201cmaintenance modes\u201d and Live Migration.\u00a0 The process will:<\/div>\n
    \n
  1. Download updates from Microsoft, WSUS, etc, or a file share, to the hosts (and this is expandable to 3rd party updates such as OEMs).<\/li>\n
  2. Put host 1 into maintenance mode \u2013 that drains it of virtual machines using Live Migration and \u2026 Quick Migration (for VMs marked as LOW priority, by default, which I DO NOT agree with).\u00a0 You can make it 100% Live Migration<\/a> so no services suffer an outage during the moves.\u00a0 The more bandwidth your Live Migration network has, the faster this will be \u2013 using 1 Gbps networking for 512 GB RAM hosts is stupid!<\/li>\n
  3. Patch and reboot host 1<\/li>\n
  4. Wait for host 1 to come back online<\/li>\n
  5. Bring host 1 out of maintenance mode<\/li>\n
  6. Repeat steps 2-5 for each host<\/li>\n<\/ol>\n
    This process orchestrates the entire process.\u00a0 All you\u2019ve go to do is make it happen:<\/div>\n