Ticket #68 (new enhancement)
More details when ReadError occurs
| Reported by: | achim | Owned by: | ben |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | bbackupd | Version: | 0.11rc2 |
| Keywords: | Cc: |
Description
Would it be possible to get more specific details whenever a ReadError? occurs? At the moment, the NotifyScript is called with a generic error:
// Notify system administrator about the final state of the backup
else if(mReadErrorsOnFilesystemObjects)
{
NotifySysadmin(SysadminNotifier::ReadError);
}
but a list of filenames/directory names that caused the problems would be fantastic. Is that implementable, maybe via errorCode or errorSubCode in the same routine?
Change History
comment:2 Changed 23 months ago by achim
It was my understanding that the NotifyScript is only called once in case one or more ReadError?(s) occured, not once for every error. I was merely wondering if the message in could read something like
WARNING: Read errors occured for the following files File A File M File Y
This would be very helpful for the e-mail notification that the users might get. It will tell them specifically what files are causing problems. At the moment, the NotifySysAdmin?.vbs defaul script is rather limited in usefulness:
subject = subjtmpl & " (unknown)" body = "The backup daemon on "&hostname&" reported an unknown error." _ & vbCrLf & vbCrLf & _ "==========================" & vbCrLf & _ "FILES MAY NOT BE BACKED UP" & vbCrLf & _ "==========================" & vbCrLf & vbCrLf & _ "Please check the logs on "&hostname&"." & vbCrLf SendMail from,sendto,subject,body

Do you really want this called thousands of times? What I'd do is to capture the logs between backup-start and backup-finish events and parse them into the form you want.