IBM Support

IBM Tivoli Storage Manager FastBack for Microsoft Exchange 6.1.x.x Known Issues and Limitations

Technote (FAQ)


This document describes the known issues and limitations for IBM Tivoli Storage Manager FastBack for Microsoft Exchange Version 6.1.x.x


The following known issues and limitations apply to Tivoli Storage Fastback for Microsoft Exchange (FastBack for Exchange) 6.1.x.x.

  • Multiple Problems Found When Using Microsoft Exchange 2010 SP3 and MAPI/CDO 6.5.8309.0

    After applying:
    • Microsoft Exchange 2010 Service Pack 3, or
    • Microsoft Exchange Messaging API (MAPI) Client and Collaboration Data Objects (MAPI/CDO) download version 6.5.8309.0

    Fastback for Microsoft Exchange will not work properly.

    Support for both items is planned for availability in Fastback for Microsoft Exchange

    Additional details for both limitations can be found in APAR IC91211 here:
  • Garbled and unreadable mailbox folder names result when mailboxes from multiple locales are restored in the same operation.

    After a mailbox restore operation, the restore mailbox folder names might be garbled and unreadable. This problem arises because Fastback for Microsoft Exchange cannot handle items that are created by using multiple language settings within the same mailbox with languages that are displayed in different character sets.

    For example, a customer has the following groups of users:
      • Users in China
        These users create folders with Simplified Chinese characters by using the locale setting CHS.
      • Users in Hong Kong
        These users create folders with Traditional Chinese characters by using the locale setting CHT.
      All of the folders are created through the Microsoft Outlook mailbox. Both China and Hong Kong users connect to the same Exchange server. Backups of this environment are completed successfully. However, if the customer runs a mailbox restore operation that includes mailbox folders created by using both the CHS and the CHT locale settings, the restored folder names include ??? characters and are generally garbled.

      1. Run a mailbox restore operation by using the CHS locale to restore only mailboxes that are created with this locale setting.
      2. Run another mailbox restore operation by using the CHT locale to restore only mailboxes that are created with this locale setting.

    The Windows system locale must be changed between the two restore operations. You might have to restart the server to change the Windows system locale.
  • Cannot connect to an Exchange 2010 mailbox unless the Client Access Server role is defined on the system.

    On an Exchange 2010 Server that does not have a defined Client Access Server role, attempts to expand a mailbox folder after opening the mailbox .edb file with FastBack for Exchange display the following warning for a mailbox folder that has not been deleted or moved:
      "This mailbox was deleted or disabled. It may take up to 15 minutes to query the active directory. Do you want to proceed?"

    This issue is known for Microsoft Exchange 2010:
      "You cannot connect to an Exchange Server 2010 mailbox by using a MAPI application when a Mailbox server and a Client Access server are installed on different computers".

    For more information about this issue, see the Microsoft support article 2385194 at the following location:

    A fix for this issue is available from Microsoft. FastBack for Exchange was updated to support the changes that are provided by this fix. Complete the following steps to resolve this issue:
      1. Install the Microsoft Update Rollup 2 for Exchange Server 2010 Service Pack 1 (2425179)
      2. Upgrade to Fastback for Exchange Version 6.1.2 or later.
      3. Ensure that the Client Access Server is sufficient for all mail restore operations. You can retrieve the Client Access Server name by using the Exchange Management Shell command:
        Get-MailboxDatabase -Identity DB_contains_mailbox_for_logon_user | select RpcClientAccessServer

      In FastBack for Exchange Version 6.1.2, if the local server has a Client Access Server role, Fastback for Exchange uses the local server as the Client Access Server by default. Or, if the local server does not have a Client Access Server role, Fastback for Exchange uses the Client Access Server that is pointed to by the mailbox database that is associated with the login name of the user.
  • The FastBack for Exchange interface hangs when you attempt to close an Exchange Server 2003 database that contains a deleted mailbox.

    To resolve this issue, install the following patch on all of the Exchange Server 2003 systems that are affected:
    Microsoft Security Update for Exchange Server 2003 SP2 (KB950159)
  • FastBack for Microsoft Exchange does not terminate completely.

    Closing the FastBack for Exchange interface might not always completely terminate the application. The FastBackExchange.exe process might continue to run after the application has otherwise shutdown. Subsequent attempts to start the application might result in the following error:
      FBSX8003E Error FastBack for Microsoft Exchange is already running

    Wait for the FastBackExchange.exe process to finish completely before restarting FastBack for Microsoft Exchange. Use the Microsoft Windows Task Manager to monitor the FastBackExchange.exe process.
  • Fastback for Microsoft Exchange cannot display an existing mailbox after opening the .edb file. Also, attempts to open the corresponding online mailbox by using the Direct Exchange Restore --> Open Mailbox operation result in the following error:
      The mailbox is currently unavailable.

    FastBack for Microsoft Exchange cannot identify the mailbox until the user completes the mailbox log on process.
    Log on to the mailbox and try the operation again.
  • Diagnostic steps to take when you cannot access an existing mailbox after opening an .edb file or during a restore from Microsoft Exchange due to an unknown cause.

    Possible scenarios:
      • When you open the .edb file and click on a mailbox for access, a message is returned indicating that the mailbox was deleted or moved.
      • When you attempt to open any active mailbox by using the Direct Exchange Restore --> Open Mailbox operation, the following error message is returned:
        The mailbox is currently unavailable

    Diagnosing the issue:
      Ensure that the initial mailbox logon was completed, then complete these steps to diagnose the issue:
        1. Open a command prompt window.
        2. Change to the Fastback for Microsoft Exchange installation directory.
        3. Run one of the following commands:
          For Microsoft Exchange 2007 or Exchange 2010 environments:
            tdpmapi.exe testmapi
          For Microsoft Exchange 2003 environments:
            tdpmapi.exe testmapi /excversion=6

      If the following error message is displayed:
        Testing MAPI [SHIVA, administrator, 8].........Failed With Error: MAPI_E_FAILONEPROVIDER
      Verify that the following conditions are met:
      • The user running the FastBack for Exchange operation has the proper Exchange permissions.
      • The user running the FastBack for Exchange operation has an existing mailbox

      If both of these conditions are met, the issue might be that the Exchange Server that hosts the mailbox for this user might not be running. Verify that the Exchange Server hosting the mailbox is available, and that the Microsoft Exchange Information Store service is running on that server.
  • FastBack Mount is consuming too much memory.

    During a restore operation, the following error message might be displayed:
      FBSM5010W FastBack Mount is consuming too much memory. Unmount some virtual volumes to reduce memory consumption. All further write operations to virtual volumes will be ignored.

    This error occurs when there is not enough memory available for FastBack Mount to perform its operations.

    Complete one, or more, of the following actions:
      1. Unmount 1 or more volumes associated with the FastBack Mount feature to free memory resources.
      2. Close other running applications to free additional memory for use by the FastBack Mount feature
      3. If you did not include the logs and checkpoint directories when opening the .edb file, retry the operation and explicitly specify the log and checkpoint directories with the command.
      4. Restart the system.
  • The parenthesis "( )" characters are not supported in Microsoft Exchange 2003 mailbox naming conventions.

    Rename the mailbox name, and do not include parenthesis characters "( )".
  • Silent install of FastBack for Exchange requires the full path must be specified for the TRANSFORMS option. Failure to specify the full path causes the installation to fail but no error messages or warning is displayed.

    When you perform a silent install of FastBack for Microsoft Exchange, specify the full path for the TRANSFORMS option of the install program. For example:
      setup /s /v"TRANSFORMS=\"C:\tsm_images\FBE\1033.mst\" /qn /l*v \"C:\fbeinstall.txt\""
  • When using a Microsoft Exchange 2003 mailbox, some calendar dates might not be displayed. Calendar dates for some instances show <StartDate> rather than the date.

    None. Current limitation in the product.
  • When using FastBack for Exchange on an alternate Exchange Server, the alternate Server must be in the same Domain as the production Exchange Server.
  • When performing a restore of public folders with Exchange 2007 or Exchange 2010, the folders must be restored to an alternate Exchange Server, other than the one where the backup was performed. Additionally, the alternate Exchange Server must not have any public folder databases defined.
  • FastBack for Exchange only supports PST files that are 2 GB or smaller, and that are in non-Unicode format.
  • When using the FastBack Mount feature, drives should be mounted with read-write access.

  • Fastback for Microsoft Exchange fail in Windows Management 3.0 environments

    After installing Windows Management Framework 3.0, backup, restore, and query operations fail with an error like:

    The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechanism, but the destination computer (EXCHDB01) returned an 'access denied' error. Change the configuration to allow Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server:

    For more information, see the about_Remote_Troubleshooting Help topic.

    According to this Microsoft blog article:

    Windows Management Framework 3.0 is not supported in Exchange 2007 or 2010 environments. Since the release of that article, Microsoft added support for the coexistence of Windows Management Framework 3.0 with Microsoft Exchange Server 2010 Service Pack 3.

    Though not directly used by Microsoft Exchange Server 2010, coexistence with Windows Management Framework 3.0 is supported by Microsoft Exchange Server 2010 Service Pack 3.

    However, Windows Management Framework 3.0 is not supported by Fastback for Microsoft Exchange at this time.

Cross reference information
Segment Product Component Platform Version Edition
Storage Management Tivoli Storage Manager FastBack Center Windows 6.1 All Editions

Document information

More support for: Tivoli Storage Manager FastBack for Microsoft Exchange

Software version: 6.1

Operating system(s): Windows

Software edition: All Editions

Reference #: 1409039

Modified date: 26 June 2013

Translate this page: