Group: Forum Members
Yes I suppose failure notifications could be made more "shouty" -- maybe the Reflect system tray icon that exists in V7 could persist with a warning overlay when a job has failed until the alert was acknowledged, for example. And if nobody was logged on when the job ran, it could pop up a dialog at the next logon that says, "There have been X failed jobs since the last user logon" -- although neither of those would be especially helpful in server use cases where there may be very long periods between interactive logons. But just as data points, the only other backup applications I've worked with in depth have been several versions of Veritas (later Symantec) Backup Exec, Retrospect, and the built-in Windows Backup tool, and none of those did things like this either, even though the first two serve arguably more critical roles in that they can be tasked with backing up multiple remote systems through agents, rather like Macrium Site Manager.
In terms of what IS available, Reflect's return code on completion is different based on the result of the job, so as long as you know how to work with batch files, VBScript, or PowerShell, you already have a "hook" that would allow doing something differently when a job fails. You'd start by having Reflect generate the initial script in the desired language, which will capture the return code from the job as a variable, and then customize subsequent action based on the value of that variable as needed. Otherwise, "shouting from the rooftops" is usually accomplished via email (plus possibly some mailbox-side rules to flag failure notifications), since even in situations where Internet connectivity isn't available to the PC running Reflect, there may still be an internal mail server or SMTP relay on the LAN that could allow this functionality to be used. But there are undoubtedly also cases where a system is kept off the Internet and there are no local SMTP resources available. And again, with V7 and a sufficiently recent version of Windows, there are also now Windows notifications, although a user has to be logged on at the time the notification is generated, which I suspect is a Windows limitation.
And out of curiosity, what is the "trivial programming exercise" to send a message to a user in an AD environment? The only thing I know of that resembles that is the Windows Messenger service, but that was disabled by default starting with XP SP2, and if memory serves, that sent the message to a particular computer, not to an AD user regardless of what device they were logged onto.