Cluster Operating System Rolling Upgrade in Windows Server Technical Preview

发布时间: 2014年10月

应用到: Windows Server Technical Preview



note注意
This content is pre-release documentation and is subject to change in future releases.

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

Important重要
This preview release should not be used in production environments.

This section describes the various transition states of the Windows Server 2012 R2 cluster that is being upgraded to Windows Server Technical Preview using Cluster OS Rolling Upgrade.

In order to keep the cluster workloads running during the Cluster OS Rolling Upgrade process, moving a cluster workload from a Windows Server 2012 R2 node to Windows Server Technical Preview node works as if both nodes were running the Windows Server 2012 R2 operating system. When Windows Server Technical Preview nodes are added to the cluster, they operate in a Windows Server 2012 R2 compatibility mode. A new conceptual cluster mode, called “mixed-OS mode”, allows nodes of different versions to exist in the same cluster (see Figure 1).

滚动操作系统升级概述

Figure 1: Cluster operating system state transitions

A Windows Server 2012 R2 cluster enters mixed-OS mode when a Windows Server Technical Preview node is added to the cluster. The process is fully reversible – Windows Server Technical Preview nodes can be removed from the cluster and Windows Server 2012 R2 nodes can be added to the cluster in this mode. The “point of no return” occurs when the Update-ClusterFunctionalLevel PowerShell cmdlet is run on the cluster. In order for this cmdlet to succeed, all nodes must be Windows Server Technical Preview, and all nodes must be online.

This section illustrates and describes the four different stages of a cluster with shared storage whose nodes are upgraded from Windows Server 2012 R2 to Windows Server Technical Preview.

“Stage 1” is the initial state – we start with a Windows Server 2012 R2 cluster.

群集操作系统滚动升级第 1 阶段

Figure 2: Initial State: Windows Server 2012 R2 Failover Cluster (Stage 1)

In “Stage 2”, two nodes have been paused, drained, evicted, reformatted, and installed with Windows Server Technical Preview.

群集操作系统滚动升级第 2 阶段

Figure 2: Intermediate State: Mixed-OS mode: Windows Server 2012 R2 and Windows Server Technical Preview Failover cluster (Stage 2)

At “Stage 3”, all of the nodes in the cluster have been upgraded to Windows Server Technical Preview, and the cluster is ready to be upgraded with Update-ClusterFuncationalLevel PowerShell cmdlet.

note注意
At this stage, the process can be fully reversed, and Windows Server 2012 R2 nodes can be added to this cluster.

群集操作系统滚动升级第 3 阶段

Figure 4: Intermediate State: All nodes upgraded to Windows Server Technical Preview, ready for Update-ClusterFunctionalLevel (Stage 3)

After the Update-ClusterFunctionalLevel PowerShell cmdlet is run, the cluster enters “Stage 4”, where new Windows Server Technical Preview cluster features can be used.

群集操作系统滚动升级第 4 阶段

Figure 5: Final State: Windows Server Technical Preview Failover Cluster (Stage 4)

Complete the following requirements before you begin the Cluster OS Rolling Upgrade process:

  • Start with a Windows Server 2012 R2 nodes cluster running Hyper-V or Scale-Out File Server.

  • Check that Hyper-V nodes have CPUs that support Second-Level Addressing Table (SLAT).

This section describes the workflow for performing Cluster OS Rolling Upgrade.

群集操作系统滚动升级工作流

Figure 6: Cluster OS Rolling Upgrade Process Workflow

Cluster OS Rolling upgrade includes the following steps:

  1. Prepare the cluster for the operating system upgrade as follows:

    1. Cluster OS Rolling Upgrade requires removing one node at a time from the cluster. Check if you have sufficient capacity on the cluster to maintain HA SLAs when one of the cluster nodes is removed from the cluster for an operating system upgrade.

    2. For Hyper-V workloads, check that all Windows Server Technical Preview Hyper-V hosts have CPU support Second-Level Address Table (SLAT). Only SLAT-capable machines can use the Hyper-V role in Windows Server Technical Preview.

    3. Check that any workload backups have completed, and consider backing-up the cluster. Stop backup operations while adding nodes to the cluster.

    4. Check that all cluster nodes are online (running).

    5. If you are running Cluster Aware Updates (CAU), stop CAU using Disable-CauClusterRole PowerShell cmdlet to prevent any nodes from being paused and drained by CAU during the Cluster OS Rolling Upgrade process.

  2. For each node in the cluster, complete the following:

    1. Using Cluster Manager UI, select a node and use the Pause | Drain menu option to drain the node or use the Suspend-ClusterNode PowerShell cmdlet.

    2. Using Cluster Manager UI, Evict the paused node from cluster, or use the Remove-ClusterNode PowerShell cmdlet.

    3. Reformat the system drive and perform a “clean Operating System install” of Windows Server Technical Preview on the node – do not perform an “in-place” or “upgrade” install of the cluster node.

    4. Using the Server Manager UI or Install-WindowsFeature PowerShell cmdlet, install any server roles that you need, such as Hyper-V.

    5. Using the Server Manager UI or Install-WindowsFeature PowerShell cmdlet, install the Failover Clustering feature.

    6. Install any additional features needed by your cluster workloads.

    7. Add the node to the appropriate Active Directory domain.

    8. Check network and storage connectivity settings.

    9. On a Windows Server Technical Preview node (not Windows Server 2012 R2, use the Failover Cluster Manager or the Add-ClusterNode PowerShell cmdlet to add the node to the cluster.

    10. Move cluster workload to the newly added Windows Server Technical Preview node as follows:

      1. Use Live Migration from the Failover Cluster Manager for virtual machines or the Move-ClusterVirtualMachineRole PowerShell cmdlet to perform a live migration of the virtual machines.

      2. Use Move from the Failover Cluster Manager or the Move-ClusterGroup PowerShell cmdlet for other cluster workloads.

  3. When every node has been upgraded to Windows Server Technical Preview and added back to the cluster, or when any remaining Windows Server 2012 R2 nodes have been evicted, do the following:

    Important重要
    • After you update the cluster functional level, you cannot go back to Windows Server 2012 R2 functional level.

    • Until the Update-ClusterFunctionalLevel PowerShell cmdlet is run, the process is fully reversible and Windows Server 2012 R2 nodes can be added to this cluster and Windows Server Technical Preview nodes can be removed.

    1. Check that all cluster roles are running on the cluster as expected, and that no cluster nodes are offline.

    2. Run the Update-ClusterFunctionalLevel cmdlet – no errors should be returned.

  4. Windows Server Technical Preview - resume normal cluster patching and backups:

    1. If you were previously running CAU, restart it using the CAU UI or use the Enable-CauClusterRole PowerShell cmdlet.

    2. Resume backup operations.

  5. Enable and use the Windows Server Technical Preview features.

    1. Users of Hyper-V virtual machines may choose to upgrade virtual machines by scheduling a brief maintenance window, turning off virtual machines, and running the Update-VMConfigurationVersion PowerShell cmdlet. This will update the virtual machine version, and enable new Hyper-V features, eliminating the need for future Hyper-V Integration Component (IC) updates.

    2. Storage pools can be upgraded using the Update-StoragePool PowerShell cmdlet - this is an online operation.

Although we are targeting Private Cloud scenarios, specifically Hyper-V and Scale-out File Server clusters, which can be upgraded without downtime, the Cluster OS Rolling Upgrade process can be used for any cluster role.

  • This feature works only for Windows Server 2012 R2 to Windows Server Technical Preview versions only.

  • Each Windows Server Technical Preview node must be reformatted /new installation only. “In-place” or “upgrade” installation type is not supported.

  • A Windows Server Technical Preview node must be used to add Windows Server Technical Preview nodes to the cluster.

  • When managing a mixed-OS mode cluster, always perform the management tasks from an uplevel node that is running Windows Server Technical Preview. Downlevel Windows Server 2012 R2 nodes cannot use UI or management tools against Windows Server Technical Preview.

  • We encourage customers to move through the cluster upgrade process quickly because some cluster features are not optimized for mixed-OS mode.

  • Do not create or resize storage on Windows Server Technical Preview nodes while the cluster is running in mixed-OS mode because of incompatibilities on failover.

  • Do not use Windows Server Technical Preview in a production environment.

  • Will you port this feature back to Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008?

    We do not have any plans to port this feature back to previous versions.

  • Can I automate this process using PowerShell?

    Yes, we have designed Cluster OS Rolling Upgrade to be automated.

  • What if I discover an issue in my cluster after Update-ClusterFunctionalLevel has been run successfully?

    If you have backed-up the cluster database with a System State backup before running Update-ClusterFuncationalLevel, you should be able to restore it on a Windows Server 2012 R2cluster node and restore the original cluster configuration.

©2014 Microsoft Corporation. All rights reserved.  This document is provided "as-is." Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. Some examples are for illustration only and are fictitious. No real association is intended or inferred. Some information relates to pre-released product which may be substantially modified before it’s commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

社区附加资源

显示: