Exchange Server Recovery Issues

Aplica-se a: System Center Data Protection Manager 2010

The following table provides troubleshooting guidance that supplements the specific error messages that you may encounter during recovery of Exchange Server data.

Exchange Server Recovery Issues

Issue Possible Cause Resolution

Recovery fails when trying to mount or dismount the Exchange Server database.

If you rename an Exchange Server storage group after protecting it, when DPM performs a recovery operation, the recovery will fail when trying to mount or dismount the database.

The caption of the Exchange Server storage group is used to mount and dismount the Exchange Server databases. If you rename the storage group, the caption stored in the protected object will be different from the actual caption and the mount and dismount operations will fail. If this occurs, we recommend that you do the following:

  • Rename the storage group back to the original storage group name.

  • When you detect a name change, update the caption name in the protected object.

  • You can use the component name to identify a storage group to mount and dismount the databases under it instead of the caption name.

ID 104: An unexpected error occurred during job execution.

Exchange Server 2007 requires credentials of an Exchange Server administrator for dismounting or mounting the database.

The DPM replication agent requires Local System account privileges, and therefore, recovery fails when trying to recover data on an Exchange Server 2007 server that is configured for clustered continuous replication (CCR).

Perform the following steps to provide the user with the Exchange Server Administrator privileges:

  1. From the command prompt, type dcomcnfg, and then click OK.

  2. On the Component Services screen, expand Component Services, expand Computers, expand My Computer, and then click DCOM Config.

  3. Right-click ExchangeCmdletsWrapper, and then click Properties.

  4. In the Properties dialog box, on the Identity tab, select This user.

  5. Provide the credentials for the account that has Exchange Server Administrator privileges, and then click OK.

Recovery to the latest Programmable Interval Timer (PIT) fails.

If the embedded database (.edb) and the streaming (.stm) files are renamed and then the databases are not dismounted and then remounted, the recovery fails.

Dismount and remount the databases, and then retry the recovery. If you cannot dismount and remount the databases, restore the files and then copy them with a clean shutdown. Then move the files to the original location and mount the database.

Mailbox recovery fails with a catastrophic error when recovering to an alternate Exchange Server 2003 database.

The restore flag was not set when attempting to recover a mailbox to an alternate Exchange Server 2003 database.

After the recovery fails, go to the Exchange Server Management Console, set the recovery flag, and then mount the database.

The Recover-RecoverableItem cmdlet fails specifying that the specified recovery options were not valid.

If you specify the active server name when recovering a storage group or database for Exchange Server Clustered Continuous Replication (CCR) through the command-line interface (CLI), the recovery fails.

The –TargetServer attribute should be ResourceGroupName.ClusterServerName.DomainName.

eseutil execution fails with error code 0xfffff764 in the Application log.

This error occurs if the .stm and .edb files that are associated with a database are not in the same folder. When this occurs, the database is not brought to a Clean Shutdown state.

To bring the database to a Clean Shutdown state, move the .stm file to the same folder as the .edb file, and then run eseutil with the appropriate parameters.