Looking back at the previous articles in our “How-to-Core basics”, we have managed to install the Core version of Windows Server 2016. As well, the required networks were set, and the storage for the virtual machines was created. In the final part of the trilogy, I’ll cover the steps left to prepare the environment in order to make your production highly available and fault-tolerant.

In part of my job, I audit some Hyper-V clusters to remediate issues such as Live Migration. Most of the time, Live Migration part is not well configured. For example, the wrong network is selected or authentication is left to CredSSP. In this topic, I’ll show you how I configure Live Migration in Hyper-V clusters (S2D or not).

Greetings, fellow sysadmins and everyone who is still wondering how to make their SQL server highly available! You’re just in time since I’ve prepared for you detailed guidelines with pictures and explanations on how to achieve this goal by using the SQL Server AlwaysOn approach! The great thing is that we are also going to configure and review the full-fledged system with the disaster recovery scenarios implemented. I’ve decided to break this topic into 3 parts. First, we will go through the process of configuring AlwaysOn Failover Cluster Instance (FCI), the next part of this series will cover the deployment of a DR site for our cluster using AlwaysOn Availability Groups, and finally, we will learn more about how to achieve the same using 3rd party software.

At Microsoft Build 2017, the Nested Virtualization support in Azure has been announced. Now you can enable nested virtualization using the Dv3 and Ev3 VM sizes – not a wide variety, but Microsoft is going to expand the support for more VM sizes in the upcoming months.