- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Backup full log vs truncated
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup full log vs truncated
They are in the downloaded log .zip. but file naming is odd. They are by job number, not name, and the backup_xxx.log has the list of runs and backup_ccc_copy.yyyyyyyyy has the results of the latest one, where xxx is the job number and yyyyyyyyy seems to be some kind of date/time code.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup full log vs truncated
Thanks. I already downloaded the full logs unzipped, found the relevant backup job (in my case backup_016.log and backup_016_copy.1687688196.log).
Amongst other things, it has the lines (start time seems to match the full log name):
start: 1687688196
finish: 1687688456
status: 0
In the filr backup_016_copy.1687688196.log, I see the following entry:
BACKUP_INFO_LOG_TRUNCATED:228
And in the dashboard via teh web UI, the backup job log shows:
... 228 lines were removed ...
After reviewing several different backup job logs, I noticed the the "truncated" message is always on line 1001, the size of the files vary from 40KB-111KB, so it seems related to line count rather than size.
All the logs I checked appear to have the same truncation going on, not the full logs at all. Any further ideas?