Link to home
Start Free TrialLog in
Avatar of Dave Robinson
Dave RobinsonFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Backup Exec 2010 email notifications

We have been using Backup Exec 2010 since approx. April 2011 and until now have had no problem with email notifications being received after every backup. A couple of weeks ago they stopped being received. Nothing on the server has been changed, no updates, new software etc.

The SMTP is working fine as I can connect with telnet. I've followed the troubleshooting here on Symantec. When I run SGMon.exe to monitor what is happening when a test email is sent I get nothing - literally nothing, I get the header of the log then not a single entry I'm not getting a notify return code or anything else that might help identify where it is failing.

Is there any other troubleshooting or obvious cause?
Avatar of tolinrome
tolinrome
Flag of United States of America image

Haven't used BE in a while. When you send a test email without sgmon running, do you at least receive the email at all? I know its not a precise solution but sometimes when I ran into BE problems, doing a reinstall solved it. I don't mean a complete reinstall, but from reinstall wizard from inside the application, takes less than 5 minutes.
Anything in the application logs?
Avatar of Dave Robinson

ASKER

Thanks for the reply, wasn't aware of the reinstall wizard, I'll give that a try first. The logs aren't showing anything relating to sending notifications at all.
Are you getting a test email at all, even if its blank etc?

Make sure you dont have the check box ticked for SMTP Authentication in the notification setup. Make sure the IP address of the BUEXEC server is listed on the Exchange server as a relay address (receive connector).
Even though you can connect to the box using telnet, try sending an email within telnet and see if you receive it.
I'm not seeing a reinstall wizard anywhere inside BE 2010, where should I be looking? I can run an install from the original media but that's looking to run the full install process again.
I can't remember exactly where it is since I do not use Backup Exec anymore. But somewhere in the Wizard of the application you can do the reinstall steps. Or you can try doing it through add/remove programs in Control Panel. Anyway, can you send a test email?
Just be careful, the uninstall inside to add/remove programs will probably uninstall the entire application. The one within the application won't.
Not sure but I may have found a potential cause. Although I can make an SMTP connection through telnet I can't actually send a mail. I get a return of 530 5.7.1 Client was not authenticated. I've checked on the Exchange server and on the hub transport receive connector anonymous users are allowed so I'm not too sure why it's doing that.

To be honest I'm not sure if that is the root of the issue or not as I'm certain no one has changed any settings on the Exchange Server and the notification emails were previously sending with no issue.
ASKER CERTIFIED SOLUTION
Avatar of tolinrome
tolinrome
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Apologies for the delay in responding but I think there is some good news. I've been testing the SMTP connection and I can now get it to work however it will only work if I set the receive connector to allow anonymous users and also set the receive connector to disable authentication.

Once I do that I can successfully send a test through Telnet and also a test through Backup Exec.

My concern now is that if I leave the receive connector in that state I have left it too open however this receive connector is only set to receive mail from remote servers that have an IP address of one of the internal servers - they are all individually listed. Am I correct in saying this is OK as it will reject an attempt to send mail through the Exchange Server if it originates from any other IP?
That is correct, if the connector is set for the IP address of your internal subnet then you're fine
Thanks for the help.
your welcome.