The number of vSphere HA heartbeat datastores for host is 1, which is less than required 2 – vSphere 6.5

This is a pesky common error that has plagued vSphere administrators for a long time.  If you do not have multiple redundant datastores, you will get this error.

The number of vSphere HA heartbeat datastores for host is 1, which is less than required 2

To fix this issue for vCenter Server Appliance 6.5, follow these simple steps.

Login to vSphere Server Appliance web host client. Go to Hosts and Clusters from the main menu. Select the cluster you want to modify from the tree.

Go to Configure tab and select vSphere Availability (used to be called vSphere HA), click Edit

Go to Advanced Options, click in the Options box and paste this:


Paste this in the value box:    true

Click OK, wait a bit for it to modify all your hosts. Done!

VMware Common Logging Service Health Alarm VCSA

If you get this service alarm, you are having a problem with your logging service in vCenter Server Appliance 6.0. Typically the log drive fills up and it is not set to auto expand so you get a critical error and logs won’t be saved.

To correct this issue, follow these steps. To view the logging health open up vCenter Web Client and navigate to Administration > System Configuration > Services > VMware Syslog Service. Verify your service is still running.


Open up Putty and access vCenter with the VCSA IP Address and root account. Run this command to check status:

service-control –status vmware-syslog

Run these command to enable shell:

shell.set –enabled true

Check the status of the log drive by running the command:

df -h

Notice that the log drive in 10GB in size and is almost full.

Go to vCenter Web Client and open up your vCenter Service Appliance Server properties and select Edit Setting in VM Hardware.

Select Manage other disks.

Go to Hard Disk 5 and increase the size from 10GB to 20GB close and save.

Go back to Putty and enter this command to set the drives to autogrow.

vpxd_servicecfg storage lvm autogrow

When the command runs successfully you should get this result.


View the VMware kb article here for more details.