When the master host in a vSphere HA cluster can no longer communicate with a slave host over the management network, the master host uses datastore heartbeating to determine if the slave host might have failed or is in a network partition. If the slave host has stopped datastore heartbeating, that host is considered to have failed and its virtual machines are restarted elsewhere.

vCenter Server automatically selects a preferred set of datastores for heartbeating. This selection is made with the goal of maximizing the number of hosts that have access to a given datastore and minimizing the likelihood that the selected datastores are backed by the same storage array or NFS server. In most cases, this selection should not be changed. However, if you must replace a selected datastore, you can go to the Cluster Settings dialog box of the vSphere Client and select the Datastore Heartbeating page to specify alternative datastores. Only datastores mounted by at least two hosts are available here. You can also see which datastores vSphere HA has selected for use by viewing the Heartbeat Datastores tab of the HA Cluster Status dialog box.

If you are using the vSphere Web Client, you can view information about heartbeat datastores by browsing to the cluster's Monitor tab and selecting vSphere HA and Heartbeat.