Archive:Day Log 4.4: Difference between revisions
(Updated and new screenshot.) |
(Added missing screenshot for error log.) |
||
| Line 19: | Line 19: | ||
==={{anchor|error log}}Error Log=== <!--T:6--> | ==={{anchor|error log}}Error Log=== <!--T:6--> | ||
The error log is the subset of the entire day log. Only error messages will be printed out here. | |||
The error log is the subset of the entire day log. Only error messages will be printed out here.</translate> | |||
[[Image:Error_log_4.4.png|center]]</translate> | |||
Revision as of 12:18, 2 March 2017
Day Log
SEP sesam writes a continuous protocol for each backup day. All modules write messages with a time stamp attached to it. Each message contains a unique code consisting of message type (I=information, W=warning, E=error ), number and originating module.
The time selection allows filtering of the output.
|
Note |
| A backup day is defined by two newday events. |
These protocols are the first and most important starting point for problem analysis. The user can find detailed help for problems and error messages in the SysAdm Guide. These errors and a PuTTy copy of the log file can be sent to support@sep.de to provide detailed information.
Error Log
The error log is the subset of the entire day log. Only error messages will be printed out here.
