Get started with Cluster OS Rolling Upgrade in Windows Server 2016! Download the evaluation version!
Cluster Operating System (OS) Rolling Upgrade is a new feature in Windows Server Technical Preview that enables an administrator to upgrade the operating system of the cluster nodes from Windows Server 2012 R2 to Windows Server Technical Preview without stopping the Hyper-V or the Scale-Out File Server workloads. Using this feature, the downtime penalties against Service Level Agreements (SLA) can be avoided.
Cluster OS Rolling Upgrade provides the following benefits:
- Hyper-V virtual machine and Scale-out File Server workloads can be upgraded from Windows Server 2012 R2 to Windows Server Technical Preview without downtime. Other cluster workloads will be unavailable during the time it takes to failover to Windows Server Technical Preview.
- It does not require any additional hardware.
- The cluster does not need to be stopped or restarted.
- A new cluster is not required. In addition, existing cluster objects stored in Active Directory are used.
- The upgrade process is reversible until the customer crosses the “point-of-no-return”, when all cluster nodes are running Windows Server Technical Preview, and when the Update-ClusterFunctionalLevel PowerShell cmdlet is run.
- The cluster can support patching and maintenance operations while running in the mixed-OS mode.
- It supports automation via PowerShell and WMI.
- The ClusterFunctionalLevel property indicates the state of the cluster on Windows Server Technical Preview cluster nodes.
This guide describes the various stages of the Cluster OS Rolling Upgrade process, installation steps, feature limitations and frequently asked questions (FAQs), and is applicable to the following Cluster OS Rolling Upgrade scenarios in Windows Server Technical Preview:
- Hyper-V clusters
- Scale-Out File Server clusters
The following scenarios are not supported in Windows Server Technical Preview:
- Cluster OS Rolling Upgrade of a cluster using storage with the Data Deduplication feature
- Cluster OS Rolling Upgrade of virtual machines with Data Protection Manager (DPM) backups
- Cluster OS Rolling Upgrade of guest clusters using virtual hard disk (.vhdx file) as shared storage
|This preview release should not be used in production environments.|
Cluster OS Rolling Upgrade Process :
The Windows Server Failover Cluster Management Pack provides both proactive and reactive monitoring of your Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 failover cluster deployments. It monitors Cluster services components—such as nodes, networks, resources, and resource groups—to report issues that can cause downtime or poor performance.
The monitoring provided by this management pack includes availability and configuration monitoring. In addition to health monitoring capabilities, this management pack includes dashboard views, extensive knowledge with embedded inline tasks, and views that enable near real-time diagnosis and resolution of detected issues.
With this management pack, Information Technology (IT) administrators can automate one-to-many management of users and computers, simplifying administrative tasks and reducing IT costs. Administrators can efficiently implement security settings, enforce IT policies, and distribute software consistently across a given site, domain, or range of organizational units.
This white paper demonstrates the capabilities and performance for Violin Windows Flash Array (WFA), a next generation All-Flash Array storage platform. With the joint efforts of Microsoft and Violin Memory, WFA provides built-in high performance, availability and scalability by the tight integration of Violin’s All Flash Array and Microsoft Windows Server 2012 R2 Scale-Out File Server Cluster.
Our configuration and requirements before we begin the Guest SQL 2014 Cluster with Shared VHDX on a Hyper-V Cluster :
- Microsoft Hyper-V 2012 R2 Cluster is running with Cluster Shared Volumes.
- We made Two virtual Machines with Microsoft Windows Server 2012 R2 called SQL01 and SQL02
- Networking Two NICS : One on the Production Switch and NIC two on the Heart Beat Switch.
This step shows how to create and then share a virtual hard disk that is in the .vhdx file format. Repeat this step for each shared .vhdx file that you want to add. For example, you may want to add one or more shared disks that will act as data disks, and a separate shared disk that you can designate as the disk witness for the guest failover cluster.
- In Failover Cluster Manager, expand the cluster name, and then click Roles.
- In the Roles pane, right-click the virtual machine on which you want to add a shared virtual hard disk, and then click Settings.
- In the virtual machine settings, under Hardware, click SCSI Controller.
- In the details pane, click Hard Drive, and then click Add.
- In the Hard Drive details pane, under Virtual hard disk, click New.The New Virtual Hard Disk Wizard opens.
- On the Before You Begin page, click Next.
- On the Choose Disk Format page, accept the default format of VHDX, and then click Next.
Note To share the virtual hard disk, the format must be .vhdx.
- On the Choose Disk Type page, select Fixed size or Dynamically expanding, and then click Next.
Note A differencing disk is not supported for a shared virtual hard disk.
- On the Specify Name and Location page, do the following:
- In the Name box, enter the name of the shared virtual hard disk.
- In the Location box, enter the path of the shared storage location.For Scenario 1, where the shared storage is a CSV disk, enter the path:C:\ClusterStorage\VolumeX, where C:\ represents the system drive, and X represents the desired CSV volume number.
For Scenario 2, where the shared storage is an SMB file share, specify the path:
\\ServerName\ShareName, where ServerName represents the client access point for the Scale-Out File Server, and ShareName represents the name of the SMB file share.
- Click Next.
- On the Configure Disk page, accept the default option of Create a new blank virtual hard disk, specify the desired size, and then click Next.
- On the Completing the New Virtual Hard Disk Wizard page, review the configuration, and then click Finish.
Important If the virtual machine is running, do not click Apply in the virtual machine settings before you continue to the next procedure. If you do click Apply on a running virtual machine, you will need to stop the virtual machine or remove and then add the virtual hard disk without clicking Apply.
- In the virtual machine settings, under SCSI Controller, expand the hard drive that you created in the previous procedure.
- Click Advanced Features.
- In the details pane, select the Enable virtual hard disk sharing check box.
Note If the check box appears dimmed and is unavailable, you can do either of the following:
- Remove and then add the virtual hard disk to the running virtual machine. When you do, ensure that you do not click Apply when the New Virtual Hard Disk Wizard completes. Instead, immediately configure sharing in Advanced Features.
- Stop the virtual machine, and then select the Enable virtual hard disk sharing check box.
- Click Apply, and then click OK.
- Add the virtual hard disk to each virtual machine that will use the shared .vhdx file. When you do, repeat this procedure to enable virtual hard disk sharing for each virtual machine that will use the disk.
|To share a virtual hard disk by using Windows PowerShell, use the Add-VMHardDiskDrive cmdlet with the –ShareVirtualDisk parameter. You must run this command as an administrator on the Hyper-V host for each virtual machine that will use the shared .vhdx file. For example, the following command adds a shared virtual hard disk (Data1.vhdx) on volume 1 of CSV to a virtual machine that is named VM1.
For the Second Guest clusternode you will add the same VHDX files you created on the first Guest clusternode and share them also like on the first clusternode.
So now we have a Shared Quorum Disk and a Shared Data Disk
The next steps :
- Bring the disks Online on the first Guest node with Disk Management
- Install Failover Cluster on both nodes.
- Make a two node Cluster
- Install a Microsoft SQL 2014 Guest Cluster.
Install Microsoft Failover Cluster.
Install Microsoft SQL 2014 Server for Clustering.
Microsoft SQL 2014 Server is installed on the Guest Cluster on top of an Hyper-V 2012 R2 Cluster
Guest SQL 2014 Cluster is running on Hyper-V 2012 R2.
So now we are ready for installing Microsoft SPF and Windows Azure Pack for Windows Server 2012 R2 🙂
We have the following configuration :
- Microsoft Operating System is Windows Server 2012 R2 in a Single forest.
- Microsoft Windows Server 2012 R2 Hyper-V Cluster
- Microsoft System Center 2012 R2 Virtual Machine Manager
- Microsoft SQL 2012 SP1
Here you see the Step-by-Step guide to add a Hyper-v node to the Cluster with System Center 2012 R2 Virtual Machine Manager :
Go to all Hosts and add the new Hyper-V node into SCVMM with this wizard.
When you see the new Hyper-V host in System Center 2012 R2 Virtual Machine Manager, you have to setup the host with all the settings from Virtual Machine Manager by opening
the properties of the new host.
Here you set the right NICs to the Logical networks.
Here we set the following NICs :
- Production network
- Management network
- Live Migration network
- Heartbeat network
After that we set the high available virtual Switches for the new Hyper-V Node :
Then you have to add the virtual NIC to the Virtual Switch :
For production we set two NICs into a Team for capacity :
When all of the properties are set, click on OK and the settings will be provisioned to the new Hyper-V node.
Before we add the new Hyper-V node to the Cluster, you can validate the Hyper-V Cluster if it’s still good and healty :
When the running Hyper-V Cluster is validated and good we can add the new Hyper-V node to the Cluster with System Center 2012 R2 Virtual Machine Manager :
This is the first of five blog posts “From Microsoft Private Cloud to Hybrid Cloud Services”.
Here you can find our Configuration hardware on-premisses and the Start of this blog series.
PRIVATE CLOUD Infrastructure :
Before we start with installing Microsoft Windows Server 2012 R2 on our hardware, it is important to check your vendor support for Windows Server 2012 R2.
For production is vendor support very important ! (Check this for your own hardware configuration first)
Microsoft built a lot of drivers into Operating System W2012R2, we use DELL Power Edge Servers and found the following about support :
Our Dell Power Edge Servers (R410 – R610 – R710 – M620) hardware configuration drivers are in the box of Windows Server 2012 R2 🙂
We already had Microsoft Windows Server 2012 Datacenter edition installed in our forest called ICTCUMULUS, with the DELL management DVD for W2012.
Dell Support & Drivers for the Power Edge R710
We successfully upgraded all the Servers from Windows Server 2012 => Windows Server 2012 R2 and we raised domain and forest functional level to R2 :
Here you see the configuration step-by step guide for Microsoft Windows Server 2012 R2 Hyper-V Cluster :
We started with building the production Teams on each Hyper-V node with Microsoft Windows Server 2012 R2 NIC-Teaming :
Enable NIC-Teaming on the local Server with Server Manager
Our two 1 Gbit NICs are both active for the capacity
- NIC 1+2 Production Team
- NIC 3 CSV for Storage (I-SCSI Trafic)
- NIC4 Heartbeat network for Cluster.
Now we have network configured we can attach the I-SCSI LUNS to the Server, with our Dell Powervault MD3200i storage box :
With the Storage Manager of Dell we made a Host Group “Hyper-V_Cluster” with the four Hyper-V nodes.
There we provision 5 LUNS ( 4 x VDISK of 1TB and 1 x VDISK for QUORUM) for the Microsoft Windows Server 2012 R2 Hyper-V nodes.
With iSCSI Initiator of Windows Server 2012 R2 we attach the storage which is provisioned with the Dell Storage Manager.
Now we have the storage presented to the Hyper-V host and can we configure the LUNS with Diskmanagement :
Do this with all the LUNS and give them the right Volume Label like for example CVS1, CSV2, CSV3, CSV4….
Now we Have Networking and Storage ready to go, we can install the Features Hyper-V and Failover Clustering of Windows Server 2012 R2.
Install prerequisite .net Framework 3.5 via de command prompt. Make sure you mount the Windows 2012 DVD in D:
Run as Administrator CMD.exe and type the following commando : dism /online /enable-feature /all /featurename:NetFx3 /source:d:\sources\sxs
- Install the following features of Windows Server 2012 R2 : Hyper-V and Failovercluster
- Update Software via Windows Update.
- Open failover Cluster Manager
In our report we had a message about Gateway :
Here we give the Cluster a name with IP-adres.
For Hyper-V we set the Storage path for the VM Configs and VHDx Disks in Hyper-V Settings for each host.
With these steps we checked our hardware that’s in the driver box of Microsoft Windows Server 2012 R2, we provisioned iSCSI Storage and made a Windows Server 2012 R2 Hyper-V Cluster.
My Next blog is all about Management with System Center 2012 R2 Virtual Machine Manager and App-Controller.