Description of problem: Since users may define 3rd party backups that run engine-backup automatically, we should refer them to last run log location in the notifications in the UI about backup not preformed.
In my opinion this one and Bug 1188143 are identical. The engine-backup procedure should add events straight to the database either on success, or on failure (no need for "started" as the backup process should be fast, even on large datacenters). The failure/success should come with a message as well, that will be put in the events table, and should contain the message (with the log path, for example). Yaniv?
(In reply to Oved Ourfali from comment #1) > In my opinion this one and Bug 1188143 are identical. > The engine-backup procedure should add events straight to the database > either on success, or on failure (no need for "started" as the backup > process should be fast, even on large datacenters). The failure/success > should come with a message as well, that will be put in the events table, > and should contain the message (with the log path, for example). > > Yaniv? Sounds good to me. Add this to the other bug and closing this one. *** This bug has been marked as a duplicate of bug 1188143 ***