IBM Tivoli Storage Manager EOS V6.1 Windows Backup-Archive Client Known Problems and Limitations

Answer

Tivoli Storage Manager Client limitations and known problems

Common Tivoli Storage Manager Client known problems and limitations
Common Windows known problems and limitations
Windows 32-bit known problems and limitations
Windows 64-bit known problems and limitations
Windows XP 64-bit known problems and limitations
VMWare consolidated backup known problems and limitations
TSM Client Configuration Wizard for Fastback Integration known problems and limitations

• Interrupt with CTRL-C

During a command line client operation, CTRL-C might result in a TSM client program exception or other unexpected behavior. To abort a command line client operation, use 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:

• Click on "Expand Entire Branch"
• Then click on "Collapse Entire Branch"
• Web Client font requirements for non-English file names
• 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.
• Browsing Web Client help

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

Error reading http request.

• Logfile 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 correct behavior. However, the log header record might be incomplete or there might not be an "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 is created and this partial log is written to the prune file.

If there is insufficient space in the file system to append an entry to the log, the TSM client continues running, but the error message is not logged.

• Some keywords have not been translated into Chinese for the BA Client:

Some keywords, such as "Snapshot", have not been translated into Chinese. This is most evident in the Backup/Archive GUI.

• If client encryption is used and you choose to stop a command line backup or archive operation when prompted for an encryption key, the entire operation will immediately end with return code (RC) 12, even if there are other files eligible for backup that do not require encryption.

• When regional settings are updated in the Java GUI preference editor, the GUI needs to be restarted in order to apply the changes.

• There are minor errors displaying ANS1036S in foreign languages:

On all platforms, in Polish, the message has an extra period on the second line and, on several platforms, the format is incorrect.

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

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 the options parameter usage are:

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 IBM Tivoli Storage Manager Administrator’s Reference.

• 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 securtiy style can be set either from:
• FilerView:


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 SnapDiff backup will be unable to perform 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.

• Windows GUI Diagnostics Information

When using the Diagnostics Window (Edit -> Java Diagnostic), the Operating System field can be reported incorrectly.
Any operating system newer than Windows Vista (for example, Windows 7, Windows Server 2008), is reported as Windows Vista.

• tsmlvsacache directory is created by LVSA driver

The LVSA driver creates tsmlvsacache directory to store internal data. This directory is not excluded from image backup.

• In certain circumstances Internet Explorer 7 fails to connect to the dsmcad. An exception is reported and the connection fails if the dsmcad is configured for COMMMetod TCPip and an IPv6 address is used for the address in Internet Explorer 7. The recommendation is to use an IPv4 address instead.

• Installation Path Limitation

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

• Single Byte character sets use 1 byte per character
• Double Byte character sets use 2 bytes per character

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

• Displaying the client GUI help on Windows Vista and Windows 2008

The Windows Help program, winhlp32.exe, does not ship with Windows Vista. Before you use the online help in the backup-archive client GUI on Windows Vista, you must first download and install the WinHlp32.exe browser from the Microsoft Download Center. See Microsoft KB Article 917607 for more information.

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

• VSS Native GUI/Web GUI

Prior to the 5.5 client, the GUI does not prevent you from selecting multiple inactive System State objects. However, you must select only the version that you want to restore. Otherwise, the results of the restore are unpredictable.

• 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 (e.g., 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 where ever your Windows directory is located). Then you need to modify the registry. IMPORTANT: The registry editor is not very forgiving of mistakes. If you are not accustomed to editing the registry, ask your NT 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:

      HKEY_LOCAL_MACHINE\
        SYSTEM\
          CurrentControlSet\
            Control\
              Nls\
                CodePage

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

        c_858.nls

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 (e.g., 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:

    HKEY_LOCAL_MACHINE\
      SYSTEM\
        CurrentControlSet\
          Control\
            Nls\
              CodePage

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:

      c_850.nls

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 on 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 in 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 legacy applications, Microsoft create 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 fail to replace the system hive of the HKEY_LOCAL_MACHINE. Use the administrator account to restore the system state instead. Backup system state using the backup operator still works. This problem does not occur for the Windows 2003 client. Backup/restore system state on Windows 2003 using the backup operator works. The problem has been reported to Microsoft.

• When running an incremental backup with a UNC file specification, omit the wildcard "*" at the end of the specification. Otherwise the root directory will not be backed up.

• Restoring from a backupset from a 3570 tape library attached to the client system is not supported.

• The Web Client applet runs as a snap-in on Microsoft Management Console when the Web Client agent is installed on Windows platforms only. The Web Client applet does not work in Microsoft Management Console for Web Client agents installed on non-Windows machines.

• When using the Web client, there are certain circumstances where the "Action Complete" dialog will be obscured from view and unselectable via the Windows taskbar, causing other windows in front of it to become unclickable until this dialog is closed. To circumvent this problem, use the Task Manager or the "alt-tab" feature of Windows to bring the "Action Complete" dialog to the foreground so it can be closed. Once this dialog is closed, the other open dialogs will become accessible.

• When using the "Preference Editor" to modify the Include-Exclude list, there are two errors that might occur when updating a statement that includes a space (for example, inclexcl c:\test dir\inclexcl.txt):
1. When you select another rule after having updated the rule with the space, the "Filename or Pattern" field will not be updated with the name of the rule with the space
2. An error message is written to the error log, similar to

09/20/2005 14:44:24 Attempt to free unknown pointer. Addr 010C0546, File \Tsm532c_g4_x32\client\winnt\DPrefsInclExclPage.cpp, Line 1492
       
This message can be ignored and will be fixed in a future release.

• 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 machine. 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 machine, allowing the scheduler service to authenticate with the server.

The above problem might occur when 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.

• If you install the V5.3.3 or higher IBM Tivoli Storage Manager API client and attempt to use the V5.3.2 or lower IBM Tivoli Storage Manager Backup-Archive client, you might receive one of the following error messages when you try to start the Tivoli Storage Manager Backup-Archive Client Scheduler service or CAD service:


Error Opening/Creating Registry Path 'SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient\Scheduler Service'
Error Opening/Creating Registry Path 'SOFTWARE\IBM\ADSM\CurrentVersion\EnterpriseMgmtClients\Services'

This is caused by the incompatibility between tsmutil1.dll from V5.3.3 and higher, and tsmutil1.dll from V5.3.2 and lower. To work around this issue, install the Version 5 Release 3, Level 3.0 (or higher) Tivoli Storage Manager Backup-Archive client with the V5.3.3 or higher API client.

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

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

• UNC names are not allowed if the local system account is set to logon

• 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 that they cannot be restored:



  Ctl3dv2.dll
  DtcSetup.exe
  NtDll.dll
  Smss.exe


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. Temporary files will start with "$TSMxxx.orginal_name". In addition to these files, the following have been identified on Windows 2003 SP1 that they can not 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 Windows\winsxs directory. Therefore, you will see at least 2 temporary files of locale.nls, 2 temporary files of smss.exe and etc.

Even though these files cannot be restored, it is no harm to your operating system. The TSM created temporary files can be deleted with the right 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 TCPIP values.

• Windows GUI appears to hang with large retrieves

Currently, there is a problem when launching the Retrieve from the main hub. It might look like the application is unresponsive, but the client is still processing information that it is received from the server and it will respond when the information has been received.

• Windows GUI Options File Configuration Wizard
  
  In the Options File Configuration Wizard domain list page (Spanish only), the combo box where file spaces are selected is too small. The combo box is usable still.


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



• Insufficient space in Javaheap


If the following messages are received from Java Virtual Machine (JVM) while running the DSM executable file:

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, issue the following should be command:
dsm -Xmx256m

• 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 occcurrences, 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 work-around 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" to "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.

• Journal-based backup:

Beginning with Version 5.4.0, the journal database format has changed.

Any pre-existing journals created by older clients will be reset the first time the 5.4.0 or higher journal daemon is started.

A full incremental backup must successfully complete after a journal is reset before the journal will be available for use by future backups.

Note that older journal databases are left intact and can be deleted.

Deleting files from a Windows Command Prompt might result in files not being expired during journal based backup.

In some cases, the Windows command interpreter uses 8.3 file names instead of long file names during delete operations. The TSM backup-archive client tries to resolve these 8.3 names to the original names backed up on the TSM server, which might require forcing a normal (non-journal based) incremental backup of the parent directory of the deleted file to ensure that it is properly expired.

Propagation of this problem can be avoided by turning off NTFS 8.3 file name creation, after which 8.3 file names will not be generated for new long file names.

To disable 8.3 file name creation, perform the following steps:

CAUTION: The following steps use the Windows regedit utility to modify the system registry. Errors in editing the registry can result in an unstable, and possibly unbootable system. Contact your system admini- strator if you are not comfortable editing the registry.

1. Start regedit.exe and locate the following registry key:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
2. Examine the "NtfsDisable8dot3NameCreation" entry. A value of 0 indicates that 8.3 name creation is enabled. A value of 1 indicates that 8.3 name creation is disabled. If the value is already 1, then close regedit since you do not need to do anything further.
3. Double-click the "NtfsDisable8dot3NameCreation" entry. This will bring up a dialog that allows you to change its value. Change the value to 1, then click "OK" to close the dialog. Close regedit.
4. Reboot the system. Note that the change does not take effect until you reboot.

Notes:
• 16-bit Windows and DOS applications will not be able to access files with long names that are created after 8.3 file name generation is disabled.
• This change affects all NTFS partitions. It does not apply to FAT or FAT32 partitions.

• 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 perfomed, the TSM Journal daemon might not correctly identify the operation as a directory "move".

• Restoring files causes the journal to record the change activity. If the restore is using the active backup copy, the change record is deleted from the journal. When restoring with a backupset, it is not possible (without querying the server) to know if the copy of the file is the active backup copy. The net result is that if the next incremental is done using the journal, these files will be backed up again. This can be avoided by performing an incremental with the -NOJOURNAL option.

• Known problems with anti-virus software

Some antivirus 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:

HKLM\Software\Intel\LANDesk\VirusProtect6\CurrentVersion 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):

[JournaledFileSystemSettings]
NotifyFilter=0x15b


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

• name changes (creations, deletions, and renames)
• size changes
• modification timestamp changes
• security (acl) changes

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 re-submit the restore request to restore the individual file.

• After upgradting from a non-Unicode TSM Client to a Unicode-enabled TSM Client (e.g., from TSM 4.1.2 to TSM 5.3.0), then if you restore files or folders containing double-byte characters mixed with single-byte characters, the names will be restored in mixed casing. This is only a display issue.

• 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 might 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 mixing the data, you can do either of the following before migrating to 64-bit Windows:

• Ask your TSM administrator to rename the existing file spaces. Once the migration is complete and you have backups of the 64-bit system object or system state data, your TSM administrator can delete the renamed file spaces. Since the 32-bit system object or system state data must not be restored to 64-bit Windows, there is little reason to retain the data.
• File spaces to rename include one or more of the following:
• SYSTEM OBJECT
• SYSTEM STATE
• SYSTEM SERVICES
• ASR
• Ask your TSM administrator to delete the existing file spaces (listed above) for your node.
• TSM Express 5.3.3 client accessing a TSM 5.4.0 server

When running a TSM Express 5.3.3 client to a TSM 5.4.0 server that was not upgraded from a TSM 5.3.7 Express server, the express interface will be displayed instead of the standard view. To get the standard view, change the CLIENTVIEW option in your dsm.opt to CLIENTVIEW=STANDARD.

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

• Windows Vista (x64) and special language characters

Windows Vista (x64) might 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.

• Windows XP 64 bit TSM Backup-Archive GUI

On Windows XP 64 bit with SP1 applied, the TSM Backup-Archive GUI (dsm.exe) will fail to launch, issuing a message "ordinal 6880 could not be located in dynamic link library mfc42u.dll". This is due to a problem with the Microsoft Foundation Class libraries shipped in SP1. Refer to Microsoft Knowledge Base article 814415 for details on this problem and instructions on how to obtain and install the fixed level of mfc42u.dll. This problem is not present in Windows 2003 Server 64 bit.

• Windows Automated System Recovery

Windows Automated System Recovery cannot be performed on 64 bit Windows due to an operating system problem in which ASR format of the system drive is attempted and fails in an infinite loop. Refer to Microsoft Knowledge Base article 817708 for details on this problem and information on how to obtain a hotfix.

• Currently there is no supported Java Runtime Environment (JRE) for 64-bit Windows so the TSM Web Client cannot be run in a 64-bit web browser. However, the Web Client can be run in a 32-bit web browser on a 64-bit Windows environment with the appropriate 32-bit JRE 1.4.1 installed.

• Known VMWare Consolidated Backup issues:
1. vcbMounter fails with virtual machine that has disk volume with software raid of type "raid5"
2. vcbMounter fails when virtual machine has a GPT type disk
3. Windows junctions and mount points within a file system cannot be accessed when mounted to the backup proxy (i.e. Sysvol junctions for a Windows domain controller)
4. vcbMounter fails when virtual machine has 2047GB virtual disk

• Performing a VMware file-level backup of Windows 2008 guest OS 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.

• TSM FastBack V5.5.1 or later version is required

The TSM Configuration Wizard for FastBack integration requires TSM FastBack v5.5.1 or a 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. When creating FastBack policy names, etc., avoid entering unicode characters. TSM Client Configuration Wizard for FastBack uses the names displayed by the FastBackShell "mount dump" command. Avoid any characters that appear differently when displayed through that command as compared to what is entered into the TSM FastBack Manager GUI. (Some UTF-8 characters might 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 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 might 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.

• English-only version

In Tivoli Storage Manager V6.1, the TSM Client Configuration Wizard for FastBack is available only in English. The messages and the online help for the wizard are also only available in English.

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