Forum Discussion

dmagnant's avatar
dmagnant
Level 3
9 years ago

SR 2013 - Generating Excessive eMail Alerts & Error Code Info Needed

Hello,

I am running System Recovery 2013 Virtual Edition (11.0.2.49853) on a number of Windows Server 2013 Hyper-V Guests.  I have the client software configured to generate email alerts for medium and high priority failures.  In the past two weeks three of the guest VMs have generated errors which have resulted, in the case of two, the generation of 36 email alerts within 37 seconds, and in the case of the third, the generation of 48 email alerts within 57 seconds.  This extreme redundancy of email alerts is something I do not recall experiencing in the past. 

The two systems that generated 36 email messages indicated error E4BD0012 with no further explanatory detail either in the email message or the event log.

The system that generated 48 email messages indicated error E7D10017 and EC8F1F61 for the high and medium priority messages respectively.  This error indicates a failure to delete an offsite backup file.

Regarding the above I have three questions:

1.) By what logic is it necessary to generate 30 to 50 repeititive email messages within a one minute span and, more importantly, is there some way to throttle this behavior?

2.) Does Veritas have any further information on error code E4BD0012?

3.) Regarding the E7D10017 and EC8F1F61 errors, nothing has changed with regard to the offsite backup NAS or the authentication used to access it.  The error messages points to a specific file, which is present.  Is there any reason this error should suddenly pop up?  The system has been backing up in this configuration without issue for nearly two years.

Thank You,

Dale

    1. There is no way to throttle it I'm afraid. The following log file may provide more details/clues - \ProgramData\Symantec\Symantec System Recovery\Logs\Symantec System Recovery.log.txt
    2. The only 'hit' I could find on our knowledgebase for that error is this (http://www.veritas.com/docs/000087625). Not sure how relevant it is though.
    3. Again, the above log file may give more clues ..