> Expert > Backup and Restore Agents > Exchange Agents > Exchange Legacy Agents > Exchange Mailbox (Classic)

Frequently Asked Questions (FAQs) for the Exchange Mailbox (Classic) Agent

Updated

Why do I use the Exchange Mailbox (Classic) Agent as opposed to the Exchange Database Agent?

Primarily, you can use the Exchange Mailbox (Classic) Agent as a system administrator tool to:

  • Perform small restore operations in the course of day-to-day database use (for example, retrieve data accidentally deleted by a user).

  • Restore part of a server (that is, a subset of the mailboxes). This can be useful when you need to bring part of a storage group or store online as quickly as possible after a system failure.

How can I use the Exchange Mailbox (Classic) Agent with other Exchange agents?

If you have all Exchange Server agents configured, you can back up Exchange data using all of them. For example, might may want to run daily backups of your private information store using the Exchange Mailbox (Classic) Agent. This way, you can restore any individual mailbox on the server to within one day of failure. You can use the Exchange Public Folder Agent to restore Public Folders or Exchange data contained in the Public Folders. At the same time, you might want to schedule monthly backups of your Exchange server using the Exchange Database Agent, with daily incremental backups in between. This way you can recover efficiently in the event of a server crash. Although your private information store is backed up by Exchange Database Agent, the backups are created differently and serve different purposes.

Can I use the Exchange Mailbox (Classic) Agent to back up Active Directory information used by Exchange?

No, use the Windows File System Agent to back up this type of data. Other types of data that are backed up by the Windows File System Agent include:

Exchange Entity

Associated Files

Personal Information Store (PST)

*.pst

Personal Address Book

*.pab

Offline Folders

*.ost

Do I need to remove the MAPI32.dll prior to performing a non-PST restore?

If you previously added the MAPI32.dll file to software_installation_directory\Base on the client to support PST recoveries to PST, then you must remove that file prior to performing a non-PST restore, recover, or retrieve operation for Exchange. Otherwise, such jobs might go into a pending state.

Must I disable circular logging for mailbox backups as I do with database backups?

No. Since Exchange Mailbox (Classic) Agent does not use transaction logs, circular logging can remain enabled providing no database backups are scheduled at the same time as a mailbox backup.

Why can I not locate the restored messages of the root folder of an Archive Mailbox when they are restored to a .pst file?

When you restore messages of the root folder of an Archive Mailbox to a PST file, the messages are restored to the Inbox folder under the PST node.

If messages from the root of Archive Mailbox and Inbox of Primary Mailbox are restored to a PST file, all the messages are treated as Primary Mailbox messages and are restored to the inbox under the PST node.

In case the Inbox folder is unavailable, the restore to PST operation creates an Inbox folder and restores the messages of the root folder of the Archive Mailbox to it.

What happens to the backup jobs after switching from Backup Only Items that Qualify for Disk Cleanup to Backup Everything?

After switching from "Backup Only Items that Qualify for Disk Cleanup" to "Backup Everything" mode, the next backup job backs up everything.

How do I fix MAPI issues?

If you experience MAPI issues, you should first do the following:

  • Check the following:

    • The Exchange Services are running.

    • The databases are mounted.

    • Check the Windows Application Event logs on the Exchange server for any errors.

    • For Exchange 2010, check the logs located in Exchange_installation_path\v14\Logging\RPC Client Access) for any errors.

  • If you cannot open an existing Outlook profile, create a new profile.

  • If you get a MAPI_E_FAIL_ON_PROVIDER (8004011d) error while running a backup, check if the Outlook profile is in the Cache Mode.

    See MAPI_E_FAIL_ON_PROVIDER (8004011d) for more details.

  • If multiple backup jobs that run in parallel are failing with profile errors, create the CreateProcessSpecificProfile additional setting.

    See Multiple Jobs Failing with Profile Errors for more details.

  • To fix Service Account permission issues, use ADSIEDIT for Exchange 2007 and set extended rights to Receive As for Exchange 2010.

    See Backup process remains in a pending state for more details.

  • For Outlook, if automatic profile creation is failing, make the service account name unique for the auto discovery process.

    See Automatic Profile Creation is Failing for more details.

  • If you receive the MAPI_E_NETWORK_ERROR, for Exchange 2010, make sure that there is connectivity to the Client Access Role Server. For Exchange 2007, make sure that there is connectivity to Mailbox Role Server.

  • If you receive the Could Not Open the Exchange Private Message Store with Profile ExchAdm (E_FAIL (0x80004005)) error message, verify that the extended rights on the service account have Receive As set on all database on the Exchange server.

    See Could Not Open the Exchange Private Message Store with Profile ExchAdm (E_FAIL (0x80004005)) for more details.

  • If you receive the ERROR CODE [28:153]: The Mailbox Profile Used by this Product is Invalid error message, verify that the extended rights on the service account have Receive As set on all database on the Exchange Server.

    See ERROR CODE [28:153] for more details.

  • For Exchange 2010, if you receive the "Cannot Open Folder for Mailbox “username” MAPI_E_NOT_FOUND (0x8004010f)" error message during backups, verify that the extended rights on the service account have Receive As set on all database on the Exchange Server.

    See MAPI_E_NOT_FOUND (0x8004010f) for more details.

  • If the backup process stops responding when you enable or disable MAPI, create a new profile with Enable Referral option selected.

    See Process Stops Responding While Enabling or Disabling MAPI for more details.

  • The process of profile creation might fail if the service account name is not unique. In addition, if you use Exchange Server 2010, verify that the Exchange server name specified in agent properties has the Client Access Role installed.

    See Unable to Log on to Microsoft Information Store or Profile Creation Is Failing for more details.

  • If the backup process stops responding with the extask.cpp:HrInitialize(1342) Initializing MAPI subsystem error message, uninstall MAPI CDO and install MAPI.

    See extask.cpp:HrInitialize(1342) Initializing MAPI subsystem error for more details.

FAQ - Can Outlook 2013 be installed on the same machine as Exchange Server 2013?

The Exchange package should not be installed on the Exchange server.