Browsing Exchange 2010/2013 databases fails with error "Backup Exec could not back up the Exchange database because it could not find a healthy copy of the database"

Article:TECH211305  |  Created: 2013-10-07  |  Updated: 2014-04-22  |  Article URL http://www.symantec.com/docs/TECH211305
Article Type
Technical Solution


Subject

Issue



Browsing Exchange 2010/2013 databases in backup job fails with error "Backup Exec could not back up the Exchange database because it could not find a healthy copy of the database". Backup if performed fails with error "Final error: 0xe0000391 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again."

 


Error



Error while Browsing Exchange databases in backup selection:

Error in the failed Backup Job Log:

Final error: 0xe0000391 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-913

Error in the debug on Exchange server:

BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:08.593 [fsys\shared] - EseProcess::Init: OpenThreadToken successful
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.123 [fsys\shared] - ESE07 process not ready
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [fsys\shared] - ESE07, failed to set options, 0x80004005
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [fsys\ese] - [EseE14::GetTargetDatabaseCopyStatus] machine:WINDOWS2012 database:Mailbox Database 1999579866 targetSite:null options:0x8 flags:0 count:0
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [fsys\shared] - ESE07 process not ready
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [fsys\ese] - Error (0x80004005) !!! EseE14::GetTargetDatabaseCopyStatus("WINDOWS2012", "Mailbox Database 1999579866") failed
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [fsys\ese] - [ESE_AttachToDLE] Fail to get database copy information. Abort the backup (0xe000038d) !!!!!
BEREMOTE: [10/07/13 09:24:09] [6728] 2013-10-07T09:24:09.139 [ndmp\ndmpsrvr] - DSEnumerator failed with -536870003: Backup Exec could not back up the Exchange database because it could not find a healthy copy of the database.

 


Cause



This issue will come up if monad.exe.config file is missing from X:\Program Files\Symantec\Backup Exec\RAWS directory on Exchange server

Note: X:\ is the volume where Backup Exec Remote Agent is installed.


Solution



If monad.exe.config file has been renamed or has been quarantined by anti-virus software then renaming/restoring back the file will fix the issue. If the file is not found then uninstalling Backup Exec Remote Agent from Exchange 2010/2013 server and then re-installing the Remote Agent will bring back the file.


Supplemental Materials

SourceUMI
ValueV-79-57344-913
Description

Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again

 



Article URL http://www.symantec.com/docs/TECH211305


Terms of use for this information are found in Legal Notices