Large Scale Installation with High Availability
This architecture fits large-scale installations and is the recommended production deployment architecture for most environments that require high availability (HA).
The Application Server is installed on several machines behind a network load balancer where additional Application Servers are added. The additional Application servers ensure that the expected load is distributed among remaining Application Servers in case one or more fail or are taken offline..
The Web Console and the Website Categorization module (if used) are installed on 2 separate machines, allowing high availability in case one of the machines fails or is taken offline.
The SQL Database Server used to store the database is located on a dedicated SQL Database Server Always On Availability Group, replicating the databases between the cluster members.
The file share used to store the recorded images is located on a dedicated file server (DFS) cluster or replicated to another server using other methods such as disk level replication or DFS.
The diagram below is an example of a Large Scale Installation with high availability.
Load Balancer Implementation
When full load balancing and high availability are required, you can use a software-based load balancer (such as Microsoft NLB) or hardware-based load balancer (such as F5). Optionally, this can be further augmented by a failover cluster for the Application Server with an active/passive cluster that has only one node operational at any given time. Also, more nodes can be added, as needed, to the failover cluster.
File System Storage
To improve performance of the MS SQL Server, it is sometimes recommended to use ObserveIT’s file system storage capabilities. In this Installation, the SQL Server is still used for user activity log and configuration data, but the actual screenshot images are stored in a file system directory structure, which is fully managed by ObserveIT.
Related Topic: