Known Issues and Limitations: Version 4.1.x IBM Spectrum Protect™ Snapshot for Microsoft Exchange & Version 7.1.x Data Protection for Microsoft Exchange

Content

Tip: Beginning with Version 4.1.3, Tivoli Storage FlashCopy® Manager is now IBM Spectrum Protect™ Snapshot. Some applications such as the software fulfillment systems and IBM License Metric Tool use the new product name. However, the software and its product documentation continue to use the Tivoli Storage FlashCopy Manager product name. To learn more about the rebranding transition, see http://www.ibm.com/support/docview.wss?uid=swg21963634.

Tip: Beginning with Version 7.1.3, Tivoli Storage Manager for Mail is now IBM Spectrum Protect™ for Mail. Some applications such as the software fulfillment systems and IBM License Metric Tool use the new product name. However, the software and its product documentation continue to use the Tivoli Storage Manager for Mail product name. To learn more about the rebranding transition, see http://www.ibm.com/support/docview.wss?uid=swg21963634.



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

• FlashCopy Manager for Microsoft Exchange Server 4.1.x --> which is a part of the IBM Tivoli Storage FlashCopy Manager 4.1.x product.
• IBM Spectrum Protect Snapshot for Microsoft Exchange Server 4.1.x --> which is a part of the IBM Spectrum Protect Snapshot 4.1.x product.
• Data Protection for Microsoft Exchange Server 7.1.x --> which is a part of the IBM Tivoli Storage Manager for Mail 7.1.x
• Data Protection for Microsoft Exchange Server 7.1.x --> which is a part of the IBM Spectrum Protect for Mail 7.1.x product.

This document describes the Known Issues and Limitations applicable to:

• FlashCopy Manager for Microsoft Exchange Server 4.1.x
• IBM Spectrum Protect Snapshot for Microsoft Exchange Server 4.1.x
• Data Protection for Microsoft Exchange Server 7.1.x

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

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
Exchange 2013 Specific Issues and Limitations
Exchange 2016 Specific Issues and Limitations
GUI Issues and Limitations
Mailbox Restore Issues and Limitations
VSS Issues and Limitations
National Language Support (NLS), and Other Issues When Operating in a Non-English Environment
Exchange Server 2010 Database Availability Group (DAG) Backups
Data Protection for VMware "application protection" Integration Related Issues and Limitations
Known Issues and Limitations Resolved with 7.1.1 / 4.1.1
Known Issues and Limitations Resolved with 7.1.2 / 4.1.2
Known Issues and Limitations Resolved with 7.1.3 / 4.1.3
Known Issues and Limitations Resolved with 7.1.4 / 4.1.4
Known Issues and Limitations Resolved with 7.1.6 / 4.1.6


General Issues and Limitations

Updates, clarifications, and corrections to the currently published version of the IBM Tivoli Storage FlashCopy Manager 4.1 publications are located in the Documentation Updates tech note at the following URL:

http://www.ibm.com/support/docview.wss?uid=swg27039330

Updates, clarifications, and corrections to the currently published version of the Data Protection for Microsoft Exchange 7.1 publications are located in the Documentation Updates tech note at the following URL:

http://www.ibm.com/support/docview.wss?uid=swg27039332

After installing either component, when you navigate to the software using the Windows desktop icon or Start menu, FlashCopy Manager Management Console is the name that is displayed.

While this name does not match the name displayed in the installation package, the software that you start from the Windows desktop is the software that you installed. The name mismatch is a known issue, but no problems occur because of the name mismatch.

Additionally, the "Help --> About" menu will list the name of the product as Tivoli Storage FlashCopy Manager. The version number represented in this menu also will not match the installed version of either component. Use the Add / Remove programs option within the Windows Control panel to confirm the installed release and level of the component.

Changing the temporary password of the TSM Configuration Wizard Marco leads to Errors

The TSM configuration wizard of Tivoli Storage FlashCopy Manager for Windows provides an option for the wizard to configure the Tivoli Storage Manager (TSM) server.

When the option is selected, an administrator can edit the TSM server configuration macro before it is submitted to the TSM server.

The generated TSM macro template includes statements which
contain a temporary password. This password will be reset during configuration using passwordaccess generate.

The problem occurs if the value of the temporary password is
changed. This because another generated script expects that specific temporary password to be used.

Changing the temporary password directly in the TSM marco could lead to errors like the following:


ACN5229E An error occurred while obtaining VSS information from the following Local DSMAgent Node: 'myNode'.
ACN0520E Failed to connect to Local DSMAGENT Node 'myNode' at address:port 'myDNSaddress:33915'.
Verify that the TSM Client Acceptor Daemon (CAD) is installed, configured, and running properly.

MM/DD/2013 18:13:58 ANS1835E PASSWORDACCESS is GENERATE, but password needed for server 'myServer'.
Either the password is not stored locally, or it was changed at the server.
MM/DD/2013 18:13:58 ANS1025E Session rejected: Authentication failure


Workaround: None. This is a permanent restriction of the product. If you are using the TSM Configuration wizard, you must not change the temporary password defined in the TSM macro called by the configuration wizard. This wizard uses this temporary password in several places.

Also, the comments included in the TSM macro used by the configuration wizard will be updated to include an additional warning that the temporary password should not be changed. (IC99664)

The following 4 naming limitations exist for:

- the Database name
- the Storage Group name
- the Mount path for 'mount backup' command.
when protected by $component.



	Limitation Description	'restore' command	'mount' command
1.	Database name or storage group name ends with 14 digits surrounded by parentheses characters. Example: db/sg name: 'DB(XXXXXXXXXXXXXX)'	Supported, but the object Id should be specified with the restore command	Supported, but the object Id should be specified with the mount command
2.	Database name or storage group name either ends with, or contains, a substring of 14 digits surrounded by parentheses characters, and is followed by the equal sign. Example: db/sg name: 'DB(XXXXXXXXXXXXXX)=DB'	Supported	Not supported
3.	Mount path for 'mount backup' command ends with 14 digits surrounded by parentheses characters. Example: mount path: 'C:\dir1\dir2(XXXXXXXXXXXXXX)'	N/A	Supported, but the object Id should be specified with the mount command
4.	Mount path for 'mount backup' command either ends with, or contains, a substring of 14 digits surrounded by parentheses characters, and is followed by the equal sign. Example: mount path: 'C:\dir1\dir2(XXXXXXXXXXXXXX)=\dir3'	N/A	Supported, but the object Id should be specified with the mount command

1. Database name or storage group name ends with 14 digits surrounded by parentheses characters. For example: 'DB(20120409153304)'

In this case you will not be able to restore the Database / Storage Group or mount backup by name. To restore or mount backup you will have to specify Object ID associated with the backup after the database / storage group name. Object ID should be surrounded by parentheses.

Example 'restore' command: tdpexcc.exe restore $db_or_sg_name($objectID) full

2. Database name or storage group name either ends with, or contains, a substring of 14 digits surrounded by parentheses characters, and is followed by the equal sign. For example: 'DB(20120409153304)=AB'

In this case you will not be able to run "mount backup" for this Database / Storage Group. There is no workaround for "mount backup" command. "restore" command is not affected.

3. Mount path for 'mount backup' command ends with 14 digits surrounded by parentheses characters. For example: 'c:\dir1\dir2(20120409153304)'

In this case you will not be able to mount a backup by name. To mount backup, you will have to specify the Object ID associated with the backup after the database / storage group name. The Object ID should be surrounded by parentheses.

Example 'mount' command: tdpexcc.exe mount backup $db_or_sg_name($objectID)=c:\path\)

4. Mount path for 'mount backup' command either ends with, or contains, a substring of 14 digits surrounded by parentheses characters, and is followed by the equal sign. For example: 'c:\dir1\dir2(20120409153304)=\dir3'

In this case you will not be able to mount backup by name. To mount the backup, you will have to the specify Object ID associated with the backup after the database / storage group name. Object ID should be surrounded by parentheses.

Example 'mount' command: tdpexcc.exe mount backup $db_or_sg_name($objectID)=c:\path\)

Note: Backup of a database or storage group name that includes one of the limitations will not be prevented. (IC79445) (IC94303)

If backup has been mounted on a remote server and a "Restore Into" operation is started, the operation will fail with:

"FMV1086E (RC104) File not found during Backup, Archive or Migrate processing"

Workaround: None. Performing a "Restore Into" operation with a backup that is mounted on a remote server is not supported. You must first unmount the backup from the remote server. (96701)

Under rare circumstances a FlashCopy Manager stand alone server backup can fail and make future stand alone backups inoperable without recommended circumvention.

The problem can only occur during the initial stand alone server backup when the FlashCopy Manager agent service is abnormally terminated while the backup is running.

The problem occurs because a saved copy of the local data bases is not available to recover to because a previous backup never completed. Also, subsequent backups fail because the database files were left in a corrupt state by the first backup.

The problem can only happen during the initial backup. Once a backup successfully completes, saved copies of the local databases are available for recovery.

Workaround: Stop the FlashCopy Manager agent service, delete all local FlashCopy Manager database files in the FlashCopy Manager staging directory, and then restart the FlashCopy Manager agent service. (98688)

Remotely Mounted backups are not removed from the storage device after manual deletion or expiration

Data Protection for Microsoft Exchange Server and FlashCopy Manager for Microsoft Exchange backups can be mounted using the Remote Mount feature. When one of these remotely mounted backups is manually deleted, or expires based on policy retention definitions, it will be deleted from the Tivoli Storage FlashCopy Manager inventory. However, the actual snapshot located on the storage device will remain.

Workaround: Ensure that remotely mounted backup images are unmounted prior to manual deletion or expiration. (33605) (33605-321)

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.




Exchange 2013 Specific Issues and Limitations

• The VSS Instant Restore process may fail with the following message:

ANS1050E Before performing the VSS Instant Restore TSM cannot lock the volume 'D:'

in environments using Microsoft Exchange 2013 SP1 and when the files to restore will be restored to a drive where either of the following Microsoft Exchange services:

• Microsoft Exchange Diagnostic
• Microsoft Exchange Health Manager

write to the directory $volume:\MonitoringDiagnosticsLogs. This prevents the VSS Instant Restore function from locking the volume for the restore operation.

Workaround: Until a change or fix from Microsoft is available, temporarily disable the 2 services specified above when it is necessary to perform a VSS Instant Restore operation to a volume where the MonitoringDiagnosticsLogs directory exists. After completion of the VSS Instant restore process, restart the 2 services.

In mixed Exchange 2010 / Exchange 2013 environments, the administrator account that you use to perform the mailbox restore must reside on an Exchange server at the same level as the mailbox that you are trying to restore. For example, if you wish to restore an Exchange 2013 mailbox, you must log on as an administrative user whose mailbox is located on an Exchange 2013 database.

If the following errors are received:

SMTP restore error "Send SMTP Messages Error: Service not available, closing transmission channel. The server response was: 4.4.1 Connection timed out Operation Failed"

Increase the time out value to avoid this problem. You can do this by modifying the following settings of the "receive connector":

(http://social.technet.microsoft.com/Forums/exchange/en-US/fd9319bd-968e-410c-aa37-4b3ae2e25b88/441-connection-timed-out), [PS] C:\Windows\system32>Set-receiveconnector -identity "TDPFORWIN\Default Frontend TDPFORWIN" -connectiontimeout:00:30:00

The Mailbox Restore filter BODY/ALLCONTENT doesn't work with Exchange 2013. This is a Microsoft issue and ticket has been opened with Microsoft.

Mailbox Restore on Exchange 2013 pops up an "Enter Password" dialog asking for Domain, User Name, and Password. This problem might be caused by changing Client Access Server settings (e.g. local server is a CAS server before, but the CAS role has been removed now). In such case, open regedit and delete RpcHttpProxyMap_TSM key in HKEY_CURRENT_USER->Software->Microsoft->Windows NT->CurrentVersion->Windows Message Subsystem

When using mailbox restore or the mailbox restore browser with Exchange Server 2013, the "Message Body Text" and "All Content" filters do not work as expected.

Problem Verification: Using mailbox restore browser, add a filter to search for some text that you know exists in a message body. Depending on the type of message, the mailbox restore browser may not return any results.

Additional Information: The MAPI search capability is handled by the Microsoft Exchange FAST/Content Indexing. As such, the mail content cannot be searched unless it has been indexed. A problem with the search capability was fixed in Microsoft Exchange 2013 CU2. However, there is an additional Microsoft limitation that prevents mail content searching immediately after an RDB is created but before Exchange FAST/Content Indexing processes have completed.

Workaround: If possible, wait several hours for the Content Indexing process to complete before attempting to perform a mailbox restore using filters. Otherwise, use another filter, or restore the entire mailbox to a PST file and then use Microsoft Exchange to search the PST file. (36410)

Exchange 2016 Specific Issues and Limitations

• In order to complete an instant restore when using Exchange 2016 CU3 the following services must be stopped:

Stop-Service -displayname "Microsoft Exchange Frontend Transport"
Stop-Service -displayname "Microsoft Exchange Mailbox Transport Submission"
Stop-Service -displayname "Microsoft Exchange Transport"
Once the restore is complete you must start the services. (129350)


GUI Issues and Limitations

When interacting with the Automation view in the MMC GUI a Tips button is available. When clicked, it displays helpful tips. The displayed tips apply to both command line and PowerShell commands but do not cover PowerShell specific options.

Workaround: Consider the following tips related to PowerShell commands in the Automation view:

- A drop down menu allows choosing between Command Line and PowerShell commands when interacting with a local computer. When interacting with a remote computer, only PowerShell commands are supported.

- Click the "Display Cmdlet Chooser" toolbar icon to toggle the display of the cmdlet chooser window.

- Enter text in the search field of the cmdlet chooser window to help find the cmdlets you are interested in. For example type: 'get' to see all FlashCopy Manager and Data Protection cmdlets that include "get" in their names.

- Click any combination of cmdlet types in the cmdlet chooser window to narrow down the list of cmdlets to only those types.

- Click the orange arrow icon in the cmdlet chooser window to copy the bare cmdlet name to the command window.

- Click on the orange plus icon in the cmdlet chooser window to copy the full text of the cmdlet to the command window. The type of each parameter will be shown as a placeholder to the right of each parameter. Double click the type (for example string) and type in the desired value.

- Click the "Display as List" toolbar icon to toggle the output between table (default) and list view.

- For general tips on interacting with PowerShell see http://technet.microsoft.com/en-us/library/bb978526.aspx or search the web for "Scripting with Windows PowerShell". (97889)

Mailbox Restore Issues and Limitations

FlashCopy Manager and Data Protection for Exchange fail to restore mailboxes to a Unicode PST file if there's other mailbox uses the same alias name as the temporary mailbox.

Workaround: Specify another temporary mailbox with unique alias name by specifying /tempmailboxalias parameter.

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)

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

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 & Exchange 2013:
- user account with membership in the Organization Management group or appropriate role assignment.

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 & Exchange 2013:
- user account with membership in the Organization Management group or appropriate role assignment.

When using the command line to restore a backup, if multiple backups are specified and one or some of the

backups fail, the error message reported by the CLI may report the wrong backup failed.

Workaround: Two workarounds exist:

1) Use the MMC GUI when you wish to restore multiple backups are the same time.
2) Do not issue a single CLI command to restore multiple backups. Instead issue multiple CLI
commands; one for each backup you wish to restore.
Example:
Do not use -> fcmcli restore G:,H: /backupdest=tsm
Instead use -> fcmcli restore G: /backupdest=tsm
fcmcli restore H: /backupdest=tsm (120822)




VSS Issues and Limitations

• "Access Denied" messages received during VSS operations with GPT-format physical disks

If you are receiving an "access denied" message and are unable to lock the volume, please refer to this Microsoft article for additional information: http://support.microsoft.com/kb/2963861 You will need to install the Microsoft hot fixes appropriate to your environment on each node within the cluster.

To resolve this issue on Windows 2012, please install: http://support.microsoft.com/kb/2962407

To resolve this issue on Windows 2012 R2, you will need to install the following updates in the order listed (due to fix dependencies):

Windows Server 2012 R2 Update March, 2014 http://support.microsoft.com/kb/2919442

Windows Server 2012 R2 Update April, 2014 http://support.microsoft.com/kb/2919355

Note: These KB's must be installed in the following order:
clearcompressionflag.exe,
KB2919355, <------------------- this install takes a long time to install.
KB2932046,
KB2959977,
KB2937592,
KB2938439, and
KB2934018

Windows Server 2012 R2 June 2014 update rollup http://support.microsoft.com/kb/2962409

Note: These KB's must be installed in the following order:
Windows8.1-KB2962409-x64.msu
Windows8.1-KB2959146-x64.msu
Windows8.1-KB2973448-x64.msu

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:
http://www.ibm.com/support/docview.wss?uid=swg21427692

TSM for Databases: Data Protection for Microsoft SQL Server Requirements:
http://www.ibm.com/support/docview.wss?uid=swg21218747

TSM for Mail: Data Protection for Microsoft Exchange Server Requirements:
http://www.ibm.com/support/docview.wss?uid=swg21219345

(89544)

• The following message:

FMV9350E (RC6055) Backup operation failed due to volume mixture. Please refer to explanation section for additional information.

should be:

FMV9350E (RC6055) Backup operation failed due to volume mixture. Please refer to the explanation in the Tivoli Storage FlashCopy Manager Messages Guide for additional information.
(87040)


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



• 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)

• 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 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 and has been fixed in the SVC 6.1.0.3 PTF (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. (65232)

• 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.

• 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)

• 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 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

• Microsoft Hotfix KB 3095663 (https://support.microsoft.com/en-us/kb/3095663) is not available on the Windows 2012 platform. As a result, instant restore operations may randomly fail with a VSS_E_PROVIDER_VETO message.


Workaround: Restart VSS service before performing instant restore operations, or upgrade the Windows operating system to Windows 2012 R2. (108601)

• When both of the following hardware providers are installed on the same system:
• IBM XIV VSS hardware provider
• Microsoft iSCSI VSS hardware provider
instant restore operations via the VSS ResyncLuns API may fail for XIV volumes.

Workaround: Uninstall the Microsoft iSCSI VSS hardware provider (108975)


• The ResyncLun feature is not supported on Windows 2008 and 2008R2. However the VSS Diagnostics Wizard still prompts to allow user to perform Resynclun tests

Workaround: Do not put a check mark next to ResyncLun test checkbox in the VSS Diagnostic Wizard when using Windows 2008 and 2008R2. (116513)


• The VSS diagnostic action is not displayed after opening the MMC configuration wizard and clicking on diagnostics when using Windows Server 2008.

Workaround: In the MMC configuration wizard expand the diagnostic node and select either trace and log files, or system information. The VSS diagnostics will then appear in the actions panel. (116515)


• The Configuration Wizard May Fail To Provision the VSS Requester On Windows 2016 Data Center In The Following Circumstances:

The configuration wizard may fail to provision the VSS Requester on Windows 2016 Data Center if the installation image
is on a mapped network drive rather such as \\servername\sharename rather than a local drive such as C:\

Even if the user clicks "Yes" to the Microsoft Windows UAC popup the VSS Requester may not provision and
errors will appear inside the installation directory in the FlashCopyManager\Provision\VssProvisioning.log directory.
MsiInstaller errors will also appear in the Windows Application event log.

Workaround: Keep the install image on a local drive rather than a network drive. (128681)

National Language Support (NLS), and Other Issues When Operating in a Non-English Environment

If a GB18030 character outside of the supported code pages shown below is used in a text editor in the MMC it will be displayed as a series of question marks such as ???.

Workaround: For Simplified Chinese, Traditional Chinese, Japanese, and Korean, the only characters that are supported in MMC text editors are the characters contained in the following code pages:

CP1381 - Simplified Chinese
CP950 - Traditional Chinese
CP932 - Japanese
CP949 - Korean

Avoid the use of characters that are not included in these code pages. (98398)

In the MMC GUI, mnemonics appear in some tool tips for Japanese and other Double Byte Character Set (DBCS) languages. This happens when the same text used for the control's label is also used for the tool tip.

Workaround: Ignore the mnemonics in tool tips (76487)

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.


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)

The powershell cmdlet parameter "DaysRetain" is not translated correctly.

Workaround: Use English help message, or use command line help messages instead of powershell cmdlet. (121083)



Data Protection for VMware "application protection" Integration Related Issues and Limitations

• The option TEMPLOGRestorepath and TEMPDBRestorepath used to overwrite default recovery database location are NOT supported with VMVSS backups created using Tivoli Storage Manager for Virtual Environments: Data Protection for VMware and must be removed from tdpexc.cfg. The TSMMOUNT system environment variable should be used in place of the TEMPLOGRestorepath and TEMPDBRestorepath options.




• Restore* of a Microsoft SQL Server or Exchange Server database from a VM backup with application protection might

terminate with messages ANS1086E and ACN5060E if the VM backup** was created under one of the following conditions:

Several virtual disks have been removed from the VM. Then the virtual machine has been powered on and the
removed disks have been added back but in a different order. The VM backup is taken without VM reboot.

The Virtual Hard Drive (VHD) is attached to the guest OS at the time that the backup was performed.


The RAM disk that emulates a hard drive is mounted in the guest OS at the time of that the backup was performed.

In these cases the VM backup might contain incorrect information about VMware virtual disk numbers which causes
the termination of restore operation with messages ANS1086E and ACN5060E.

Workaround:

At backup stage:
Avoid all the conditions that are listed previously. If a virtual disk has been added, reboot the VM before performing a VM backup.
Before a VM backup, make sure that there is no VHD or RAM disk attached in the guest OS.

At restore stage:
To restore the database from the affected backup:
1. Determine which VMware virtual hard drive corresponds to the volume that stores the database.
2. Mount the appropriate virtual disk from the appropriate backup using Recovery Agent.
3. Manually restore the database using files from mounted backup.

* A restore operation is performed using the following products:
• Tivoli Storage FlashCopy Manager for Microsoft Exchange Server
• Tivoli Storage FlashCopy Manager for Microsoft SQL Server
• Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server
• Tivoli Storage Manager for Mail: Data Protection Microsoft Exchange Server

** A backup operation is performed using the Tivoli Storage Manager for Virtual Environments: Data Protection for VMware.




Known Issues and Limitations Resolved with 7.1.1 / 4.1.1

To perform Mailbox Restore (IMR) operations on Exchange Server 2010, the Exchange Server that you are performing the mailbox restore on cannot 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)

When FlashCopy Manager or Data Protection for Exchange restore a large number of messages using Mailbox Restore Browser, the restore speed gets slower and slower as the restore goes on.

Workaround: The following methods can help to reduce the restore time.
* Use a filter to reduce the number of messages to be restored. For example, use the "Received Date" filter to get all of the messages within one week instead of restoring all messages.
* If you need to restore the whole mailbox, using "Restore to Unicode PST file" can usually get better performance than using the Mailbox Restore Browser.




Known Issues and Limitations Resolved with 7.1.2 / 4.1.2

After applying Microsoft Exchange 2013 CU6, the following functions will not complete successfully:

- mailbox restore of a deleted mailbox
- mailbox restore to a unicode PST file

with:
- FlashCopy Manager for Microsoft Exchange Server 4.1.1
- Data Protection for Microsoft Exchange 7.1.1

These issues are addressed via APAR IT05554 http://www.ibm.com/support/docview.wss?uid=swg1IT05554

• In a Stand Alone environment (i.e. there is no TSM Server in the environment), the custom configuration Wizard does not save the updated VSS Requester node name to the same options file name when a custom options file exists.


Workaround: When you change the VSS Requester node name, update the custom options file name at the same time.
(75919)

• In a Stand Alone environment (i.e. there is no TSM Server in the environment), the custom configuration Wizard does not set a default "VSS Requestor node name". Instead, the VSS Requestor node name is has an empty value and therefore requires the user to provide the node name every time that configuration is run.


Workaround: None.
(75918)

• The following parameters (-logfile, -tracefile, -traceflags) will not provide the documented function with the following cmdlets (Get-FcmFsConfig, Set-FcmConfig). If these parameters are used with mentioned cmdlets, no log or trace files will be generated.


Workaround: The -Tracecmdlet parameter can be used with the Get-FcmFsConfig, Set-FcmConfig cmdlet for tracing and logging info. (98486)


• Attempts to delete an Exchange VSS Local backup will generate an error messages (ANS5250E and ANS1449W) in the TSM Backup-Archive Client log (dsmerror.log) similar to the following:


07/08/2014 09:17:20 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::deleteSnapshot
TSM function : VSS[DeleteSnapshots] for request '{9ad4b464-cb3f-4bc0-9f22-4448316a3368}' returned 'VSS_E_OBJECT_NOT_FOUND'
TSM return code : 131
TSM file : ..\..\common\winnt\vssreq.cpp (4179)
07/08/2014 09:17:20 ANS5250E An unexpected error was encountered.
TSM function name : vssDeleteSnapshot
TSM function : deleteSnapshot() failed
TSM return code : 131
TSM file : ..\..\common\winnt\vssback.cpp (2953)
07/08/2014 09:17:20 ANS1449W A non-critical, unexpected error was encountered.
Deletion of a snapshot(Set/Volume) failed. Probable cause, snapshot does not exists anymore. Continuing Process...
TSM snapShot ID : {9ad4b464-cb3f-4bc0-9f22-4448316a3368}
TSM function name : vssDeleteSnapshot()
TSM function : Deletion of Snapshot failed, Continuing...
TSM return code : 0
TSM file : ..\..\common\winnt\vssback.cpp (7078)
07/08/2014 09:17:39 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::deleteSnapshot
TSM function : VSS[DeleteSnapshots] for request '{68ba9027-7000-473c-a0b5-b6fbda4d2a9c}' returned 'VSS_E_OBJECT_NOT_FOUND'
TSM return code : 131
TSM file : ..\..\common\winnt\vssreq.cpp (4179)
07/08/2014 09:17:39 ANS5250E An unexpected error was encountered.
TSM function name : vssDeleteSnapshot
TSM function : deleteSnapshot() failed
TSM return code : 131
TSM file : ..\..\common\winnt\vssback.cpp (2953)
07/08/2014 09:17:39 ANS1449W A non-critical, unexpected error was encountered.
Deletion of a snapshot(Set/Volume) failed. Probable cause, snapshot does not exists anymore. Continuing Process...
TSM snapShot ID : {68ba9027-7000-473c-a0b5-b6fbda4d2a9c}
TSM function name : vssDeleteSnapshot()
TSM function : Deletion of Snapshot failed, Continuing...
TSM return code : 0
TSM file : ..\..\common\winnt\vssback.cpp (7078)


Workaround: None. The messages ANS5250E and ANS1449W can safely be ignored as the corresponding shadow copy (or copies) for the VSS local backup(s) have already deleted from system VSS.
(73027)

Known Issues and Limitations Resolved with 7.1.3 / 4.1.3

Backup of a VM with application protection fails when one (or more) Microsoft Exchange Server 2013 databases are dismounted

In this scenario, a virtual machine with application protection enabled was backed up using Tivoli Storage Manager
for Virtual Environments: Data Protection for VMware 7.1.2. However, the virtual machine contained one (or more)
Microsoft Exchange Server 2013 databases that were dismounted. As a result, the backup operation fails with
the following warning message:


ANS9432W IBM Tivoli Storage Manager application protection failed to truncate application logs on virtual
machine 'VM-name'.


Workaround: Mount the Exchange Server 2013 database, then run the backup operating again. (84115)

Exchange Database Availability Group name is not displayed for databases included in VMVSS backups

In this scenario, a virtual machine with application protection enabled was backed up with Tivoli Storage Manager
for Virtual Environments: Data Protection for VMware 7.1.2. The virtual machine contained one (or more)
Microsoft Exchange Server databases. Subsequent use of FlashCopy Manager or Data Protection for
Microsoft Exchange commands to query information about these databases will not display the DAG node name prefix.

For example, the output of the command:

tdpexcc query tsm *

will not the Database Availability Group (DAG) node name prefixes for databases contained in the VMVSS backup.

Workaround: None (87911)

Unsupported restore tasks when the Microsoft Exchange Server database changes after virtual machine backup

An Exchange Server database restore or user mailbox restore from the backed up virtual machine are not
supported when either of the following issues occur after the virtual machine is backed up using Tivoli Storage
Manager for Virtual Environments:Data Protection for VMware:

-The database is relocated to a different volume.
-The database path changes. (93737)

Microsoft Exchange Server mailbox history not collected

When Tivoli Storage Manager for Virtual Environments: Data Protection for VMware creates an application consistent backup of a virtual machine that hosts Microsoft Exchange Server, the mailbox history is not collected.
(94481) (94482)

The remote management features of the MMC GUI interface support the addition of remote computers using the "Manage Computers" action in the "Actions" pane. Remote computers can be added individually or in groups. Once a group is created and selected, there are three group tabs available: Group Dashboard, Group Reports, and Group Commands.

The Group Commands tab provides the ability to execute commands across multiple computers. This Group Commands view has a toolbar icon labeled Tips. However, clicking the Tips button does not display any tips.

Workaround: There are 2 ways to work around this problem:
1) Use the online help to obtain more information
2) Select a local computer, then select an instance of an SQL Server, Exchange Server, or File System under the option "Protect and Recover Data" in the tree view. Then select the Automation tab. Click the Tips button there for some tips on submitting commands. The same tips apply to the Groups Commands view. (87911)

After using the MMC wizard to define a machine for remote operations, the check box that allows you to select an application environment for configuration will be available even when the application status is still "in progress". If you attempt to use this option while the application status is still "in progress", the configuration wizard will disappear when you click the "Next" button.

Workaround: Wait until the previous operation completes, and the application status is in either the "configured" or "not configured" state, before attempting to configure the application environment. (92519)



Known Issues and Limitations Resolved with 7.1.4 / 4.1.4

After using the presnapshotcmd or the postsnapshotcmd option for a backup operation, the next backup operation will continue to use the presnapshotcmd or the postsnapshotcmd even when the option is not defined for the new backup.

Workaround: Restart dsmcad.exe process (102503)

When using the MMC GUI interface to remotely manage a system that is not in the same domain as the local system, the "Restore Into" dialog does not list databases for the remote system.

Workaround:
Option 1: Use the command line to perform the restore operation
Option 2: Use the MMC GUI interface from the local host.
(102915)



Known Issues and Limitations Resolved with 7.1.6 / 4.1.6

The Archive Mailbox restore fails to restore when the mailbox alias folder field is left blank, or if a forward slash "/" is used. The error message ACN0151E will appear.

Workaround: Use normal characters in the mailbox alias folder field when performing a restore, such as "archive_folder" (116286)

When the Windows volume automount feature is disabled on the offload server, VSS offloaded backups will terminate with the message:

RC: 418 FMV5280E (RC920) Object enumeration from a file set or file list failed

This occurs because the imported VSS snapshot volume can not be accessed.

Workaround: Enable the Windows volume automount feature on the offload server. (108785)