Skip to content

Commit 899233c

Browse files
author
Vamsi Kavuru
committed
adding adh-redeploy section
1 parent 8b6a436 commit 899233c

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/virtual-machines/dedicated-hosts-how-to.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -732,7 +732,7 @@ $hostRestartStatus.InstanceView.Statuses[1].DisplayStatus;
732732

733733
## Redeploy a host
734734

735-
Redeploying a host will move the host and all associated VMs to a different node of the same SKU. None of the host parameters would change except for the ‘Host asset ID’, which corresponds to the underlying Node Id. During redeploy operation host's provisioning state will change from 'Provisioning succeeded' to 'Updating', once the redeploy operation is complete the provisioning state will revert to ''Provisioning succeeded'.
735+
If a VM or the underlying host remains unresponsive after following all the potential troubleshooting steps users can trigger service healing of the host and not wait for the platform to initiate the repair. Redeploying a host will move the host and all associated VMs to a different node of the same SKU. None of the host parameters would change except for the ‘Host asset ID’, which corresponds to the underlying Node Id.
736736

737737
> [!WARNING]
738738
> Redeploy operation involves service healing hence would result in loss of any non-persistent data such as data stored on ephemeral disks. Save your work before redeploying.
@@ -756,7 +756,6 @@ az vm host redeploy \
756756
--name myDedicatedHost
757757
```
758758

759-
760759
---
761760

762761
## Deleting a host

0 commit comments

Comments
 (0)