This document describes the known problems and limitations for IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server Version 5.5.0 .
This document describes the Known Issues and Limitations Data Protection for SQL V5.5.0.
To obtain a full list of Known Issues and Limitations for all V5.5.x levels of DP for SQL, please refer to the following tech note:
Note: The doc link above includes the entries listed in this document as well.
Note: Data Protection for SQL VSS operations requires the following software products to be installed:
- IBM Tivoli Storage Manager for Databases - Data Protection for SQL
- IBM Tivoli Storage Manager Backup/Archive Windows Client
- IBM Tivoli Storage Manager for Copy Services
General problems and limitations
- DP for SQL may fail with the following error:
ANS0328E (RC45) The specified objects failed the merge test.
when the management class is changed from the previous backup, and the new objects have different copy destinations, or if the VEREXIST, VERDELETE, RETONLY, RETEXTRA values change for the management class. This is a limitation of the product recorded in APAR IC33026.
Workaround: You can use a new Nodename for your backups or rename the Filespaces for the current backups. Both circumventions will allow you to retain the older backups and also allow you to perform the new backups with different management class settings than the original.
- Invalid characters on screens of Polish installations packages
When installing the product using the Polish installation executables, some invalid characters may appear on the installation screens. This is a known problem currently under investigation (35522).
- Running Data Protection for SQL in an unsupported locale
If you run Data Protection for SQL 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 Data Protection for SQL. 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.
- Running Data Protection for SQL with a locale for English that is not US English
US English (enu) is the only "English" locale supported by Data Protection for SQL. Failure to set the language to ENU in the tdpsql.cfg will result in error messages every time that you launch Data Protection for SQL just as if you were using a non-English locale without installing the corresponding language pack. (IC75977)
- PASSWORD option in the DSM.OPT file is ignored
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.
- Specifying a non-default date format with a point-in-time restore may fail
When Data Protection for SQL has been configured to use a non-default date format, point-in-time restore operations will fail and the following error message will be received:
An exception occurred while executing a Transact-SQL statement or batch.
Invalid value specified for STOPAT parameter.
RESTORE LOG is terminating abnormally.
Changed database context to 'master'. (HRESULT:0x80131501)
To work around this issue, use the default date format. This is a known problem currently under investigation (36559).
- HRESULT 0x80131501 received during a restore operation
If Wait for Tape Mounts for File Information option is not selected on the Restore Database or Restore Groups/Files panel of the Data Protection for SQL GUI, a Legacy restore operation might fail with the following error message:
File '<name>' cannot be restored to '<file name>'. Use WITH MOVE to identify a valid location for the file. Problems were identified while planning for the RESTORE statement. Previous messages provide details. RESTORE DATABASE is terminating abnormally. Changed database context to 'master'. (HRESULT:0x80131501)
To work around this issue, select the Wait for Tape Mounts for File Information option and refresh the tree view by clicking on the Refresh Tree View button before specifying relocation parameters in the Relocate dialog box. This is a known problem currently under investigation (36454).
- User-specified FILE or GROUP logical names are not validated at backup time
If FILE or GROUP values other than a wildcard character "*" have been specified in a BACKUP command, Data Protection for SQL will not validate that all logical names are valid. If an invalid group or file name is provided as a value for the above-mentioned options, the value will be ignored and no error message displayed. This is a known problem currently under investigation (36340).
- Restore Progress dialog box may show truncated error messages
When Data Protection for SQL displays error message(s) in the Restore Progress dialog box, the last part of the error message may be truncated. To work around this issue, examine the Data Protection for SQL error log file; it will contain the complete error message(s). This is a known problem currently under investigation (36460).
- Data Protection for SQL 5.5.0 requires upgrading the TSM Backup/Archive client to version 5.5.0 (or later)
Data Protection for SQL version 5.5.0 installs a new version (5.5.0) of the Windows TSM Client API. This new TSM API version is not compatible with previous versions of theTSM Backup/Archive client due to the new encryption library being used. If you use the Backup/Archive client, you must upgrade it to version 5.5.0 (or later) when upgrading Data Protection for SQL to version 5.5.0.
- Backup-archive client executables might not start after installing the version 5.5.0 (or later) Tivoli Storage Manager API on a Windows system that has the version 5.4.x backup-archive client installed
The Tivoli Storage Manager API is shipped with several IBM Tivoli applications. When installing more than one of these applications, only the latest version of the Tivoli Storage Manager API is retained on the system. This is by design since the Tivoli Storage Manager API normally maintains backward compatibility with applications implemented with an earlier version of the API. However, due to changes in encryption support in the Tivoli Storage Manager clients at version 5.5.0, an incompatibility was introduced between the version 5.5 Tivoli Storage Manager API and the version 5.4.x Windows backup-archive client, which share common encryption functions. This problem can occur when products that use the Tivoli Storage Manager API, such as Tivoli Storage Manager Data Protection version 5.5 (or later), are installed on a system where the 5.4.x backup-archive client exists AND the API product also distributes the version 5.5 (or later) Tivoli Storage Manager API. This issue affects all version 5.4.x backup-archive clients running on Microsoft Windows where the Tivoli Storage Manager API is at version 5.5.0 (or later).
When using a product that distributes the Tivoli Storage Manager API at level 5.5 (or later) on the same Windows system where a 5.4 level of the backup-archive client is installed, upgrade the backup-archive client to 5.5 (or later). If the backup-archive client cannot be upgraded to a version 5.5 (or later), set ENCRYPTIONTYPE DES56 in the dsm.opt. file for the backup-archive client to avoid the problem. This circumvention should be considered only if you do not use Tivoli Storage Manager client encryption or you do not require AES128 encryption.
- Failure to truncate transaction logs
Data Protection for SQL version 5.5.0 does not truncate the transaction logs during a full or differential backup. This is a known problem currently under investigation.
VSS related problems and limitations
- Metro / Global Mirror configurations are not supported with Tivoli Storage FlashCopy Manager components running on the Windows platform.
- Error message "ANS1950E (RC4345)" when trying to perform a VSS backup of a large number of SQL databases
When using Data Protection for SQL to perform a VSS backup of a large number of SQL databases, the following error message may be received:
ANS1950E (RC4345) Backup using Microsoft volume shadow copy failed
In addition, the DSMERROR.LOG for the Local DSMAGENT may contain this information:
10/17/2007 14:01:49 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::SaveXmlDocument
TSM function : CreateFile() failed for file C:\adsm.sys\vss_staging\SAGAN_SQL\188.8.131.52\20071017140051\TSM_Backup.xml' return code '32'
TSM return code : 0
TSM file : vssreq.cpp
To work around this issue, perform the VSS backups by specifying a fewer number of databases in a single invocation. Microsoft does not recommend more than a few dozen in a single operation. It is possible that the SQL Writer may get into an error state that requires a restart of the SQL Writer and/or SQL Server service. This is a known problem currently under investigation (36535).
- 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 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.
- Misleading message when performing VSS restores of multiple databases in a single operation
When performing a VSS restore of multiple databases, messages might be displayed similar to the following:
Beginning VSS restore of 'db1', 'db2', 'db3'...
Restoring 'db3' using file-level copy from a snapshot volume.
Beginning VSS restore of 'db1', 'db2', 'db3'...
Preparing for restore of 'db3' from TSM backup.
The second message in both cases is misleading since it indicates that only one of the databases is being restored. In fact, all databases are being restored. This is a known problem currently under investigation (36250).
- DSMAGENT hang during offloaded backup failure
When trying to execute a Data Protection for SQL offloaded VSS Backup request of more than one SQL database, if there is a failure in one of the requests before a snapshot is executed, the remote DSMAGENT service could hang. To work around this issue, stop the remote DSMAGENT service when this occurs.
- DSMAGENT hang caused by invalid DSMAGENT options file
Data Protection for SQL VSS operation 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.
- Side effect of changing the DSMAGENT TCPSERVERADDRESS option
If the TCPSERVERADDRESS option in the DSMAGENT options file is changed from numeric form to name form or from name form to numeric 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. To work around this issue, make sure TCPSERVERADDRESS is not changed from numeric form to name form or from name form to numeric form once backups have been created. If this is unavoidable, and you want to retain the current local snapshot backups, contact IBM service for additional instructions.
- DSMAGENT memory leak during frequent VSS backups
In rare situations where Data Protection for SQL 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.
- VSS Instant Restore in a Microsoft Cluster Server (MSCS) environment requires Microsoft HOTFIX 919117
Performing VSS Instant Restore operations with the SQL Server running in a Microsoft Cluster Server environment requires the following:
- Microsoft Windows Server 2003 Service Pack 2 (SP2) (or later)
- Microsoft hotfix KB 919117
You must call Microsoft to get access to this hotfix. If you do not have this hotfix installed, you should make sure to choose the Data Protection for SQL GUI option to "Disable VSS Instant Restore" or the Data Protection for SQL 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 operations in an MSCS failover situation
When performing VSS operations with the SQL Server running in a Microsoft Cluster Server environment, Data Protection for SQL VSS backups stored on local VSS disks may be removed if a Data Protection for SQL VSS operation is run on the failed over machine. This is due to the Microsoft limitation that allows VSS snapshots to be seen by only one machine at a time combined with the Tivoli Storage Manager policy management reconciliation code. Make sure your backup plan takes this into consideration.
- ACO0520E received if Tivoli Storage Manager Client Acceptor Daemon is not running
When Data Protection for SQL has been configured for VSS operations and the Tivoli Storage Manager Client Acceptor Daemon has not been started, the following error message will be received during QUERY TSM <database name> command:
ACO0520E Failed to connect to Local DSMAGENT Node '<node name>' at address:port 'x.xx.xxx.xxx:xxxx'. Verify that the Tivoli Storage Manager Client Acceptor Daemon (CAD) is installed, configured, and running properly.
There are two possible workarounds for this problem. The first method is to start the Tivoli Storage Manager Client Acceptor Deamon. Alternatively, LOCALDSMAGENTNODE and REMOTEDSMAGENTNODE options can be removed from the TDPSQL.CFG configuration file, if Data Protection for SQL will not be used for VSS operations. This is a known problem currently under investigation (36435).
- ACO5124E received during a backup operation
When Data Protection for SQL has been configured for VSS operations and the BACKUPMethod option has been set to VSS in the TDPSQL.CFG configuration file, the following commands will fail:
- BACKUP <database name> DIFFFULL
- BACKUP <database name> FILE
- BACKUP <database name> GROUP
- BACKUP <database name> SET
- BACKUP <database name> LOG
The following error message will be received:
ACO5124E Invalid command. Data Protection for SQL only supports VSS backup type of FULL.
To work around this issue, make Legacy the default backup method by setting BACKUPMETHOD to LEGACY in the configuration file. BACKUPMETHOD=VSS will need to be specified for VSS operations. Alternatively, DIFFFULL, FILE, GROUP, LOG, and SET backups can be performed from GUI. This is a known problem currently under investigation (36681).
- VSS Instant Restore operations fail in SAN Volume Controller
VSS Instant Restore operations will fail when Data Protection for SQL 5.5.0 is used in combination with SVC 4.2.1 (or later) or SVC 4.3.x environments. This is a known problem that is being investigated. (IC60174)
See information above.