IBM Tivoli Storage Manager V5.5 Windows Backup-Archive Client Known Problems and Limitations

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.

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"

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

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.

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

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

ANS1676W: You are doing an authoritative cluster database restore. The process may seem to hang before and after the file is restored. This is because it may need to start the cluster service if it is not up and take all the resources offline. After the cluster database is restored, the cluster service will be restarted for changes to be in effect. The cluster service on all other nodes also have been shutdown. They will be restarted. This may take a few minutes.

Explanation: The restore will seem to be paused at time because before the restore, Tivoli Storage Manager ensures the cluster service is up on the restoring node and all the resources are taken offline. After the cluster database is restored, the cluster service on the restoring node is in a paused state. The cluster service on other nodes were shutdown. All services need to be retarted. If some of the services cannot be started automatically, you can try to restart them.

System action: Processing continues.

User response: No action.

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

• 'Backup-Archive GUI' is now 'Backup-Archive GUI.'
• 'Backup-Archive Command Line' is now 'Backup-Archive Command Line.'
• 'Administrative Command Line' is now 'Administrative Command Line.'

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

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.

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.

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.

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

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, specifically Ypogegrammeni and Prosgegrammeni diacritic marks, will always be backed up by the 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 charcters 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.

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.

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.

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.

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.

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

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM. RC = 13.

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

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.

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

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.

The journal database format changed beginning with the 5.4.0 client

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.

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

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

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

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

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.

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.

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.

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.

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.

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.

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

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:

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

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.

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

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

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.

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