Utilizing promon for backup failure alerts

[urgent]

Howdy,
I've got a script running that generates daily reports for the last successful backup using the vst as a source.

Recently i've noticed that this process is not 100% proof and there's few situations that the database backup status time stamp doesn't align perfectly with the logic in the script i have.

I though of something before diving into the script again and figure out what to change, What if i can use promonitor since it actually "flags" the status for the last backup if it was a success or a failure and use that specifically to alert upon failures ?

I'd appreciate it if someone have come across such configuration and have an idea if promonitor (bravepoint) offers such functionality to alert upon failed backups.
Or using the VST to look for failed backups if its actually marked and flagged within its table.

Thanks in advanced !

 

[Rob Fitzpatrick]

I've never used BravePoint's ProMonitor so I can't help you there. But I assume their support people can.

These KB articles may help you:
How to determine if a full database backup or incremental database backup has completed successfully?
http://knowledgebase.progress.com/articles/Article/P124620/p

MstrBlk._MstrBlk-Tainted VST field returns only a value of 0 when 16 expected.
http://knowledgebase.progress.com/articles/Article/P136722/p

Note what the article says:

The above methods only directly allow you to determine WHEN the last SUCCESSFUL backup was done, but don't by themselves allow you to determine IF the last ATTEMPTED backup was successful. In other words, these methods don't report if the last attempted backup failed, but do provide confirmation of the successful backup, if you know when the last backup was supposed to have taken place. There is currently no way to determine if the last attempted backup was successful except by further coding.

That said, I suspect there may be some way to accomplish this. I am able to reproduce the (1553) error ("The last backup was not completed successfully.") in a test database. The error appears onscreen and in the DB log after opening the database. So obviously there is some flag that is set within the database to indicate this state. But it is not _MstrBlk._MstrBlk-Tainted. As of 10.2B07, it still shows 0 when it should show 16. I haven't yet tested with 11.3.1.