Exchange 2003 backup with Granular Recovery Technology (GRT) option enabled fails if two databases with the same database file names are included in the same backup job

  • Modified Date:
  • Article ID:000035443


Exchange 2003 backup with Granular Recovery Technology (GRT) option enabled fails if two databases with the same database file names are included in the same backup job.

This also applies if the Exchange databases are stored in nondefault locations. Check each loaction and confirm no duplicate names, even on different volumes.

Error Message

Database was not found, or could not be accessed
Final error: 0xe00002fe - Cannot log on to MAPI with the specified credentials. Review the resource credentials for the job, and then run the job again.


SGMON debug log shows the following error message:

 JetExternalRestore(2) - ERROR::RC = -1216 - -1216 An outstanding database attachment has been detected at the start or end of the recovery, but the database is missing or does not match attachment info.


Exchange 2003 backup with GRT enabled fail if the backup contains a storage group which contains two Exchange database files with the same name but located in different paths.

For Example

Exchange 2003 contains storage group named First Storage Group. This storage group contains two mailbox stores Test1 and Test2 with the same database file name 'Test.edb' located in C:\Program Files\Exchsrvr\MDBDATA\test.edb and C:\Program Files\Exchsrvr\MDBDATA\Exchdata\test.edb respectively.


To workaround the issue follow either of the steps listed below:

1. Run non-GRT backups of Exchange and use Recovery Storage Group to restore the mailboxes/mail items.


2. Backup the databases separately however note that in this case the transactions logs will not be flushed.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers. 
There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here.  Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.  For information on how to contact Symantec Sales, please see

Applies To

This issue has been reported with Backup Exec 11d, 12.0, 12.5 and Backup Exec 2010

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)