IBM Support

IBM Tivoli Storage Manager EOS V6.2 Windows backup-archive client known problems

Technote (FAQ)


This document contains warnings and known problems for the IBM Tivoli Storage Manager V6.2 Windows backup-archive clients.


Tivoli Storage Manager Client limitations and known problems


Common Tivoli Storage Manager Client warnings (applies to all modifications of version 6.2)

Back to Contents

Common Tivoli Storage Manager Client known problems and limitations (applies to all modifications of version 6.2)
  • Interrupt with CTRL-C

    During a command line client operation, pressing CTRL-C might result in a TSM client program exception or other unexpected behavior. To abort a command line client operation, press the 'Q' key instead of CTRL-C.

  • Web Client tree expansion

    When using the Web Client, the browser can crash if you do the following, using the view menu item in the backup or restore tree window:

  • Web Client font requirements for non-English file names

    For browsers running on AIX, the browser machine must have the WorldType fonts (available as package X11.fnt.ucs.ttf - AIXwindows Unicode True Type Fonts on the AIX distribution media) installed.

    For browsers running on Windows, the browser machine must have the Arial Unicode MS font installed. This font is available with MS Word 2002 and MS Office XP. See Microsoft's KB article 287247 for installation instructions. If you require this font, contact your Microsoft representative.

  • Log file out of space handling

    If any log file (dsmerror.log, dsmsched.log, or dsmwebcl.log) runs out of space during a session, writing to that log ceases, but other processing continues. End of processing return codes will reflect all errors and conditions, not just those we were able to log.

    To prevent this problem, set the ERRORLOGMAXSIZE (for dsmerror.log) or SCHEDLOGMAXSIZE (for dsmsched.log and dsmwebcl.log) options to limit the log size to available space. Note that using these options causes the log data that would exceed the maximum to be written at the beginning of the log, overwriting the oldest entries.

  • ERRORLOGMAX and SCHEDLOGMAX behavior in out-of-space conditions:

    If the specified maximum error log file size is greater than the available free space on the specified file system and the log is being transitioned from a non-wrapped log to a wrapped log, the following error message will be issued:

    ANS1521E Failure writing to a Tivoli Storage Manager log     or log-related

    file: <LOG FILE NAME> , errno = 28, There is not enough space in the file system

    This is the correct behavior. However, the log header record might be incomplete or there may be no "END OF DATA" text marker at the end of the error log. After space has been made available, the TSM client will subsequently treat the log as unwrapped because a valid header record is not found. A new log will be created and this partial log will be written to the prune file.

    If there is insufficient space in the file system to append an entry to the log, the TSM client will continue to run, but the error message will not be logged.

  • Some keywords have not been translated into Chinese for the backup-archive client:

    Some keywords, such as "Snapshot", have not been translated into Chinese. This is most notably evident in the backup-archive client GUI.

  • Handling spaces in file names in schedule definitions

    When defining or updating a schedule objects parameter or the schedule options parameter with file specifications that contain blank spaces, use quotation marks around each file specification that contains blanks, then single quotes around all of the specifications. The following are some examples of proper usage of the objects parameter:

    For Windows clients:

    objects=’"c:\home\proj1\Some file.doc"’
    objects=’"c:\home\proj1\Some file.doc" "c:\home\Another file.txt" c:\home\noblanks.txt’
    objects=’"c:\home\My Directory With Blank Spaces\"’
    objects=’"c:\Users\user1\Documents\Some file.doc"’
    objects=’"c:\Users\user1\Documents\Some file.doc" "c:\Users\user5\Documents\ Another file.txt" c:\Users\user3\Documents\noblanks.txt’ objects=’"c:\Users\user1\My Directory With Blank Spaces\"’

    This will ensure that c:\home\proj1\Some file.doc is treated as a single file name, as opposed to two separate files (c:\home\proj1\Some, and file.doc). Some examples of options parameter usage:

    options='-preschedulecmd="c:\home\me\my files\bin\myscript" -postschedulecmd="c:\home\me\my files\bin\mypostscript" -quiet'
    options='-presched="c:\home\me\my files\bin\precmd" -postsched=finish'

    You can also refer to the objects and options parameter information for the define schedule and update schedule commands in the appropriate IBM Tivoli Storage Manager Administrator’s Reference.

  • Java GUI does not start with invalid option in options file

    In rare cases, when there is an error in the dsm.opt file, the Java GUI will not start properly. The Java GUI will attempt to start, but at some point after 70%, the title screen disappears and nothing appears to happen.

    To work around the problem, refer to the dsmerror.log or dsmj.log file in the installation directory or from where the command to start the Java GUI was issued for the offending option, and remove it manually from the options file. You should be able to restart the client without problems.

  • Reset button does not function properly in Preference Editor Communications Panel

    On certain systems, the Communications panel in the Preference editor will not display correctly when the Reset button of the preference editor is invoked. When you click the Reset button, the list of communication methods might not display the proper list after the reset is complete.

    If there is a need to reset the communication panel back to the original settings, exit out of the preference editor and restart it.


    The value for the IMAGEGAPSIZE option should not be specified outside the listed ranges for MB and GB units. If it is, the client will not report it as an error.

  • Select all after applying filter from Backup window

    After applying a filter to a directory in the Backup window, when you check the check box for this filtered directory, the corresponding files in the file view on the right are not checked (not selected). To select the files in that filtered directory, click on the name of the checked directory and the boxes next to the filtered files are checked.

  • The list of new and changed messages in client_message.chg is not up-to-date

    The client_message.chg file that is included with the client does contain the current list of new and changed client messages from V6.1.0 to V6.2.0. See this technote for the list of V6.2 new and changed client messages:

  • Connection Information dialog might not appear in certain situations

    The Connection Information dialog might not appear correctly in certain situations. An exception will be logged in the dsmj.log file when this occurs. This will occur when you do the following:
    1. Start the Java GUI.
    2. Change password (Utilities -> Change Password).
    3. After successfully changing the password, click either the Backup, Restore, Archive, or Retrieve button.
    4. Attempt to open the Connection Information dialog (File -> Connection Information).

Back to Contents

Windows client warnings (applies to all modifications of version 6.2)
  • Windows PE

    When running the client as described in the Tivoli Field Guide "Tivoli Storage Manager Recovery Techniques Using Windows Preinstallation Environment (Windows PE)" you will receive the error message:

    ANS1464S Cannot load ICC encryption library

    Because the scenarios described in the field guide are not run from a fully installed TSM client, the registry entry indicating the location of the ICC encryption library does not exist. Since the recovery scenarios described in the field guide do not involve TSM encrypted files, you can bypass this error by modifying your client options file and specifying the option ENCRYPTIONTYPE DES56. This prevents the client from attempting to load the ICC encryption library.

  • Image backup does not work with shared memory protocol.

    To use the SHAREDMEM (shared memory) communications method, the TSM server and client must be executed by the same user. If the server and client are started by different accounts, then they will not be able to establish a connection with each other.

  • VM backup and restore: VMware off-host backups using vStorage for Data Protection API and VMware Consolidated Backup(VCB)
    • Restoring Netware Full VM Image files

      Netware is not listed as a fully supported guest operating system of VMware's Converter 3 tool. Attempting to use Converter on Full VM image files restored with TSM will result in an error. Other tools, such as VMKFSTOOLS from VMware, can be used to complete the restore of these Full VM Image files. For a list of fully supported guest operating systems and complete restore instructions refer to the VMware documentation.

      See the VMware Converter 3 Release Notes at:

    • Consolidated Backup of virtual machine data that is stored on local storage devices or NAS requires ESX Server 3.5 or ESX Server 3i version 3.5 in combination with VirtualCenter version 2.0.x or later.

      Tivoli Storage Manager attempts to use the VCB over-the-network protocol that was added in VCB V1.1, when there is a failure using the shared SAN. In certain cases, VMware Consolidated Backup will not report a failure on backup with the over-the-network support when running VCB V1.1 with an older ESX Server 3.0.x. Shared SAN should be used whenever possible.

      See the VMware Consolidated Backup 1.1 Release Notes at:

    • vStorage File-level backup operations can cause a crash of dsmc.exe or dsmcsvc.exe when processing certain virtual machines with very complex disk configurations. The exact virtual machine disk configuration which triggers this crash is unknown, but it was encountered on one occasion with a virtual machine having more than thirty volumes spread across six virtual VMDK disks. The volumes included a complicated mix of various software RAID types, spanning multiple disks and using different stripping. The call stack of the crash will be similar to:

      Stack Trace:
      vixMntapi.dll, VixMntapi_FreeVolumeInfo()+205696 bytes
      vixMntapi.dll, VixMntapi_FreeVolumeInfo()+219128 bytes
      vixMntapi.dll, VixMntapi_FreeVolumeInfo()+75736 bytes
      vixMntapi.dll, VixMntapi_FreeVolumeInfo()+78327 bytes
      vixMntapi.dll, VixMntapi_OpenDiskSet()+138 bytes

Back to Contents

Common Windows client known problems and limitations

Common Windows client known problems and limitations in version 6.2.3
    If the following messages are received from Java Virtual Machine (JVM) while running the DSM executable:

    JVMST109: Insufficient space in Javaheap to satisfy allocation request
    JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
    JVMDG315: JVM Requesting Heap dump file

    these errors indicate that your JVM maximum heap size is too small. The default value is 64 MB. To increase the maximum heap size and avoid this issue, add the -Xmxn (where n is size in MB) option on DSM startup. For example, to increase the maximum heap size to 256 MB, specify the following:

    dsm -Xmx256m

Common Windows client known problems and limitations in version 6.2.2 (applies to all modifications of version 6.2.2)
  • After restoring your machine with Automated System Recovery (ASR) you might see that the COM+ DB browser does not show COM objects. To resolve this issue you must reset the Microsoft Distributed Transaction Coordinator log file and restart the MS DTC service. To do this, issue the following commands:
    msdtc -resetlog
    net start msdtc
  • If you run a full volume backup of a CIFS mapped NetApp or N-Series volume, all the snapshots under the ~snapshot directory might also be backed up. To avoid this problem, exclude the ~snapshot directory from backups.

Common Windows client known problems and limitations in version 6.2 (applies to all modifications of version 6.2)
  • While performing an incremental backup using the snapdiff option on a Windows TSM Client, the CIFS default security type must have NTFS-Style. The CIFS security style can be set either from:

      Filer View -> CIFS -> Configure -> Security
      Use Group ID Permissions: No
      Default Security Style: ntfs

    or by issuing the following qtree command: qtree security /vol/nnn ntfs.

    If the CIFS security is set to mixed or unix, the client will be unable to perform the snapshot difference backup because the share will appear to be FAT and not NTFS, and will return the message: ANS2837E Failed to perform incremental backup operation using snapshot difference as the user id and password for NAS Filer have not been configured correctly.

    In addition, attempts to access a restored volume after a full volume restore to a new destination might lead to an access denied message from Windows unless the CIFS security is set to NTFS.
    Access is denied.

  • Hyper-V backup support

    Microsoft Hyper-V support is provided for the following configurations:

    Due to the tight integration of Microsoft Failover Clustering with Cluster Shared Volumes and Hyper-V, the following considerations apply when using TSM in this environment:

      • VM restores should only be performed by a B/A Client installed on the cluster node that is the current owner of the VM (see ServerManager->Features->Failover Cluster Manager->(clustername)->Services and Applications to see the VM configurations of the cluster)
      • VMs currently owned by different nodes which have files on a common Cluster Shared Volume cannot be backed up simultaneously. The second backup will fail as the shared volume will be owned by the first node (see ServerManager->Features->Failover Cluster Manager->(clustername)->Cluster Shared Volumes to see which node owns the volume)
      • If your cluster environment normally has all VMs running/owned by a single node with other nodes simply to provide failover support
        • Consider running the TSM Scheduler as a failover service to periodically backup all VMs (i.e. dsmc backup vm * -vmbackuptype=hypervfull).
      • If your cluster environment normally has some VMs running/owned by one node with other VMs running/owned by other nodes
  • Intermittent problem with Active Directory individual object restore

    Active Directory queries ("query adobjects" command) and restores ("restore adobjects" command) can occasionally fail. In case of failure, the following error message may or may not be issued:

    ANS5821E Cannot connect to Active Directory.

    A retry of the operation should resolve the issue. If you see it constantly failing after several retries, contact TSM support.

  • Installation Path Limitation

    TSM Client utilizes the Microsoft Windows Installer. Currently, there is an installation path limitation of 256 bytes.

    Also note: TSM Client language packs use the install path of the base client install, so a base install of the TSM Client that uses the maximum number of bytes in its install path might cause the language pack installation to fail.

  • Changing TSM Features/Components using the "Programs and Features" "Change" process

    On Windows Vista, the mechanism for changing installed TSM client components fails. The following error is reported:

    1: Failed to install ISKernel Files.
    Make sure you have appropriate privileges on this machine.

    The failure occurs when you change the TSM install from the "Programs and Features" section of the control panel. To work around this problem, run the TSM Client setup.exe from the extracted image (default placement is c:\tsm_images), or launch the CD-ROM and choose the client installation. Another alternative is to completely uninstall the client, then reinstall the client with the features that you want.

  • Windows Server 2003 - backup/restore system objects

    When restoring an inactive version of DHCP, you must also restore the corresponding inactive version of the System State. Otherwise the DHCP service will not start.

  • System State restore failed with Windows error 87 while replacing or restoring registry on Windows 2008 R2.

    Starting from Windows 2008 R2 and Windows 7, the registry key HKLM\COMPONENTS might not exist on the system. This registry key os created during installation of additional server roles or features. Only the Windows Operating System can create this key, applications are not allowed. Therefore, during System State restore on a clean system, the restore process might fail. To fix this problem, install any additional server role before attempting a System State restore.

  • VSS image backup might fail after a VSS image restore on small volumes (about 500 MB).

    On Windows Vista and later operating systems, VSS stores snapshot data on the volume on which the snapshot is being taken. This data located in the "System Volume Information" directory. On a 500 MB disk it takes about 350 MB to create the snapshot. TSM backs up only used blocks during the image backup. The data internal to VSS is also saved as part of the image. During an image restore, TSM recovers all image data. In this case, a second VSS image backup is not possible because of the lack of free space on the hard disk. VSS cannot create a snapshot for TSM due to the lack of space.

  • Euro symbol (?) support

    The euro symbol does not display correctly in the Command Line client. This is a Microsoft Windows limitation since the OS does not officially have a euro symbol-compatible code page (for example, cp858). In order to enable this support, you will need to first contact Microsoft for the cp858 file (c_858.nls) and install it under c:\WINNT\System32\ (or wherever your Windows directory is located). Then you need to modify the registry. IMPORTANT: The registry editor requires extreme accuracy. If you are not accustomed to editing the registry, ask your Windows administrator to make this change for you.

    To enable support for the 858 code page, do the following:

      1. Start the registry editor.
      2. Navigate to the following registry key:


      3. In the right-hand pane of the registry editor, locate the name "850". Change the value of the "850" name to the following:


      4. Close the registry editor. Reboot Windows. The TSM command line client should now display the euro symbol correctly. NOTE: Make sure your console is using a euro-capable font (for example, Lucida Console).

    To enable support for the Latin 1 code page, do the following:
      1. Start the registry editor.
      2. Navigate to the following registry key:


      3. In the right-hand pane of the registry editor, locate the name "850". It should have a null (empty) value. Change the value of the "850" name to the following:


      4. Close the registry editor. The TSM GUI should now display the menus correctly.
  • File names with Greek polytonic key combinations and Windows Vista

    File names with Greek polytonic key combinations, specifically Ypogegrammeni and Prosgegrammeni diacritic marks, will always be backed up by the Backup-Archive client during incremental backup even if the file has not changed. The problem is due to inaccuracies in the case folding rules for these characters. The problem only occurs on Windows Vista and not other Microsoft operating systems. A problem report has been opened with Microsoft to correct this behavior.

    The problem will occur with characters which occupy the Unicode code points U+1F88 through U+1FF3. Note that these characters represent a very specific subset of Greek characters and will most likely not occur in file names.

  • ANS1334W message during system drive restore on Windows Vista

    It is normal to see many warnings while attempting to restore junction points on the system drive. In Windows Vista, the default location of the user data has changed. To enable interoperability with older applications, Microsoft created junction points at the deprecated locations to point to the new locations. For example "C:\Documents and Settings" is now a junction point that points to "C:\Users". It is expected to have many junction points in the user data folder.

  • Restore system state on Windows Vista failed with RC 4323 when running as a backup operator

    When running as a backup operator, RegUnLoadKeyEx() returns access denied error (RC 5) during the merge process of the registry key. This causes the TSM client to fail to replace the system hive of the HKEY_LOCAL_MACHINE. Use the administrator account to restore the system state instead. Backup of the system state using the backup operator still works. This problem does not occur for the Windows 2003 client. Backup and restore of the system state on Windows 2003 using the backup operator works. The problem has been reported to Microsoft.

  • When installing the TSM scheduler service while the TSM server is down or otherwise unreachable, the node password will not be stored on the client computer. Without a stored password, the scheduler service cannot connect to the TSM server. To resolve this, after the TSM server becomes available, use the command line or GUI client to connect to the server, and enter the password when prompted. This will cause the password to be stored on the client computer, allowing the scheduler service to authenticate with the server.

    This problem might occur when you are setting up a scheduler running through a firewall using the server-initiated sessions. In this case, start the scheduler from the command line (dsmc schedule) and enter the node's password when prompted. After the password is updated, stop the command line scheduler (press the 'q' key twice), then restart the scheduler service.

  • After an image has been restored to a plain file using the -imagetofile option with the "restore image" command, a data copy utility will be needed to transfer the image data from the file to a disk volume. While IBM does not provide such a utility, there are several ports of the Unix "dd" command available for Windows. You can get one of those ports here:

    As an example, you can enter the following command to copy the image data from the file x.img to the volume x: with the block size of 1 megabyte:

    c:\> dd if=x.img of=\\.\x: bs=1M

  • ANS1009W An error occurred processing the operating system include/exclude statements. The error was detected while processing: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM. RC = 13.

    See for detailed information and a solution.

  • Restoring system state

    Starting with the 5.4.0 TSM client, files that are protected by the System File Protection (SFP) are restored to temporary files and replaced on reboot. Any in-use system files are also restored to temporary files and replaced on reboot. The following files have been identified by Microsoft as ones that cannot be restored:


    You will see temporary files for those that can not be restored on your machine after the reboot because they cannot be renamed to the original file names. The names of the temporary files will begin with "$TSMxxx.orginal_name". In addition to these files, the following have been identified on Windows 2003 SP1 that they cannot be restored if the file on the machine is exactly the same as the restored file. This is a problem on Windows 2003 SP1 only and not on Windows 2003 R2.

  kbdal.dll, kbdaze.dll, kbdazel.dll, kbdblr.dll, kbdbu.dll, kbdcr.dll, kbdcz.dll, kbdcz1.dll,
  kbdcz2.dll, kbdest.dll, kbdgkl.dll, kbdhe.dll, kbdhe220.dll, kbdhe319.dll, kbdhela2.dll, kbdhela3.dll,
  kbdhept.dll, kbdhu.dll, kbdhu1.dll, kbdkaz.dll, kbdkyr.dll, kbdlt.dll, kbdlt1.dll, kbdlv.dll, kbdlv1.dll,
  kbdmon.dll, kbdpl.dll, kbdpl1.dll, kbdro.dll, kbdru.dll, kbdru1.dll, kbdsl.dll, kbdsl1.dll, kbdtat.dll,
  kbdtuf.dll, kbdtuq.dll, kbdur.dll, kbduzb.dll, kbdycc.dll, kbdycl.dll

    On Windows Vista, in addition to the ones identified by Microsoft, locale.nls cannot be restored. These files are hard links to the files in the Windows\winsxs directory. Therefore, you will see at least two temporary files of locale.nls, two temporary files of smss.exe, and so on.

    Even though these files cannot be restored, this does not harm to your operating system. The temporary files TSM created can be deleted with the proper permissions.

  • Problem with the Windows GUI Preference Editor Communications tab

    In the Windows GUI preference editor, there is a problem with the Communications tab. When the "USEDIRCTORY YES" option is set in your dsm.opt file, you can still use the Preference editor to make changes to Named Pipe and TCP/IP values.

  • Windows GUI is unresponsive during large retrieves

    Currently there is a problem when launching a retrieve operation from the main window. It might look like the application is unresponsive, but the client is still processing information that is received from the server. The client will respond when the information has been processed.

  • Windows GUI Options File Configuration Wizard

    In the Options File Configuration Wizard domain list page in the Spanish client, the combo box where file spaces are selected is too small. However, the combo box is still usable.

  • Windows GUI local backupset restore

    If you do not select a backupset location after being prompted, you will receive the "Operation stopped by user" error message.

  • Windows GUI Preference Editor

    In the Windows GUI preference editor Diagnostic tab, the warning is not removed from the filename box when tracing is disabled and an error exists.

  • Web Client performance workaround

    Disable Java caching from the Java Control Panel to help improve performance on the Web client on the browser machine.

TSM Client Automatic Deployment known problems and limitations
    • Client installation images and temporary files are not removed after an automatic restart

      After the client deployment, the deployment manager tries to remove the self-extracting installation images and temporary files. However, if the deployment manager automatically restarts the client computer, the reboot interrupts the cleanup and the self-extracting images and temporary files are not removed. The deployment status will be "Success".

    • A client deployment requires a reschedule if the deployment process missed the set start time

      To ensure all system resources are released before the new client installation, the client deployment utilizes a two-step process:

        1. The setup script registers the deployment process with Windows Task Scheduler as a task to run at a set start time. The setup script exits and all system resources used by the backup archive client are released.
        2. At the start time, the operating system triggers the deployment process, which is independent of the client.

      However, if the start time is missed, the deployment status is "Unknown" and the ANE4252E message is logged in the setup.log file. The client deployment requires a reschedule.

    • A client deployment requires a reschedule if the extraction of the installation image hangs

      If the extraction of the installation image takes longer than 10 minutes, the deployment status is "Stopped", and the client deployment requires a reschedule.

    • The client deployment status is "Failed" with exit code 259 if the installation takes more than one hour

      If the installation of the new client takes longer than one hour, the deployment manager times out with a deployment status of "Failed" and Microsoft installer return code 259, which indicates that no data is available. Check the installBA.log for the actual installation result.

Back to Contents

Windows 32-bit client known problems and limitations (applies to all modifications of version 6.2)
  • Browsing Web Client help issue

    When browsing the Web Client help, the following error message might be logged in the dsmerror.log on the system where the TSM Client Acceptor resides:

    Error reading http request.

  • Windows XP and Windows 2003 automated system recovery (ASR)

    ASR recovery restores the system to the point of latest backup. There is no explicit support for point in time or inactive system state recovery. Point in time recovery could be accomplished by generating a backupset at the desired operating system state for later use.

    In rare occurrences, the TSM ASR restore process proceeds before the TSM Client installation has completed. This issue has only exhibited itself on Windows 2003 systems using a minimal hardware configuration. The following workaround can be used to complete the process:

      1. On the ASR floppy disk, uncomment the "pause" command after the waitforevent command in the tsmasr.cmd file:

          Change statement
          "REM pause"

      2. Save the changes to the floppy.
      3. Restart the ASR restore procedure using the modified floppy.
      4. When the pause statement is reached, the console will display "Press any key to continue...", wait 3-5 minutes for the installation of the client to finish. Alternatively, you can use the second command-line window to monitor the creation of the %SystemRoot%\temp\~tsmasr\baclient folder.
      5. Press any key to continue the ASR restore procedures.
  • Moving a directory from Windows Explorer using cut and paste can result in the old and new directories not being properly backed up or expired during a journal based backup under certain circumstances.

    A directory move operation can be done from a command prompt with the move or rename command, or from Windows Explorer using drag and drop or cut and paste.

    The TSM Journal daemon assumes that a "move directory" operation has occurred when a delete directory operation is followed immediately by a create directory operation.

    If a delete directory operation is not followed by a create directory operation (for the same directory), the delete operation is assumed to be for a single directory object and not as the result of a move operation.

    For a move operation, journal based backup must force a normal incremental backup of both directories in order to ensure that all files in the deleted directory are expired correctly, and that all files in the destination directory are backed up correctly.

    For a single directory delete operation, only the directory itself is expired on the TSM server.

    Since it is possible to perform other operations between the time a Windows Explorer directory cut operation is performed and when the follow-on paste operation is performed, the TSM Journal daemon might not correctly identify the operation as a directory "move".

  • Known problems with anti-virus software

    Some anti-virus software can incorrectly generate change notifications to the TSM journal service, causing files that have not changed to be incorrectly backed up during journal based backup.

    Development is currently working with virus protection vendors to fix these problems. If you see these problems with virus protection vendors not listed below, report the problem to your virus protection software vendor or IBM support.

    Symantec Norton Anti-Virus Corporate Edition (Nav)

    Symantec has implemented an interim fix which eliminates most incorrect change notifications generated during Nav scan processing.

    This interim fix was incorporated into Nav CE version 7.51 and must be obtained from Symantec technical support.

    The complete fix is included in Norton Anti-Virus Corporate Edition 8.0 and higher.

    Customers should refer to Knowledge Base article 4011082926 and the CRT STS number (Defect 362082, Incident 421919).

    Note that the initial interim fix still generates some incorrect notifications for attribute (read-only, archive, etc) bitmask changes, and requires a registry setting for NAV and a Journal Based Backup .ini file setting.

    Note that this fix will prevent Nav from preserving the last access timestamp on any scanned objects.

    The Journal Based Backup service must also be configured to not generate change notifications for last accessed timestamp changes and attribute bitmask changes.

    Two changes must be made to enable this fix:

      1. Set the following DWORD registry value:

              NoFileMod = 1

      This setting prevents Nav from caching and restoring timestamps and security information during scan processing.
      2. Include the following in the Based Backup .ini file (tsmjbbd.ini):


    This setting will generate change notifications for the following type of change activity:

    It will not generate notification for last access timestamp or attribute bitmask changes.

  • Restoring data with multiple TSM encryption keys

    If you need to restore a group of files that have been encrypted by TSM, with more than one encrypt key for the group, the files might not be restored. The error log will show an error in dsmerror.log:

    ANS4014E Error processing '\\spike\c$\want\dollar': unknown system error (150) encountered. Program ending.

    The restore will continue, but the file will not be restored. You need to resubmit the restore request to restore the individual file.

  • Windows 32-bit and 64-bit interoperability

    Windows 32-bit applications have a different HKEY_LOCAL_MACHINE\SOFTWARE registry tree from 64-bit applications. This means that the 32-bit and 64-bit TSM API are mutually exclusive and their passwords will be stored in different locations in the registry tree. Thus the 32-bit API will not be able to access the password entries generated by the 64-bit API.

    For example:

    The 64-bit BA client package will only install a 64-bit scheduler. But another application could be using the 32-bit API. If the scheduler and application share the same node name, then the generated passwords stored in the registry in encrypted form could become out of sync. If the application changes the password, the 32-bit portion of the registry will be updated with the new password, but the 64-bit portion of the registry will not reflect this change.

    To alleviate password synchronization issues between 32-bit and 64-bit Windows clients, use a separate node name for each client.

  • Windows image backup and restore

    The TSM client can back up a consistent snapshot of a volume, but it cannot guarantee consistency of applications which store data on multiple (different) volumes. For example, the TSM client can back up the image on drive F:, but if Application A keeps its main data files on drive F: and its log files are on drive G:, then when the TSM client restores drive F: the data files might not be in sync with whatever changes might have gone into the log files on drive G: since the image backup of drive F:.

    If an unrecoverable read failure occurs during image backup, the following message is displayed:

    ANS0322E (RC4161) no text available for this return code.

    The return code 4161 means device read error.

  • Bad Sectors on a drive

    If part of the volume resides on an area of the drive with bad sectors TSM will skip those sectors while sending image data to the server, displaying the warning message ANS2026W. In some rare cases an attempt to read data from bad sectors may lead to device read failure with image backup failing. If this is the case the possible workarounds are:

      1. If the volume is formatted (not raw) use full incremental backup instead of image backup.
      2. If the volume resides on an IDE drive, try moving the data to a SCSI drive. SCSI drives are more robust in terms of bad sector recovery.
  • On Windows XP Only

    When restoring an NTFS image over a FAT volume, or vice versa, Windows Explorer might not immediately reflect the change in volume format (NTFS or FAT). After rebooting, Windows Explorer will show the correct volume type. Note that you can see the changed type right away from the Computer Management (MMC) -> Disk Management console.

  • Preference Editor Include-Exclude limitation (Native GUI)

    In the "Include-Exclude" tab of the preference editor, file exclusion is only supported for "Incremental" backup types. File exclusion is not supported for NAS or Image. It will add the option to the options file, but the option will not be honored.

  • Open File Support for Windows XP
    • Terminal Services

      Open File Support is not supported in a Terminal Services session. This is due to a limitation within Terminal Services where a new volume is not visible to the current session unless the user logs off and logs back in again. The Web client can be used for remote OFS operations.

    • LVSA and Setup Wizard

      If the temporary installation directory (e.g., c:\tsm_images) is removed or there is no installation media present, the Setup Wizard will fail operations which require files from the installation media or temporary installation directory with the following error message:

      ANS3010E  The Logical Volume Snapshot Agent wizard operation failed.

      To bypass this error point the Setup Wizard to the correct temporary installation directory or the installation media.

      If the client is installed in a path that contains DBCS characters, the QUERY SYSTEMINFO command does not correctly display the install path in the REGISTRY section of the output.

  • Problems migrating from 32-bit to 64-bit

    The restore of system objects backed up from 32-bit Windows environments to 64-bit Windows environments (and vice versa) is not supported.

    The restore of DFS links backed up from 32-bit Windows environments to 64-bit Windows environments (and vice versa) is not supported.

    When migrating from 32-bit Windows to 64-bit Windows, it is recommended that you avoid backing up the 64-bit system object or system state data into the same file spaces containing the 32-bit system object or system state data. This precludes inadvertently restoring the 32-bit data, which is incompatible with 64-bit Windows.

    To avoid commingling the data, you can do either of the following before migrating to 64-bit Windows:

  • Connecting to server SSL port by mistake

    If a client connects to SSL port on the server but the client doesn't have SSL enabled, the client would seem to hang until the session times out on the server.

    The client doesn't have a way to tell whether server is expecting SSL or not. If you forget to enable SSL on the client, it will try to connect with regular (non-SSL) session to server's SSL port. The connection will "hang" because both client and server would wait on expected responses from each other.

    To avoid this situation, make sure you set SSL option to "yes" along with setting the TCPPort to server's SSL port.

Back to Contents

Windows 64-bit client known problems and limitations (applies to all modifications of version 6.2)
  • Windows Vista (x64) and special language characters

    Windows Vista (x64) may not correctly display certain characters in non-English settings when running command line programs (dsmc and dsmadmc). It will work correctly with the code page set to 1252. To change the code page on a command prompt, enter the command chcp 1252

  • TSM Backup-Archive Client FTP package on Windows Vista on x64

    Currently there is a problem when you extract the TSM Backup-Archive Client Windows x64 FTP package on Windows Vista. The following error might be displayed:

    "The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

    Follow these steps to install the package:

      1. Download the TSM BA Client x64 package onto a non-Windows Vista x64 machine
      2. Launch the .exe FTP package - This will expand the TSM BA Client files into a directory on the machine. The default is ("c:\tsm_images").
      3. Exit the installation by selecting "Cancel" when the "Choose Setup Language" dialog appears.
      4. Copy the expanded TSM BA Client directory to the target Windows Vista x64 machine.
      5. On the Windows Vista x64 machine, launch file "setup.exe" (or "setup."), located within that directory structure (default is "c:\tsm_images\TSM_BA_Client") to launch the installation.
      6. Follow the prompts to complete the installation.

    This issue will be addressed in a future TSM BA Client release.

Back to Contents

VMware backup known problems and limitations

VMware backup known problems and limitations in version 6.2.3 (applies to all modifications of version 6.2.3)

VMware off-host Full VM backup using vStorage APIs
  • Platform string set to "TDP VMware"

    When the Tivoli Storage Manager for Virtual Environments (TSM for VE) license file is installed on a VMware vStorage Backup server, the platform string stored on the TSM server will be set to "TDP VMware" for any nodename used on that machine since that machine is licensed for TSM for VE. This platform string can be used in the context of PVU calculations. If a nodename is being used to back up the machine with standard backup-archive client functions (for example, file-level or image backup), then this platform string should be interpreted as a backup-archive client for the purposes of PVU calculations.
  • Full VM incremental support (TSM for Virtual Environments - TDP for VMware)

    Full VM block level incremental support is provided in the Tivoli Storage Manager Backup-Archive Client version 6.2.3 level for those customers who have purchased the "Tivoli Storage Manager for Virtual Environment - Data Protection for VMware" product. Full VM incremental backup requires VMware Change Block Tracking (CBT) and is only available on virtual machines on ESX 4.0 or later host with virtual hardware level 7.

    To enable the Backup-Archive Client full VM incremental support (dsmc backup vm -mode=incremental), run the install package for "TSM for Virtual Environment - TDP for VMware". Under custom install, select the "Data Protection for VMware Enablement File" component. The "Data Protection for VMware Mount" component can also be installed on the same machine to enable the individual file restore from full VM backups. When using these features, use the Client Preference Editor to ensure backup type is set to FULLVM and VM Full type is set to use the vStorage APIs.
  • RDM Physical Compatibility Mode and Independent disks (also applies to V6.2.2)

    Backups are not supported for virtual machines that have either independent disks (either persistent or non-persistent), or that have raw device mapping (RDM) disks configured in physical compatibility mode. RDM disks configured in virtual compatibility mode are supported.
  • Client-side deduplication performance and return code=254

    VMware off-host Full VM backups with client-side deduplication enabled fails with return code=254. Error message: ANS7899E The client referenced a deduplicated extent that does not exist on the TSM server. This error can occur when a Tivoli Storage Manager server expiration or similar process is either in the process of removing a deduplicated extent or has an extent locked during the backup. A subsequent backup should succeed.

    When running heavy backup loads on the TSM server, if multiple warnings with the RC=254 or an increase backup run time is noticed when client-side deduplication is enabled, disable client-side deduplication for the VMware backup proxy node. This issue is not seen when using server-side deduplication.

  • SAN I/O failure reported on vixDiskLib_Read() as vStorage API error message: "One or more parameters supplied is invalid", API rc=16000 (also applies to V6.2.2)

    When using SAN transport, the backup or restore of a virtual machine might report the following error during a temporary SAN I/O failure:

       ANS9365E VMware vStorage API error.
             TSM function name : vddksdkRead
             TSM file          : vmvddksdk.cpp (2238)
             API return code   : 16000
             API error message : One of the parameters supplied is invalid
       ANS0361I DIAG: vmbackvddk.cpp      (3579): ANS1111I VmProcessExtent(): vddksdkRead() rc=-1, startSector=2621952, numSectorsToRead=512
       ANS1228E Sending of object 'VM_1234' failed

    When an error occurs in SAN transport path, the Virtual Disk Development Kit (VDDK) reports the invalid parameter error. When TSM tracing is turned on, the redirected VDDK trace callback will report "SAN I/O failure". This error is only seen when TSM tracing is on. To proceed, retry the backup or restore operation. If the problem persists, use the NBD(LAN) transport to work around the issue. To force the NBD transport, use the following TSM client option:


  • VMware Transports(SAN, hotadd, NBDSSL, NBD) - VMVSTORTRANSPORT option

    Use the VMVSTORTRANSPORT option with the backup VM or restore VM command to specify the transport to be used with the vStorage API for Data Protection (VADP). The transport determines how VADP accesses virtual disk data. Valid transports include any order or combination of san, hotadd, nbdssl, and nbd separated by a colon. The first transport in the list that is available in the environment will be used. NBD or network based data transfer is the LAN transport and should be available in all environments. It is not necessary to set this option. The default value is to use the VADP order which is currently defined as "san:hotadd:nbdssl:nbd". This option is passed directly to the VADP API.

    Place the VMVSTORTRANSPORT option in the client options file (dsm.opt). The following are some common examples:

    1. Current default order of transports when none is specified:
                VMVSTORTRANSPORT san:hotadd:nbdssl:nbd

    2. When the SAN path is temporary unavailable, fail the backup so as not to impact the LAN:
                VMVSTORTRANSPORT san
    3. Disable the use of hotAdd when running the backup server inside VM:
               VMVSTORTRANSPORT nbdssl:nbd
    4. Select NBD even when NBDSSL is available for better performance:
               VMVSTORTRANSPORT nbd  
  • Restore to ESX server instead of to vCenter (also applies to V6.2.2)

    Restoring a virtual machine to the ESX server, when that VM was backed up from vCenter, requires the -datacenter=ha-datacenter parameter on the restore command.

  • Virtual machine fails to start after a restore to ESX server instead of vCenter

    If after a restore to an ESX/ESXi host, the virtual machine fails to start with the following error, it means that the virtual machine did not rollback after the remove snapshot operation.

          Error: Power On virtual machine 'vmname' fails
          Reason: The parent virtual disk has been modified since the child was created.

    Using the "Edit virtual machine setting" dialog from the vSphere Client, one will find that all the VMDKs have zero size and point to file ending in 000001 ( [datastore] vmname/vmname-000001.vmdk)

    Solution: Edit the virtual machine configuration to point to the correct vmdk files. Each snapshot VMDK ([datastore] vmname/vmname-000001.vmdk) must be "Removed" by selecting the "Remove from virtual machine and delete files from disk" option. Then the real VMDK ([datastore] vmname/vmname.vmdk) can be added back.

    This problem can be avoided by restoring to a vCenter or using the hotAdd transport.

  • "Clear lazy zero" is repeated in VMware vCenter task during VM Restore

    When performing a virtual machine restore using vSphere 4.0 when using SAN transport, "Clear lazy zero" is repeated in VMware vCenter task and the performance of the restore drops. VMware, instead of zeroing a VMDK as it is created, will set the lazy zero bit on each block and will clear it at a later time. These are informational messages only. To work around the performance issue, restore to the ESX server instead of a vCenter.

  • Thin-provisioned disk (also applies to V6.2.2)

    There is a known problem in current VMware vSphere release in which a snapshot disk does not show the correct thin or thick trait based on the disk's property. As a result, a snapshot backup of a virtual machine with a thin-provisioned disk from disk properties will, upon restore, be restored with thick-provisioned disk attribute.

    See the following VMware Knowledge Base article for detailed information: 

VMware backup known problems and limitations in version 6.2.2 (applies to all modifications of version 6.2.2)
    Tivoli Storage Manager client does not display virtual machines in Virtual Center linked mode. Tivoli Storage Manager development believes that this is a VMware issue. The VMware Virtual Infrastructure (VI) API does not support the Virtual Center in linked mode. You must set up a backup proxy to connect to each vCenter server. You can connect to the Tivoli Storage Manager client only one vCenter server at a time.
VMware off-host Full VM backup using vStorage APIs
  • VMware Change Block Tracking (CBT) support for content-aware backups (also applies to V6.2.3)

    Tivoli Storage Manager Full VM backup will use VMware Change Block Tracking (CBT) support if it is available to enable content-aware (used-block only) backups. VMware CBT requires ESX 4.0 or later host (with virtual hardware 7). Tivoli Storage Manager will turn on CBT during the first backup of the virtual machine. You cannot perform Full VM backups on virtual machines that do not support CBT, for example, on a ESX 3.5 host. In this case, both used and unused areas of the disk will be backed up and an informational message will be logged to the dsmerror.log. The Backup window in the backup-archive GUI or the client command 'dsmc show vm all' will display the CBT status.

  • Scheduler service running as "Local System Account" can consume large amounts of memory (also applies to V6.2.3)

    Running the TSM scheduler as a Windows Service running as "Local System Account" can consume large amounts of memory when processing Full VM backups using vStorage APIs (for example, TSM server define schedule action=BACKUP subaction=VM when vmbackuptype=FULLVM and vmfulltype=VSTOR). When running on a backup proxy with multiple scheduler services, the memory used on a single scheduler service process can jump to 800 MB when processing 20-30 VMs. This condition is not seen on every backup attempt. When running multiple scheduler services, for example 8-10, on a single backup proxy, and more than a single process sees the increased memory usage, the performance of the entire backup and system can be effected.

    Temporary fix: Set up the TSM scheduler to run as a Windows Service running as "Administrator Account". IBM is working with VMware for a fix to run as "Local System Account".

  • Client-side deduplication performance and return code=254

    VMware off-host Full VM backups with client-side deduplication enabled fails with return code=254. Error message: ANS7899E The client referenced a deduplicated extent that does not exist on the TSM server. This error can occur when a Tivoli Storage Manager server expiration or similar process is either in the process of removing a deduplicated extent or has an extent locked during the backup. A subsequent backup should succeed.

    Fix: When running heavy backup loads on the TSM server, if a VM backup fails multiple times with RC=254 or an increase backup run time is noticed when client-side deduplication is enabled, disable client-side deduplication for the VMware backup proxy node. This issue is not seen when using server-side deduplication.

  • Incorrect level of the VMware Tools (also applies to V6.2.3)

    When a backup VM operation fails consistently with the following error in the dsmerror.log, an incorrect level of the VMware Tools may be installed inside the guest OS:

          ANS9365E VMware vStorage API error.
               TSM function name : visdkWaitForTask
               TSM file          : vmvisdk.cpp (2811)
               API return code   : 78
               API error message : Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

    It might be necessary to uninstall and reinstall the latest version of VMware Tools on the guest OS virtual machine. 

    If the problem persists, refer to the following VMware Knowledge Base (KB) article for detailed information and solution:

    Title: "Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine".

  • Long running snapshot delete (also applies to V6.2.3)

    A backup VM operation might fail if the snapshot deletion of a failed prior run requires a longer time to complete than the timeout value set by VMware vCenter. The following error might appear in dsmerror.log as a result of this timeout value that is exceeded by the vStorage API:

      ANS9365E VMware vStorage API error, API error message: "server refused connection", API return code:14009
      ANS9365E VMware vStorage API error, API error message: "Operation failed since another task is in progress"

    If this happens, no action is necessary. The snapshot delete will continue to be processed. The next backup attempt should succeed.

    See the following VMware Knowledge Base article for detailed information:

  • Change Block Tracking (CBT) needs a reset (also applies to V6.2.3)

    When a backup VM operation fails with one of the following warning messages in the dsmerror.log file, it might be necessary to reset the VMware Change Block Tracking (CBT) for the virtual machine:

       ANS9365E VMware vStorage API error.
          TSM function name : visdkQueryChangedDiskAreas
          TSM file          : vmvisdk.cpp (3592)
          API return code   : 12
          API error message : SOAP 1.1 fault: "":ServerFaultCode[no subcode]"A specified parameter was not correct. deviceKey"  

       ANS9365E VMware vStorage API error.
          TSM function name : visdkPrintSOAPError
          TSM file          : vmvisdk.cpp (885)
          API return code   : 12
          API error message : SOAP 1.1 fault: "":ServerFaultCode[no subcode]"Error caused by file /vmfs/volumes/4ade85fd-81f49624-57f5-000e0cdd0d21/winxp-32/winxp-32.vmdk"

    This can occur if the ESX server is shutdown or rebooted without first entering the maintenance mode. It might also occur when a backup is attempted through both the ESX Server and vCenter at the same time for the same VM. Change Block Tracking is needed by Tivoli Storage Manager to back up content-aware (used-block only areas of the disk). If CBT is in this failed state, the client will continue with the backup, and back up the used and unused areas of the disk.

    Fix: Run a single backup with the test flag vmbackup_cbt_reset:

      Example:  dsmc backup vm 'myvm' -testflag=vmbackup_cbt_reset.

    This testflag will require a snapshot and snapshot delete to turn off CBT, and a second snapshot to turn on CBT so it should not be set permanently as it could impact backup performance.

  • English/7bit ASCII Virtual Machine names (also applies to V6.2.3)

    There are some limitations of the VMware vStorage APIs and in Tivoli Storage Manager processing virtual machines with non-English/7bit ASCII characters in the name. Tivoli Storage Manager support for VMware backup and restore is limited to English Virtual Machine names. Names using other languages is not supported at this time.

VMware consolidated backup known problems and limitations in version 6.2 (applies to all modifications of version 6.2)
  • Performing a VMware file-level backup of Windows 2008 guest OS may can result in the following warning messages in the dsmerror.log file:

    09/06/2008 10:37:08 ANS1990W The 'G:\vcbstore\filelevel\Win2008\digits\1\' volume mreturn code is '106'.
    09/06/2008 10:37:08 QueryVolMountPoints(G:\vcbstore\filelevel\Win2008\letters\C\):
    09/06/2008 10:37:08 ANS1990W The 'G:\vcbstore\filelevel\Win2008\letters\C\' volume return code is '106'.

    Tivoli Storage Manager development believes that this is a VMware issue. After applying the fix for KB934336 on a 32-bit VCB proxy everything works as expected; the error occurs only on a 64-bit VCB proxy even after the fix. On a 64-bit VCB proxy, the Windows API FindFirstVolumeMountPoint() fails with error 5 ( access denied) only for the C: drive of the 2008 virtual machine.

    This error is reported at the backup discovery phase, but the actual backup works fine.

Back to Contents

TSM Client Configuration Wizard for Fastback Integration known problems and limitations

Known problems and limitations in version 6.2.2
  • The LVSA driver creates the tsmlvsacache directory to store internal data. This directory is not excluded from image backup.

Known problems and limitations in version 6.2 (and all modifications of version 6.2)
  • TSM FastBack V5.5.1 or later version is required

    The TSM Configuration Wizard for FastBack integration requires TSM FastBack v5.5.1 or later version.

  • TSM FastBack Viewable Storage is not supported for Client Groups

    When creating TSM FastBack Client Groups, use the selections from the server/volume panel. If you chose an entry from the Viewable Storage, you receive a FastBack warning message - FBSG10571 - recommending that this selection not be used. The TSM for FastBack integration will NOT work for any selections made from the Viewable Storage, and unpredictable results will occur if such a selection is made.

  • Unicode characters are not supported by FastBack

    TSM FastBack does not support Unicode characters, so when creating FastBack policy names, etc., be sure to avoid entering Unicode characters. TSM Client Configuration Wizard for FastBack uses the names displayed by the FastBackShell "mount dump" command, so avoid any characters which appear differently when displayed via that command versus what is entered into the TSM FastBack Manager GUI. (Some UTF-8 characters may be formatted differently by FastBack for display purposes and will not work with the TSM Client Configuration Wizard for FastBack).

  • The TSM FastBack credential file is required On the FastBack installation drive, a directory named \FastBackTSMScripts must exist and must contain the credential.txt file for the TSM for FastBack integration. The TSM Client Configuration Wizard for FastBack will create subdirectories and script files in this directory, so care must be taken not to delete files that might be needed for subsequent scheduled TSM backups

    On the FastBack installation drive, a directory named \FastBackTSMScripts must exist and contain the file credential.txt for the TSM for FastBack integration. The TSM for FastBack integration will create subdirectories and script files into this directory, so care must be taken not to delete files which may be needed for subsequent scheduled TSM backups.

  • Avoid FastBack Policy names that differ only by underscores and spaces

    The subdirectories created for script files are named as follows:

    \FastBackTSMScripts\Policy\server\volume (e.g. C:\FastBackTSMScripts\Policy_Name_1\TESTMACHINE\C)

    To avoid problems with spaces appearing in these scripts, the directory names are created by converting any spaces ' ' to underscores '_'. Hence these two Policy names "Policy with spaces" and "Policy_with_spaces" will both be stored to the same directory and overwrite each other if both are used for the TSM Client Configuration Wizard for FastBack.

  • The "Schedule Start" and "Register FastBack Client as Client Node" pages that simplify the TSM schedule startup procedure are available for the Java GUI only.

    These pages are not available if you use the wizard in the Web Client.

  • JDK Limitations for TSM Configuration Wizard for FastBack - Web Client version

    The TSM Configuration Wizard for FastBack on the Web Client requires IBM SDK 1.5 or Sun JRE 1.6. IBM SDK 1.6 is not supported.

  • Resource Bundle Error Messages displayed in the dsmerror.log when running the wizard - Web Client version only

    The following Resource Bundle Error messages might be displayed in dsmerror.log when running the Tivoli Storage Manager Configuration Wizard for FastBack from the Web Client:

    Error opening input file com/ibm/ps/uil/nls/UilInternalResources_en.class

    These errors do not affect the functioning of the Web Client wizard and can be ignored.

Back to Contents

Document information

More support for: Tivoli Storage Manager

Software version: 6.2

Operating system(s): Windows

Reference #: 1417529

Modified date: 13 March 2011