IBM Support

Known Issues and Limitations: Version 8.1.x IBM Spectrum Protect™ Snapshot for Microsoft SQL & Version 8.1.x Data Protection for Microsoft SQL

Preventive Service Planning


Abstract

This document details the Known Issues and Limitations for IBM Spectrum Protect™ Snapshot for Microsoft SQL Server 8.1.x and Data Protection for Microsoft SQL Server 8.1.x

Content


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

  • IBM Spectrum Protect Snapshot for Microsoft SQL Server 8.1.x --> which is a part of the IBM Spectrum Protect Snapshot 8.1.x product.
  • Data Protection for Microsoft SQL Server 8.1.x --> which is a part of the IBM Spectrum Protect for Databases 8.1.x product.


This document describes the Known Issues and Limitations applicable to:

  • IBM Spectrum Protect Snapshot for Microsoft SQL Server 8.1.x
  • Data Protection for Microsoft SQL Server 8.1.x


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

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


General Issues and Limitations

  • Updates, clarifications, and corrections to the currently published version of the IBM Spectrum Protect Snapshot 8.1.x publications are located in the Documentation Updates tech note at the following URL:

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

  • Updates, clarifications, and corrections to the currently published version of the Data Protection for Microsoft SQL 8.1.x publication are located in the Documentation Updates tech note at the following URL:

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

  • Some of the IBM publications refer to Microsoft SQL Server 2012 even though Microsoft SQL Server 2012 is not supported at the Data Protection for Microsoft SQL Server 8.1.x level.

  • After installing either component, when you navigate to the software using the Windows desktop icon or Start menu, Spectrum Protect Snapshot 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 IBM Spectrum Protect Snapshot. 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 Configuration Wizard Macro leads to Errors


The configuration wizard of IBM Spectrum Protect Snapshot for Windows provides an option for the wizard to configure the IBM SPectrum Protect server.

When the option is selected, an administrator can edit the Spectrum Protect server configuration macro before it is submitted to the Spectrum Protect server.
The generated Spectrum Protect 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 Spectrum Protect macro 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 theConfiguration wizard, you must not change the temporary password defined in the Spectrum Protect macro called by the configuration wizard. This wizard uses this temporary password in several places.

Also, the comments included in the Spectrum Protect 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 Mount path for 'mount backup' command.

when protected by $component.

Limitation Description
'restore' command
'mount' command
1. Database 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 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 ends with 14 digits surrounded by parentheses characters. For example: 'DB(20120409153304)'

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

Example 'restore' command: tdpsqlc.exe restore $db_name($objectID) full

2. Database 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. 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 name. The Object ID should be surrounded by parentheses.

Example 'mount' command: tdpsqlc.exe mount backup $db_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 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 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)

  • SQL backups may fail if the primary storage pool is associated to a non-writable copy storage pool. For example: If the copy storage pool is set to "read-only", does not have enough scratch volumes allocated, or the "Auto-copy" mode is set to "Client".


The expected result is that the backup would continue and be automatically redirected to the primary storage pool instead.

Workaround: Resolve the storage pool configuration issue on the Spectrum Protect Server and re-run the backup when such an error is detected. (62000)

  • ACO0261I There are no backups for the server named {SQLServerName}


Error ACO0261I is witnessed when querying or attempting to restore a backup, even though the backup is successfully stored to and exists on the IBM Spectrum Protect Server.

This issue may be caused by a known limitation of the Microsoft SQL Server. Additional diagnostic details are available here:
http://www.ibm.com/support/docview.wss?uid=swg21967472

  • Final error reporting status information associated with backup of both standard and AAG databases in a single command


When performing a legacy backup of a database list which contains both standard and AAG databases, the final error message in the log file and command output may not reflect the correct status of the backup operation when the destination TSM nodes for the AAG and standard databases are different. i.e. UseAlwaysOnNode option is not set. This occurs because such a backup command is processed internally as two separate backup operations: the first one for AAG databases and the second one for standard databases. Either of these two operations could fail, for the same or different reasons, or be successful, independently from each other. However, the final command status displayed by Data Protection for Microsoft SQL Server is that of the error message for the first failure. This table summarizes this approach:

Case # AAG dbs backup status Standard dbs backup status The final command status
1 success success success
2 error 'A' success error 'A'
3 success error 'B' error 'B'
4 error 'A' error 'B' error 'A'


For example, if the AAG database group backup fails with:

"ACO5204E None of the specified databases exist, or are available for backup."

and the backup of standard database group is successful, the final message for the backup command will be ACO5204E.

Workaround: Backup AAG databases separately from standard databases or use the the AlwaysOn TSM node for both database types (UseAlwaysOnNode option).

  • Under rare circumstances a Spectrum Protect Snapshot 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 Spectrum Protect Snapshot 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 Spectrum Protect Snapshot agent service, delete all local Spectrum Protect Snapshot database files in the Spectrum Protect Snapshot staging directory, and then restart the Spectrum Protect Snapshot agent service. (98688)

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


IBM Spectrum Protect Snapshot 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)

  • 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

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

  • 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 theIBM Spectrum Protect 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.

  • A legacy backup of an availability database from a non-readable secondary replica cannot be restored with database files relocation.


Workaround: If the backed up database is not on the current server, try restoring the database to the original location. If the backed up database exists on the current server, move the existing database files to a different location and restore the backup as a new database. When the operation completes, the database files are in the original location. (IT08974)

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

The iSCSI disks is mounted directly in the guest OS at the time of backup.

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:
• IBM Spectrum Protect Snapshot for Microsoft Exchange Server
• IBM Spectrum Protect Snapshot for Microsoft SQL Server
• IBM Spectrum Protect for Databases: Data Protection for Microsoft SQL Server
• IBM Spectrum Protect for Mail: Data Protection Microsoft Exchange Server

** A backup operation is performed using the IBM Spectrum Protect for Virtual Environments: Data Protection for VMware.

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

  • In certain situations when using the MMC interface to restore a SQL database backup to some

alternate location, the Restore button is not disabled in the "Alternate Location Restore Settings" form.
This happens after the end-user is warned that a restore operation cannot be performed on non-readable secondary
replica the 'Restore to alternate location' radio button is grayed out, but the 'Restore' button is clickable.
If the restore operation is still performed then the operation fails as expected. This bug allows the restore
operation while the right MMC behavior would be to prevent the restore operation to proceed and eventually to
fail as expected. A warning message already announced that the restore operation cannot be successfully performed.

Workaround: None, you cannot restore on non-readable secondary replica of a SQL AAG database. (120898)

  • A restore of a vss backup with a quote in the name will not work due to a Microsoft SQL Server VSS Writer limitation. Microsoft SQL Server VSS Writer does not consider quotes as special symbol for SQL Server and will run the restore command as is without adding escape symbols.


Workaround: Use ‘relocatedir’ and ‘into’ options in vss restore command in order to restore data and log database files.
Then attach restored files into a database manually on SQL Server. (120205)

  • Error message ACO5424E may occur when using SQL Server 2016. Starting with SQL Server 2016, the Client Tool Connectivity is not part of the default database management installation of SQL Server. This is described in Microsoft technote https://msdn.microsoft.com/en-us/library/ms143786.aspx If the Client Tool Connectivity is not installed, the user may encounter error message ACO5424E with reason code "SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified"


Workaround: Install the Client Tools Connectivity on affected SQL Server 2016 machines

  • IBM Spectrum Protect Snapshot for Microsoft SQL and Data Protection for Microsoft SQL do not support restore scenarios that require the "WITH KEEP_REPLICATION" option in the "RESTORE" Transact-SQL command. Please see this Microsoft technote for more information: https://msdn.microsoft.com/en-us/library/ms188223.aspx


Workaround: None

  • When "BackupDestination Both" is in the TDP configuration file, the CLI and Cmdlets to delete/remove a backup will

fail with error "ACO5170E Missing, blank, or invalid Local DSMAGENT Node Name is not allowed."


Workaround: Remove "BackupDestination Both" from the TDP configuration file. (131753)

  • The log file of the IBM Spectrum Protect Data Protection for SQL Server does not display all of the databases on the database input list line when the operation is performed upon a list of SQL databases more than 4,000 characters long. The database list is truncated with ellipsis (the symbol of three dots).


Workaround: None (130316)

  • The IBM Spectrum Protect client agent service (dsmagent.exe) crashes if a data protection command is executed

right after the agent is restarted. This issue can also occur if a data protection command is executed directly
after a stopped agent is started.


Workaround: Wait 30 seconds after starting or restarting the IBM Spectrum Protect client agent service before
executing any commands (130880)

  • Renaming of the SQL database is not supported if only casing is changed during the renaming. Such a renaming may cause the restore failure with "ANS1302E (RC2) No objects on server match query".


Workaround: If after renaming the database and subsequent backup the restore fails with ANS1302E, check
filespaces existing on the TSM server. If there are two filespaces that differ only by casing in
the database name, rename one of the them depending on which db need to be restored.


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)

  • 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 following limitation applies to the support of remote management capabilities of the MMC GUI interface.


Remote management is not supported in an x86 (32-bit) environment. Therefore, you cannot connect to an x86-based
machine to run remote management features. You can manage x86 environments locally only.

Workaround: To run remote management features, you must connect to an x64-based (64-bit) environment.

  • The file browser window opened during a explore action contains some invalid directory entries when the

backup was mounted RW.

Workaround: None, the User can ignore the invalid entries. (130973)

  • After a user mounts a backup, they can use the "Explore" action to browse the files at the mounted location via a

file explore window. The File Explore window has a "Open" button, which a user would assume would open the
selected file. However, when the "Open" button is pressed, the File Explore window is closed.

Workaround: A user can use the native windows file explore to browse and open files at the mounted location. (130972)

  • The help topics view in the main tool bar does not contain the online help as expected.


Workaround: The online help can be viewed from the action menu and the navigation tree. (146654)

  • When trying to display the list of SQL database back ups through the Microsoft Management Console (MMC), an error occurs when there are no SQL database back ups to display. The Get-SqlBackup cmdlet shows that the query completed with a failed status. Additional detail shows errors like one of the following:


1. Error: RC: 112
ACO5550I There are no backups matching the filespec * and the server name *.

2. Error: RC: 113
ACO0261I There are no backups for the server named *.

3. Error: RC: 114
ACO5551I There are no backups matching the criteria specified for server name *.

4. Error: RC: 120
ACO0576I There were no items found.

5. Error: RC: 1909
ACO5552I No matches were found for the criteria specified.

All these errors are expected because there are no SQL database back ups. The correct response is a completed status of success showing no SQL databases in the MMC.


Workaround: Since no SQL databases are displayed, the failure can be ignored (147874)


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 IBM Spectrum Protect Client level installed for the level of IBM Spectrum Protect Snapshit 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 IBM Spectrum Protect 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. (89544)

IBM Spectrum Protect™ SnapshotRequirements:
http://www.ibm.com/support/docview.wss?uid=swg21427692

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

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

  • 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 IBM spectrum Protect Snapshot 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.

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

  • 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 IBM Spectrum Protect Snapshot 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 IBM Spectrum Protect Snapshot 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.

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

  • The hover help of the VSS Options property page in MMC does not display well in Windows 2012


Workaround: None (128422)

  • Backups might fail if a volume migration of OLVM volumes is ongoing. IBM Spectrum Protect Snapshot is able to protect OLVM volumes before and after their migration. Before the migration IBM XIV Provider for Microsoft Windows Volume Shadow Copy Service is configured to use the source XIV system as storage device.

Workaround: Once the disks are migrated, IBM XIV Provider for Microsoft Windows Volume Shadow Copy Service needs to be reconfigured to use the target XIV system as the storage device for the backup.


PowerShell (PS) cmdlets Issues & Limitations

  • Changing multiple configuration options via a single PowerShell command results in errors when the -Configfile option is also used


When using a single Windows PowerShell command to change 2 or more configuration options, and the -Configfile option is also used, errors may occur.

For example: The following command specifies to change both the "logfile" and "logprune" configurations in the file: C:\Program Files\Tivoli\tsm\TDPSql\tdpsql.cfg

PS C:\Users\Administrator> Set-DpSqlConfig -logfile tdpsql_new.log -logprune 45 -ConfigFile "C:\Program Files\Tivoli\tsm\TDPSql\tdpsql.cfg"

This command results in the errors that follow and the updates are not completed.

Set-DpSqlConfig : RC: 1207
ACO0104E Invalid option:
set

LOGPrune=45

"/CONFIGfile=C:\Program Files\Tivoli\tsm\TDPSql\tdpsql.cfg"
At line:1 char:1
+ Set-DpSqlConfig -logfile tdpsql_new.log -logprune 45 -ConfigFile "C:\Program Fil ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (Capability.Impl....Sql.SqlContext:SqlContext) [Set-DpSqlConfig], Exception
+ FullyQualifiedErrorId : 1207,IBM.Tivoli.TSM.Cmdlets.SQL.SetDpSqlConfig


Workaround:

Option 1: Use separate PowerShell commands to set each configuration option individually. For example:

PS C:\Users\Administrator> Set-DpSqlConfig -logfile tdpsql_new.log -ConfigFile "C:\Program Files\Tivoli\tsm\TDPSql\tdpsql.cfg"
PS C:\Users\Administrator> Set-DpSqlConfig -logprune 45 -ConfigFile "C:\Program Files\Tivoli\tsm\TDPSql\tdpsql.cfg"

Option 2: Use the MMC interface to set the parameters.

Note: This problem is resolved in the following levels:
Data Protection for Microsoft SQL Server 7.1.0.1
FlashCopy Manager for Microsoft SQL Server 4.1

  • 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 SQL Server will print the message ANS0200W " A message repository is not  available for your system's configured language xxx.  The US English message repository is used instead."  if the message repository for that language is not installed.
This in turn may lead to the message "Failed - Error: PowerShell Job is in Stopped state. The  operation might not be completed successfully" output when you work in Powershell or the GUI .


Workaround:  The Powershell job itself is completed. The message "The operation might not be completed  successfully" is incorrect and the backup or restore completed successfully.


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

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


If you run IBM Spectrum Protect Snapshot 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 IBM Spectrum Protect Snapshot for SQL or Data Protection for SQL. The error messages displayed will look similar to the following:

"ANS0101E Unable to open English message repository 'tdpsXXX.txt'"
"ANS0102W Unable to open the message repository tdpeXXX.txt. The American English repository will be used instead"
"ANS0113E" Message repository 'tdpsenu.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 IBM Spectrum Protect Snapshot 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 IBM Spectrum Protect Snapshot for SQL. Failure to set the language to ENU in the tdpsql.cfg will result in error messages every time that you launch IBM Spectrum Protect Snapshot for SQL or Data Protection for SQL just as if you were using a non-English locale without installing the corresponding language pack. ( IC75977 )

  • When using the custom PowerShell cmdlets, and the Windows system is set to double byte Unicode languages such as Korean or Traditional Chinese, then the output of "Get-Help IBM-SPS-cmdlet -Full" or "Get-Help IBM-SPS-cmdlet -Detail" might display some parameters with a space in the middle of the word, and the alignment will not match the English version.


Workaround: There is a partial workaround for the space in the middle of the word, but not the alignment issue. Run "Get-Help IBM-SPS-cmdlet -ShowWindow" instead of "Get-Help IBM-SPS-cmdlet -Full" or "Get-Help IBM-SPS-cmdlet -Detail" (130527)

Document information

More support for: IBM Spectrum Protect for Databases

Component: Data Protection for MS SQL

Software version: 8.1.0, 8.1.2, 8.1.4, 8.1.6, 8.1.7, 8.1.8

Operating system(s): Windows

Reference #: 1992685

Modified date: 27 June 2019