Multiple management servers (clustering) (explained)
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. The automatic process of switching over the management server services to run on another server in the cluster takes up to 30 seconds.
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.
The allowed number of failovers is limited to two within a six-hour period. If exceeded, management server services are not automatically started by the clustering service. The number of allowed failovers can be changed to better fit your needs.
Requirements for clustering
- Two machines with Microsoft Windows Server 2012 or newer. Make sure that:
- All servers that you want to add as cluster nodes are running the same version of Windows Server
- All servers that you want to add as cluster nodes are joined to the same domain
- You have log-in access to the Windows account as the local administrator
About clusters in Microsoft Windows Servers, see Failover clusters https://docs.microsoft.com/en-us/windows-server/failover-clustering/create-failover-cluster.
- A Microsoft SQL Server installation
Either an external SQL Server and database installed outside the server cluster or an internalSQL Server service (clustered) within the server cluster (creating an internal SQL Server service requires the use of the Microsoft® SQL Server® Standard or Microsoft® SQL Server® Enterprise edition, which can work as a clustered SQL Server).
When connecting the management server to the database, depending on your system configuration password settings, you may be asked to provide the current system configuration password. See System configuration password (explained).