Microsoft recently announced additional support scenarios for using Guest Clusters in Azure. In this blog post, let’s have a look how we can build a two node SQL 2016 Guest clustering in Azure using Windows Server 2016 Storage Spaces Direct. Utilizing Guest clusters in Azure enables mission critical application such as a SQL backend to function with greater availability if a single instance fails. By using Failover clustering and also placing virtual machines in an availability set, ensure that the application can work regardless of a hardware failure / Host updates or an application instance failure.
In this blog post let’s looks at creating a Storage Spaces Direct Hyper Converged solution using three virtual machines. For production deployment, it is recommended to use physical servers instead of virtual machines. I will be using Windows Server 2016 Technical Preview 5 version which was just released few days back for this blog post. Before I move any further, I would like to highlight some of the key features introduced part of Windows Server 2016 Technical Preview 5
In this blog post we will look at how we can continue to use Windows Server Technical Preview and extend its expiry date till 1st OCT 2015. At the moment when we login to Server Technical Preview before applying the hotfix, we get following message (I have another blog post earlier regarding this http://nirmalt.com/2015/04/04/this-build-of-windows-will-expire-soon-windows-server-technical-preview/) Checking on Windows Version (winver) Microsoft recently released a hotfix which will extend the time duration of Windows Server Technical Preview.
In this blog post, we will look at configuring Cloud Witness, a new quorum option introduced in Windows Server vNext Technical Preview (OCT 2014 Release). Cloud witness was introduced as an option similar to a File Share Witness, but hosted on Azure without having to maintain any infrastructure within your datacenter. This allows us to have multi-site clusters without having the need to have a 3rd site as a witness.
Cluster Product group presented multiple sessions at TECH2014 which took place in Houston from 12th to 15th May 2014. please find below list of sessions which were presented at the event. 1) ****DCIM-B354 Failover Clustering: What’s New in Windows Server 2012 R2 2) ****DCIM-B364 Step-by-Step to Deploying Microsoft SQL Server 2014 with Cluster Shared Volumes 3) ****DCIM-B349 Software-Defined Storage in Windows Server 2012 R2 and Microsoft System Center 2012 R2
Microsoft has released updated Media files containing Windows Server 2012 R2 / Windows 8.1 Client Update on Volume License Service Center. This new media kit is recommended to be used for any future deployments since it contains all security fixes since RTM. Updated ISO files can be obtained from following sources MSDN (For Evaluation) TECHNET (For Evaluation) Volume Licensing Service Center (Enterprise Deployment) more details please visit http://blogs.technet.com/b/windowsserver/archive/2014/04/14/updated-volume-license-media-available-today-for-windows-server-2012-r2-update.aspx
Microsoft recently released a consolidated update package for Windows Server 2012 R2 and Windows 8.1 Client. this is the new service baseline for Windows Server 2012 R2 systems and it can be either downloaded using Microsoft Download Center or using Windows Update. Microsoft earlier released this update to Microsoft MSDN/TechNet Subscribers and today it will be made available to Volume License customers as an updated Windows Server 2012 R2 ISO media.
In this blog post, we will look at creating a Two Node File Server Cluster Step 01 – Prepare your storage and Networks. In this demonstration I’m using Two Windows Server 2012 R2 Virtual Machines. I have two networks on each VM. One network for client communication and the other for cluster communication. I’m using iSCSI shared storage for this environment. Step 02 – Next step would be for us to install Failover Cluster Features on both nodes.
In this post we will look at how we can add a disk resource to a cluster and also how to convert a disk in to a CSV (Cluster Shared Volume) storage. first step is to have eligible storage available within the cluster. storage could be, any shared storage that you present to your cluster such as Serial Attached SCSI / Fiber Channel / iSCSI or even Shared VHDX. more information on Storage requirements please visit http://technet.
In this blog post we will look at an issue relating to sharing the same iSCSI Storage network for cluster communication. Looking at networking best practices for creating a Windows Server 2012 Failover Cluster, it is recommend that we separate iSCSI storage traffic from Cluster Communication. iSCSI needs to be on a separate dedicated network and it is not recommended to share iSCSI Storage Trafic & Network communication traffic. At the time of cluster being created, it will automatically disable the network for cluster communication if it is used for iSCSI Storage traffic and this will cause the cluster creation to fail.