User`s guide

21
log tabs. Events older that X months will be deleted.
Delete alert logs older than X months
Delete event logs older than X months
Delete scan logs older than X months
Clean up every X minutes – settings above will be
applied every X minutes.
When deleting events (by administrator or functions
described above) no physical cleaning directly from the
database le is done. To clean the events directly from the
database (this will compact the size of database le), it is
necessary to set the following option:
Compact every X (days, weeks, months)
During this activity the service of RA server is
temporarily stopped (for maximum few minutes) till
the database is “cleaned”. In this time the RA server will
not be able to accept console requests and workstation
information. Therefore it is no recommended to do this
activity too often and during the heavy trac.
Loggig Log
Enable logging
– enables logging of RA server events
NOD32 RA server is able to log to the le (Log
lename), whereas the size of this le can be restricted
(Rotate when greater than). If it greater, it is rotated. In
Log verbosity part it is possible to set the verbosity of log
events.
At the same time it is possible to enable log to OS
application log (Log to OS application log) or enable log
over database (not recommended).
Replication Log
Replication „to“ settings
Enable „to“ replication – enables replication –
described in “Large Hierarchical Networks” chapter.
Upper server – the address (IP or according to DNS)
of superior RA server to which the data replication from
just congured RA server will be applied. From the picture
in “Large Hierarchical Networks” chapter it is obvious
what should be written in this column, see upper server
attribute.
Replicate every XX minutes – replication frequency
(every XX minutes)
Replicate Up Now – instant application to chosen
upper server
Checkboxes on the left part enable to dene log
types (alert, event, scan), which can be replicated
(transferred) to superior RA server on administrator’s
request. Checkbox in the right part enables dening if this
should be done automatically (Automatically replicate ...).
It is not necessary to activate automatic log replication.
Administrator can request them individually from inferior
server any time. Thus the transmission band among RA
servers can be partly saved.
Replication „from“ settings
Enable „from“ replication – ticking this option in Allow
servers column allows to dene RA servers (their name),
from which the RA server will accept replication requests.
Higher number of servers can be separated by commas.
Standard replication runs on TCP 2846 port, thus it
can be changed (on inferior server directly in this tab, on
superior – upper server in Other Settings tab).
Other settings Tab:
SMTP settings
Server - SMTP Server address, through which the
reports will be sent, or requests for remote installation
via email
Sender address
- e-mail address which will be set as
the „sender“ in outgoing e-mails.
Allow new clients
– Clients are, by default, added to
the list (the Clients tab in console) automatically at the
moment when RAS registers the rst attempt to establish
connection from a new, so far unregistered client module
of NOD32 Control Center. Ticking this option enables
automatic adding of new clients to the clients list. If you
leave this option unchecked, automatic adding will not
be enabled. The setting does not apply to new clients,
which were added to the clients list from child servers by
replication.
Automatically reset “New” ag by new clients
–
denes whether a newly added client will be marked by
the attribute New or not (turned o = the attribute New
assigned). More detailed information can be found in the
chapter “Clients”.
In the lower part numbers of ports where the RA
server will “listen” can be changed.
chapter 2 / Centralized management – NOD32 Remote Administrator