Log Settings (Server)
Use this dialog box to define a maximum log size and what DeviceLock Enterprise Server should do if the log becomes full.
NOTE: These settings are stored in the database and they are specific to the log but not to DeviceLock Enterprise Server. This means that, if there are several DeviceLock Enterprise Servers using one database, all have the same log settings.
Enable the Control log size flag to allow DeviceLock Enterprise Server to control the number of records in the log and delete outdated records (if necessary) to clean up the space for new ones. Otherwise, if the Control log size flag is disabled, DeviceLock Enterprise Server uses all available space for the SQL Server's database to store the log.
In the Maximum log size parameter you can specify the maximum number of records that this log can contain. Please note that, if there is more than one DeviceLock Enterprise Server using this database, then the actual number of records in the log can be a little larger (by a couple of records) than the specified value.
To specify what DeviceLock Enterprise Server should do when the log is full (when Maximum log size is reached) select one of these options:
- Overwrite events as needed - the server will overwrite old events if Maximum log size is reached.
- Overwrite events older than - specifies that records that are newer than this value will not be overwritten (specified in days).
- Do not overwrite events (clear log manually) - the server will not overwrite old events if Maximum log size is reached and you will need to clear events manually.
If you wish to reset current settings to the default values, use the Restore Defaults button. Default values are:
- The Maximum log size parameter is set to 10,000 records.
- The Overwrite events older than option is selected and set to 7 days.
If there is no space for new records in the audit or shadow log and there is nothing to delete then DeviceLock Enterprise Server doesn't remove data from remote users' computers. This prevents you from loosing the data due to lack of space in the log. When some space becomes available in the log, DeviceLock Enterprise Server moves the remaining data from users' computers to this log. It's best to avoid accumulating shadowed or audit data on users' computers. We recommend that you monitor the DeviceLock Enterprise Server's log on a periodic basis, watch for warning messages and adjusting log settings appropriately.
If there is no space for new records in the deleted shadow data log and there is nothing to remove, then DeviceLock Enterprise Server just drops any new records. To avoid loosing audit records in this way, we recommend that you monitor DeviceLock Enterprise Server's log on a periodic basis and watch for warning messages there.
If there is no space for new records in the server's log and there is nothing to remove, then DeviceLock Enterprise Server just drops any new records.