About Windows Server Failover Clustering (WSFC)

If your VMS environment requires continuous access that cannot tolerate hardware and software failures without any system interruption, then a viable system solution is Windows Server Failover Clustering (WSFC).

In some cases, for example a small retail shop, the operation of the VMS is not critical enough to warrant the cost of additional hardware. Instead, the shop accepts that failures can be addressed within a day or two by fixing or replacing the server. But, if your VMS environment requires high-availability, then WSFC can be a cost-effective way of achieving that.

WSFC is a group of independent servers that work together to increase the availability of applications and services. If a cluster node or service fails, the services that are hosted on that node can be automatically or manually transferred to another available node.

The management server can be installed on multiple servers within a cluster of servers. This ensures that the system has very little downtime. If a server in the cluster fails, another server in the cluster automatically takes over the failed server's job running the management server.

It is only possible to have one active management server per surveillance setup, but other management servers may be set up to take over in case of failure.

By default, the Management Server service limits the number of times a failover occurs to twice within a six-hour period. If this is exceeded, the Management Server services are not automatically started by the clustering service. This limit can be changed to better fit your needs.

This document provides an outline on creating a high availability environment with Microsoft Failover Clustering on two server nodes by:

This document provides a general outline of WSFC. Refer to the Microsoft documentation (https://msdn.microsoft.com/en-us/library/hh270278) for more detailed information.

There are many ways to set up failover clustering. This document shows a simple example of one way: a Failover Cluster Instance (FCI) with shared storage.

We recommend you refer to the Microsoft documentation (https://msdn.microsoft.com/en-us/library/hh270278) for more information about failover clustering.

This document is primarily intended for:

  • Surveillance system architects, designers and integrators

  • Large-scale surveillance project consultants

  • Installers