Understanding Multi-Server Architecture and Basics |
  
|
Understanding Multi-Server Architecture and Basics |
|
Nx Witness implements the unique hive architecture that enables high redundancy , performance and provides almost unlimited scalability. Servers can be located in a local network, behind NAT or even in a different location – they will act as a single cluster allowing users to view cameras and control the whole system from a single workstation.
If several Servers are working together they should somehow connect to each other. To do so servers have the unique identifier - System Name, that allows server to group together. If Server discovers another Server with the identical System Name in a local network, they merges automatically. If System names are different, Server will display other one in Resource Tree under 
Other Systems.
If Servers are in different subnets, it is necessary to specify other Server's IP to make them merge in separate networks (behind NAT or over the Internet).
When Servers are merged, they are constantly synchronizing all data between each other so it doesn't matter what server Client is connected to. If a video is requested from a remote Server, the one Client is connected to will be proxying the video traffic. Licenses are combined as well: if 4 licenses were activated on server 1 and 10 – on Server 2, System will have 14 Licenses total after the servers are merged.
Thus, the only thing Administrator should do to merge systems, is to assign the same system names to all Servers. Opposite, to split Systems Administrator needs to assign different system names.