Hello

This was a top request from customers so we have listened and implemented it in BE 2010.

Check out BE 2010 at www.backupexec.com

Thanks for the ideas and keep them coming.

Peter 

Under what circumstance is a "missed" job not a failure? 

This is a BUG. It's a core function of backup managment, and it was a blatant design FAIL--one that could have been easily fixed. Now you want to sell that bug fix as a feature? Please. 

Would tend to agree with your comments, except that part about "easily fixed". ;-)

BE's job engine saw it differently however. The job never ran, so it never had a chance to end up in the state of "Failed" or "Successfull" that was needed to actually trigger the alert and subsequent notification that we all wanted to see.

Sorry for the amount of time it took to implement this alert, but it is there now in BE 2010. Let us know if its working as you need it to.

We definitely will try to be more responsive in the future on these critical requests. 

Peter

Hello,

I think I missed your main point. You wanted this hotfixed in 12.5 as a "bug".

We have good news. This patch is now available for download here seer.entsupport.symantec.com/docs/345174.htm as well as via LiveUpdate in BE 12.5.

I think this does hopefully help resolve one of your main complaints that you did not want to upgrade just to have this resolved.

Again, apologies for taking so long.

Peter