Several ESS Servers can be installed in an anti-virus network. Each Enterprise Agent connects to one of them; each Server with connected anti-virus workstations functions as a separate anti-virus network as described in previous Chapters.
Dr.Web ESS allows to connect such anti-virus networks by transferring data between Enterprise Servers.
A Server can send to another Server
◆software and virus database updates (only one of them is to receive updates from the Dr.Web GUS servers);
|
It is recommended to schedule a task for updating from the GUS on subordinate Enterprise Servers in case the parent Enterprise Server is inaccessible. This will allow the Agents connected to a subordinate Enterprise Server to receive updated virus databases and program modules. For more, read p. Editing the Configuration of the Repository. |
◆information on virus events, statistics, etc.
The program provides for two types of connections between the Dr.Web Enterprise Servers:
◆a parent-child type of connection, where the principle Server transfers updates to the subordinate one and receives information about events,
◆a peer to peer connection, where data types and transfer directions are set up individually.
An example of a multi-server structure is presented in Figure below.
|
A multi-server network
Here are some advantages of a multi-server anti-virus network:
◆receipt of updates from the Dr.Web GUS servers by one principle Enterprise Server and their subsequent distribution to the other Servers directly or through intermediates;
◆distribution of workstations between several Servers, decreasing the load on each of them;
◆consolidation of data from several Servers on one Server; the possibility to view all the data through the Dr.Web Control Center connected to such Server.
|
The Dr.Web ESS anti-virus monitors and prevents the creation of cyclic data flows. |