Exchange 2010 backup or resource credential test fails with the error "0xe000038d - Backup Exec could not backup the Exchange database because it could not find a healthy copy of the database".

Article:TECH125261  |  Created: 2010-01-25  |  Updated: 2013-10-17  |  Article URL http://www.symantec.com/docs/TECH125261
Article Type
Technical Solution


Issue



Exchange 2010 backup or resource credential test fails with the error "0xe000038d - Backup Exec could not backup the Exchange database because it could not find a healthy copy of the database".


Error



"0xe000038d - Backup Exec could not backup the Exchange database because it could not find a healthy copy of the database".

UMI: V-79-57344-909


Solution



1. Ensure that the Exchange Management tools are installed on the Backup Exec media server.  http://www.symantec.com/docs/HOWTO24128  

2. Ensure that the Backup Exec logon account being used to access the Exchange server is part of the Local Administrators group on the Exchange 2010 server.

3. Ensure that the Backup Exec logon account is a member of the "Organization Management" Role Group in Exchange 2010. To confirm the same please follow the steps mentioned below.
 
a. Open the Exchange "Role Based Access Control (RBAC) User Editor" (Figure 1 and Figure 2)

Figure 1:

 

Figure 2:

 

b. Add the Backup Exec LOGON account to the group (if missing) and click "OK" and then "Save". (Figure 3)

Figure 3:

 

c. Verify the Backup Exec LOGON account is now a member of the group. (Figure 4)

Figure 4:

 

d. Log out of the Exchange "Role Based Access Control (RBAC) User Editor."

 
4. Registry rights on the remote agents may be missing. Uninstall and reinstall the Remote Agent. 
 
5. Exchange VSS writer is failed. If the Exchange writer is failed, to make it stable, either restart the Exchange information store service or restart the server. (Recommended to do out of production hours).
 
6. Exchange replica writer is unavailable on passive node. If the Exchange replica writer is missing, please restart Exchange replication writer service. If the issue persists, contact Exchange Administrator or Microsoft. This issue is seen in DAG - passive copy backup.

In case if your Exchange Administrator configured the registry keys given in the below Technet article, to take windows Backup of Exchange passive node, you may face this issue.

http://technet.microsoft.com/en-us/library/dd876851.aspx

Caution:
Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

In this case please change the value of the DWORD value Enablevsswriter to 1 and restart Exchange Replication Service.

7. Exchange Management shell is missing on passive. (Noticed after installing Exchange 2010 SP1). 

Please check whether Exchange Management Shell shortcut is present in the Start->Programs->Microsoft Exchange Server 2010. If not please get it configured with help of Exchange Admin or Microsoft. Please refer to the below link for a workaround if you have this issue.

http://blogs.technet.com/b/nawar/archive/2010/09/03/exchange-management-shell-ems-missing-after-applying-exchange-2010-sp1.aspx


 


Supplemental Materials

SourceUMI
ValueV-79-57344-909
Description

0xe000038d - Backup Exec could not backup the Exchange database because it could not find a healthy copy of the database


SourceError Code
Value0xe000038d
Description

Backup Exec could not backup the Exchange database because it could not find a healthy copy of the database


SourceRight Now Web
ValueUsing Windows Server Backup to Back Up and Restore Exchange Data
Description

 http://technet.microsoft.com/en-us/library/dd876851.aspx




Legacy ID



346417


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


Terms of use for this information are found in Legal Notices