Use the Replace VSA Cluster Member wizard to replace an ESXi host that failed or underwent storage configuration changes.

You can use a newly installed ESXi host as a replacement. You can also use an existing host that underwent storage reconfiguration or was repaired after a failure. The management IP of the existing ESXi host can be reused.

To reduce the amount of network traffic required during the replacement operation you can retrieve the VSA .vmdk files from a local directory on the ESXi host rather than from vCenter Server. See Deploy VSA Clusters from Local Copies of VSA System Disks.


  • Power off and delete the VSA appliance from the ESXi host that needs to be replaced.
    Caution: If you do not delete the VSA appliance, it will attempt to rejoin the cluster when you later add the host to the cluster. This might cause unpredictable consequences.
  • Power off and remove from the vCenter Inventory the ESXi host that needs to be replaced.
  • Add a replacement ESXi host to vCenter Server. Make sure that the replacement host does not have any remaining VSA appliances.
  • Make sure to power off or migrate any running virtual machines on the replacement host, otherwise the host will not be able to join the VSA HA cluster. With running virtual machines, setting the Enhanced vMotion Capability (EVC) baseline property to highest value makes the host available for inclusion into the cluster and the replace task completes properly. However, the host will not be a part of the HA cluster and the virtual machines on that ESXi host will not be HA-protected.


The wizard deploys a vSphere Storage Appliance on the replacement ESXi host and configures the appliance to join the VSA cluster and replace the failed VSA cluster member.