help • App. L: High Availability Solution for SwyxWare • Configuring the SwyxWare HealthMonitor • Check Installation
L.6.3 Check Installation
To check whether the installation of SwyxWare and the HealthMonitor was successful, you can carry out the following steps:
1 In the Windows Service Manager, check that all SwyxWare services are running. Alternatively, you can use this PowerShell command to do this:
 
get-service | where-object { $_.Displayname -match "Swyx" -and $_.StartType -match "Auto" } | format-table Status, Name, DisplayName
 
2 Make sure VMWare in vSphere vCenter receives the Heartbeat from SwyxWare.
In operation
Set HealthMonitor
The default settings of the HealthMonitor should be appropriate in most cases. The HealthMonitor checks the SwyxWare services by sending a "SIP Options" or "HTTP Request" every 10 seconds to each SwyxWare service and waiting for a response for 500ms. You can adjust both the interval and the waiting time for each service. To do this, set the following values for the corresponding service in the "appSettings.json" file:
 
"probingIntervalSeconds": 10,
"responseTimeoutMilliseconds": 500
 
Restart the HealthMonitor service once to make the changes effective.
Back-up/Restore via VEEAM
For details on backing up and restoring virtual machines using VEEAM, see: https://www.veeam.com
* 
If you have installed SwyxWare HealthMonitor and are using the Heartbeat in VMWare vSphere or Hyper-V for monitoring, make sure to stop the HealthMonitor service BEFORE you have to stop the SwyxWare services e.g. for maintenance purposes. The HealthMonitor logs off from vSphere or Hyper-V when the service is stopped, so vSphere or Hyper-V no longer expects heartbeats.