|
| 1 | +--- |
| 2 | +title: Suspend and resume Azure Stack HCI, version 23H2 clusters for planned maintenance operations |
| 3 | +description: Learn how to suspend and resume cluster nodes for planned maintenance operations. |
| 4 | +author: ronmiab |
| 5 | +ms.author: robess |
| 6 | +ms.topic: how-to |
| 7 | +ms.service: azure-stack |
| 8 | +ms.subservice: azure-stack-hci |
| 9 | +ms.custom: |
| 10 | + - devx-track-azurecli |
| 11 | +ms.date: 09/17/2024 |
| 12 | +#Customer intent: As a Senior Content Developer, I want to provide customers with content and steps to help them successfully suspend and resume their cluster nodes for planned maintenance. |
| 13 | +--- |
| 14 | + |
| 15 | +# Suspend and resume Azure Stack HCI, version 23H2 clusters for maintenance |
| 16 | + |
| 17 | +[!INCLUDE [hci-applies-to-23h2](../../includes/hci-applies-to-23h2.md)] |
| 18 | + |
| 19 | +This article describes how to suspend a cluster node for planned maintenance, such as powering off the machine to replace non-hot-pluggable components. It also provides instructions on how to resume the cluster node once maintenance is complete. |
| 20 | + |
| 21 | +## Suspend a cluster node |
| 22 | + |
| 23 | +To suspend a cluster node, first suspend the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool. |
| 24 | + |
| 25 | +To suspend a cluster node, follow these steps: |
| 26 | + |
| 27 | +1. Log on to one of the cluster nodes with a user that has local administrator permissions. |
| 28 | +1. To suspend the cluster node, run this command: |
| 29 | + |
| 30 | + ```powershell |
| 31 | + Suspend-clusternode -name “MachineName” |
| 32 | + ``` |
| 33 | +
|
| 34 | + Here's example output: |
| 35 | +
|
| 36 | + ```console |
| 37 | + PS C:\programdata\wssdagent> Suspend-ClusterNode ASRRlS3lRl5ull |
| 38 | +
|
| 39 | + Name State Type |
| 40 | + ---- ----- ---- |
| 41 | + ASRRls3lRl5ull Paused Node |
| 42 | + ``` |
| 43 | +
|
| 44 | + > [!NOTE] |
| 45 | + > Running this command may take some time, depending on the number of VMs that need to be migrated. |
| 46 | +
|
| 47 | +1. Confirm that the node is successfully suspended. |
| 48 | +
|
| 49 | + ```powershell |
| 50 | + Get-clusternode |
| 51 | + ``` |
| 52 | +
|
| 53 | + Here's example output: |
| 54 | +
|
| 55 | + ```console |
| 56 | + PS C:\programdata\wssdagent> get-clusternode |
| 57 | +
|
| 58 | + Name State Type |
| 59 | + ---- ----- ---- |
| 60 | + ASRRlS3lRl5u09 Up Node |
| 61 | + ASRRlS3lRl5Ull Paused Node |
| 62 | + ``` |
| 63 | +
|
| 64 | +1. To ensure that no new VMs are placed on the node, remove the node from the active Arc VM Configuration. **This step can only be done using PowerShell**. |
| 65 | +
|
| 66 | + ```powershell |
| 67 | + Remove-MocPhysicalNode -nodeName “MachineName” |
| 68 | + ``` |
| 69 | +
|
| 70 | +## Resume a cluster node |
| 71 | +
|
| 72 | +To resume a cluster node, first resume the cluster node in Windows Failover Clustering. You can use various tools for this step, such as Windows Admin Center, Failover Cluster Manager, or PowerShell. We recommend using PowerShell as some steps can only be performed using that tool. |
| 73 | +
|
| 74 | +To resume a cluster node, follow these steps: |
| 75 | +
|
| 76 | +1. Log on to one of the cluster nodes with a user that has local administrator permissions. |
| 77 | +1. To resume the cluster node, run this command: |
| 78 | +
|
| 79 | + ```powershell |
| 80 | + Resume-clusternode -name “MachineName” |
| 81 | + ``` |
| 82 | +
|
| 83 | + Here's example output: |
| 84 | +
|
| 85 | + ```console |
| 86 | + PS C:\programdata\wssdagent> Resume-ClusterNode ASRRlS3lRl5ull |
| 87 | +
|
| 88 | + Name State Type |
| 89 | + ---- ----- ---- |
| 90 | + ASRRls3lRl5ull Up Node |
| 91 | + ``` |
| 92 | +
|
| 93 | + > [!NOTE] |
| 94 | + > Running this command may take some time, depending on the number of VMs that need to be migrated. |
| 95 | +
|
| 96 | +1. Confirm that the node is successfully resumed. |
| 97 | +
|
| 98 | + ```powershell |
| 99 | + Get-clusternode |
| 100 | + ``` |
| 101 | +
|
| 102 | + Here's example output: |
| 103 | +
|
| 104 | + ```console |
| 105 | + PS C:\programdata\wssdagent> Get-clusternode |
| 106 | +
|
| 107 | + Name State Type |
| 108 | + ---- ----- ---- |
| 109 | + ASRRlS3lRl5u09 Up Node |
| 110 | + ASRRlS3lRl5Ull Paused Node |
| 111 | + ``` |
| 112 | +
|
| 113 | +1. Add the node to the active Arc VM Configuration. **This step can only be done using PowerShell**. |
| 114 | +
|
| 115 | + ```powershell |
| 116 | + Remove-MocPhysicalNode -nodeName “MachineName” |
| 117 | + ``` |
| 118 | +
|
| 119 | +1. Verify that your storage pool is healthy. |
| 120 | +
|
| 121 | + ```powershell |
| 122 | + Get-Storagepool -friendlyname “SU_Pool1” |
| 123 | + ``` |
| 124 | +
|
| 125 | + Here's example output: |
| 126 | +
|
| 127 | + ```console |
| 128 | + PS C : \programdata\wssdagent> get-storagepool -FriendlyName "SU1_Pool" |
| 129 | +
|
| 130 | + FriendlyName Operationalstatus HealthStatus IsPrimordial IsReadOnly Size AllocatedSize |
| 131 | + ------------ ----------------- ------------ ------------ ---------- ---- ------------- |
| 132 | + SUl_Pool OK Healthy False False 131.28 TB 1.8S TB |
| 133 | + ``` |
| 134 | +
|
| 135 | + > [!NOTE] |
| 136 | + > If the pool is not reported as healthy, check the status of the storage repair jobs using the `get-storagejob` command. |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments