Verify that the failover cluster is working

Before deploying your failover cluster to production, you can validate your configuration with some simple steps.

Check the service startup type

Verify that the Failover Cluster Manager can control the VMS services by checking the service startup type.

  1. On a node that belongs to the failover cluster, go to Windows Services.

  2. Verify that the startup type for the Management Server, Data Collector Server, and Log Server services is set to Manual.

  3. Repeat the same steps on the remaining failover cluster nodes.

Check service status

Make sure that the Failover Cluster Manager shows the actual status of the nodes.

  1. In Failover Cluster Manager, expand your node and go to roles. Then, click your node.

  2. In the Resource tab, check the status of the Management Server, Data Collector Server, and Log Server services.

  3. Go to the owner node, open Services, and compare the service status of the three VMS services.

If the statuses do not match, start and stop the role. Then, repeat the steps above.

Trigger a failover

After ensuring that the configuration is set up correctly, you can trigger a failover manually.

  1. Restart the node that runs the VMS services.

  2. From the Failover Cluster Manager, see which node has become the new owner node.

  3. Go to the new owner node and verify that the Management Server, Data Collector Server, and Log Server services are running on that node.

  4. Go to the other node members and verify that the services are stopped.

Log in

Try logging in to XProtect Management Client or XProtect Smart Client using the cluster address.

If the configuration is working properly, you should be able to connect seamlessly to the running management server using the cluster address.