tag:blogger.com,1999:blog-18507326538821338232024-08-29T00:43:58.087+05:30Unknownnoreply@blogger.comBlogger18125tag:blogger.com,1999:blog-1850732653882133823.post-160707471341282162011-07-29T01:12:00.002+05:302011-07-30T18:38:39.900+05:30

OS Platform: AIX 6.1TSM server Version:6.2.2.30 ANR2971E Database backup/restore/rollforward terminated -DB2 sqlcode -2071 error. This error comes when libApiTSM64 library file could not be loaded which resides in /usr/tivoli/tsm/client/api/bin64 directory. Reinstall the latest version of ba client and problem should be resolved. In my case I installed 6.2.2.3 which is the latest client version

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-68777980001568073102011-07-23T00:53:00.002+05:302011-07-30T18:39:42.665+05:30

GPFS mmbackup uses dsm.opt at default location i.e. /usr/tivoli/tsm/client/ba/bin in case of AIX if file is inside bin64 then we need to create symbolic link for dsm.opt to point at default location. Or this problem could be because of a filesystem earlier mounted as NFS made local.

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-42947172374026959822011-07-21T01:30:00.004+05:302011-07-30T18:42:07.850+05:30

I came across a situation where I was asked whether LTO3 media written on LTO4 drive is readable in LTO3 drive.Answer is yes because LTO does not allow writing a different format on one media type.I have seen this in one of my customer's environment where library is using a mix of LTO3 and LTO4 drives with all LTO3 media and there has never been any issue while restoring data using LTO3 drives ,

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-41006963700280076292011-07-19T14:00:00.000+05:302011-07-19T14:00:01.669+05:30

ftp://ftp.software.ibm.com/storage/devdrvr

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-5988962298786851282011-07-19T13:41:00.004+05:302011-07-30T18:43:25.463+05:30

Tapeutil utility has been replaced by ITDT( IBM Tape Diagnostic Tool) which is a separate utility and can be downloaded from IBM fix central or ftp site. IBM tape device driver (i.e. Atape.driver) comes with AIX filesets.

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-5757947716065435702011-07-15T02:50:00.001+05:302011-07-20T00:28:00.626+05:30

Oops!! I found that the primary storage pool volumes which have been ejected from library using move media command are not returning into scratch status, these are showing as empty volumes in q vol command. To resolve the problem I ran  move media on one of the volume and that deleted the volume from storage pool and now this can be used as scratch.Command used for moving media: move media &

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-25128637734842097042011-07-14T01:13:00.000+05:302011-07-14T01:13:12.618+05:30

TSM Server Version: 6.1 OS Platform: AIX 6.1 You can move TSM DB from one location to alternate location using following method:Create new directories where you want to move DB. Make sure DB instance user is the owner of these directories. List these directories inside a file. List each directory on a single line.For  example below are the contents of file dbvol.txt /tsmdb/db001/tsmdb/db002/

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-83345962625151990652011-07-10T18:36:00.002+05:302011-07-31T23:59:05.428+05:30

Procedure same as explained in article "Upgrading tsm 6.1 to the next maintenance level"

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-61685163872491507162011-07-10T18:24:00.003+05:302011-08-01T00:02:01.730+05:30

Existing TSM version: 6.1.4.3Target TSM version: 6.2.2.30OS Platform: AIX 6.1 64 bit Prerequisites:DB2 requires IOCP to be enabled on AIX platforms. Enable this manually using "smitty iocp". If the problem persists contact a technical service representative. DB2 instance user id and password should be ready before installation /opt/tivoli/tsm must be having 2000 MB allocated For installation

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-29926417228607223752010-12-03T00:34:00.005+05:302011-08-20T00:29:11.980+05:30

TDP for exchange version:6.1.2.1BA client version:6.2.1.0TSM server version:6.1.4.2Exchange OS Plateform Version:2008 R2 body { margin: 0 0 0 0; padding:0 0 0 0 }td,div { font-family:Tahoma;font-size:8pt;vertical-align:top }body { margin: 0 0 0 0; padding:0 0 0 0 }.transcript { background-color:#d2d2d2; }.messageBlock { margin-left:4px; margin-bottom:3px }.message { margin-left:100px;

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-57539636092482947502010-11-28T10:23:00.001+05:302011-07-10T02:09:54.667+05:30

1. Query Library Data: mtlib -l /dev/lmcp0/ -qL | more 2.Query Volume Count: mtlib -l /dev/lmcp0/ -qK 3.Query Statistical Data: mtlib -l /dev/lmcp0/ -qS 4.Query Volume Inventory: mtlib -l /dev/lmcp0/ -qI 5.Query Expanded Device Information: mtlib -l /dev/lmcp0/ -qD -E 6.Query Mounted volumes: mtlib -l /dev/lmpc0/ -qM 7.Query Reserverd volumes: mtlib -l /dev/lmcp0/ -qR

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-361068054679758112010-11-28T10:15:00.000+05:302011-07-10T00:32:35.057+05:30

Initial TSM server version:6.1.3.2Target TSM server version:6.1.4.2OS Plateform version:AIX 6.1.4.0 64 bit Download tsm server code from IBM ftp site: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/AIX/6.1.4.2/Halt tsm server. Halting TSM server would automatically stop DB2 server. If after stopping TSM server db2 still keep on running ( process db2sync ) then it can

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-44885717356162616512010-11-27T23:52:00.000+05:302010-11-28T09:35:38.432+05:30

TSM ba client version:6.1.3.2 OS plateform version:Windows 2008 R2 I noticed that clients which are at level 6.1.3.2 they backup slow than those which are at 6.2.0.1. I upgraded clients to version 6.2.0.1 and found improvements in backup performance. I noticed that clients which are running on windows 2008 R2 with exchange 2010 configured and running are specially backing up slow. I am planning

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-1850732653882133823.post-65737222353102699622010-11-27T20:06:00.001+05:302011-07-14T14:40:17.499+05:30

TSM Server Version:6.1.3.2 OS Plateform Version:AIX 6.1 64 bit I recently faced that expire inventory runs very slow on tsm 6.1.3.2 and hangs on some particular node's data expiration. I noticed hanging on some nodes was random in nature. I was expecting windows 2008 system state the culprit and responsible for this mess but I found that it was hanging on some AIX nodes as

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-47574623832542610702010-11-23T03:53:00.002+05:302011-07-10T16:13:18.056+05:30

Exchange Server OS Plateform: Windows 2008 R2TDP for Exchange version: 6.1.2.1TSM ba client version: 6.2.1.0 TDP for exchange 6.1.2.1 needs ba client version 6.2.1.0 to be installed.For detailed system requirements for TDP for exchange 6.1 click on below link.http://www-01.ibm.com/support/docview.wss?&uid=swg21430691#VSSProvider Requirements Detailed Documentation available on following

Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-1850732653882133823.post-12196995344385211572010-11-22T21:01:00.001+05:302011-07-30T19:06:05.133+05:30

TSM ba client version=6.2.1.0Client OS version=Windows 2008 R2 Recently I faced this problem of tsm clients behind firewall miss their scheduled backups.I deleted  CAD and configured tsm scheduler directly to poll tsm server.This resolved the problem. Probable reason could be that when TSM server contacts tsm client behind firewall it fails to contact tsm client and hence

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-1850732653882133823.post-16850203329024863302010-11-22T20:53:00.002+05:302011-07-30T19:06:58.688+05:30

TSM Cleint Version=6.2.1.0OS version=Windows 2008 R2 ANS0106E Message index not found for message 14085 This error comes because dscenu.txt file gets corrupted.This could be because of the upgradation of client while scheduler service running.Uninstalling and reinstalling ba client can resolve the problem or the very simple fix of this problem is to copy the file dscenu.txt from other client

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-1850732653882133823.post-47645762330964504192010-11-16T20:08:00.000+05:302011-07-10T00:40:20.870+05:30

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/

Unknownnoreply@blogger.com0