Table of Contents
Advertisement
PRAESENSA
–
–
11.5
Database
On the Database tab, the properties of the logging database can be defined.
Recent events
Use the Recent events block to define the number of recent events that is displayed in the
Logging Viewer.
Database file
Use the controls in the Database file block to define:
1.
2.
3.
Flush events
Use the controls in the Flush events block to flush events from the logging database. Proceed
as follows:
1.
2.
3.
4.
Bosch Security Systems B.V.
The location of the overflow files.
–
This can either be entered in the Folder field or selected from the file system with
the Browse button.
The critical size of the overflow files in the Critical size field.
–
When the critical size is reached, the Logging Server displays a message: The
Logging Server overflow files have reached their critical size. Please clear or delete
the overflow files.
–
When the overflow files have been deleted or reduced in size, the Logging Server
must be restarted to remove this message.
–
Notice: The overflow files are comma separated value files (*.csv).
The location of the logging database. This can be entered in the upper text box.
–
Notice: For experts only: the logging database is a Microsoft® Access file, which also
can be opened with Microsoft® Access. If for any reason the database becomes
corrupted and the Logging Server is not able to access the database, the database
can be repaired with Microsoft® Access.
The critical size of the logging database. When the critical size is reached, the Logging
Server displays the following message:
–
The Logging Server database has reached its critical size. Please decrease the
logging expiration periods.
It is possible to make a back‑up of the logging database (even if the Logging Server is
running). When a back-up is made of a running Logging Server, it is advised to wait for a
moment at which a low number of events is expected (i.e. when there are almost no
running calls). Events that occur while the back‑up is made will not be copied to the
logging database.
If the fault events must be flushed from the logging database, put a checkmark in the
Fault events check box.
If the general events must be flushed from the logging database, put a checkmark in the
General events check box.
If the call events must be flushed from the logging database, put a checkmark in the Call
events checkbox.
Click the Flush now button to flush the selected type of events from the logging
database.
–
If the Move expired events to overflow file field of the selected type of events on the
Logging Expiration tab contains a checkmark, the selected type of events are flushed
to an overflow file.
–
If the Move expired events to overflow file field of the selected type of events on the
Logging Expiration tab does not contain a checkmark, the selected type of events are
deleted from the database.
Configuration manual
Optional: Using the Logging Server | en 123
2020-09 | V1.20 | PRAESENSA 1.20
Advertisement
Table of Contents
