4 4 3:Tips for Backup Troubleshooting
Analyzing SEP sesam log files is very useful for detecting the operation(s) that caused errors or malfunctions, for example, in case of unsuccessful backup.
SEP sesam creates two protocols or log files for each backup day: the status file (<date of day>.status) and the day log (<date of day>.prt). An error log (<date of day>) is a subset of the day log, where only error messages are recorded.
Log files can be printed or sent by email. The directory where the log files are stored is
<SEPsesam>/VAR/prot. You can check backup logs (state, day or error) in the GUI (Main Selection -> Logging -> State/Day Log/Error Log). As of 4.4.3 Beefalo V2, you can also check your system logs online by using new Web UI. For details, see SEP sesam Web UI.
Tips for backup troubleshooting
In the case of an unsuccessful backup, you should follow these tips:
- Find out when the problem occurred using the day log (.prt) and the status log (.status). The day log shows the causal progression of all SEP sesam activities of the backup day. The files with a file extension ending in .prt.err contain just the error messages from the day log.
- Display the directory files chronologically (with ls -lart on Linux).
- Log files should be read backward from the end of file. If a backup has failed, the indication of errors and their causes may usually be found at the end of the respective log file.
- Compare non-working and working backups:
- Check when was the last successful backup of this task.
- Detect the differences between not and bck logs by comparing two different backups.
- Find out if there were any changes in the network or on the client.
- The values of database calls in DB_ACCESS have the following explanations:
- result = 1: The database access is OK.
- msg > 0: Amount of the result > 0.