The Backup Exec console does not show individual mailboxes in the restore selections for successful Granular Recovery Technology (GRT) enabled backup sets when the database files have an extension other than the default.


The Backup Exec console does not show individual mailboxes in the restore selections for successful Granular Recovery Technology (GRT) enabled backup sets when the database files have an extension other than the default.


In Exchange by default the extension of the mailbox store or the public folder database files is set to .EDB and .STM. The extension can be changed to a non default one at the time the database is created.

However Backup Exec currently does not support GRT enabled backups of such Exchange Databases with non-default extension. If a GRT enabled backup is attempted on such databases then the following behavior is noted even though the backup job is successful.

1. If the backups are targeted to a Backup to Disk (B2D) device, then the Mailbox/Public Folder Store with non default extension itself will not be seen in the restore view.

2. If backups are targeted to a tape device, then the Mailbox Store is seen, but the selections cannot be extended further to display the individual mailboxes.

This behavior can be caused by the extension of the Mailbox/Public Folder Store database file being different than the default. Granular Restore Technology currently only supports database files using .EDB and .STM extensions. If any other extensions is used like for example .MDB, no granular restore view of mailboxes for this database will be displayed.  

Note: This behavior is present in GRT enabled backups for Exchange 2000 and Exchange 2003 only.


I. Use available tools from Microsoft to move the mailboxes to a new or existing Mailbox Store that has a database file with .EDB extension. For instructions on how to move the mailboxes and/or create new Mailbox Stores please review the product documentation for Microsoft Exchange.

II. In the event of a restore from existing backup set(s) please refer the suggestions/alternatives mentioned below:

   1. For backup sets on disk:

    If the backups were done to a B2D device, then the restore selection has to be made from the root of the Storage Group and all databases in the Storage Group have to be restored together with the Mailbox Store(s) that has the non supported database file extension. All the databases within the storage group will be restored along with the Mailbox Store that may not be viewable under Restore Selections.
    It will not be possible to run a restore of the database with non-default extension by itself. The entire Storage Group will have to be restored. If the entire Storage Group cannot be restored to the production Exchange server, then the restore can be done to a recovery server. Please refer the Related Documents section for more information.  
     Note: While running the restore to the recovery server, uncheck the option to commit and mount the database in the restore job properties. Once the restore completes copy over the restored database and temp files to the production exchange server and recover the database using ESEUTIL.  Please refer Microsoft documentation for more information on how to recover a single database using ESEUTIL.
    2.  For backup sets on tape:

     If the backup was done to Tape Device, then a Mailbox Store Database restore will function as normal.

     If an individual mailbox needs to be restored, then the corresponding mailbox database can be restored to the Recovery Storage Group (RSG). Following a successful restore to the RSG, the contents of the required mailbox can be exported using the Exmerge tool.

      Note: For Exchange 2003 if the Information Store backup is done using Volume Shadow Copy Service (VSS) then such backup sets cannot be restored to a RSG.

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.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see 
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

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)