AZ-801 · Question #168
You have a Windows Server 2019 Storage Spaces Direct cluster named Cluster1. Cluster1 has four nodes that contain virtual machines. You need to perform an in-place upgrade of Cluster1 to Windows…
This question tests knowledge of the Windows Server Cluster Rolling Upgrade (CRU) process for a Storage Spaces Direct (S2D) cluster, which allows an in-place OS upgrade node-by-node while maintaining VM availability throughout.
Question
Explanation
This question tests knowledge of the Windows Server Cluster Rolling Upgrade (CRU) process for a Storage Spaces Direct (S2D) cluster, which allows an in-place OS upgrade node-by-node while maintaining VM availability throughout.
Approach. The correct approach is a Cluster Rolling Upgrade performed in this order for each node: (1) Suspend/Drain the cluster node - this live-migrates all VMs off the node to remaining nodes, ensuring zero downtime; (2) Evict the node from the cluster - this safely removes it from the S2D pool; (3) Upgrade the node OS to Windows Server 2022 (in-place upgrade); (4) Re-add the node to the cluster and resume it, allowing VMs and storage to rebalance back. Repeat for every node. After all nodes are upgraded: (5) Update the cluster functional level using Update-ClusterFunctionalLevel, and finally (6) Update the storage pool version using Update-StoragePool. This sequence maintains a mixed-OS cluster temporarily (2019 + 2022 nodes coexist), which S2D and Failover Clustering support during the transition window.
Concept tested. Windows Server Cluster Rolling Upgrade (CRU) with Storage Spaces Direct - specifically the node-by-node drain, evict, upgrade, re-add, resume sequence, followed by cluster functional level and storage pool version updates to complete the upgrade.
Reference. Microsoft Docs: 'Cluster OS Rolling Upgrade' - https://learn.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade
Topics
Community Discussion
No community discussion yet for this question.