====== Errors clients ======
===== Debug / trace =====
==== VM backup VMware ====
C:\Program Files\Tivoli\TSM\baclient>
dsmc ba vm VMPRD01 -asnode=VM-DC1 -mode=iffull -verbose -traceflag=vm -tracefile=trace.log
===== Errors =====
==== SSL Error and/or VSS not working ====
VSS hang, or SSL errors
Password and SSL certificates are located into folders in : C:\ProgramData\Tivoli\TSM\baclient\\
* Stop TSM services
* Move all folders C:\ProgramData\Tivoli\TSM\baclient\
* authenticate the clients using dsmc
* start TSM services
==== backup incremental pending on Linux on Power ====
If the first incremental is success, and then incremental never ends, then try:
TCPWINDOWSIZE 64
==== Unreconized characters ====
ANS4042E Unrecognized characters during backup of data from Linux clients. Unable to backup data containing foreign characters.
ANS4042E Object name 'xxxx' contains one or more unrecognized characters and is not valid.
Cause
Performing Manual backups:
If manual backups generate the ANS4042E error, the user’s locale environment settings are not able to handle foreign characters.
Performing Scheduled backups (using scheduler service or dsmcad service)
The scheduler and dsmcad services started from the inittab may not have the proper locale environmental settings regardless of the user’s locale settings.
Resolving the problem
Correcting the problem above requires changing the locale settings for the operating system.
1. To check the current locale settings, please run the following script. The shell script exp.sh can be started via /etc/inittab to give the locale settings at start time of the Linux system. The contents of the shell script:
#! /bin/sh
exec 1>/root/exp.out 2>>/root/exp.out
export
locale
2a. If performing manual backups, change the variables LANG and LC_CTYPE to en_US:
export LANG=en_US
export LC_CTYPE=en_US
2b. If performing scheduled backups and if the scheduler is being started from the inittab a script must be used to change the locale settings.
Script for the scheduler:
Example for an /etc/inittab entry:
tsm2:345:once:/opt/tivoli/tsm/client/ba/bin/start_dsmcsched.sh > /tmp/dsmcsched.txt 2>&1
Example for the script "start_dsmcsched.sh":
#!/bin/sh
DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
DSM_DIR=/opt/tivoli/tsm/client/ba/bin/
DSM_LOG=/opt/tivoli/tsm/client/ba/bin/
LANG=en_US
LC_ALL=en_US
export DSM_CONFIG DSM_DIR DSM_LOG LANG LC_ALL
cd /opt/tivoli/tsm/client/ba/bin
dsmc sched & > /tmp/schedok.txt 2> /tmp/schederr.txt
2c. If performing scheduled backups using dsmcad and if the dsmcad is being started from the inittab a script must be used to change the locale settings.
Script for the dsmcad:
Example for an /etc/inittab entry:
tsm1:345:once:/opt/tivoli/tsm/client/ba/bin/start_dsmcad.sh > /tmp/dsmcad.txt 2>&1
Example for the script "start_dsmcad.sh":
#!/bin/sh
DSM_CONFIG=/opt/tivoli/tsm/client/ba/bin/dsm.opt
DSM_DIR=/opt/tivoli/tsm/client/ba/bin/
DSM_LOG=/opt/tivoli/tsm/client/ba/bin/
LANG=en_US
LC_ALL=en_US
export DSM_CONFIG DSM_DIR DSM_LOG LANG LC_ALL
cd /opt/tivoli/tsm/client/ba/bin
dsmcad & > /tmp/cadok.txt 2> /tmp/caderr.txt
==== Restore file server faster ====
I have had a number of customers lately call me to complain about restores of a
single directory on a large file server running for many hours without
transferring any data. In each case I have suggested they use
TESTFLAG DISABLENQR
Each time the next restore would run in minutes.
Many of you know that this simply changes the restore from the post TSM 3.1 "No
Query Restore" back to the older "Classic" restore.
==== LANGUAGE ERRORS ====
If you have this kind of message, reinstall TSM packages