IBM Tivoli Storage Manager V5.5 Windows Backup-Archive Client Warnings

Tivoli Storage Manager Client Warnings

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

• Data Encryption

  If data encryption is used, even if ENCRYPTKEY SAVE is used, you will be prompted for the encryption key password on the first backup after you upgrade from a 5.3.x or lower client to a 5.4 or 5.5 client. You should continue to use the same password you have been using before the upgrade, to avoid problems.

• Tivoli Storage Manager journal default notification buffers for 32-bit Windows

It is recommended to adjust the notification buffer sizes to the value in the range from 64 Kbytes to 4 Kbytes.
• ANS2203E Error Accessing Disk Cache.

If you see this message, the cause might be the volume used for the disk cache is not being shared. Or the share does not include write permissions. It is better for performance, if you do not use a share for the disk cache.
Use the option DISKCACHELOCATION to change its location.

• OFS and long name support.

When using the open file support feature with either VSS or LVSA, the maximum supported pathname can be exceeded during the processing of objects which normally would not exceed the maximum path length. This occurs because TSM internally adds the snapshot volume name to the path of the objects being processed, and the path becomes too long. The snapshot volume name can be up to MAX_FSNAME_LENGTH which is 1024 characters. This means the Maximum support path length for the OFS backup is in the range of 7k.

• JBB will revert to full incremental backup after upgrading to the 5.5.1 client
  
  The journal database structure has been changed in the 5.5.1 client to optimize database size. As a result, the first backup after upgrading to the 5.5.1 client will be a full incremental, even if the PreserveDbOnExit=1 option is set.

• Path Lengths Greater than 1K for JBB monitored filesystems

  The Tivoli Storage Manager Version 5.5.0 Windows client is capable of backing up and restoring files that have path lengths greater than 1 K. Previously, paths longer than 1 K were not processed by Tivoli Storage Manager. A failure would be logged in the dsmerror.log and the Tivoli Storage Manager server activity log. That failure would be the following message:

  ANS14031E Name exceeds an internal Tivoli Storage Manager limit.

  An error would also be logged in the jbberror.log file stating:

  dbUpdEntry(): Insert(): errno = 22, "Invalid argument" jnlDbCntrl(): Error updating the journal for fs 'M:', dbUpdEntry() rc = -1, last error = 22 handleDbResultCode(): db access error -1 returned from db method 'dbUpdEntry'. handleDbResultCode(): Database error on journal db file 'D:\jbb1\tsmM__.jdb', journal will be restarted.

  For JBB to manage files with paths greater than 1K, a modification to tsmjbbd.ini is necessary. This is the procedure to follow if any file space JBB is monitoring has a path greater than 1 K. Follow this procedure only if it is absolutely necessary to have JBB manage these long paths. IBM has seen poor performance with JBB and long file paths, and is working on a fix.

  1. Stop the tsmjbbd service.
  Control panel->Admistrative Tools->Services->TSM Journal Service
  
  2. Edit the tsmjbbd.ini file, which is located in the tsm install directory.
  
  3. Add "dbkeysize=8448" just after the [JournalSettings] stanza.
  [JournalSettings] dbkeysize=8448
  
  4. Restart the tsmjbbd service.
  Control panel->Admistrative Tools->Services->TSM Journal Service.