Known Issues and Limitations: Version 3.1 FlashCopy® Manager for Microsoft Exchange & Version 6.3 Data Protection for Microsoft Exchange

Preventive Service Planning


Abstract

This document details the Known Issues and Limitations for FlashCopy Manager® for Microsoft Exchange Server V3.1.x and Data Protection for Microsoft Exchange Server V6.3.

Content

The following components share the same known issues and limitations. The components are:

    • FlashCopy Manager for Microsoft Exchange V3.1 --> which is a part of the IBM Tivoli Storage FlashCopy Manager V3.1 product
    • Data Protection for Microsoft Exchange V6.3 --> which is a part of the IBM Tivoli Storage Manager for Mail V6.3 product.

This document describes the Known Issues and Limitations applicable to:
    • FlashCopy Manager for Microsoft Exchange V3.1
    • Data Protection for Microsoft Exchange 6.3

    Note: The Known Issues and Limitations information for the other components that are a part of IBM Tivoli Storage FlashCopy Manager 3.1 are located at the following URL:
    http://www.ibm.com/support/docview.wss?uid=swg21506404


This document is divided into linked sections for ease of navigation. You may use the links below to jump to the desired section of the document.

General Issues and Limitations
GUI Issues and Limitations
Mailbox Restore Issues and Limitations
VSS Issues and Limitations
Exchange Server 2007 Continuous Cluster Replication Information
Exchange Server 2010 Database Availability Group (DAG) Backups



General Issues and Limitations
  • 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

    Data Protection for Microsoft Exchange Server and FlashCopy Manager for Microsoft Exchange Server will not work properly.

    Support for both items is planned for availability in Data Protection for Microsoft Exchange Server 6.4.0.2 and 6.4.1 and FlashCopy Manager for Microsoft Exchange Server 3.2.1.

    Additional details for both limitations can be found in APAR IC90654 here: http://www.ibm.com/support/docview.wss?uid=swg1IC90654


  • Data Protection for Microsoft Exchange and FlashCopy Manager 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:

    http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx

    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 Data Protection for Microsoft Exchange Server or FlashCopy Manager for Microsoft Exchange Server at this time.

    Workaround:
    For Exchange 2007: As per the above Microsoft blog article, remove the Windows Management Framework 3.0 update if it has already been deployed into an Exchange 2007 or 2010 environment.

    In Exchange 2010 environments, support for Windows Management Framework 3.0 is delivered via APAR IC90654. ( IC89531) ( IC90654)

  • Message number ACN6032E displays garbled text in place of the actual RSG or database name

    Instead of displaying the name of the affected database or recovery storage group name in the message:
      ACN6032E Cannot restore mailbox because there is an existing recovery storage group or database $name on the Exchange Server.

    garbled characters are shown. (88991)

  • On Windows Server 2008 R2 x64 the DSMAGENT code crashes if the TSM Client Acceptor service stops while performing a VSS INSTANT RESTORE operation with the following error:
      FMV1017E (RC-50) Session rejected: TCP/IP connection failure

    For example, dsmcrash.log contains the following:
      2011/07/21 17:44:27
      IBM Tivoli Storage Manager
      Version: 6.3.0.42 110707C
      Build date: Thu Jul 07 23:18:06 2011
      dsmagent.exe caused exception C0000005 (EXCEPTION_ACCESS_VIOLATION) at 000000003F1885DE

      Register dump:
      Crash dump successfully written to file 'C:\PROGRA~1\Tivoli\tsm\baclient\dsmcrash.dmp'
      Stack Trace:
      0x000000003F1885DE (0x00B38690 0x00000001 0x00000000 0x3F2FB99C) dsmagent.exe, cXMLiterator::cXMLiterator()+810190 bytes
      0x000000003F188A65 (0x00B0DEC8 0x00000000 0x00000000 0x00000000) dsmagent.exe, cXMLiterator::cXMLiterator()+811349 bytes
      0x000000003F2FB686 (0x3F7F3078 0x00000000 0x000003E8 0x00000000) dsmagent.exe, cXMLiterator::cXMLiterator()+2329974 bytes
      0x000000003F2FAE53 (0x00000001 0x00000001 0x00BEFEB0 0x00B0DE40) dsmagent.exe, cXMLiterator::cXMLiterator()+2327875 bytes
      0x000000003F3057E5 (0x00B13740 0x01593C60 0x00002449 0x00B0DE40) dsmagent.exe, cXMLiterator::cXMLiterator()+2371285 bytes
      0x000000003F0C5932 (0x00330640 0x3F74C910 0x015A0954 0x00000000) dsmagent.exe, cXMLiterator::cXMLiterator()+12322 bytes
      0x000000003F0C178A (0x00000000 0x00000000 0x00000000 0x00000000) dsmagent.exe
      0x0000000076E7652D (0x00000000 0x00000000 0x00000000 0x00000000) kernel32.dll, BaseThreadInitThunk()+13 bytes
      0x0000000076FAC521 (0x00000000 0x00000000 0x00000000 0x00000000) ntdll.dll, RtlUserThreadStart()+33 bytes

    Workaround: Restart the TSM Client Acceptor service, and perform again the VSS INSTANT RESTORE operation. (72561)

  • The Data Protection for Exchange INACTIVATE command does not accept the BACKUPDESTination or BACKUPMETHod optional parameters even though the online help shows them as possible parameters. In addition, if you use the INACTIVATE command with the OBJECT optional parameter, the application may fail.

    Workaround: Do not use the BACKUPDESTination, BACKUPMETHod, and OBJECT optional parameters. (77433)

  • In an Exchange 2007 environment, when Legacy backups are performed, Data Protection for Exchange is a multithread application that uses asynchronous execution threads to transfer data between the Exchange servers and Tivoli Storage Manager servers. To accomplish this, multiple data buffers are used to allow one thread to receive data from one side, while another thread sends data to the other side. Currently the GUI does not provide a mechanism to set or change the number and size of buffers that are allocated.

    Workaround: You can set number of buffers and buffer size that Data Protection for Exchange will use in the configuration file.
      (Default configuration file for Data Protection for Exchange is C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.cfg)

      Set number of buffers with the below entry
        BUFFERS 3

      Set the buffer size with the below entry
        BUFFERSIZE 1024

      Additionally you can perform backups and restores using the CLI. Refer to your users guide for complete CLI syntax.
        The CLI option to set the number of buffers is:
          /buffer=<numofbuffers>
        The CLI option to set the buffer size is:
          /buffersize=<buffersize>
    (77995)

  • In an Exchange 2007 environment, if a Recovery Storage Group exists then all Legacy restores will go to the Recovery Storage Group; Not to the Storage Group where the backup was taken. Currently no indication from the Flash Copy Manager GUI is given that a Recovery Storage Group exists. In addition, should a properly prepped Recover Storage group exist and a Legacy restore is requested, if the "Replay Restored AND Current Logs" recovery option is set to true the restore may fail. The Flash Copy Manager GUI will not disallow this action.

    Workaround: You can use the Microsoft Exchange Troubleshooting Assistant or the Exchange Management Shell do discover if a Recovery Storage Group exists. When doing legacy restores into a Recovery Storage Group set the "Replay Restored AND Current Logs" option to false. (77384)

  • Detail policy(management class) information is not available to view when connected to TSM Server for the purpose of binding backup objects with policies. There is no functional side-affect.

    Workaround: Use ADMIN client or TSM Server to view detail properties. (76334)

  • When performing legacy backup operations, the BUFFERSIze option value must be an exact multiple of 8 or the following message is seen:
      "ACN5798E MS Exchange API HRESEBACKUPREADFILE() failed with HRESULT: 0xc7ff1004"

    Workaround: Specify a BUFFERSIze that is an exact multiple of 8. (47167).

  • When performing RESTOREFILES operations with DBCS storage group names, the subdirectory names created may not contain all characters of the original storage group name. In this situation, the data restored is still valid and can be used without error.

    Workaround: None.

  • Through the use of repeated restore attempts, it is possible for a storage group to become unrecoverable with the current transaction log even though the Exchange recovery process is told not to replay the current transaction log. For example, when using these options:
      - Command line option: /RECOVER=APPLYRESToredlogs
      - GUI check box: "Replay Restored Logs ONLY"
      - ESEUTIL option: /t

    Workaround: Erase all current transaction log files for the storage group being restored and retry the operation. This is a Microsoft Exchange Server issue.

  • If you run FlashCopy Manager for Exchange or Data Protection for Exchange on a machine that is running in an unsupported language and locale combination, you must set the LANGUAGE option to a supported language and locale combination or you will receive an error message each time you launch FlashCopy Manager for Exchange or Data Protection for Exchange. The error messages displayed will look similar to the following:
      "ANS0101E Unable to open English message repository 'tdpeXXX.txt'"
      "ANS0102W Unable to open the message repository tdpeXXX.txt. The American English repository will be used instead"
      "ANS0113E" Message repository 'tdpeenu.txt' has an invalid control record."
      "Starting client using default English language"

    After the error messages are displayed, the application will launch and use the US English language and locale combination.

    Workaround: Set the LANGUAGE option to a supported language and locale option.

  • The password option in the Tivoli Storage Manager client options file (dsm.opt, by default) is ignored. This is working as designed. You must use PASSWORDACCESS GENERATE if you do not want to be prompted for a password.


    Workaround: Set PASSWORDACCESS to a value of GENERATE.




GUI Issues and Limitations

  • When using the MMC GUI interface to perform a Tivoli Storage FlashCopy Manager for Microsoft Exchange Server VSS Instant Restore of an active copy of a database from a LOCAL backup to the same machine where the backup was taken, it will fail with the message:
      Error Dismounting DB: DBNAME. Error invoking PS cmdlet Dismount Database.

    However in this case, the database had already been dismounted as a part of the process to
    Restore a Database Availability Group database copy backup on Exchange Server 2010.

    Workaround options:
    • Perform the instant restore using the CommandLine interface.
    • Use the Fast Restore to copy the files being restored instead of flashing the entire volume.
    • Upgrade to Data Protection for Exchange 6.4, or FlashCopy Manager for Exchange 3.2, where this problem is fixed.
    (80814)

  • MMC Cannot open the file flashcopymanager.msc after removing component

    When installing either:
    • Data Protection for Microsoft SQL Server
    • FlashCopy Manager for Microsoft SQL Server

    on the same system as either of these components:
    • Data Protection for Microsoft Exchange Server
    • FlashCopy Manager for Microsoft Exchange Server

    both components must be installed into the same root directory path because they all use the same MMC GUI interface code.

    For example:
      C:\Program Files\Tivoli\TSM\TDPSql
      C:\Program Files\Tivoli\TSM\TDPExchange

    If the components are not installed into the same root directory path, the removal of one component will also remove the MMC GUI interface. Therefore, the remaining component will not be able to use the MMC GUI and lead to the error with attempts to use the GUI:
      MMC Cannot open the file flashcopymanager.msc after removing component
      This may be because the file does not exist, is not an MMC
      console, or was created by a later version of MMC. This may also
      be because you do not sufficient access rights to the file.

    Workaround: Reinstall the MMC GUI by again installing the component that remains.

  • The "Minimum VSS Requestor Level" status may show as "passed" even though a down level TSM Backup-Archive Client is installed

    From within the MMC configuration wizard, the "Requirement Check" page includes a status of the "Minimum VSS Requestor Level". This validation check will indicate a "passed" status in some scenarios where the minimum level of the VSS Requestor or TSM Backup-Archive Client required for that level is not installed. Attempts to perform VSS operations will fail with a message similar to:
      Failed - ANS2040E (RC5853) While attempting to communicate with the remote client

    Workaround: Ensure that you have the minimum required VSS Requestor or TSM Backup-Archive Client level installed for the level of FlashCopy Manager on Windows, Data Protection for Microsoft Exchange Server, or Data Protection for Microsoft SQL Server code in use. If a down level version of the VSS Requestor or TSM Backup-Archive Client is installed, update that level to the minimum required. You can verify the minimum level required for your environment via the HW & SW Requirements tech notes for your respective software and level.

    FlashCopy Manager Requirements: TSM for Databases: Data Protection for Microsoft SQL Server Requirements: TSM for Mail: Data Protection for Microsoft Exchange Server Requirements: (89544)

  • When configuring support for Exchange the TSM configuration wizard in the MMC GUI will display a "Cluster Check" warning indicating that the VSSALTSTAGGINGDIR value is not set in the TDPExchange\dsm.opt file even though the value exists and is valid. The wizard is not correctly detecting the VSSALTSTAGGINGDIR value.

    Workaround: Ignore the warning. (89493)

  • MMC GUI Exchange Properties are adding blank option entries in tdpexc.cfg.

    Interacting with the property pages for Exchange may cause the following entries to be written to the tdpexc.cfg file with no values specified:

    REMOTEDSMAgent
    TEMPDBRESTorepath
    TEMPLOGRESTorepath
    TEMPMAILBOXAlias
    CLIENTACcessserver

    Data Protection for Exchange and FlashCopy Manager for Exchange will ignore these empty values and there is no impact to the system.

    Workaround: The empty values can be removed from tdpexc.cfg manually if desired. (88734)

  • The MMC GUI will crash during a mount operation if all windows drive letters are in use.

    Workaround: The user can use the CLI to avoid the MMC GUI crash. (88234)

  • The TSM and Local configuration wizards in the MMC may get to the Configuration page and have the Configuring Services rule fail.

    Workaround: Click the Re-Run button and the configuration process should complete successfully. (88813)

  • When run on Windows Server 2003, the TSM and Standalone configuration wizards do not check for KB934016 and KB940349. When performing VSS backups the following messages may be displayed:
      FMV4056I Pre-requisite Microsoft Windows hotfix 'KB934016' is not installed.
      FMV4056I Pre-requisite Microsoft Windows hotfix 'KB940349' is not installed.
    Workaround: Manually check for these hot fixes before running a configuration wizard on Windows Server 2003. (89196)

  • The TSM and Local configuration wizards in the MMC will display a Custom Configuration page. The page will display 1582 as the default value for the HTTP port. This value is stored in the registry for use by the TSM Client Acceptor Daemon (CAD). However that value is being ignored and so it needs to be placed in the custom options file directly.

    Workaround: Edit the custom option file (...\baclient\custom.opt by default) and add the httpport value directly in the form httpport xxxx. Then, restart the custom client acceptor service using the name provided in the configuration wizard ("custom client acceptor" by default). For example by issuing the commands:
      net stop "custom client acceptor"
      net start "custom client acceptor"

    The CAD will then respond to requests at that httpport value. (89432)

  • When using Data Protection for Microsoft Exchange Server the MFC GUI online help displays version 6.1.2, even though the installed product is version 6.3.0. The MFC GUI is a stabilized component and will not be updated with new function.

    Workaround: None. (65558)
  • After changing the name of a database within a storage group, a command-line legacy restore fails but a GUI legacy restore works. This is because the command-line client checks each and every database against the current Exchange server whereas the GUI does not. The error message on the command-line client is:
      ACN5067E None of the storage groups or databases entered exist. Or, if they do exist, and you are using Exchange 2000 or Exchange 2003, the databases have not been dismounted.

    Workaround: Dismount all databases manually and use the GUI to perform the legacy restore operation when this occurs. This is a known problem currently under investigation (24658).

  • Status Display Period for Dashboard information is "Last Hour" instead of "Last 7 Days" i.e. information from only last hour will be displayed by default.

    Workaround: Select appropriate display period from Dashboard properties. (77238)

  • The MMC GUI Scheduling Wizard may disappear (it goes to the background) when the template drop down button is selected.

    Workaround: Click the mouse outside the drop down button area and the wizard will reappear as it is brought to the foreground. (77453)

  • When using the MMC GUI to restore backups, if you have the "Auto Select" restore option set to true and you have a backup strategy that creates backups with a mix of incremental and differential backups the Auto Select function will incorrectly select additional backups to restore in some cases.
      Scenario 1
      1) FULL
      2) DIFF
      3) INCR
      4) INCR

      Scenario 2
      1) FULL
      2) INCR
      3) DIFF
      4) DIFF

    In both scenarios above if you were to select backup Number 3, auto select will also select the FULL (backup number 1). This is not the expected behavior. When a mix of incremental and differential backups is encountered ,auto select should not make any additional selections.

    Workaround: Use the recover options too set "Auto Select" to false and manually select the backup(s) to restore (77354)

  • The MMC GUI Exchange recover tab, Mailbox Restore view may display invalid characters as part of message ACN6032E. For example:
      ACN6032E Cannot restore mailbox because there is an existing recovery storage group or database ?~ ?on the Exchange Server.

    Workaround: Ignore the invalid characters. (77566)

  • The MMC GUI Scheduling wizard provides an Hourly schedule option taking a begin time, end time, and repeat interval. Scheduling an HOURLY task to repeat every 1 hour with an end time of 60 minutes or less from the Start time is not valid as the duration (end time - begin time) must be greater than the repeat interval.
      If you try to perform such an action in FCM, the result is a message indicating that the task was scheduled successfully, however the task does NOT get scheduled and no error message returned.

      Workaround: Ensure that the duration is greater than the repeat interval. In the example above setting the repeat interval to 1 hour and the end time to be 61 minutes after the start time would be fine. (77637)

    • The MMC GUI configuration wizards may fail to install, configure or start client services if the services are in use during the configuration process. Note that the client services are reinitialized during the configuration process and no backup or restore activity should be in progress during configuration. An error message similar to the following may be displayed:
        Could not start the client acceptor. Start the s3rvice to continue. For example, at a Windows command prompt issue: net start "TSM Client Acceptor"

      Workaround: Ensure that there is no backup / restore activity in progress during configuration. Typically the fastest way to resolve a service related issue in the configuration wizard is to ensure that there is no backup / restore activity and click the Re-run button. (77339)

    • Extraneous "ActiveInactive" phrase appear in output of "QUERY TSM * /detail" command. Also, Backup Object State field is empty.

      Workaround: None. (77878)

    • The MMC GUI Exchange Protect tab does not set the Backup destination based on the tdpexc.cfg file. It will show and use a value of TSM until the value is changed in the Action pane.

      Workaround: Select the desired backup destination in the Action pane. (77596)

    • On the MMC GUI Exchange Recover tab there are three views available: Database Restore, Mailbox Restore, and Mailbox Restore Browser. In each view filter rules are not maintained. The rules must be re-entered after switching between views.

      Workaround: Filters can be saved and recalled to files at any time. To work around this issue save the filter to a file before switching views and then load the filter from the file after returning to the original view. (76601)

    • The MMC GUI may hang while communicating with a TSM server if the provided TSM administrator password has expired.

      Workaround: Ensure that the TSM server admin password is not expired. To clear the hang, in Windows Task Manager, either end the process "dsmadmc.exe" allowing the MMC GUI to continue, or end the mmc.exe process and the MMC GUI will exit. (77131)




    Mailbox Restore Issues and Limitations

    • 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

      Data Protection for Microsoft Exchange Server and FlashCopy Manager for Microsoft Exchange Server will not work properly.

      Support for both items is planned for availability in Data Protection for Microsoft Exchange Server 6.4.1 and FlashCopy Manager for Microsoft Exchange Server 3.2.1.

      Additional details for both limitations can be found in APAR IC90654 here: http://www.ibm.com/support/docview.wss?uid=swg1IC90654

    • The Exchange mailbox restore browser cannot restore a deleted mailbox that has a display name different than the mailbox alias.

      Workaround: Use command line interface to restore the mailbox. (88889)

    • During batch mailbox restore operations, the MMC GUI communicates with the tdpmapi.exe process to perform the actual restore. When restoring a large number of mailboxes at a time, the tdpmapi.exe backend process might crash. In low memory environments, this crash might occur with as few as six mailboxes. In normal memory environments, it might take up to 100 mailboxes at a time to reproduce the problem.

      Workaround: Restore fewer mailboxes at a time. Monitor the mailbox restore operation and determine which mailboxes still need to be restored, and restore them separately. (77141)

    • Unable to restore mailboxes that contain parentheses in the mailbox alias.

      Workaround: Contact support regarding the availability of a workaround. (77440)

    • Performing an Individual Mailbox Restore (IMR) may result in a crash if both Legacy and VSS backups have been created for the storage group where the mailbox resides.

      Workaround: There is no current workarounds for this issue. An APAR will be open to address this issue. (77226)

    • Selecting Help on Individual Mailbox Restore(IMR) page results in help for restoring database being displayed instead of help for IMR.

      Workaround: Select appropriate page from the Table of Content (77234)

    • MAILBOXFILTER by time/date only works with default formats

      The command line for individual mailbox restore supports multiple date and time formats.
        Date Formats:
        1 MM/DD/YYYY
        2 DD-MM-YYYY
        3 YYYY-MM-DD
        4 DD.MM.YYYY
        5 YYYY.MM.DD

        Time Formats
        1 HH:MM:SS
        2 HH,MM,SS
        3 HH.MM.SS
        4 HH:MM:SSA/P

      During an mailbox restore operation if a non-default date and/or time format is set (Non-default is any date and time format other than 1), and the /MAILBOXFILTER=STARTDATETIME option is used to specify a start and end date to restore the individual mailbox. The stat and end date will be ignored and all mail for the individual mail box will be restored.(65191)

    • In order to perform Mailbox Restore (IMR) operations on Exchange Server 2010, the Exchange Server that you are performing the mailbox restore on can not have a recovery database defined. IBM is working with Microsoft to resolve this issue This is a known Microsoft problem with reference number 110051477034945. Until that problem is resolved, you will see the following error message when performing a mailbox restore when a recovery database already exists:
        ACN6032E Cannot restore mailbox because there is an existing recovery storage group or database <database name> on the Exchange Server.

      Workaround: Remove the existing recovery database and perform the mailbox restore operation again. (60522)

    • Mailbox Restore limitation between Exchange 2003 and Exchange 2010

      After you move mailboxes from Exchange 2003 to Exchange 2010, you will no longer be able to perform mailbox restore operations using the backups taken from Exchange 2003. This restriction exists because Exchange 2010 changes the mailbox information that is stored in Active Directory.

      Workaround: Restore the appropriate Exchange 2003 databases into the Recovery Storage Group. Then, use ExMerge to copy the messages to the desired location.

    • Mailbox not accessible via MAPI (MAPI_E_FAILONEPROVIDER)

      There are multiple reasons for this error:
      • Mailbox does not exist
      • Mailbox has never been sent to or logged into
      • Mailbox database is not mounted
      • Insufficient privilege to access mailbox (see Installation & User's Guide publication)
      • Exchange server where mailbox database is located is not available or down
      • Microsoft Information Store service is not running
      • Microsoft Exchange System Attendant service is not running

    • Creating Profile (MAPI_E_NETWORK_ERROR) reported on Windows 2008

    This problem occurs during the following circumstances:
      1. Existing Exchange 2003 environment hosted completely on a 32-bit Windows Server 2003.
      2. An Exchange 2007 server hosted on Windows Server 2008 is added into this Exchange organization.
      3. Installed the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 download to provide client MAPI support on the Exchange 2007 server.
      4. Installed Data Protection for Exchange 6.1.0 on the Exchange 2007 Server and it always fails when creating the MAPI profile for the mailbox on the local Exchange 2007 Server. It fails when calling IMsgServiceAdmin::ConfigureMsgService and returns MAPI_E_NETWORK_ERROR.
    Relevant Microsoft MAPI BLOG: http://blogs.msdn.com/stephen_griffin/archive/2008/08/15/mapi-and-ipv6.aspx
      The workaround is to disable IPv6 on the Exchange Server:

        In the Network Connections folder, obtain properties for all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under "This connection uses the following items". This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface. Add the following registry value (DWORD type) set to 0xFFFFFFFF:
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents

        This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect. Opened Microsoft Support Case SRX0809196000563 on (09/19/08)

      • Logging on to MAPI (MAPI_E_LOGON_FAILED)

        The two most common reasons for this error are:
          1. User running mailbox restore has insufficient privilege to access mailboxes through MAPI.
          2. User running mailbox restore does not have a live accessible Exchange mailbox in the domain.

        The user account requirements for running Mailbox Restores from FlashCopy Manager or Data Protection for Exchange require that the user has sufficient privilege as described below:
          Exchange 2010:
          - user account with membership in the Organization Management group.

          Exchange Server 2007:
          - user account with membership in the Exchange Organization Administrators group.

          Exchange 2003:
          - user account with Exchange Administrator role and membership in the local Administrators group

      • The MAPI Spooler (mapisp32.exe) could not be started
          Missing or Damaged File (mapisp32.exe)

        A missing Mapisp32.exe file can cause this problem. The Mapisp32.exe file might have been removed or renamed by your anti-virus program.

        Exchange Server 2007 and 2010:
          Uninstall / Reinstall MAPI CDO 1.2.1 package.

      • MAPI Problems after Outlook is installed on Exchange Server


        Exchange and Outlook MAPI implementations are incompatible and Outlook should never be installed on an Exchange Server running IMR. In the event that this occurs, the following procedure might reconcile the issue:
          1. Uninstall Outlook from Exchange Server
          2. Reinstall MAPI CDO 1.2.1 package.
          3. Remove any existing TSMPROFILE profiles (this will not be necessary for later drivers): MFCMAPI Instructions:
            i. Bring up MFCMAPI, select the "Profile" menu.
            ii. Select "Show Profiles"
            iii. Delete all profiles that begin with "TSMPROFILE"
            iv. Select profile to delete and either:
              a. right click on selected profile and press "Delete Profile"
              b. from "Actions" menu select "Delete Profile"
              v. Exit MFCMAPI
      • MAPI Library Initialization Failure (MAPI_E_CALL_FAILED)


        Initialization of MAPI libraries fails as onset, usually indicative of a problem with the MAPI CDO 1.2.1 installation. Example trace output from:
          tdpmapi TESTMAPI /tracefile=<trace filename>
            ... ( 332): MAPIHandler::initialize(), current directory is <C:\Program Files\Tivoli\TSM\TDPExchange>
            ... ( 344): MAPIInitialize error: MAPI_E_CALL_FAILED
            ... ( 350): MAPIHandler::initialize(), reset current directory to <C:\Program Files\Tivoli\TSM\TDPExchange>
            ... ( 363): Exit MAPIHandler::initialize(), hr = MAPI_E_CALL_FAILED

        If installed, uninstall and reinstall the latest download from this Microsoft Web site:
        http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E&amp;displaylang=en

      • Creating Profile ConfigureMsgService Error: 0x81002746

        Undocumented MAPI error that is related to the restoremailbox user having access to their mailbox.
      This problem is most likely because the user does not have a live Exchange mailbox.

      Troubleshooting steps:
      1. Check the user has sufficient privilege in the domain.
      2. Check that the user has a live Exchange mailbox and has access to it.
      3. If these do not solve the problem, try explicitly granting full access for the user to their mailbox.

      Microsoft link on granting full access to a mailbox for a user:
      http://technet.microsoft.com/en-us/library/aa996343.aspx


      Reference from the internet on this problem:
        Only a mail-enabled user account can create MAPI profiles. The "Local System account" is not mail-enabled and therefore cannot create MAPI profiles. In addition, a MAPI profile is associated to the user that creates it. So even if there was a profile with the required name, it cannot be found if the services are run by the "Local System account".
      • MAPI_E_NO_ACCESS: The user does not have permission's.

        Try again running mailbox restore again with from an user account that meets the following:
          Exchange 2010:
          - user account with membership in the Organization Management group.

          Exchange Server 2007:
          - user account with membership in the Exchange Organization Administrators group.

          Exchange 2003:
          - user account with Exchange Administrator role and membership in the local Administrators group




      VSS Issues and Limitations


      • DSMAGENT crash when a volume is mapped to more than 1 path

        When a database has files located on a single volume mapped with multiple paths, the DSMAGENT will crash while logging error C_SNAP_INVALID_PAIR (6054) in the DSMAGENT error log.

        For example: The same volume is mapped as both M:\data and C:\MP_M\logs
        where M: and C:\MP_M are volume paths to the same volume.

        This mapping configuration is not supported. However, DSMAGENT should not crash if it configuration is encountered.

        Workaround: Unmount the volume so that it has a only single volume path. Subsequently, reconfigure the Microsoft SQL Server database and/or the Microsoft Exchange Server database to use the single volume path. (88988)

      • Metro/ Global Mirror configurations are not supported with Tivoli Storage FlashCopy Manager components running on the Windows platform.

      • On Exchange Server 2010, when performing a VSS restore of a database that has been rebuilt or recreated (has a new database GUID value), you must specify the restore operation using the "Restore Into" options. For the GUI, that consists of clicking the right-mouse button, while the mouse is over the selected backup being restored and then choosing the database that matches the database being restored. For the command-line interface, that consists of using the "/INTODB=original-database-name" option, where "original-database-name" matches the database being restored. The list of conditions that require using the "Restore Into" option when performing VSS restore operations are as follows:

        - Restoring a backup of a database that has been recreated since the VSS backup was done
        - Restoring a backup of a database that has been relocated since the VSS backup was done
        - Restoring a backup of a database that has been renamed since the VSS backup was done
        - Restoring a backup of a database into a Recovery database
        - Restoring a backup of a database into an alternate database

      • When performing VSS restore operation, if you are restoring a VSS backup of a storage group that contains databases that do not currently exist in the live storage group, the files for the old databases will still be restored but you will not see any message indicating that there is a problem. This is a harmless situation.

        Workaround: If you do not want the additional data to be restored, you can perform a partial VSS restore operation and only select the desired databases that you would like to be restored.

      • Performing VSS Instant Restore operations with the Exchange Server running in a Microsoft Cluster Server environment requires the following:

        - Microsoft Windows Server 2003 Service Pack 2 (or later)
        - Microsoft hotfix KB 919117

        If you do not have this hotfix installed, you should make sure to choose either the GUI option to "Disable VSS Instant Restore" or the CLI option "/INSTANTRestore=NO". Failure to have the hotfix installed or to disable the VSS Instant Restore operations can result in restore processing errors


      • VSS Instant Restore is not working from the MMC GUI when multiple SQL or Exchange databases are stored on the same volume.

        The MMC GUI performs a separate restore of each selected backup item leveraging the backup item's object ID. This does not work correctly when using instant restore and multiple SQL or Exchange databases are on the same volume.

        Any of the following workarounds can be used:
          A) From the MMC GUI, disable VSS Instant Restore when performing a restore. The restore will be performed using Fast Restore.
          B) Perform the restore using the command line or MFC GUI
          C) Avoid the issue by placing databases on separate volumes.

        Note that it is a recommended best practice to place each database on a separate volume when using instant restore. (77745)

      • When using IBM System Storage SAN Volume Controller v6.1.0 and/or IBM Storwize® V7000 disk systems, VSS Backups and Restores may take longer to complete than with earlier versions of IBM System Storage SAN Volume Controller. This is resolved by applying the appropriate SVC 6.1.x fix when available. This problem is tracked via SVC APAR IC73044. (65377)

      • During VSS backup operations the following error may be recorded in the Windows event log

        Device IO Control, generic_floppy_drive, Incorrect function

        The event log entry may look similar to this:
          DeviceIoControl(\\?\fdc#generic_floppy_drive#6&amp;2bc13940&amp;0&amp;0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000308,0x00560000,0000000000000000,0,00000000002BD110,4096,[0]), Incorrect function.

        This error recorded in the Windows event log does NOT indicate the backup operation failed and can be ignored. (62535)

      • Failure when trying to snapshot the volume where the IBM System Storage VSS hardware provider is installed

        If you attempt to perform a VSS snapshot of the volume where the IBM System Storage VSS hardware provider software is installed, the snapshot will fail if the snapshot set contains a DS6000, DS8000, or SVC LUN. To work around this issue, move the IBM System Storage VSS hardware provider installation to a volume not being used in snapshot operations. This is a known problem with the IBM System Storage VSS hardware provider that is currently under investigation.

      • When using SAN Volume Controller 5.1 (or later) and using space-efficient volumes where multiple target volumes exist, if you perform a VSS Instant Restore of an inactive backup after a cluster failover, the VSS Instant Restore may fail.


        Workaround: Perform the following steps on the failover cluster node where the restore is being performed:
          1. Run the Windows "DISKPART" command.
          2. Rescan the disks on the system:
            diskpart> rescan
          3. Select the snapshot disks, bring them online, and reset their read-only attribute:
            diskpart> sel disk 4
            diskpart> online disk
            diskpart> attrib disk clear readonly
          4. Repeat step 2 for all disks being restored.
          5. Exit the Windows "DISKPART" command:
            diskpart> exit
          6. Rerun the VSS Instant Restore operation.

        (61722)

      • Failure in VSS Provider communications can result in premature removal of VSS LOCAL backups. If you are performing VSS LOCAL backup operations and connection problems occur with the VSS Provider, Windows is not able to see the existing snapshots managed by that VSS Provider during query operations. If this happens, TSM may remove the inventory of those backups on the TSM Server. IBM is working with Microsoft to resolve this issue This is a known Microsoft bug with reference number Windows 8 bug 5583. Microsoft has documented the issue in the following KB:

        http://support.microsoft.com/kb/2025800

        Workaround: Before issuing TSM VSS commands, make sure VSS Provider communications is working correctly. (49369_1 and Microsoft reference number 109090353881466)

      • When running command-line interface (CLI) operations, if the screen is locked through an operation like "Quick Edit Mode" or "Cntrl-S", the VSS operation may fail.

        Workaround: Unlock the screen and/or hit the Enter key to resume operations. (55378)

      • In some cases, when deleting shadow copies on systems containing SVC LUNs managed with MPIO and SDDDSM, the system hangs and requires a hard reboot. This is not a TSM problem but can occur when running TSM VSS operations. The problem is currently being investigated by IBM

        Workaround: None. (56260)

      • If the TCPSERVERADDRESS option in the DSMAGENT options file is changed (from numeric form to name form or from name form to numeric form or from long name form to short name form or from short name form to long name form) after VSS backups stored on LOCAL devices have already been performed, it is possible that Tivoli Storage Manager meta data files stored in the ADSM.SYS directory structure could be left in an incorrect state. This will cause previous VSS backups stored on LOCAL devices to be expired prematurely due to the method in which Tivoli Storage Manager uses TCPSERVERADDRESS for reconciliation indexing.

        Workaround: Make sure TCPSERVERADDRESS is not changed once LOCAL VSS backups have been created. If this is unavoidable, and you want to retain the current local snapshot backups, contact IBM service for additional instructions.

      • Parallel VSS restore operations are not supported on Microsoft Windows 2003 and Microsoft Windows 2008.

        Workaround: Perform VSS restore operations sequentially.

      • Failure when using the IBM System Storage VSS hardware provider on a system that contains GUID Partition Table (GPT) disk partitions
        When using the IBM System Storage VSS hardware provider, if you attempt to perform a VSS snapshot on a machine that contains GPT disk partitions, the snapshot will fail. To work around this issue, change to Master Boot Record (MBR) partitions or wait for the IBM System Storage VSS hardware provider to support GPT disk partitions. This is a known problem with the IBM System Storage VSS hardware provider that is currently under investigation.

      • DSMAGENT hang caused by invalid DSMAGENT options file
        VSS operations may hang due to an invalid option in the DSMAGENT options file (DSM.OPT). To work around this issue, correct the invalid option in the DSMAGENT options file, stop the DSMAGENT service, and retry the operation.

      • DSMAGENT memory leak during frequent VSS backups

        In rare situations where FlashCopy Manager for Exchange or Data Protection for Exchange is running extremely frequent VSS backups, it can cause the Tivoli Storage Manager Remote Client Agent Service (DSMAGENT) to remain loaded. If that happens, it is possible that the DSMAGENT service memory usage will continue to grow. To work around this issue, stop the DSMAGENT service in between VSS backups





      Exchange Server 2007 Continuous Cluster Replication Information


      • Transaction logs not truncated after VSS backup of a Passive CCR node on Exchange 2007 SP3

        After a VSS backup of an Exchange Cluster Continuous Replication passive node, the Exchange logs on the active node are not truncated. This can lead to the log volume running out of space, or it may cause incremental or differential backups on the passive node to fail. For additional details related to this issue, please refer to the following document published by Microsoft:
        http://support.microsoft.com/kb/2297394



      Exchange Server 2010 Database Availability Group (DAG) Backups
      • Exchange DAG status information is not translated Exchange status "DAG status" is shown as English string in MMC and CLI, regardless what language pack is installed.

        Workaround: N/A (76706)


      Cross reference information
      Segment Product Component Platform Version Edition
      Storage Management Tivoli Storage FlashCopy Manager FlashCopy Manager for Microsoft Exchange Windows 3.1

      Rate this page:

      (0 users)Average rating

      Add comments

      Document information


      More support for:

      Tivoli Storage Manager for Mail
      Data Protection for MS Exchange

      Software version:

      3.1

      Operating system(s):

      Windows

      Reference #:

      1506409

      Modified date:

      2013-03-13

      Translate my page

      Machine Translation

      Content navigation