System setup - Security Center 5.9

Security Center Installation and Upgrade Guide for Windows Cluster 5.9

Security Center 5.9

This section describes the setup and configuration of a two node (two servers) failover cluster on a Windows Server 2012 R2 operating system. Your Security Center server and SQL Server 2012 will be protected by the Windows cluster.

Before installing and configuring your clustered Security Center system, you require the following:

  • A Windows Server 2012 R2 failover cluster must already be installed and operational.
  • A Microsoft SQL Server 2012 instance must already be installed and operational.
  • You must have the Security Center installation package available.
The configuration that we will be using requires three distinct networks:
Data network
Used for general network communications. This network should be used for video traffic, access control, DNS queries, time synchronization, remote management, and Active Directory authentication. Additionally, a floating IP address must be configured on this network for connecting the clustered Security Center services, the non-clustered Security Center services that may be running on standalone servers, and the Security Center Client applications.
Cluster network
Used for inter-node communication only. It is recommended to dedicate a separate network on a different subnet for the cluster heartbeat. If there are only two nodes in the cluster, using a crossover link between them is recommended.
Storage network
External storage is required for successful Windows clustering of a Security Center system. The storage will contain the SQL database files, the Security Center files and (possibly) the video recording files.
NOTE: As of Windows 2008, all clustered nodes must be part of the same Active Directory domain and must be capable of resolving each other’s host names via DNS or the host file. It is recommended to deploy multiple redundant domain controllers and DNS servers on the DATA network to ensure the cluster’s uptime in case of domain controller or DNS server failure.