Trying to understand my TSM system

tondox · Apr 19, 2012

Hi. I'm new of this forum, actually this is my first thread.
I am a low-experienced System Administrator on Linux platform.
My English is poor, so I apologize in advance for any wrong way of expressing myself.
Recently I have been put in charge of administer an archiving/backupping system based on TSM 5.3. I'm trying to understand how everything works, but, to be honest, I'm a little bit confused.

What I know about my system:

I have two machines, one works only as dsm client and the other one only as dsm server. Both are connected to a SAN, which is a shared filesystem mounted on /root_data. This is the Archive space. Machines are also connected to a TapeLibrary (IBM 3584) where to migrate and/or backup data.

How I start the System (as by procedure I've inherited):

first of all I execute command “dsmmigfs start” on the two machines, and wait for these processes to start: dsmracalld, dsmmonitord, dsmscoutd, dsmrootd. Actually there is also a “dsmwatchd nodetach” always running.

Then I start dsm-server by command:

Code:

# dsmserv.rc start

and wait for process running:

Code:

# ps -ef | grep dsm
root     2302	1	1 09:21 	pts/1	00:00:00 ./dsmserv QUIET
root     2314 2302  	0 09:21 	pts/1	00:00:00 ./dsmserv QUIET
root     2315 2314  	0 09:21 	pts/1	00:00:00 ./dsmserv QUIET
root     2316 2314  	0 09:21 	pts/1	00:00:00 ./dsmserv QUIET

so I’ll get some TCP port to LISTEN (this is dsm-server):

Code:

# netstat -puntav | grep LISTEN | grep dsm
tcp        0      0 0.0.0.0:1510	0.0.0.0:*	LISTEN      2302/dsmserv
tcp        0      0 0.0.0.0:1003	0.0.0.0:*	LISTEN      20754/dsmrootd
tcp        0      0 0.0.0.0:1580	0.0.0.0:*	LISTEN      2302/dsmserv
tcp        0      0 0.0.0.0:818		0.0.0.0:*	LISTEN      20567/dsmrecalld
tcp        0      0 0.0.0.0:1500	0.0.0.0:*	LISTEN      2302/dsmserv

Then I start dsm-client:

Code:

# /etc/init.d/dsmcad start
# /etc/init.d/dsmsched start
# ..../tsm/client/hsm/bin/hsmagent

And wait for processes to run:

Code:

# ps -ef | grep dsm
root	2178 	1  	0 09:25 ? 	 ..../tsm/client/ba/bin/dsmcad -RunAsService
root	2179 2178  	0 09:25 ? 	 ..../tsm/client/ba/bin/dsmcad -RunAsService
root	2180 2179  	0 09:25 ? 	 ..../tsm/client/ba/bin/dsmcad -RunAsService
root	2181 2179  	0 09:25 ? 	 ..../tsm/client/ba/bin/dsmcad -RunAsService
root	2279 	1  	0 09:25 pts/3 ..../tsm/client/ba/bin/dsmc sch -RunAsService
root	2285 2279  	0 09:25 pts/3 ..../tsm/client/ba/bin/dsmc sch -RunAsService
root	2286 2285  	0 09:25 pts/3 ..../tsm/client/ba/bin/dsmc sch -RunAsService

even here I have some TCP port listening:

Code:

# netstat -puntav | grep LISTEN | grep dsm
tcp        0      0 0.0.0.0:898		0.0.0.0:* LISTEN	8353/dsmrootd
tcp        0      0 0.0.0.0:1581	0.0.0.0:* LISTEN	2178/dsmcad
tcp        0      0 0.0.0.0:36028	0.0.0.0:* LISTEN	2178/dsmcad
tcp        0      0 0.0.0.0:1501	0.0.0.0:* LISTEN	2279/dsmc
tcp        0      0 0.0.0.0:734		0.0.0.0:* LISTEN	7763/dsmrecalld

This is the dsm.opt on dsm-client:

Code:

SErvername   	TSM_QUI
tapeprompt     	no
followsymbolic 	yes
replace        		prompt
subdir         		yes
optionformat   	standard
restoremigstate 	no
domain         		/
domain         		/root_data
domain         		/TSM_LOG

This is my dsm.sys on dsm-client:

Code:

candidatesinterval 1        
checkfororphans    yes      
checkthresholds    5 
kernelmessages     yes  
maxcandprocs       5 
maxmigrators       3
maxrecalldaemons   3
maxreconcileproc   3
maxthresholdproc   1
migfileexpiration  3
minmigfilesize     10000
minrecalldaemons   3
reconcileinterval  24
SErvername  TSM_QUI
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   IP-SERVER
   TCPclientaddress   IP-CLIENT
   schedmode          prompted
   compression        no
   memoryefficientbackup yes
   tcpwindowsize      64
   tcpbuffsize        32
   tcpnodelay         yes
   largecommbuffers   no
   passwordaccess     generate
   nodename           dsmclient
   httpport           1581
   tcpclientport      1501
   schedlogname       ..../tsm/client/ba/log/dsmsched.log
   errorlogname       ..../tsm/client/ba/log/dsmerror.log
   inclexcl           ..../tsm/client/ba/bin/inclexcl.list
   * dirmc              mcdir
   schedlogretention  8 D
   errorlogretention  8 D
   queryschedperiod   1
   changingretries    3
   commrestartdur     5
   commrestartinterv  15
   retryperiod        5
   maxcmdretries      4

The inclexcl.list on dsm-client:

Code:

include /.../*                 migbck
include /.../*.*               migbck

exclude /TSM_DB/*.*
exclude /TSM_DB/*
exclude /TSM_LOG/*.*
exclude /TSM_LOG/*

include /TSM_LOG/tsm_config/*  migbck
include /root_data/*.* migbck
include /root_data/*   migbck

exclude /root_tmp_data/*.*
exclude /root_tmp_data/*

exclude /root_data/bck/*
exclude /root_data/bck/*.*

include /root_data/mig/.../*.* mig
include /root_data/mig/.../*   mig

exclude.backup /root_data/mig/.../*.*
exclude.backup /root_data/mig/.../*

exclude.backup /root_data/mds/.../*.*
exclude.backup /root_data/mds/.../*

include /root_data/migbck/.../*.* migbck
include /root_data/migbck/.../* migbck

exclude.spacemgmt /root_data/bck/.../*.*
exclude.spacemgmt /root_data/bck/.../*
include.backup /root_data/bck/.../*.* bck
include.backup /root_data/bck/.../*  bck

exclude /.../*.log      migbck
exclude /opt/tivoli/tsm/client/ba/log/* migbck

This is the output of dsmdf command on dsm-client (on the server output is empty):

Code:

# dsmdf
IBM Tivoli Storage Manager
Command Line Space Management Client Interface
  Client Version 5, Release 3, Level 4.0
  Client date/time: 04/11/12   09:31:32
(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

HSM		FS	Mgrtd	Pmgrtd	Mgrtd	Pmgrtd	Unused	Free
Filesystem	State	Size	Size	Files	Files   Inodes	Size

/root_data	a	102.79T	7680K	1403236 15	16.62M	268.18G

My schedules:

Code:

TSM_QUI>query event * * begind=today begint=00:00:00 endd=today endt=23:59:59
04/11/12   19:00:00  BACKUP_GIORNALIERO_ROOT_DATA	DSMCLIENT	Future
04/11/12   19:00:00  BACKUP_GIORNALIERO_ROOT_DATA	DSMSERVER	Future
04/11/12   23:30:00  STARTAUTOMIG			DSMCLIENT	Future
04/11/12   23:30:00  STARTAUTOMIG			DSMSERVER	Future

Since I have dsm-client running just on one machine, is it normal to have those schedules duplicated? I think I should remove di DSMSERVER ones. Do you agree? Also… is it normal dsm-client processes are running just on one machine? Or it should be running on both?

The /root_data is used for 70% and every days dsmautomig hangs, so I restart everything and percentage goes down to 64%.

Please help me to make a good tuning!

If I forgot some important information, just tell me.

drivechip · Apr 19, 2012

Since I have dsm-client running just on one machine, is it normal to have those schedules duplicated? I think I should remove di DSMSERVER ones. Do you agree? Also… is it normal dsm-client processes are running just on one machine? Or it should be running on both?

This are two different nodes. I guess DSMServer is backup for TSM server itself.

The /root_data is used for 70% and every days dsmautomig hangs, so I restart everything and percentage goes down to 64%.

Please help me to make a good tuning!

If I forgot some important information, just tell me.

What does STARTAUTOMIG (q sched f=d)? Do you use HSM?

tondox · Apr 19, 2012

This are two different nodes. I guess DSMServer is backup for TSM server itself.

May you help me to verify whether "DSMServer is backup for TSM server itself" ?!

Is this useful?:

Code:

TSM_QUI>q node
DSMCLIENT                       Linux86      PD_MPFA                    <1          1,654       No
DSMCLIENT_LOCAL                 Linux86      PD_MPFA                 1,263          1,281       No
DSMSERVER                       Linux86      PD_MPFA                    <1          1,654       No
DSMSERVER_LOCAL                 Linux86      PD_MPFA                    <1          1,633       No

Code:

TSM_QUI>q node DSMCLIENT f=d
                     Node Name: DSMCLIENT
                      Platform: Linux86
               Client OS Level: xxx
                Client Version: Version 5, Release 3, Level 4.0
            Policy Domain Name: PD_MPFA
         Last Access Date/Time: 04/19/12   13:24:26
        Days Since Last Access: <1
        Password Set Date/Time: 10/09/07   09:16:10
       Days Since Password Set: 1,654
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact:
                   Compression: Client
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: No
        Registration Date/Time: 10/09/07   09:16:10
     Registering Administrator: PIPPO
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 36.94 M
       Bytes Sent Last Session: 89.83 M
      Duration of Last Session: 0.01
   Pct. Idle Wait Last Session: 59,227,066.67
  Pct. Comm. Wait Last Session: 36,483.33
  Pct. Media Wait Last Session: 302,616.67
                     Optionset:
                           URL: http://dsmclient:1581
                     Node Type: Client
    Password Expiration Period:
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 6
        Auto Filespace Rename : No
             Validate Protocol: No
                   TCP/IP Name: dsmclient
                TCP/IP Address: IP-CLIENT
            Globally Unique ID: xxx
         Transaction Group Max: 0
               Data Write Path: ANY
                Data Read Path: ANY
            Session Initiation: ClientOrServer
            High-level Address:
             Low-level Address:
        Collocation Group Name:
              Proxynode Target:
               Proxynode Agent: DSMSERVER

Code:

TSM_QUI>q node DSMSERVER f=d
                     Node Name: DSMSERVER
                      Platform: Linux86
               Client OS Level: xxx
                Client Version: Version 5, Release 3, Level 4.0
            Policy Domain Name: PD_MPFA
         Last Access Date/Time: 04/19/12   08:20:32
        Days Since Last Access: <1
        Password Set Date/Time: 10/09/07   09:17:49
       Days Since Password Set: 1,654
         Invalid Sign-on Count: 0
                       Locked?: No
                       Contact:
                   Compression: Client
       Archive Delete Allowed?: Yes
        Backup Delete Allowed?: No
        Registration Date/Time: 10/09/07   09:17:49
     Registering Administrator: PIPPO
Last Communication Method Used: Tcp/Ip
   Bytes Received Last Session: 605.46 M
       Bytes Sent Last Session: 87.93 M
      Duration of Last Session: 1,745.71
   Pct. Idle Wait Last Session: 0.00
  Pct. Comm. Wait Last Session: 0.00
  Pct. Media Wait Last Session: 0.00
                     Optionset:
                           URL: http://dsmserver:1581
                     Node Type: Client
    Password Expiration Period:
             Keep Mount Point?: No
  Maximum Mount Points Allowed: 6
        Auto Filespace Rename : No
             Validate Protocol: No
                   TCP/IP Name: dsmserver
                TCP/IP Address: IP-SERVER
            Globally Unique ID: xxx
         Transaction Group Max: 0
               Data Write Path: ANY
                Data Read Path: ANY
            Session Initiation: ClientOrServer
            High-level Address:
             Low-level Address:
        Collocation Group Name:
              Proxynode Target: DSMCLIENT
               Proxynode Agent:

Code:

# dsmmigfs q -detail /root_data
IBM Tivoli Storage Manager
Command Line Space Management Client Interface
  Client Version 5, Release 3, Level 4.0
  Client date/time: 04/19/12   13:40:28
(c) Copyright by IBM Corporation and other(s) 1990, 2006. All Rights Reserved.

File System Name:       /root_data
High Threshold:         65
Low Threshold:          61
Premig Percentage:      1
Age Factor:             2
Size Factor:            1
Quota:                  999999999
Stub Size:              262144
Server Name:            TSM_QUI
Max Candidates:         500000
Min Partial Rec Size:   0
Min Stream File Size:   0
MinMigFileSize:         0
Preferred Node:         dsmclient          Node ID: 1
Owner Node:             dsmclient          Node ID: 1
Source Nodes:           dsmserver

What does STARTAUTOMIG (q sched f=d)? Do you use HSM?

Code:

TSM_QUI>q sched f=d
            Policy Domain Name: PD_MPFA
                 Schedule Name: BACKUP_GIORNALIERO_ROOT_DATA
                   Description:
                        Action: Incremental
                       Options:
                       Objects:
                      Priority: 5
               Start Date/Time: 10/09/07   19:00:00
                      Duration: 1 Hour(s)
                Schedule Style: Classic
                        Period: 1 Day(s)
                   Day of Week: Any
                         Month:
                  Day of Month:
                 Week of Month:
                    Expiration:
Last Update by (administrator): PIPPO
         Last Update Date/Time: 09/29/09   14:58:52
              Managing profile:

            Policy Domain Name: PD_MPFA
                 Schedule Name: STARTAUTOMIG
                   Description: avvia il processo di migrazione
                        Action: Command
                       Options:
                       Objects: /root/script/startAutomig
                      Priority: 5
               Start Date/Time: 11/11/07   23:30:00
                      Duration: 1 Hour(s)
                Schedule Style: Classic
                        Period: 1 Day(s)
                   Day of Week: Any
                         Month:
                  Day of Month:
                 Week of Month:
                    Expiration:
Last Update by (administrator): PIPPO
         Last Update Date/Time: 09/30/09   14:20:14
              Managing profile:

tondox · Apr 19, 2012

Yes, I use HSM (I guess):

Code:

# ps -ef | grep hsm
root      1769     1  0 Apr13 ?        00:00:40 /opt/tivoli/tsm/client/hsm/bin/dsmwatchd nodetach
root      1779  1769  0 Apr13 ?        00:00:00 /opt/tivoli/tsm/client/hsm/bin/dsmwatchd nodetach
root      1780  1779  0 Apr13 ?        00:00:00 /opt/tivoli/tsm/client/hsm/bin/dsmwatchd nodetach
root      8532     1  0 Apr18 ?        00:00:00 /opt/tivoli/tsm/client/hsm/bin/hsmagent
root      8533  8532  0 Apr18 ?        00:00:00 /opt/tivoli/tsm/client/hsm/bin/hsmagent
root      8534  8533  0 Apr18 ?        00:00:00 /opt/tivoli/tsm/client/hsm/bin/hsmagent

drivechip · Apr 20, 2012

OK, can you determine with your migration hangs everyday? Please have a look into the logs of the client.

tondox · Apr 20, 2012

drivechip said:
OK, can you determine with your migration hangs everyday? Please have a look into the logs of the client.

Ok, I'll give a look into my logs.

May you please explain me what HSM exactly is and what exactly does.

Also I'd like to understand something about the inclexcl.list.
What is the difference between these two lines?:

Code:

exclude /TSM_LOG/*.*
exclude /TSM_LOG/*

What is the difference between "exclude", "exclude.spacemgmt" and "exclude.backup"?
What does it mean three consecutive dots (/.../) in a path?

Do you think that lines in my inclexcl.list are in a reasonable order?

drivechip · Apr 20, 2012

tondox said:
May you please explain me what HSM exactly is and what exactly does.

The content of the link is old but the basic functionality is still the same: http://tsm-symposium.oucs.ox.ac.uk/2003/papers/Christian.pdf
Or the product description http://www-01.ibm.com/software/tivoli/products/storage-mgr-space/

tondox said:
Also I'd like to understand something about the inclexcl.list.
What is the difference between these two lines?:

Code:

exclude /TSM_LOG/*.* exclude /TSM_LOG/*

I think one line is to exclude the directory content itself and the other to exclude all subdirectories.

tondox said:
What is the difference between "exclude", "exclude.spacemgmt" and "exclude.backup"?

exclude is for all types. .spacemgmt only for hsm and .backup only for backups.

tondox said:
What does it mean three consecutive dots (/.../) in a path?

Wildchar

tondox said:
Do you think that lines in my inclexcl.list are in a reasonable order?

I do not know TSM on linux very well. On windows the excludes are executed from the buttom to the top of the file.

tondox · May 29, 2012

Hi to all!

I think problem on migration stems from problem on backup, since files are not migrated if they are not backupped first. If this is right, I have to troubleshoot the backup first of all.

This log has some information which is not completely clear to me:

Code:

ANR2121W ATTENTION: More than 2 MB of the database has changed and the last database backup was more than 24 hours ago. Use the BACKUP DB command to provide for database
recovery.
ANR0482W Session 6 for node DSMCLIENT (Linux86) terminated - idle for more than 60 minutes.
ANR2121W ATTENTION: More than 2 MB of the database has changed and the last database backup was more than 24 hours ago. Use the BACKUP DB command to provide for database
recovery.
ANR2750I Starting scheduled command BA_DEVCONF ( run BA_DEVCONF ).
ANR2017I Administrator PIPPO issued command: RUN BA_DEVCONF
ANR2017I Administrator PIPPO issued command: BACKUP DEVCONFIG
ANR2394I BACKUP DEVCONFIG: Server device configuration information was written to all device configuration files.
ANR1462I RUN: Command script BA_DEVCONF completed successfully.
ANR2753I (BA_DEVCONF):ANR2394I BACKUP DEVCONFIG: Server device
ANR2753I (BA_DEVCONF):configuration information was written to all
ANR2753I (BA_DEVCONF):device configuration files.
ANR2753I (BA_DEVCONF):ANR1462I RUN: Command script BA_DEVCONF
ANR2753I (BA_DEVCONF):completed successfully.
ANR2751I Scheduled command BA_DEVCONF completed successfully.
ANR2750I Starting scheduled command BA_VOLHIST ( run BA_VOLHIST ).
ANR2017I Administrator PIPPO issued command: RUN BA_VOLHIST
ANR2017I Administrator PIPPO issued command: BACKUP VOLHISTORY
ANR2463I BACKUP VOLHISTORY: Server sequential volume history information was written to all configured history files.
ANR1462I RUN: Command script BA_VOLHIST completed successfully.
ANR2753I (BA_VOLHIST):ANR2463I BACKUP VOLHISTORY: Server sequential
ANR2753I (BA_VOLHIST):volume history information was written to all
ANR2753I (BA_VOLHIST):configured history files.
ANR2753I (BA_VOLHIST):ANR1462I RUN: Command script BA_VOLHIST
ANR2753I (BA_VOLHIST):completed successfully.
ANR2751I Scheduled command BA_VOLHIST completed successfully.
ANR2750I Starting scheduled command COPIA_DB ( run COPIA_DB ).
ANR2017I Administrator PIPPO issued command: RUN COPIA_DB
ANR2017I Administrator PIPPO issued command: EXPIRE INVENTORY wait=yes
ANR0984I Process 2 for EXPIRE INVENTORY started in the FOREGROUND at 11:00:28 AM.
ANR0811I Inventory client file expiration started as process 2.
ANR2753I (COPIA_DB):ANR0984I Process 2 for EXPIRE INVENTORY started
ANR2753I (COPIA_DB):in the FOREGROUND at 11:00:28 AM.
ANR2753I (COPIA_DB):ANR0811I Inventory client file expiration
ANR2753I (COPIA_DB):started as process 2.
ANR4391I Expiration processing node DSMCLIENT, filespace /root_data, fsId 1, domain PD_MPFA, and management class MIGBCK - for BACKUP type files.
ANR4391I Expiration processing node DSMCLIENT, filespace /, fsId 2, domain PD_MPFA, and management class MIGBCK - for BACKUP type files.
ANR4391I Expiration processing node DSMSERVER_LOCAL, filespace /, fsId 2, domain PD_MPFA, and management class MIGBCK - for BACKUP type files.
ANR2369I Database backup volume and recovery plan file expiration starting under process 2.
ANR2753I (COPIA_DB):ANR2369I Database backup volume and recovery
ANR2753I (COPIA_DB):plan file expiration starting under process 2.
ANR0812I Inventory file expiration process 2 completed: examined 383 objects, deleting 78 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0
errors were encountered.
ANR2753I (COPIA_DB):ANR0812I Inventory file expiration process 2
ANR0386I The BUFPoolsize has been changed to 32816.
ANR2753I (COPIA_DB):completed: examined 383 objects, deleting 78
ANR2753I (COPIA_DB):backup objects, 0 archive objects, 0 DB backup
ANR2753I (COPIA_DB):volumes, and 0 recovery plan files. 0 errors
ANR2753I (COPIA_DB):were encountered.
ANR0987I Process 2 for EXPIRE INVENTORY running in the FOREGROUND processed 78 items with a completion state of SUCCESS at 11:00:28 AM.
ANR2753I (COPIA_DB):ANR0987I Process 2 for EXPIRE INVENTORY running
ANR2017I Administrator PIPPO issued command: BACKUP DB dev=LTO type=full wait=yes
ANR2753I (COPIA_DB):in the FOREGROUND processed 78 items with a
ANR2753I (COPIA_DB):completion state of SUCCESS at 11:00:28 AM.
ANR0984I Process 3 for DATABASE BACKUP started in the FOREGROUND at 11:00:29 AM.
ANR2753I (COPIA_DB):ANR0984I Process 3 for DATABASE BACKUP started
ANR2280I Full database backup started as process 3.
ANR2753I (COPIA_DB):in the FOREGROUND at 11:00:29 AM.
ANR2753I (COPIA_DB):ANR2280I Full database backup started as process
ANR2753I (COPIA_DB):3.
ANR8337I LTO volume A00458L2 mounted in drive DRV0 (/dev/IBMtape0).
ANR0513I Process 3 opened output volume A00458L2.
ANR1360I Output volume A00458L2 opened (sequence number 1).
ANR4554I Backed up 72448 of 822336 database pages.
ANR2753I (COPIA_DB):ANR4554I Backed up 72448 of 822336 database
ANR2753I (COPIA_DB):pages.
ANR4554I Backed up 483584 of 822336 database pages.
ANR2753I (COPIA_DB):ANR4554I Backed up 483584 of 822336 database
ANR2753I (COPIA_DB):pages.
ANR1361I Output volume A00458L2 closed.
ANR0515I Process 3 closed volume A00458L2.
ANR4550I Full database backup (process 3) complete, 822336 pages copied.
ANR2753I (COPIA_DB):ANR4550I Full database backup (process 3)
ANR2753I (COPIA_DB):complete, 822336 pages copied.
ANR0985I Process 3 for DATABASE BACKUP running in the FOREGROUND completed with completion state SUCCESS at 11:02:13 AM.
ANR2753I (COPIA_DB):ANR0985I Process 3 for DATABASE BACKUP running
ANR2753I (COPIA_DB):in the FOREGROUND completed with completion
ANR2017I Administrator PIPPO issued command: DELETE VOLHISTORY todate=today-1 type=dbb
ANR2753I (COPIA_DB):state SUCCESS at 11:02:13 AM.
ANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.
ANR2017I Administrator PIPPO issued command: DELETE VOLHISTORY todate=today-30 type=all
ANR2753I (COPIA_DB):ANR2467I DELETE VOLHISTORY: 1 sequential volume
ANR2753I (COPIA_DB):history entries were successfully deleted.
ANR2467I DELETE VOLHISTORY: 1 sequential volume history entries were successfully deleted.
ANR2753I (COPIA_DB):ANR2467I DELETE VOLHISTORY: 1 sequential volume
ANR1462I RUN: Command script COPIA_DB completed successfully.
ANR2753I (COPIA_DB):history entries were successfully deleted.
ANR2753I (COPIA_DB):ANR1462I RUN: Command script COPIA_DB completed
ANR2753I (COPIA_DB):successfully.
ANR2751I Scheduled command COPIA_DB completed successfully.

Someone may help me, please, to understand what's going on looking at this log?!

My backup is done on a scheduled base. How can I start it manually from the dsmadm console prompt? (Or dsmc console prompt - I didn't catch the difference between the two consoles).

drivechip · May 29, 2012

tondox said:
Hi to all!

My backup is done on a scheduled base. How can I start it manually from the dsmadm console prompt? (Or dsmc console prompt - I didn't catch the difference between the two consoles).

Code:

 backup db t=f d=<device class>

tondox · May 31, 2012

My device class is LTO:

Code:

TSM_QUI>q stg f=d

               Storage Pool Name: COPYPOOL
               Storage Pool Type: Copy
               Device Class Name: LTO
              Estimated Capacity: 35,500 G
              Space Trigger Util:
                        Pct Util: 7.5
                        Pct Migr:
                     Pct Logical: 99.8
                    High Mig Pct:
                     Low Mig Pct:
                 Migration Delay:
              Migration Continue:
             Migration Processes:
           Reclamation Processes: 1
               Next Storage Pool:
            Reclaim Storage Pool:
          Maximum Size Threshold:
                          Access: Read/Write
                     Description: pool di doppia copia
               Overflow Location:
           Cache Migrated Files?:
                      Collocate?: No
           Reclamation Threshold: 60
       Offsite Reclamation Limit: No Limit
 Maximum Scratch Volumes Allowed: 100
  Number of Scratch Volumes Used: 10
   Delay Period for Volume Reuse: 0 Day(s)
          Migration in Progress?:
            Amount Migrated (MB):
Elapsed Migration Time (seconds):
        Reclamation in Progress?: No
  Last Update by (administrator): PIPPO
           Last Update Date/Time: 06/01/12   05:30:29
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
         Continue Copy on Error?:
                        CRC Data: No
                Reclamation Type: Threshold


               Storage Pool Name: SP_BACKUP_TAPE
               Storage Pool Type: Primary
               Device Class Name: LTO
              Estimated Capacity: 260,174 G
              Space Trigger Util:
                        Pct Util: 1.0
                        Pct Migr: 1.9
                     Pct Logical: 99.8
                    High Mig Pct: 90
                     Low Mig Pct: 70
                 Migration Delay: 0
              Migration Continue: Yes
             Migration Processes: 1
           Reclamation Processes: 1
               Next Storage Pool:
            Reclaim Storage Pool:
          Maximum Size Threshold: No Limit
                          Access: Read/Write
                     Description: stg pool contenente i backup dei dati
               Overflow Location:
           Cache Migrated Files?:
                      Collocate?: No
           Reclamation Threshold: 60
       Offsite Reclamation Limit:
 Maximum Scratch Volumes Allowed: 700
  Number of Scratch Volumes Used: 13
   Delay Period for Volume Reuse: 1 Day(s)
more...   (<ENTER> to continue, 'C' to cancel)
          Migration in Progress?: No
            Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
        Reclamation in Progress?: No
  Last Update by (administrator): PIPPO
           Last Update Date/Time: 06/01/12   05:30:29
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
         Continue Copy on Error?:
                        CRC Data: No
                Reclamation Type: Threshold


               Storage Pool Name: SP_SPACEMANAGMENT_TAPE
               Storage Pool Type: Primary
               Device Class Name: LTO
              Estimated Capacity: 204,492 G
              Space Trigger Util:
                        Pct Util: 53.9
                        Pct Migr: 69.6
                     Pct Logical: 100.0
                    High Mig Pct: 90
                     Low Mig Pct: 70
                 Migration Delay: 0
              Migration Continue: Yes
             Migration Processes: 1
           Reclamation Processes: 1
               Next Storage Pool:
            Reclaim Storage Pool:
          Maximum Size Threshold: No Limit
                          Access: Read/Write
                     Description: contiene i file migrati a nastro
               Overflow Location:
           Cache Migrated Files?:
                      Collocate?: Node
           Reclamation Threshold: 60
       Offsite Reclamation Limit:
 Maximum Scratch Volumes Allowed: 700
  Number of Scratch Volumes Used: 487
   Delay Period for Volume Reuse: 1 Day(s)
          Migration in Progress?: No
            Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
        Reclamation in Progress?: No
  Last Update by (administrator): PIPPO
           Last Update Date/Time: 06/01/12   05:30:29
        Storage Pool Data Format: Native
            Copy Storage Pool(s):
         Continue Copy on Error?:
                        CRC Data: No
                Reclamation Type: Threshold

I'd like to understand these parameters:
Estimated Capacity
Pct Util
Pct Migr
Pct Logical
High Mig Pct
Low Mig Pct

When I try to manually backup:

Code:

TSM_QUI>backup db t=f d=LTO
ANR2020E BACKUP DB: Invalid parameter - D.
ANS8001I Return code 3.

Part of my dsmsched.log:

Code:

05/25/12   19:00:02 --- SCHEDULEREC OBJECT BEGIN BACKUP_GIORNALIERO_ROOT_DATA 05/25/12   19:00:00
05/25/12   19:00:02 Incremental backup of volume '/'
05/25/12   19:00:02 Incremental backup of volume '/root_data'
05/25/12   19:00:02 Incremental backup of volume '/TSM_LOG'
05/25/12   19:00:07 ANS1898I ***** Processed     2,500 files *****
05/25/12   19:00:08 ANS1898I ***** Processed     3,000 files *****
...
...
...
05/25/12   19:47:20 ANS1898I ***** Processed   580,000 files *****
05/25/12   19:47:29 ANS1898I ***** Processed   580,500 files *****
05/25/12   19:47:36 Session established with server TSM_QUI: Linux/i386
05/25/12   19:47:36   Server Version 5, Release 3, Level 4.0
05/25/12   19:47:36   Server date/time: 05/25/12   19:47:36  Last access: 05/25/12   19:01:19
05/25/12   19:47:37 ANS1898I ***** Processed   581,000 files *****
05/25/12   19:47:37 Session established with server TSM_QUI: Linux/i386
05/25/12   19:47:37   Server Version 5, Release 3, Level 4.0
05/25/12   19:47:37   Server date/time: 05/25/12   19:47:37  Last access: 05/25/12   19:47:36

05/25/12   19:47:37 ANS1999E Incremental processing of '/root_data' stopped.

05/25/12   19:47:37 --- SCHEDULEREC STATUS BEGIN
05/25/12   19:47:37 Total number of objects inspected:  581,079
05/25/12   19:47:37 Total number of objects backed up:       31
05/25/12   19:47:37 Total number of objects updated:          0
05/25/12   19:47:37 Total number of objects rebound:          0
05/25/12   19:47:37 Total number of objects deleted:          0
05/25/12   19:47:37 Total number of objects expired:          1
05/25/12   19:47:37 Total number of objects failed:           0
05/25/12   19:47:37 Total number of bytes transferred:    31.12 MB
05/25/12   19:47:37 Data transfer time:                   44.84 sec
05/25/12   19:47:37 Network data transfer rate:          710.55 KB/sec
05/25/12   19:47:37 Aggregate data transfer rate:         11.16 KB/sec
05/25/12   19:47:37 Objects compressed by:                    0%
05/25/12   19:47:37 Elapsed processing time:           00:47:34
05/25/12   19:47:37 --- SCHEDULEREC STATUS END
05/25/12   19:47:37 ANS1026E The session is rejected: There was a communications protocol error.

05/25/12   19:47:37 --- SCHEDULEREC OBJECT END BACKUP_GIORNALIERO_ROOT_DATA 05/25/12   19:00:00
05/25/12   19:47:37 ANS1512E Scheduled event 'BACKUP_GIORNALIERO_ROOT_DATA' failed.  Return code = 12.
05/25/12   19:47:37 Sending results for scheduled event 'BACKUP_GIORNALIERO_ROOT_DATA'.
05/25/12   19:47:37 Results sent to server for scheduled event 'BACKUP_GIORNALIERO_ROOT_DATA'.

05/25/12   19:47:37 ANS1483I Schedule log pruning started.
05/25/12   19:47:37 ANS1484I Schedule log pruning finished successfully.

Part of my dsmerror.log:

Code:

05/25/12   17:32:20 ANS4039E Could not establish a session with a TSM server or client agent.  The TSM return code is -50.
05/25/12   17:32:20 ANS5216E Could not establish a TCP/IP connection with address 'IP-SERVER:1500'. The TCP/IP error is 'Connection refused' (errno = 111).
05/25/12   17:32:20 ANS4039E Could not establish a session with a TSM server or client agent.  The TSM return code is -50.
05/25/12   17:32:20 ANS5216E Could not establish a TCP/IP connection with address 'IP-SERVER:1500'. The TCP/IP error is 'Connection refused' (errno = 111).
05/25/12   17:32:20 ANS4039E Could not establish a session with a TSM server or client agent.  The TSM return code is -50.
05/25/12   17:32:21 ANS5216E Could not establish a TCP/IP connection with address 'IP-SERVER:1500'. The TCP/IP error is 'Connection refused' (errno = 111).
05/25/12   17:32:21 ANS4039E Could not establish a session with a TSM server or client agent.  The TSM return code is -50.
05/25/12   19:47:36 sessRecvVerb(): Invalid verb received.
05/25/12   19:47:36 sessRecvVerb(): Invalid verb received.
05/25/12   19:47:36 sessRecvVerb(): length=0000, verb=00,magic=01
05/25/12   19:47:36 sessRecvVerb(): length=0000, verb=00,magic=01
05/25/12   19:47:37 sessRecvVerb(): Invalid verb received.
05/25/12   19:47:37 sessRecvVerb(): Invalid verb received.
05/25/12   19:47:37 sessRecvVerb(): length=0000, verb=00,magic=01
05/25/12   19:47:37 sessRecvVerb(): length=0000, verb=00,magic=01
05/25/12   19:47:37 ANS1999E Incremental processing of '/root_data' stopped.

05/25/12   19:47:37 ANS1026E The session is rejected: There was a communications protocol error.

05/25/12   19:47:37 ANS1512E Scheduled event 'BACKUP_GIORNALIERO_ROOT_DATA' failed.  Return code = 12.

What is the "reclamation" ?

drivechip · Jun 1, 2012

tondox said:
My device class is LTO:

I'd like to understand these parameters:
Estimated Capacity
Pct Util
Pct Migr
Pct Logical
High Mig Pct
Low Mig Pct

Have a look to the help:

Code:

help update stgp

or

Code:

help define stgp

Code:
When I try to manually backup:

Code:

TSM_QUI>backup db t=f d=LTO ANR2020E BACKUP DB: Invalid parameter - D. ANS8001I Return code 3.

Sorry, my vault.

Code:

backup db dev=LTO t=f

What is the "reclamation" ?

http://publib.boulder.ibm.com/infoc...ic=/com.ibm.itsm.srv.doc/c_reclaim_works.html

tondox · Jun 6, 2012

I think I should troubleshoot this error:

Code:

05/25/12   19:47:37 --- SCHEDULEREC STATUS BEGIN
05/25/12   19:47:37 Total number of objects inspected:  581,079
05/25/12   19:47:37 Total number of objects backed up:       31
05/25/12   19:47:37 Total number of objects updated:          0
05/25/12   19:47:37 Total number of objects rebound:          0
05/25/12   19:47:37 Total number of objects deleted:          0
05/25/12   19:47:37 Total number of objects expired:          1
05/25/12   19:47:37 Total number of objects failed:           0
05/25/12   19:47:37 Total number of bytes transferred:    31.12 MB
05/25/12   19:47:37 Data transfer time:                   44.84 sec
05/25/12   19:47:37 Network data transfer rate:          710.55 KB/sec
05/25/12   19:47:37 Aggregate data transfer rate:         11.16 KB/sec
05/25/12   19:47:37 Objects compressed by:                    0%
05/25/12   19:47:37 Elapsed processing time:           00:47:34
05/25/12   19:47:37 --- SCHEDULEREC STATUS END
05/25/12   19:47:37 ANS1026E The session is rejected: There was a communications protocol error.

I tryed to google the ANS1026E error, but I did't reach some useful information.

drivechip · Jun 6, 2012

Please check that you have the latest version of B/A Client installed. Scroll up and look for furhter errors.

tondox · Jun 8, 2012

drivechip said:
Please check that you have the latest version of B/A Client installed. Scroll up and look for furhter errors.

B/A I think means Backup/Automig. Well... I'll try to look for the version, but I don't think I have the latest version, my TSM is an old version.

Sometime I find this:

dsmsched.log

Code:

Time remaining until execution: Querying server for next scheduled event.
06/07/12   00:25:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:25:36 Will attempt to get schedule from server again in 5 minutes.
06/07/12   00:25:36
Time remaining until execution: Querying server for next scheduled event.
06/07/12   00:30:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:30:36 Will attempt to get schedule from server again in 5 minutes.
06/07/12   00:30:36
Time remaining until execution: Querying server for next scheduled event.
06/07/12   00:35:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:35:36 Will attempt to get schedule from server again in 5 minutes.
06/07/12   00:35:36
Time remaining until execution: Querying server for next scheduled event.
06/07/12   00:40:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:40:36 Will attempt to get schedule from server again in 5 minutes.
06/07/12   00:40:36

dsmerror.log

Code:

06/07/12   00:20:35 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:25:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:30:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:35:36 ANS1029E Communication with the  TSM server is lost.
06/07/12   00:40:36 ANS1029E Communication with the  TSM server is lost.

but I'm sure there are not network problems.

Each scheduled backup starts good and ends with
ANS1026E The session is rejected: There was a communications protocol error
everyday.

Trying to understand my TSM system

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

drivechip

tondox

Active Newcomer

Data Privacy Impact Assessment

Sponsor ADSM.ORG

Navigation Menu

NordVPN 3 Months FREE

Forum statistics