ADSM-L

Re: [ADSM-L] Scheduler problem

2010-04-13 08:07:38
Subject: Re: [ADSM-L] Scheduler problem
From: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 13 Apr 2010 15:05:41 +0300
Hello Richard,

I do not think problem is so simple.



> Check the dsmerror.log on the client for possible error indications.

There is nothing in dsmerror.log.



> Assure that the TSM server parameters for the client have it going at client 
> port 1501 for the session, and not some odd port.

IP Address and port is not set, so default is 1501. Client options are not set 
as well.



> From the TSM server system, at an OS prompt, do 'telnet <ClientNetname> 1501':

[tsmsrv1][/tsm/bin]>tn sms-prodsrv 1501

Trying...

Connected to sms-prodsrv.bkme.com.

Escape character is '^T'.

tn>

In dsmerror.log:

04/13/2010 14:42:01 sessInit: Starting communications initialization

04/13/2010 14:42:01 sessInit: Transitioning: sInit state ===> sTRANSERR state

04/13/2010 14:42:02 ANS0361I DIAG: Error reading http request.



> Use the TSM server command 'DEFine CLIENTAction' to perform a test command:

Command: 'define clientaction sms-prodsrv action=incremental objects=D:'

IBM Tivoli Storage Manager

Command Line Administrative Interface - Version 5, Release 4, Level 2.0

(c) Copyright by IBM Corporation and other(s) 1990, 2008. All Rights Reserved.

Session established with server BKME: AIX-RS/6000

  Server Version 5, Release 5, Level 4.1

  Server date/time: 04/13/2010 14:46:53  Last access: 04/13/2010 14:42:24

ANS8000I Server command: 'define clientaction sms-prodsrv action=incremental 
objects=D:'

ANR2500I Schedule @1 defined in policy domain NT.

ANR2510I Node SMS-PRODSRV associated with schedule @1 in policy domain NT.

ANR2505I 1 schedules were defined for DEFINE CLIENTACTION.

ANS8002I Highest return code was 0.



Incremental backup for D: has been done immediately:

ANS8000I Server command: 'q act or=client node=sms-prodsrv'

Date/Time: 04/13/2010 14:50:40   Message: ANE4952I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects inspected:   23,119(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4954I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects backed up:       70(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4958I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects updated:          0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4960I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects rebound:          0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4957I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects deleted:          0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4970I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects expired:          0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4959I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of objects failed:           0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4965I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of subfile objects:          0(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4977I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of bytes inspected:      3.51 GB(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4961I (Session: 18109, Node: 
SMS-PRODSRV)  Total number of bytes transferred: 26.51 MB(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4963I (Session: 18109, Node: 
SMS-PRODSRV)  Data transfer time:                    0.03 sec(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4966I (Session: 18109, Node: 
SMS-PRODSRV)  Network data transfer rate:        848,592.83 KB/sec(SESSION: 
18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4967I (Session: 18109, Node: 
SMS-PRODSRV)  Aggregate data transfer rate:        574.89 KB/sec(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4968I (Session: 18109, Node: 
SMS-PRODSRV)  Objects compressed by:                   77%(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4976I (Session: 18109, Node: 
SMS-PRODSRV)  Total data reduction ratio:           99.27%(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4969I (Session: 18109, Node: 
SMS-PRODSRV)  Subfile objects reduced by:               0%(SESSION: 18109)

Date/Time: 04/13/2010 14:50:40   Message: ANE4964I (Session: 18109, Node: 
SMS-PRODSRV)  Elapsed processing time:            00:00:47(SESSION: 18109)

ANS8002I Highest return code was 0.



I have an idea about a source of problem.

I have MS SQL database on the same server.

There is dedicated node name and scheduler for SQL database.

So I am running two schedulers and only one CAD service.

Everything was working fine with TSM Client 6.1.3.2, but I have upgraded this 
server to 6.2.0.0 recently and started to have this problem.

I have found something strange on server. Command "netstat -a" gives:



TCP    sms-prodsrv:ms-sql-s  sms-prodsrv.KUWAIT.AUB.NET:0  LISTENING

TCP    sms-prodsrv:1501       sms-prodsrv.KUWAIT.AUB.NET:0  LISTENING

TCP    sms-prodsrv:1501       sms-prodsrv.KUWAIT.AUB.NET:0  LISTENING

TCP    sms-prodsrv:1581       sms-prodsrv.KUWAIT.AUB.NET:0  LISTENING



As you see there are two (???????!!!!!!!!) LISTENNING for port 1501.

My minimal knowledge in TCP/IP says it is impossible.

What do you think about it?



Regards,



Grigori G. Solonovitch



Senior Technical Architect



Information Technology  Ahli United Bank Kuwait http://www.ahliunited.com.kw



Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail: Grigori.Solonovitch 
AT ahliunited DOT com



Please consider the environment before printing this Email





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Sims
Sent: Tuesday, April 13, 2010 2:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Scheduler problem



Grigori -



Some ways to pursue...



Check the dsmerror.log on the client for possible error indications.



Assure that the TSM server parameters for the client have it going at client 
port 1501 for the session, and not some odd port.



>From the TSM server system, at an OS prompt, do 'telnet <ClientNetname> 1501':

When you do Ctrl+], then press Enter to get the "telnet>" prompt, and then 
quit, the client dsmerror log should contain like:

  04/13/10   07:13:24 sessInit: Starting communications initialization

  04/13/10   07:13:24 sessInit: Transitioning: sInit state ===> sTRANSERR state

This verifies physical connectability from server to client, as in no 
firewalling preventing access.



Use the TSM server command 'DEFine CLIENTAction' to perform a test command 
which will leave evidence on the client, such as a command to report time of 
day, directed to a file.  (DEFine CLIENTAction may take a while to kick off, so 
give it some time.)



    Richard Sims



Please consider the environment before printing this Email.

________________________________
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail 
message and any attachments hereto may be legally privileged and confidential. 
The information is intended only for the recipient(s) named in this message. If 
you are not the intended recipient you are notified that any use, disclosure, 
copying or distribution is prohibited. If you have received this in error 
please contact the sender and delete this message and any attachments from your 
computer system. We do not guarantee that this message or any attachment to it 
is secure or free from errors, computer viruses or other conditions that may 
damage or interfere with data, hardware or software.

<Prev in Thread] Current Thread [Next in Thread>