Known issues and problems of Tivoli Storage Manager (TSM) 7.1 in UNIX and LINUX TSM Clients


IBM has released its next and new version of Tivoli Storage Manager which is IBM TSM V7.1 for their customers from 13th December 2013. This TSM V7.1 can be downloaded from Passport Advantage or FTP sites if you are a IBM customer. Nevertheless, how many new versions with new fixes/patches are released for any kind of software it still consists some bugs and issues, so does TSM V7.1. IBM has shared some of the known issues in this new TSM version 7.1. In this post we will see some of the known issues observed in new TSM Version 7.1 Backup-Archive Clients on UNIX and LINUX platforms. Go to this link for known TSM V7.1 issues in Windows clients.

Limitations and Problems in IBM TSM V7.1 on all UNIX & LINUX Platforms

1) Files that have been backed up or archived with the V7.1 Tivoli Storage Manager API cannot be restored or retrieved with a previous version API, regardless of the server level. The data must be restored or retrieved by a V7.1 level or higher API.

2) A writable log file is required for backup and restore operations. The DSMI_LOG environment variable or the dsm.sys file (on UNIX and Linux clients) or the dsm.opt file (on Windows clients) errorlogname option must be set to a path that the user of the application can write to. If the user performing the backup or restore does not have write permissions to the log file, the process will fail. The TSM API return code for this situation is 106 (Access to the specified file or directory is denied). 

3) If you back up or archive data from a Tivoli Storage Manager Version 7.1 client, you cannot restore or retrieve that data using a Tivoli Storage Manager Version 6.4 or earlier client. 

4) When trying to take journal based backup with -absolute option it shows the below error
ANS7559E The absolute option requires specifying the NoJournal option when performing a Journal Based Backup for backing up fs 

The backup works but all files are not backed up. To fix this problem, add the -nojournal option to the command.

5) When Journal Based Backup (JBB) is configured and running during TSM client upgrade, the first backup after the upgrade will be progressive incremental, i.e. it will not use the journal. Incremental backup can take more time comparing to JBB. To prevent this stop the journal daemon before upgrading the client. Restart the daemon when the upgrade is complete.

6) When you are trying to do a client node open registration with the passwordaccess generate is set in the client option file and if an invalid password is given at the first attempt, the second attempt will also fail even if you give the correct password. You have to close the session and retry the open registration again.

7) If you are using TSM client 7.1 GUI for the initial configuration, the configuration wizard may reports a protocol violation. In addition to that the Domain panel will not list the file systems to select for the domain option. You can ignore these errors and continue with the configuration. Once you successfully completes the initial configuration, you can use the preference editor to set the Domain option.

Also Read: Different types of libraries supported by IBM Spectrum Protect (TSM)

8) Most of us generally use CTRL-C frequently to abort or cancel the command, but in TSM 7.1 it will give some serious problems. pressing CTRL-C during command line client operation might result in a TSM client program exception or other unexpected behavior. You can use 'Q' key instead of CTRL-C to abort any command. Stop using CTRL-C from IBM TSM 7.1.

9) 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 to run, but the error message will not be logged.

10) When defining a client schedule in the TSM Server, you should use single quotations ('') and double quotations (''") correctly for OBJECTS & OPTIONS parameter if the file specifications contains blank spaces. For example
objects=’"c:\Users\user1\Documents\Some file.doc" "c:\Users\user5\Documents\ Another file.txt" c:\Users\user3\Documents\noblanks.txt’ 
objects=’"c:\home\proj1\Some file.doc"’
options='-preschedulecmd="c:\home\me\my files\bin\myscript" -postschedulecmd="c:\home\me\my files\bin\mypostscript" -quiet'

11) Data that has been backed up from Mac OS versions prior to Mac OS X will not have the correct file owner or permissions when restored on Mac OS X. After the restore is complete, use the "sudo chown" and "sudo chmod" commands to set them.

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

13) Files backed up or archived with DES-56 encryption on Intel platforms such as Linux86 cannot be restored or retrieved on non-Intel platforms (for example, AIX), and vice versa. AES-128 is the recommended encryption method.



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

15) When you select an item in the filelist tree of Backup window, the drop-down box for backup type will be permanently disabled. To re-enable this, exit the Backup window and reload the window. Disable Java caching from the Java Control Panel to help improve performance on the Web client on the machine running the browser. 

16) Client-side data deduplication might require additional memory during backup or archive processing. You might need to increase the system limit on the size of the data area (segment). To check current setting of the limit, run the following command
    ulimit -d

To update the limit, run the following command: 
    ulimit -d <new value>
or 
    ulimit -d unlimited

17) In AIX, If you use the memoryefficient=diskcachemethod option for full incremental backup, you might need large amounts of disk space. Ensure that large file support is enabled on the file system that is being used for the disk cache file.

18) In AIX, When running ssh localhost dsmc command, the TSM client uses the server stanza defined in the dsm.opt file in the default installation directory, /usr/tivoli/tsm/client/ba/bin64 for the 64-bit client, ignoring the environment variable DSM_CONFIG, if it is set. Ensure that the dsm.opt file in the default installation directory has the correct server stanza when you invoke dsmc with ssh.

19) In AIX, If the COMMMethod or LANFREECommmethod options are set to SHAREdmem, the AIX environment variable EXTSHM needs to be turned on to enable extended shared memory. In order to turn on EXTSHM setting, do one of the following

To make this a permanent change, add the following line to the /etc/environment file: 
EXTSHM=ON
To make the change in the immediate shell, enter: 
EXTSHM=ON
export EXTSHM
 This change is effective until you log out of this shell. 

20) In HP-UX, 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.

Also Read: Installation & Configuration of TSM Storage Agent (Lanfree Backup)

21) In HP-UX , 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.

22) In HP-UX , During image backup and restore over LANFree, pressing Ctrl-C can lead to a core dump of the client. Such operations must be avoided during image backup or restore.

23) In LINUX, When restoring to NFS-mounted file systems, remount them using the mount option "noac" to prevent NFS-related errors that are not detectable by the client. The performance can be raised for NFS by using larger values for the options rsize and wsize (for example 8192).

24) In LINUX, When restoring an image with XFS file system to another location, you might see the message appear on the screen
"ANS1066E The restore operation completed successfully, but the file system could not be remounted"  
The mount of XFS file system is not possible because by default XFS does not allow the mount of several XFS file systems with the same FS UUID simultaneously. Use the XFS mount option "nouuid" to mount XFS file systems with the same UUID or manually change FS UUID using xfs_admin utility.

25) In LINUX, If the host name shown with the hostname command is not specified in the /etc/hosts file, there will be no GUID support available. If you want to have GUID support, you must add the host name into the /etc/hosts file.

Also Read: Why is it important to use DIRMC option during backups ?

26) In LINUX X86, If you want to start the TSM scheduler using inittab, ensure that the required language environment is set. You can do this by starting a script that first sets the environment and then starts the scheduler. See also the section that handles SBCS in this file.

27) In Solaris, If the DISABLENQR YES (Classic Restore) option is set, the restore performance of the Solaris client is slower when compared to previous releases. Depending on how much load you put on the system, the restore may take up to 25% more time.

28) For image backup, the file systems are unmounted and re-mounted read-only if you use COPYSERIALIZATION=STATIC in order to prohibit access during the backup. However, you might still be able to change the size of the file system by using a volume manager for all values of copy serialization. Such operations must be avoided during image backup.




What Others are Reading Now...

0 Comment to "Known issues and problems of Tivoli Storage Manager (TSM) 7.1 in UNIX and LINUX TSM Clients"

Post a Comment