IBM Tivoli Storage Manager V5.4 HP-UX Backup-Archive Client Known Problems and Limitations

Common Tivoli Storage Manager Client 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.

• Search/Filter (Web/Java GUI)

  The Search/Filter function might appear unresponsive when searching through very large file systems. This is caused by the Java Virtual Machine (JVM) running out of memory. You should see a "java.lang.OutOfMemoryError" in the Java console.

  The Search/Filter function is not supported for Data Protection for Lotus Domino and Data Protection for WAS objects.

• Web Client Security Exception

  If you get a Security Exception error when running the Web Client in your browser due to the Web Client trying to open a TCP/IP socket to a socks server, disable the proxy server via your browser settings or Java Plugin control panel. See the "Starting a Web Client Session" section in Chapter 3 "Getting Started" of the "IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive Clients Installation and User's Guide" for more information.

• Web Client concurrent restore

  Running more than one restore or retrieve operation at the same time from the Web Client might cause the browser to hang when destination or message windows from the different restore/retrieve processes appear on the screen at the same time. If you observe such behavior, close the Web Client browser windows, stop the TSM Agent service, then try again using only one Web Client session.

• 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 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.
• 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 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 running, but the error message will not be logged.

• If client encryption is used and you choose to abort 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.

Common Unix and Linux known problems and limitations

• TSM editor in various terminal environments

  The TSM interactive-mode command line editor is designed to work in the following terminal environments:

  • xterm --- This is the default if terminal type not recognized.
  • xterm (Linux KDE)
  • aixterm
  • dtterm
  • VT-100
  • Iris ANSI
  
  Each of these terminals has a slightly different key map, so certain keys, e.g., destructive backspace, or the arrow keys, may not be supported on your workstation. If your terminal type is not supported, or you find working with the supplied editor support to be inconvenient, then add EDITOR NO to your dsm.opt file to use the native input support. Using this option will disable interactive-mode command recall.
• DBCS support

  The current TSM Client design does not allow for entering DBCS characters when running the Backup/Archive command line client in loop/interactive mode. There are two work-arounds for this:

  1. Run dsmc in batch mode
  2. Turn the Editor off by setting EDITOR NO in your dsm.sys
• Client interoperability
  • Files backed up or archived by the z/OS Unix System Services client cannot be restored or retrieved by any other TSM Unix client. Files backed up or archived by any other TSM Unix client cannot be restored or retrieved by the z/OS Unix System Services client.
  • Files backed up or archived with DES-56 encryption on Intel platforms, e.g., Linux86, cannot be restored or retrieved on non-Intel, e.g., AIX, and vice versa. AES-128 is the recommended encryption method.
• Problems with different JRE versions
  • There are several different Java Runtime Environment (JRE) versions available. Depending on the version and the operating system, there are some known problems related to JRE. See the Software Requirements section for the supported and required JRE version to be used with the TSM Java GUI for this platform.
  • Some JRE versions have problems transfering the cursor focus to the components. For example it could be that shortcuts of the menu (e.g., ALT-F to open the file menu) and Combo-boxes in a modal dialog by pressing the mouse button may not get the focus correctly. To solve that problem you need to transfer the cursor focus manually to that component by pressing the TAB key (or CTRL-TAB) several times.
• Preference Editor limitations (Java GUI)
  • The domain list in the "Backup" tab of the preferences editor does not reflect any domains excluded via the dash operator after "domain ALL_LOCAL" in the domain statement of the client options file.
  • When any option is changed in the preferences editor of the Java GUI, the domain list is rewritten to the client options file.
  • When using the preferences editor to modify the Include-Exclude list, and the selected rule contains a space (for example, /test dir/inclexcl.txt), the rule will not be correctly displayed in the "Filename or Pattern" field. To work around this problem, you can either manually update this field via the "Browse" button, or manually type in the correct path. This will be fixed in a future release.
  • If dsm.sys contains a sufficiently large number of entries for the GROUPS, USERS, VIRTUALMOUNTPOINT, DOMAIN, INCLUDE, or EXCLUDE options, the Preference Editor might end with error message "The data size for all options has exceeded the maximum transferable data size". To work around this problem, manually edit dsm.sys and remove any unnecessary entries. If entries cannot be removed, then the Preferences Editor cannot be used. This will be fixed in a future release.
  • The Preferences Editor invoked from the UNIX Backup-Archive Client Java GUI uses the DSM_CONFIG variable instead of the passed parameter "optfile".
• Java GUI and Web client limitations
  • The Web/Java GUI client will fail to restore a directory if a filespace with the same name exists on the Tivoli Storage Manager server. You might see the error message "No Objects on the server match query" or "ANS1395E The destination filespace or drive letter is unavailable. The following object is not processed: Filespace: '/'".

    For example, '/opt' is a file system backed up by Tivoli Storage Manager. After reinstalling the machine, '/opt' is a directory below file system '/'. File system '/opt' no longer exists on the Tivoli Storage Manager client machine. The file system '/' and all of its subdirectories, including directory '/opt', is backed up by Tivoli Storage Manager. At this point there are both '/' and '/opt' file spaces on the Tivoli Storage Manager server for this Tivoli Storage Manager client node. Trying to restore files out of filespace '/', directory '/opt' fails using the Web/Java GUI (dsmj) client.

    If you experience this problem, the workaround is to use the command line Tivoli Storage Manager client to restore the files. Put the file space name in curly brackets.

      Example:  
     dsmc restore "{/}opt/subdirectory/*" -subdir=yes
    

  • The maximum trace file size (tracemax) for the Java GUI preference editor is 2147483647 MB. This is a temporary workaround until the preference editor can accommodate larger numbers.
• File names containing characters with code > 127

  If you would like to back up files with names containing characters with a code > 127 please ensure that you have chosen a SBCS character set for your locale. The default code page C or the code page POSIX supports characters up to 127 only. Files whose names contain special characters will be skipped if C or POSIX is used.

  It is strongly recommended to perform a system backup by using a SBCS character set to prevent any file or directory from being skipped. This behavior for different locales is intended.

• Restore and retrieve using FOLLOWSYMBOLIC option

  If you want to restore or retrieve to a destination path that contains a symbolic link to a directory, please use "FOLLOWSYMBOLIC Yes" setting either during the operation or in your client options file (dsm.opt). This setting will allow you to restore or retrieve the original directory tree underneath the destination path. Otherwise, you will get ANS4029E error during restore or retrieve.

• Option and input files in DBCS locales

  If you create TSM client option and input files(such as dsm.opt, dsm.sys and filelists) using different SBCS locales or using DBCS locales, the TSM client may not correctly process the file names in those files. You may receive error messages ANS1228E or ANS4005E.

  Ensure that all TSM client option and input files (dsm.opt, dsm.sys, filelist, etc) are created in the same SBCS locale as the TSM client.

Common HP known problems and limitations

• VxFS sparse file restore
  When a sparse file is restored in the Veritas file system, it can occupy more disk space than it did originally at the time of backup. This is a limitation caused by the inner workings of the space allocation algorithm used by the file system.
• Raw logical volume backup does not support devices other than logical volumes, such as /dev/dsk/c0t0d1. Logical volume devices usually take the form /dev/vgXY/lvolAB.
• ACLs on Veritas filesystems (vxfs) are supported only on version 3.3 with filesystem layout 4.
• Because of the limited functionality of the dtterm application, not all function keys of the command line Clients operate as desired. The Control-Left and Control-Right combinations and the Home and End key do not work.
• The default limit of the data segment size of a process in HP-UX (11.23) is 64 MB. When backing up large file systems, the TSM Client may exceed this limit and thus run out of memory. To increase this limit the kernel needs to be modified in the following way:
  1. As root user, start "sam".
  2. Select "Kernel Configuration"
  3. Select "Configurable Parameters"
  4. Locate "maxdsize" and increase its value through the menu entry "Actions/Modify Configurable Parameter...", e.g. set it to 268435456 for a 256 MB max size of the data segment.
  5. The kernel gets rebuilt by sam after this change and the system needs to be rebooted for the new setting to take effect.
• For image backup the filesystems are umounted and re-mounted read-only in order to prohibit access during the backup. However, you may still be able to change the size of the filesystem by using a volume manager. Such operations must be avoided during image backup.
• The tape prompt option is not supported for the Web GUI.
• When doing image backup directly to tape, the RESOURCEUTILIZATION option value cannot exceed the value of the MAXNUMMP on the server for that node. If it does,the backup can fail with an Unknown System Error message.
• After installation of the "Required Patch Bundle for HP-UX 11i v2, September 2004", dsmc can hang if TCPWINDOWSIZE is set too values that are multiple of 64. To solve the problem, please upgrade to HP-UX patch level July 2005 or newer.

HP-UX (HP11) known problems and limitations

• During image backup and restore over LANFree, ctrl-c can lead to a coredump. Such operation have to be avoided during image backup or restore.
• To display the Java GUI in Traditional Chinese or Simplified Chinese you have to install additional patches for the fonts:
       HP-UX 11i
           PHSS_26975 - s700_800 11.11 Chinese-S TrueType fonts patch
           PHSS_26977 - s700_800 11.11 Chinese-T TrueType fonts patch
  
• To get the full performance for HSM you have to install a Veritas Filesystem patch. The patch names are:
       PHKL_29896 and PHCO_29897
  

  For more information and download please visit http://itrc.hp.com