ADSM.ORG - TSM Server

TSM 6 Conversion Progress / Duration

GregE — Wed, 22 May 2013 13:57:27 GMT

Solaris 10

Does the TSM 6 DB conversion process give a summary of duration without my having to monitor it and time it manually?

Unable to install ISC console in New windows OS

Hiten — Mon, 20 May 2013 09:21:55 GMT

Hi,

In our organisation we are planning to install the ISC console version 6.0.2 but its showing attached error. We have checked & installed jvm before installation but still getting error.

OS:Windows 2008 x64 bit R2

Actually we are planning to install & check the TSM version 5.5 in same os but isc console itself not getting installed.

Attached Files

log.txt (3.2 KB)

TSM v6.3 on AIX 7.1 Sequential File Pool Anomoly....

jharris — Mon, 20 May 2013 07:17:34 GMT

I have a sequential file pool 'DIR_BAK_E_F' used just for DIR_MC objects and it rapidly ran out of scratch volumes.

Upon inspection I noticed that the volumes were not reaching their maximum capacity, before being 100% full and a new file volume was created. I inspected the file system and the files appear to be created to the correct size of the device class, but query volume shows that these volumes are full with hardly no utilisation. I then moved the data from one of those FULL volumes and the process completes showing only around 12MB copied.

Any idea's why the volumes aren't storing the maximum amount of data as defined by the device class?

Some details below:
4:44:46 PM DDVTSM01 : q stg DIR_BAK_E_F
Storage Device Estimated Pct Pct High Low Next Stora-
Pool Name Class Name Capacity Util Migr Mig Mig ge Pool
Pct Pct
----------- ---------- ---------- ----- ----- ---- --- -----------
DIR_BAK_E_F DIR_MC 21 G 0.3 0.3 90 70

4:37:13 PM DDVTSM01 : q vol stgp=DIR_BAK_E_F
Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
/tsmstg/dir_mc/0000024F- DIR_BAK_E_F DIR_MC 15.0 M 100.0 Full
.BFS
/tsmstg/dir_mc/00000250- DIR_BAK_E_F DIR_MC 12.7 M 100.0 Full
.BFS
/tsmstg/dir_mc/00000251- DIR_BAK_E_F DIR_MC 20.2 M 100.0 Full
.BFS
/tsmstg/dir_mc/00000252- DIR_BAK_E_F DIR_MC 11.3 M 100.0 Full
.BFS
/tsmstg/dir_mc/00000253- DIR_BAK_E_F DIR_MC 1,024.0 M 0.1 Filling
.BFS

root@ddvtsm01 /tsmstg/dir_mc #l
total 12652120
drwxrwxr-x 2 root tsmsrvrs 4096 May 20 16:38 .
drwxrwxr-x 21 root tsmsrvrs 4096 May 10 12:14 ..
-rw------- 1 tsminst1 tsmsrvrs 1073741824 May 20 16:28 00000250.bfs
-rw------- 1 tsminst1 tsmsrvrs 1073741824 May 20 16:28 00000251.bfs
-rw------- 1 tsminst1 tsmsrvrs 1073741824 May 20 16:36 00000252.bfs
-rw------- 1 tsminst1 tsmsrvrs 1073741824 May 20 16:38 00000253.bfs
-rw------- 1 tsminst1 tsmsrvrs 85721088 May 20 16:38 00000254.bfs
-rw------- 1 tsminst1 tsmsrvrs 2097152000 May 19 22:41 dir_bak_e_d.vol

05/20/2013 16:36:50 ANR0515I Process 163 closed volume
/tsmstg/dir_mc/00000253.BFS. (SESSION: 9154, PROCESS:
163)
05/20/2013 16:36:50 ANR0986I Process 163 for MOVE DATA running in the
BACKGROUND processed 17,413 items for a total of
12,543,874 bytes with a completion state of SUCCESS at
16:36:50. (SESSION: 9154, PROCESS: 163)

4:43:11 PM DDVTSM01 : q devc dir_mc f=d
Device Class Name: DIR_MC
Device Access Strategy: Sequential
Storage Pool Count: 1
Device Type: FILE
Format: DRIVE
Est/Max Capacity (MB): 1,024.0
Mount Limit: 100
Mount Wait (min):
Mount Retention (min):
Label Prefix:
Library:
Directory: /tsmstg/dir_mc
Server Name:
Retry Period:
Retry Interval:
Shared:
High-level Address:
Minimum Capacity:
WORM: No
Drive Encryption:
Scaled Capacity:
Primary Allocation (MB):
Secondary Allocation (MB):
Compression:
Retention:
Protection:
Expiration Date:
Unit:
Logical Block Protection:
Last Update by (administrator): ADMXXXX
Last Update Date/Time: 05/20/2013 16:08:44

/etc/security/limits file, root and tsminst1 unlimited file size.
root:
fsize = -1
data = -1
stack = -1
core = -1
rss = -1
nofiles = -1

tsminst1:
fsize = -1
data = -1
stack = -1
core = -1
rss = -1
nofiles = -1

Tsm lan free backup - performance tuning tips required

anandgmenon — Fri, 17 May 2013 13:44:07 GMT

Hi Team,

We are implementing TSM LAN Free backups for few of our AIX Clients .

However we dont see much improvement in the "Backup elapsed processing time".

Please find below a snapshot of our config.

Kindly help us with a few tips to boost performance.

dsm.sys

tcpwindows 63
tcpbuff 512
txnbytel 25600
tcpnod yes
compression no
enablelanfree yes
lanfreecommmethod SharedMem

lanfreeshmport 1510

dsmsta.opt

COMMmethod TCPIP
COMMmethod SHAREDMEM
TCPPort 1500
TCPWindowsize 63
TCPNodelay YES

SHMPort 1510

Library Setup

We are using a TS3310 tape library with 2 LTO5 drives ( one drive defined as control Path ).

Both the drives are zoned to each TSM Client . Each drive is zoned via a dedicated Tape adapter.

Both the SAN Switch ports as well as the Tape drive ports are set to 8G speed instead of auto negotiation.

Present Data transfer rates

Total number of objects inspected: 204,738
Total number of objects backed up: 639
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 63
Total number of objects failed: 0
Total number of bytes inspected: 111.11 GB
Total number of bytes transferred: 18.81 GB
LanFree data bytes: 18.80 GB
Data transfer time: 209.98 sec
Network data transfer rate: 93,949.76 KB/sec
Aggregate data transfer rate: 26,228.38 KB/sec
Objects compressed by: 0%
Total data reduction ratio: 83.07%
Elapsed processing time: 00:12:32

TSM 6.2 Multiple DB backups with difference in expiration days

elaurens — Fri, 17 May 2013 08:00:48 GMT

Hello everyone,

First time posting here since I couldn't find what I'm looking for using the search tool.
Not sure if what I'm trying to do is possible w/ TSM, but it couldn't hurt to ask, right? ;)

The situation is the following; we have a lot of decentralized TSM servers and I would like to accomplish having 4 full DB backups on the decentralized server and 1 full weekly (on saturday) DB backup of every decentralized server at our main office. Since I want to automate the whole process, I make sure that TSM deletes all the (expired) DB backup files (volumes) on disk.

The following commands are part of the maintenance script running on the decentralized servers:

//Create full DB backup on disk @decentralized server and on disk @centralized server
backup db devclass=FILEDB type=FULL wait=yes
backup db devclass=OFFDB type=FULL wait=yes

//Deleting DB backup volumes
set drmdbbackupexpiredays 4
set drmfileprocess yes
move drmedia * source=dbbackup enddate=today-4 wherestate=mountable tostate=vault
move drmedia * source=dbbackup wherestate=vaultretrieve tostate=onsiteretrieve

The result of this is that I'm having the 4 full DB backups on the decentralized server, but that it's only keeping them for 4 days on my centralized server. The DB backups on the centralized server needs to be kept for a whole week (until the next backup is taken)

My question is, is it possible to set a different expiration "policy" on a db backup depending on where they are stored? Or is there another way to achieve what I'm trying to do?

Thx in advance for your answers! :)

TSM 6.3.3 AIX 7.1 ANR2981E Database backup terminated DB2 sqlcode -2033 sqlerrmc 106

jharris — Fri, 17 May 2013 07:18:28 GMT

OK,

I'm in the process of building a few TSM 6.3.3 servers on AIX 7.1.

My first instance works perfectly, but the second instance won't backup the database when dsmserv has been automatically started after a system reboot. I get the following error: ANR2981E Database backup terminated due to environment or setup issue related to file access - DB2 sqlcode -2033 sqlerrmc 106

I'm pretty sure this is just a simple file security/pathing problem, so I've tried everything I can think of regarding environment variable, file/folder ownership, deleting the tsmdbmgr.log file, reseting the dsmapipw password (multiple times) and examining the necesarry option file stanza's for any sneaky typo's...

But wait, here's the kicker... If I halt the server, login with account 'tsminst1' and make sure I'm in the instance folder /home/tsminst1/tsminst1 , I can run '/opt/tivoli/tsm/server/bin/dsmerv -q' then issue a backup db command via a dsmadmc console and it all works fine. If I then halt the server again, reboot and let the /etc/inittab run the dsmserv process, it fails.

The /etc/inittab file has the following line in it:
tsminst1:2:once:/opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1 -i /home/tsminst1/tsminst1 -q >/dev/console 2>&1

Any help would be much appreciated as I've got another two instances I need to build asap.

speeding up the maintenance script

foobar2devnull — Tue, 14 May 2013 10:28:18 GMT

Hi all,

I got my maintenance script doing its job well but it seems that with the increase in nodes my migration and replication times are becoming ridiculously long. I'd like to shorten those times but wanted some advice rather than blindly do the changes in production and risk getting burnt.

My instance is composed of two disk pools (PD01, PD02) that are copied to a copy tape pool (CT01) and then migrated to a primary tape pool (PT01). Once all this is done, I do reclamation on both tape pools. I have a library with 5 drives.

The script is run from a bash script and the important steps I take are these:

BACKUP STGPOOL PD01 CT01 WAIT=YES
BACKUP STGPOOL PD02 CT01 WAIT=YES
BACKUP STGPOOL PT01 CT01 WAIT=YES

BACKUP DB devclass=lto5 type=full wait=yes

MIGRATE STGPOOL PD01 WAIT=YES LOWMIG=0 DURATION=240
MIGRATE STGPOOL PD02 WAIT=YES LOWMIG=0 DURATION=240

EXPIRE INVENTORY SKIPDIRS=NO WAIT=YES DURATION=240 RESOURCE=8

RECLAIM STGPOOL PT01 WAIT=YES THRESHOLD=60 DURATION=300
RECLAIM STGPOOL CT01 WAIT=YES THRESHOLD=60 DURATION=300

What I'd like to do is run some jobs in parallel but I want, for example, to avoid starting a backing up of the DB before the data is moved from the disks to CT01. I suspect that playing with the "WAIT=YES/NO" will not help so how should I do it? Would creating admin scripts and calling them separately solve my problem?

Call admin script: copy
BACKUP STGPOOL PD01 CT01 WAIT=NO
BACKUP STGPOOL PD02 CT01 WAIT=YES
BACKUP STGPOOL PT01 CT01 WAIT=YES

This would start the two first process in parallel and the third would only start if the second finished.

But what happens if the first process takes longer to finish than the last two?

In short, I'm at a loss on how to shorten my maintenance script time without running the risk of overlapping maintenance jobs that should not.

Any help and pointers to documentation are very welcome :)

How to identify nodes NOT in a nodegroup

Leigh — Mon, 13 May 2013 09:02:58 GMT

Hi,
We're starting to use nodegroups, one for each type of backup, i.e. MS SQL, Windows Filesystem, DB2, etc, etc. on a v6.3 TSM Server. Does anyone have a nice method to identify nodes that are not a member of a nodegroup?

You'll notice that nodegroup is not in 'select * from nodes' (even though it is in q no * f=d), and you can't really join a select statement in something like 'select node_name from nodes where node_name not in (select node_name from nodegroup)' because of how the nodegroup table is setup.

I don't really want to have to export stuff into Excel, etc... just wondering if anyone has a nice clever way to achieve this.

Need Help Undoing A Mistake

GLMONROE — Wed, 08 May 2013 16:10:54 GMT

I'm kinda new to TSM Administration. I was looking to reduce some mount point exceeded problems, and thought it would be a good idea to Share a Device Class among everyone by selecting the check that says to share the device class in the Modify Device Class Panel. I didn't expect it to set it up as a library.

This device class is a large sequential FILE storage on DISK. Now that I have this library defined, I haven't defined any paths to this library at all yet. I realized I probably shouldn't have shared this device class. Can I delete this Library from this Device without losing all the inventory in the DB? I have a large number of volumes that have been used among many storage pools defined to this device class.

Did I just totally shoot myself in the foot, and just waiting to shoot myself in the head?

TSM version 4.2.3 Define Library path.

dthomas — Tue, 07 May 2013 16:03:49 GMT

Yes I know it's not supported stuff, but i'm stuck with that problem and need help.
We have an hold server 4.2.3 that I need to rebuild to retrieve the information on the tapes ( LTO1 and 2). I did define the library but whe I want to define the library path I always get an error "INVALID PARAMETER - SRCTYPE" and if I remove this parameter I get "ONE OR MORE PARAMETERS ARE MISSING. Does this ring a bell?

Can anyone help!
Thank you all

TSM 6.3.3 windows, recent restore gets data from primary tapepool instead of Diskpool

Fattire — Tue, 07 May 2013 15:42:57 GMT

TSM 6.3.3 on windows server 2008 R2. testing phase still. backing up a test node data at night to 1 tb diskpool, cache=yes. After morning Admin tasks, migration, copy to tapepools, etc, i try to restore a file just backed up that night, and it goes to pull the data from tape. I thought with cache=yes, it would be quicker for TSM to get the data from the Diskpool. Is there another parameter I am missing somewhere that I don't have set correctly?

I've been reading where Tivoli reccommends Cache=no( because of time taken to erase old files). we've always had it cache=yes just because of this feature(restores quicker if it can find it on Diskpool). we backup only about 70 nodes a night.

thanks for any guidence.

tsm: SFC_BKUP_SERVER>q stgpool diskpool f=d

Storage Pool Name: DISKPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 1,100 G
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 100.0
High Mig Pct: 80
Low Mig Pct: 0
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes:
Next Storage Pool: TAPEPOOL
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description: Main storage pool
Overflow Location:
Cache Migrated Files?: Yes
Collocate?:
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed:
Number of Scratch Volumes Used:
Delay Period for Volume Reuse:
more... ( to continue, 'C' to cancel)

Migration in Progress?: No
Amount Migrated (MB): 172,718.34
Elapsed Migration Time (seconds): 1,928
Reclamation in Progress?:
Last Update by (administrator): ADMIN
Last Update Date/Time: 05/07/2013 09:44:48
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?: Yes
CRC Data: No
Reclamation Type:
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Auto-copy Mode: Client
Contains Data Deduplicated by Client?: No

Script to combine tape serial number with special device name on LINUX OS.

balkark — Mon, 06 May 2013 22:09:42 GMT

Does anyone have a script that does this?
Just need to list all the /dev/tape# with the matching SN.

List Drive
ls -l /dev/IBM*

List SN.
udevadm info --attribute-walk --name /dev/IBMtape0 | grep serial_num |cut -d'"' -f2

I got a script for AIX but need one for Linux. Any help greatly appreciated.

Problems with DIRPOOL by Export Data to another TSM-Server

tasmacher — Thu, 02 May 2013 13:38:09 GMT

We just migrate from one TSM 5.5.4 infrastructure to a TSM 6.3.2 infrastructure. In the new TSM environment, there is no more DIRPOOL. Now we have the problem that some systems have written in the old TSM environment into the existing DIRPOOL. When migrating data (via "export server") then cancels the export with an error message that the DIRPOOL is not available in the new TSM environment. There is the possibility of the data DIRPOOL with the command "move data to another storage pool" in the backup pool to migrate. Our solves the problem? Or are there other problems?

Define Library

GregE — Wed, 01 May 2013 19:44:26 GMT

TSM is connected to a TS3584 library. In TSM the library is defined as "LIBRARY01."

In the actual library, it has a single partition and ALMS enabled. The partition is named "LIB01"

What, if any, issues can come from these names NOT being exactly the same? With this single partitioned library, is this a problem??

New error on TSM6.3.3 ANR3619W. How to fix

pfviv — Sun, 28 Apr 2013 14:46:40 GMT

Hi.

After upgrading my servers to TSM 6.3.3 I am getting this message in the act log.

ANR3619W The user limit for open files is below the recommended minimum value of 4096.

I have tried to search the forum an internet, but haven't find anything useful.
IBM say: User response - Set the user limit so that it is equal to or greater than the recommended minimum value.

My problem is where to set this parameter TSM or the Operating system

Could someone please help me with this.

TSM is running on RedHat 6.4 (Santiago)

Ivan
(Sorry for my terrible English)