Someone will be my hero if they can figure this out for me....
We are running BackupExec on two separate boxes within our network -- one copy on our corporate domain, the other within a DMZ domain. The 'corporate' version of BackupExec is 9.1 (rev 4691) and is running on Windows 2003 Server. The 'DMZ' version is BackupExec 9.0 (rev 4454) running on Windows 2000.
Here's what's going on.... both of these servers are setup to notify me each night (via SMTP/email) when a job has succeeded or failed. Currently, neither of those notifications is working. Easy enough to fix, right? Well, not quite. On both servers, when I choose to "test" the SMTP configuration the message comes through just fine and very quickly! Not once has the "test" ever failed on either server. I have the recipient configured, enabled, and selected within every backup job, but notifications are never received. On the 'DMZ' instance, however, I restarted all of the services and received notifications for about 3 days -- and two emails each time -- then they stopped working after that. The 'corp' instance has never notified me properly following a backup job. On both servers, the backups themselves are working just fine.
Ok. Here's the last wrench in this situation. Our 'corporate' domain is new and so is the install of BackupExec 9.1. Also, we're running a new install of Exchange 2003. The 'DMZ' install of BackupExec has not changed at all in this domain switch *except* that it's now pointing to a different IP address for SMTP communication. Again, the "test" messages work just fine. I would understand if my new install were mis-configured and notifications were messed up, but I can't find any reason why the old(er) install of BackupExec 9.0 in our 'DMZ' domain would've been affected by any of this. Hmmm.
Anyhow, my apologies for the lengthy description. I hope someone might be able to point me in the right direction.