Known Issues and Limitations: Version 3.2.x FlashCopy® Manager for Microsoft SQL & Version 6.4.x Data Protection for Microsoft SQL

Preventive Service Planning


Abstract

This document details the Known Issues and Limitations for FlashCopy Manager® for Microsoft SQL Server V3.2.x and Data Protection for Microsoft SQL Server V6.4.x

Content


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

  • FlashCopy Manager for Microsoft SQL V3.2 --> which is a part of the IBM Tivoli Storage FlashCopy Manager V3.2 product
  • Data Protection for Microsoft SQL V6.4 --> which is a part of the IBM Tivoli Storage Manager for Databases V6.4 product.

This document describes the Known Issues and Limitations applicable to:
  • FlashCopy Manager for Microsoft SQL V3.2.x
  • Data Protection for Microsoft SQL 6.4.x



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
VSS Issues and Limitations
National Language Support (NLS), and Other Issues When Operating in a Non-English Environment



General Issues and Limitations


  • If a stand-alone Data Protection for Microsoft SQL Server package is installed on a system where Tivoli Storage FlashCopy Manager is already installed, and the Data Protection for Microsoft SQL Server component is also already installed at the same level as the stand-alone package, the Data Protection license enablement file will not be installed.


    Workaround: Manually copy the file sqlclient.lic from the installation media to the TDPsql folder. By default, this folder is located at:
      c:\program files\tivoli\tsm\TDPsql.


    (77952) (85882) (IC86907) (IC82568)

  • Any action requiring that the Data Protection for Microsoft SQL Server's license enablement file be present, will fail with the following error when the license is not present on the system:
      FMY5960E This product is not licensed to run data protection operations to a Tivoli Storage Manager server. A valid DP for SQL license file could not be located. With the current licenses only data protection operations to a Flash Copy Manager virtual server can be run. , FMY5960E This product is not licensed to run data protection operations to a Tivoli Storage Manager server. A valid DP for SQL license file could not be located. With the current licenses only data protection operations to a Flash Copy Manager virtual server can be run.

    It is correct for this message to be displayed in this scenario. However, the message is displayed two times. (85672)

  • When using Data Protection for Microsoft SQL Server, or FlashCopy Manager for Microsoft SQL Server, the database name can not end with 14 digits surrounded by parentheses characters.

    For example:
      Database or
      Storage Group Name
      Supported? Reason
      DB(20120409153304) not supported Database name ends with 14 digits surrounded by parenthesis
      DB20120409153304 supported Database name ends with 14 digits but they are not surrounded by parenthesis
      DB(2012040915330) supported Database name is surrounded by parenthesis but only has 13 digits within them
      DB(abcdefghijklm1) supported Database name ends with 13 characters and only 1 digit surrounded by parenthesis
    (IC79445)

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

    FlashCopy Manager for Microsoft SQL or Data Protection for Microsoft SQL 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)

  • Under rare circumstances, a backup in a FlashCopy Manager stand-alone environment (e.g. no TSM integration) can fail in such a way that future stand alone backups are not possible without implementation of the recommended circumvention.

    The problem can only occur during the initial stand-alone server backup when the DSMAGENT is abnormally terminated while the backup is running. When this occurs, a saved copy of the local FlashCopy Manager database is not available for recovery because the previous backup never completed. This causes subsequent backups to fail because the database files were left in a corrupt state by the previous backup.

    This issue can only occur during the initial backup.

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

  • When a backup process will include multiple components, such as DB1, DB2, and DB3, the behavior for mounting local snapshots differs when the snapshots are mounted remotely.


    Example backup scenario with multiple components via the command line:

      tdpsqlc backup db1,db2,db3 ....


    or via the MMC GUI interface:
      Select multiple components (rows)
      Press the "Backup" button.

    When the backup is made as described in the examples above, and a local mount is done, the only component(s) that you will see at the mount point are the ones that were specified on the mount command.

    In contrast, when a remote mount is done you will see all the components, specified as a part of the backup, at the mount point.

    For example:

    If an SQL backup was created like:
      tdpexcc backup db1,db2,db3 ...

    and then after the backup completed, a remote mount command was issued on a server other than the one where the backup was created:
      tdpexcc mount backup db2=c:\mnt /remotecomputer=server2 /remotecomputeruser=user /remotecomputerpassword=passwd

    you would see directories for db1, db2 and db3 at the mount point c:\mnt rather than just db2.
    (85502)

  • Legacy backups may fail when an EXCLUDE statement that excludes all backups (e.g. exclude \...\*) is used in the Data Protection for Microsoft SQL Server's dsm.opt file where there is also an INCLUDE statement for specific backup types.

    Workaround:

    Add an additional include statement as shown in this example:

    exclude \...\* --> excludes all database from backup
    include \...\dbName\full* --> includes full backups of dbName (or any other backup type)
    include \...\dbName\full*\* --> NEW STATEMENT NEEDED to include sub objects of the backup

  • In the "Files" view of the MMC GUI, files which have been deleted from an SQL database remain in the "Files" view until the group from which removed file belongs is also removed. Attempts to restore the deleted file will fail.

    Workaround:
    Option 1: Do not attempt to restore any file that has been deleted from the SQL database.
    Option 2: Set the QUERYOPTIMIZATION option to zero in the Data Protection for Microsoft SQL Server's configuration file (tdpsql.cfg) and retry the operation.
    (88682)

  • When running the stand-alone or TSM configuration wizard, the wizard may fail during the Configuration step. Specifically, the Configuring Services task may show a "Failed" status.

    Workaround: Use the Re-Run button to perform the operation again. (88813)

  • When using the /PITDATE and /PITTIME options to remote mount a backup via the command line interface, these two options will be ignored and the active backup will be mounted instead.

    Workaround: Use the <object-id> positional parameter to specify the specific inactive backup to mount. (87250)

  • The "object-id" parameter is missing from the fcmcli help for the mount command.

    Workaround: The fcmcli mount command syntax, including the "object-id" parameter, is documented in the Installation and Users Guide. (87252)

  • The value displayed in the Physical Path column of the SQL Server | Protect | Files view of the MMC GUI will not display the actual physical path if running on a secondary replica of an AlwaysOn availability group and the physical path is different on the primary and secondary replicas.

    Workaround: To see the actual physical path, issue the following T-SQL statement in SQL Server Management Studio:
      select * from master.sys.master_files

    (81487)

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

  • Not all files will be displayed in the "Relocate" window for backups created before the fix was applied.

    The fix for APAR IC71334, corrects the Data Protection for SQL problem described in the APAR so that the problem no longer occurs for future backups. However, the fix applies to the backup of meta data which contains the information about DBase datafiles. All backups created before installation of the fix still have the wrong meta data information. No data is lost and all data files can be restored successfully. However, even after the installation of the fix, not all files will be displayed in the "Relocate" window for backups created before the fix was applied. For backups created before the fix was applied, please use the command line work around example provided in the LOCAL FIX section of this APAR.
      Note: The command line string should not exceeded 8192 characters.
    The fix was first made available in Data Protection for SQL 5.5.4.2, and FlashCopy Manager for SQL 2.2.1.

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

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

  • When using the command line to query backups for a Microsoft SQL Server AlwaysOn availability database, /QUERYNode=BOTH does not return the associated AlwaysOn backups.

    Workaround: Retry the operation specifying /QUERYNode=ALWAYSON
    (33359) (33359-410)

  • The LogEstimate value from tdpsql.cfg file is ignored. The default value of 0 will be used

    Workaround: Specify the /LOGESTimate value on the tdpsqlc command line.
    (30654) (30654-410)



G UI Issues and Limitations

  • The "Restore to Point-in-Time" Action is activated when full+log or diff+log items are selected from different databases. The Action should be disabled when backups from different databases are selected. An error message will be displayed for any backups that couldn't be restored.

    Workaround: To avoid an error message, do not select combinations of full,differential,log backups from different databases before clicking the Point in Time restore action. Select backups from a single database to use Point in Time restore. (86931)

  • When the stand-alone Data Protection for Microsoft SQL Server package is installed (e.g. there is no Tivoli Storage FlashCopy Manager or TSM for Copy Services license installed also), the command line help shows that both /backupdestination and /backupmethod are available options for the BACKUP LOG and BACKUP DIFF FULL commands.

    However, when a Tivoli Storage FlashCopy Manager or TSM for Copy Services license is not installed, only /backupdestination=tsm and /backupmethod=legacy are valid options for the BACKUP LOG and BACKUP DIFF commands.

    Workaround: Do not use /backupdestination or /backupmethod with the BACKUP LOG and BACKUP DIFF commands. (87396)

  • When TDP for sql package installed without FCM License and BA client installed as well. In MMC GUI, when user selects database and perform backups from context menu. The backup destination "Local" and "Both" are enabled for selection when they should not. This is because the current context menu does not check the FCM license.

    Workaround: Use the action pane to select the backup destination since action pane has the right selection displayed.(77682)

    When using the SQL Recover view of the MMC GUI interface to delete CopyFull backups, selecting a CopyFull backup may show as FULL instead of CopyFull. The command completes successfully but the backup is not deleted.

    Workaround: Use the DELETE BACKUP command from the command line and specify COPYFULL as the backup type.
    (35733)

  • The SQL Backup "Files" view in the MMC GUI interface shows files that have been removed from a database. SQL Server maintains information about database files after they are deleted until the containing filegroup is deleted. The MMC GUI interface is incorrectly displaying those files as being available for backup.

    Workaround: To avoid the error do not select any files that have been deleted from a database. Alternatively, set 'queryoptimization 0' in the tdpsql.cfg file which will bypass the issue. Please note that turning off query optimization (by setting it to 0) may result in slower query performance especially when many thousands of databases are in the environment.
    (88682) (34547)

  • When interacting with the SQL Recover view of the MMC GUI interface, backups of AlwaysOn availability databases taken on a secondary replica display as Full instead of CopyFull.

    Workaround: Backups on secondary replicas are always CopyFull backups. For each backup, the MMC GUI displays a column indicating whether it was taken on a secondary replica or not. Note the value in the Secondary Replica column, and if it shows yes, consider that the backup is a CopyFull backup.
    (33152) (33152-410)

  • When using the FlashCopy Manager MMC GUI with multiple SQL Server instances in a Standalone configuration, the VSS policy binding property page will show bindings for both instances.

    Workaround: The Server name is shown for each policy binding record. Ignore the Policy Binding statements that are targeted for a different SQL Server instance than the one currently selected.
    (32273) (32273-410)

  • When the Data Protection for Microsoft SQL package installed, Tivoli Storage FlashCopy Manager specific VSS Backup options appear in the SQL Server VSS Backup property page. The page contains FlashCopy Manager options such as "remote DSMAGENT node name" and "import VSS snapshots only when needed."

    Workaround: Data Protection for Microsoft SQL Server does not support the "remote DSMAGENT node name" and "import VSS snapshots only when needed" settings. These settings can be ignored.
    (30133) (30133-410)

  • With the Data Protection for Microsoft SQL package installed, Tivoli Storage FlashCopy Manager specific VSS Backup options appear in the VSS policy binding page. Specifically, "Local" appears as a backup destination.

    Workaround: Data Protection for Microsoft SQL Server only supports a backup destination of TSM. The "Local" destination option can be ignored.
    (30131) (30131-410)


VSS Issues and Limitations

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

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

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

  • DSMAGENT hang during off-loaded backup failure

    When trying to execute a off-loaded 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.

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

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

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

  • 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. This is a known Microsoft bug with reference number 109090353881466. IBM is working with Microsoft to resolve this issue.

    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.


  • 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 SQL or 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
  • DSMAGENT memory leak during frequent VSS backups

    In rare situations where FlashCopy Manager for SQL or 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.



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

  • In the MMC GUI, mnenomics 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 tooltip.

    Workaround: Ignore the mnemonics in tool tips (76487)

  • When running in a locale that has variable-length characters such as Japanese or Chinese, some command-line interface output text may not be aligned properly.

    Workaround: N/A. This is a display issue only and will not affect operations. (61208_3)

  • Running Data Protection for SQL or FlashCopy Manager for SQL in an unsupported locale

    If you run FlashCopy Manager for SQL or 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 FlashCopy Manager for SQL or 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 or FlashCopy Manager 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 and FlashCopy Manager for SQL. Failure to set the language to ENU in the tdpsql.cfg will result in error messages every time that you launch FlashCopy Manager for SQL or Data Protection for SQL just as if you were using a non-English locale without installing the corresponding language pack. (IC75977)

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager for Databases
Data Protection for MS SQL

Software version:

6.4, 6.4.1

Operating system(s):

Windows

Reference #:

1608294

Modified date:

2013-09-17

Translate my page

Machine Translation

Content navigation