This is the TSM client scheduler problem:

See below: IODM01DB missed last night backup, it supposed to start at
20:00. There is no "ANR2561I Schedule prompter contacting" message. It only
reported when it missed the scheduler. Compared to the one working showing
the calling message on GODM11DB starting at 3:00.

tsm: GO2ADSM03>q actlog begind=-1 begint=20:00 search=iodm01db
Date/Time            Message
--------------------
----------------------------------------------------------
05/18/03   21:00:01  ANR2578W Schedule IODM01DB_DAILY_SEL in domain
                      DOMINO_DOMAIN for node IODM01DB has missed its
scheduled
                      start up window.
tsm: GO2ADSM03>q actlog begint=03:00 search=godm11db
Date/Time            Message
--------------------
----------------------------------------------------------
05/19/03   03:00:20  ANR2561I Schedule prompter contacting GODM11DB
(session
                      9073) to start a scheduled operation.
05/19/03   03:00:22  ANR0406I Session 9075 started for node GODM11DB
(WinNT)
                      (Tcp/Ip 10.1.2.4(4178)).
05/19/03   03:00:23  ANR2507I Schedule GODM11DB_DAILY_SEL for domain
                      DOMINO_DOMAIN started at 05/19/03 03:00:00 for node
                      GODM11DB completed successfully at 05/19/03 03:00:23.

On top of this here is the failing nodes and its timing:

Here is summary of backup result:

(Embedded image moved to file: pic07596.pcx)

The legend: M stands for Missed. When missed happened, there is nothing
recorded in TSM activity log showing any problem or invoke scheduled
activity. There is nothing in the clients. Since, there is no original
request from the server, there is no responsibility from the client. I
think this is TSM scheduler issue. Could you kindly search TSM database to
see if there is any hit or fixes?

Whatever left in blank showing the backup does not miss its schedule. We
had rebooted our TSM server on Friday, the backup on the 5/17 is working.
However, it failed the next day. There is no consistency that which one
will work or not.

We had upgraded our TSM server on May 1. There is no problem reported until
other none related schedule enable and caused these schedules in the funny
state.

Frank Tsao
Frank.Tsao AT sce DOT com
PAX 25803, 626-302-5803
FAX 626-302-7131



                      Andrew Raibeck
                      <storman AT US DOT IBM.C        To:       ADSM-L AT 
VM.MARIST DOT EDU
                      OM>                      cc:
                      Sent by: "ADSM:          Subject:  Re: The TSM scheduler 
does not work after the upgrade to
                      Dist Stor                 5.1.6.1
                      Manager"
                      <[email protected]
                      .EDU>


                      05/19/2003 09:42
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






When troubleshooting any kind of technical problem, hard data is of great
importance. The current problem description is very vague. Can you provide
more specific information?

1) How do you KNOW the schedules are failing? What EXACTLY are you looking
at that indicates the schedules are failing?

2) In answer to Charles's question, you wrote: "There is no report of
anything in the client.".  If this is indeed true, then this would suggest
to me that the client scheduler is not running, which is a very important
factor in getting a successful backup   :-)     The scheduled event can
not run if the scheduler is not running on the client. If the scheduler is
actually running on the client machine, then there must be SOMETHING in
dsmsched.log or dsmerror.log.

b) What are the contents of dsmsched.log and dsmerror.log?

c) What are the contents of dsm.sys and dsm.opt?

d) What does the TSM server activity log show for this node for the
timeframe in which the schedule is supposed to run?

e) Show the output from QUERY SCHEDULE domainname schedulename F=D

f) Show the output from QUERY NODE nodename F=D

g) Include any other technical details that you can provide regarding this
issue.

That should be a good start.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Frank Tsao, email is tsaof AT sce DOT com" <Frank.Tsao
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/19/2003 09:02
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: The TSM scheduler does not work after the
upgrade to 5.1.6.1



The query output from "q opt" shows that the DisableScheds  No.

There is nothing reported around that time.

There is no report of anything in the client.

Frank Tsao
Frank.Tsao AT sce DOT com
PAX 25803, 626-302-5803
FAX 626-302-7131



                      "Hart, Charles"
                      <charles.hart@MED        To: ADSM-L AT VM.MARIST DOT EDU
                      TRONIC.COM>              cc:
                      Sent by: "ADSM:          Subject:  Re: The TSM
scheduler does not work after the upgrade to
                      Dist Stor                 5.1.6.1
                      Manager"
                      <[email protected]
                      .EDU>


                      05/19/2003 08:11
                      AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






Few Questions To ask....
        1) Schedules enabled in dsmserv.opt?
        2) What does the Activity Log state around the Scheduled time
        3) Client Side dsmseched log?



-----Original Message-----
From: Frank Tsao, email is tsaof AT sce DOT com [mailto:Frank.Tsao AT SCE DOT 
COM]
Sent: Monday, May 19, 2003 10:09 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: The TSM scheduler does not work after the upgrade to 5.1.6.1


We had the performed the upgrade of TSM server from AIX 4.3.3 to AIX
5.1_ML3 and TSM from 4.2.1.11 to 5.1.6.1. We converted all these to 64 bit
software.

After the upgrade everything works fine until we activated some of the
schedules that has been deactivated (after the upgrade) due to NT window
sliding problem. Now we had fixed this bug. So we activated the schedules.

The activation does not bring these associated nodes alive and we found
that the schedules had not been touched also failed. We had recycled TSM
application with no help. We had rebooted our TSM hardware box with only
one day of success. Now all the schedules had been falling like autumn
leaves.

Does any one seen this problem? Can any one had any fixes?

Frank Tsao
Frank.Tsao AT sce DOT com
PAX 25803, 626-302-5803
FAX 626-302-7131

pic07596.pcx
Description: Binary data