升級叢集作業系統Cluster operating system rolling upgrade

本文內容

作業系統循環升級叢集讓系統管理員可以而停止 HYPER-V 或延展檔案伺服器工作負載升級叢集節點作業系統。Cluster OS Rolling Upgrade enables an administrator to upgrade the operating system of the cluster nodes without stopping the Hyper-V or the Scale-Out File Server workloads.使用這項功能，可避免當機損失針對服務層級合約 (SLA)。Using this feature, the downtime penalties against Service Level Agreements (SLA) can be avoided.

執行 HYPER-V 一樣和延展檔案伺服器 (SOFS) 工作負載容錯可以升級（叢集中的所有節點都執行），Windows Server 2012 R2 的 Windows Server 2016（叢集所有叢集節點都都執行），而中斷。Failover clusters running Hyper-V virtual machine and Scale-out File Server (SOFS) workloads can be upgraded from Windows Server 2012 R2 (running on all nodes in the cluster) to Windows Server 2016 (running on all cluster nodes of the cluster) without downtime.其他叢集工作負載，例如 SQL Server 中，將不提供容錯移轉到 Windows Server 2016 所花費的時間（通常不會超過五分鐘）。Other cluster workloads, such as SQL Server, will be unavailable during the time (typically less than five minutes) it takes to failover to Windows Server 2016.

它並不需要任何額外的硬體。It doesn't require any additional hardware.雖然您可以新增額外叢集節點暫時小群集叢集 OS 循環升級期間改善可用性叢集來處理。Although, you can add additional cluster nodes temporarily to small clusters to improve availability of the cluster during the Cluster OS Rolling Upgrade process.

請確認 HYPER-V 節點有 Cpu 支援第二層級位址表格（造板條）使用其中一項下列方法。Verify that the Hyper-V nodes have CPUs that support Second-Level Addressing Table (SLAT) using one of the following methods;-檢視您會造板條相容？WP8 SDK 秘訣 01描述兩種方法來檢查是否 CPU 支援 SLATs 文件- Review the Are you SLAT Compatible? WP8 SDK Tip 01 article that describes two methods to check if a CPU supports SLATs-下載Coreinfo v3.31若要判斷是否 CPU 支援造板條工具。- Download the Coreinfo v3.31 tool to determine if a CPU supports SLAT.

在「步驟 3」、節點叢集中的所有已升級至 Windows Server 2016 和叢集已準備好升級的 Update-ClusterFunctionalLevel PowerShell cmdlet。At "Stage 3", all of the nodes in the cluster have been upgraded to Windows Server 2016, and the cluster is ready to be upgraded with Update-ClusterFunctionalLevel PowerShell cmdlet.

注意

這個階段程序可以完全還原，且 Windows Server 2012 R2 節點可以新增至此叢集。At this stage, the process can be fully reversed, and Windows Server 2012 R2 nodes can be added to this cluster.

叢集 OS 循環升級程序Cluster OS Rolling Upgrade Process

叢集 OS 循環升級包含下列步驟：Cluster OS Rolling upgrade includes the following steps:

準備叢集作業系統升級，如下所示：Prepare the cluster for the operating system upgrade as follows:

作業系統循環升級叢集需要一次移除叢集一個節點。Cluster OS Rolling Upgrade requires removing one node at a time from the cluster.檢查是否有容量不足時其中一個節點叢集移除作業系統升級叢集維持哈 Sla 叢集上。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.亦即，您需要到另一個節點容錯移轉工作負載的功能的叢集 OS 循環升級程序期間移除一個節點時嗎？In other words, do you require the capability to failover workloads to another node when one node is removed from the cluster during the process of Cluster OS Rolling Upgrade?叢集有一個節點中移除的叢集 OS 循環升級時，請執行所需的工作負載的容量嗎？Does the cluster have the capacity to run the required workloads when one node is removed from the cluster for Cluster OS Rolling Upgrade?

當的第一個 Windows Server 2016 節點加入叢集時，叢集進入「混合 OS」模式，並叢集核心資源的移到 Windows Server 2016 節點。When the first Windows Server 2016 node joins the cluster, the cluster enters "Mixed-OS" mode, and the cluster core resources are moved to the Windows Server 2016 node.「混合 OS」模式叢集是完整功能叢集新節點執行舊節點與相容性模式中的位置。A "Mixed-OS" mode cluster is a fully functional cluster where the new nodes run in a compatibility mode with the old nodes.「混合 OS」模式是叢集暫時性模式。"Mixed-OS" mode is a transitory mode for the cluster.這不是會永久與他們叢集節點所有更新中四個星期會如預期般針對。It is not intended to be permanent and customers are expected to update all nodes of their cluster within four weeks.

Windows Server 2016 節點成功新增至後叢集，您可以（選擇性）移叢集工作負載的部分新加入節點以重新工作負載平衡叢集，如下所示：After the Windows Server 2016 node is successfully added to the cluster, you can (optionally) move some of the cluster workload to the newly added node in order to rebalance the workload across the cluster as follows:

當您已升級至 Windows Server 2016 和加回叢集，每個節點或任何其他 Windows Server 2012 R2 節點上有移除，執行下列動作：When every node has been upgraded to Windows Server 2016 and added back to the cluster, or when any remaining Windows Server 2012 R2 nodes have been evicted, do the following:

使用「容錯移轉叢集管理員 UI 或Get-ClusterGroup cmdlet，檢查所有叢集角色執行叢集上如預期般運作。Using the Failover Cluster Manager UI or the Get-ClusterGroup cmdlet, check that all cluster roles are running on the cluster as expected.以下的範例，可用儲存空間未使用，改為使用 CSV，因此，會顯示可用的儲存離線狀態（看到圖 18）。In the following example, Available Storage is not being used, instead CSV is used, hence, Available Storage displays an Offline status (see Figure 18).

每個 HYPER-V 主機] 節點中叢集上可以 HYPER-V VM 設定版本升級排程簡短維護視窗的使用者，備份、關閉虛擬電腦，然後執行Update-VMVersion cmdlet（看到圖 22）。On each Hyper-V host node in the cluster, Hyper-V VM configuration versions can be upgraded by scheduling a brief maintenance window with users, backing up, turning off virtual machines, and running the Update-VMVersion cmdlet (see Figure 22).這將會更新一樣版本，以及新 HYPER-V 功能，不需要 HYPER-V 整合元件 (IC) 未來的更新。This will update the virtual machine version, and enable new Hyper-V features, eliminating the need for future Hyper-V Integration Component (IC) updates.可以從 HYPER-V 節點裝載 VM 中，執行下列 cmdlet 或-ComputerName參數可從遠端更新 VM 版本。This cmdlet can be run from the Hyper-V node that is hosting the VM, or the -ComputerName parameter can be used to update the VM Version remotely.在此範例中，以下我們 VM1 設定版本從升級 5.0 7.0 善用 Production 檢查點（應用程式一致備份），和二進位 VM 設定檔此 VM 設定版本與相關的許多新 HYPER-V 功能。In this example, here we upgrade the configuration version of VM1 from 5.0 to 7.0 to take advantage of many new Hyper-V features associated with this VM configuration version such as Production Checkpoints (Application Consistent backups), and binary VM configuration file.

可以使用升級儲存集區更新-StoragePool PowerShell cmdlet-這是 online 作業。Storage pools can be upgraded using the Update-StoragePool PowerShell cmdlet - this is an online operation.

雖然我們的目標私人雲端案例中，尤其是 HYPER-V 和延展檔案伺服器叢集，而當機，升級作業系統循環叢集程序可以升級可用於任何叢集角色。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.

常見問題集Frequently asked questions

多久容錯移轉叢集在執行作業系統混合模式？How long can the failover cluster run in mixed-OS mode?我們建議針對完成的四個星期中升級。We encourage customers to complete the upgrade within four weeks.有許多最佳化 Windows Server 2016 中。There are many optimizations in Windows Server 2016.我們已經順利升級 HYPER-V 和延展檔案伺服器叢集零中斷的四個小時總中。We have successfully upgraded Hyper-V and Scale-out File Server clusters with zero downtime in less than four hours total.

作業系統循環升級叢集運作的任何叢集工作負載嗎？Does Cluster OS Rolling Upgrade work for any cluster workload?它 SQL server 運作？Does it work for SQL Server?是的作業系統循環升級叢集適用於任何叢集工作負載。Yes, Cluster OS Rolling Upgrade works for any cluster workload.不過，它是 HYPER-V 和延展檔案伺服器叢集的唯一零中斷。However, it is only zero-downtime for Hyper-V and Scale-out File Server clusters.其他大部分的工作負載收取某些當機（通常幾分鐘）時他們錯誤移轉及容錯移轉是需要叢集 OS 循環升級程序期間至少一次。Most other workloads incur some downtime (typically a couple of minutes) when they failover, and failover is required at least once during the Cluster OS Rolling Upgrade process.

可以自動執行此程序使用 PowerShell 嗎？Can I automate this process using PowerShell?是的我們已設計叢集 OS 循環無法使用 PowerShell 自動升級。Yes, we have designed Cluster OS Rolling Upgrade to be automated using PowerShell.

大叢集的額外工作負載與錯誤後移轉的容量，我是否可以升級多個節點同時？For a large cluster that has extra workload and failover capacity, can I upgrade multiple nodes simultaneously?[是]。Yes.當升級作業系統叢集從移除一個節點時，叢集將會有一個較節點容錯移轉的因此必須容錯減少的移轉的容量。When one node is removed from the cluster to upgrade the OS, the cluster will have one less node for failover, hence will have a reduced failover capacity.大容錯移轉容量不足，無法工作負載與叢集，可以同時升級多個節點。For large clusters with enough workload and failover capacity, multiple nodes can be upgraded simultaneously.您可以暫時將提供工作負載改進和錯誤後移轉容量叢集 OS 循環升級程序期間叢集叢集節點加入。You can temporarily add cluster nodes to the cluster to provide improved workload and failover capacity during the Cluster OS Rolling Upgrade process.

可以使用就地升級為每個節點，而不是使用清潔作業系統安裝重新系統磁碟機格式化嗎？Can I use in-place upgrade for each node instead of using clean-OS install by reformatting the system drive?我們不會鼓勵就地升級的 Windows Server、使用，但我們已經知道運作有時候可用預設驅動程式。We do not encourage the use of in-place upgrade of Windows Server, but we are aware that it works in some cases where default drivers are used.請仔細朗讀叢集節點就地升級過程中顯示所有警告訊息。Please carefully read all warning messages displayed during in-place upgrade of a cluster node.