Re: scheduler problem

2006-08-24 04:31:41
Subject: Re: scheduler problem
From: goc <goran.k AT VIP DOT HR>
Date: Thu, 24 Aug 2006 10:22:05 +0200
thank you very much for your inputs ...

you guys rock :-)

----- Original Message -----
From: "Andrew Raibeck" <storman AT US.IBM DOT COM>
Sent: Wednesday, August 23, 2006 10:52 PM
Subject: Re: scheduler problem

There is too little information to do any more than speculate (guess).

When troubleshooting problems, you need to consider the system as a whole,
and not focus only on the area where the problem was immediately evident
(in this case, dsmsched.log). For TSM, you need to consider, at a minimum,
the TSM server (where the schedule is defined), the TSM client scheduler
(which writes dsmsched.log) , the TSM client acceptor (CAD) which you are
using to manage the scheduler, and the environment as a whole (client
machine, server machine, network, and any other related patterns that
might provide insight).

So with that in mind, your investigations should include examination of:

- The TSM server activity log for the duration of the schedule window
(from 17:43 through whatever the duration of the schedule is).
- The TSM server schedule definition and associations, to ensure that the
schedule definition or associations have not changed unexpectedly.
- The TSM client acceptor log file (dsmwebcl.log).
- The TSM client error logs (dsmerror.log, dsierror.log)
- The TSM client schedule log (dsmsched.log, which you've already examined
- The TSM client options file to verify that the options are configured
correctly for your environment

Also check the following:

Prevalence of the problem. For example, determine whether this happens
every day, or just one time. Check whether any other clients are affected,
or if only this one client is affected.

Check whether there are any networking issues (network itself, firewall,
etc.) that might have contributed to the schedule being missed

Check whether the CAD was stopped, or the machine powered down at the time
the schedule was to run.

Check the schedule duration. Very short duration (for example, 5 minutes
or less) might not run. Make sure the schedule has a reasonable duration.
I recommend at least 1 hour.

Check whether the TSM server was running and available to clients at the
time the backup was supposed to run.

There are almost certainly other things to investigate, too, but this
should help you get started.



Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
Internet e-mail: storman AT DOT com

IBM Tivoli Storage Manager support web page:

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

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/23/2006
07:09:56 AM:

yeah, okay ... thanks
so ... what do you think why is there 8 hours gap ?

----- Original Message -----
From: "Large, M (Matthew)" <Matthew.Large AT RABOBANK DOT COM>
Sent: Wednesday, August 23, 2006 3:44 PM
Subject: Re: scheduler problem

Fairly basic stuff here - the TSM scheduler must be running within the
schedule window if you want TSM to do something.

This line in the schedule log:
08/22/06   14:39:53 Scheduler has been stopped.

And this line after it:
08/22/06   22:39:55 Scheduler has been started by Dsmcad.

Indicate that the scheduler was not up when the TSM server tried to
contact it - I guess you have it as a MISSED schedule?

Quote "Either the window has elapsed or the schedule has been deleted
:-S which is not true"

TSM is correct in reporting that the window had elapsed.

We have shadow scripts here to ensure that if the scheduler falls over,
the script picks it up again. It may be worth your while implementing
something like this if you want to make sure you don't miss the
scheduled window for backup.

Not to appear rude, but, this is simple stuff - please either go an a
course or read the manual(s).


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: 23 August 2006 14:16
Subject: [ADSM-L] scheduler problem

hi all, please look at this

  14:39:53 ------------------------------------------------------------
08/22/06   14:39:53 Schedule Name:         SDB_EXP_SCHED01
08/22/06   14:39:53 Action:                Incremental
08/22/06   14:39:53 Objects:               /db/sdb11/backup01/backup/
08/22/06   14:39:53 Options:               -su=yes -preschedulecmd="su -
oracle -c /db/sdb11/backup01/backup/sd"
08/22/06   14:39:53 Server Window Start:   17:43:00 on 08/22/06
  14:39:53 ------------------------------------------------------------
08/22/06   14:39:53 Scheduler has been stopped.

08/22/06   22:39:55 Scheduler has been started by Dsmcad.
08/22/06   22:39:55 Querying server for next scheduled event.
08/22/06   22:39:55 Node Name: SDB
08/22/06   22:39:55 Session established with server TSM01: AIX-RS/6000

why didn't scheduler start at 17:43 on 22.8 (yesterday) ????
the message in error log says :

Either the window has elapsed or the schedule has been deleted

:-S which is not true

i'm confused. i asked for help month ago and nothing :-)

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
the intended recipient only. If you have received this email in error,
please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
contents of this information is strictly prohibited. Although we have
reasonable precautions to ensure no viruses are present in this email,
cannot accept responsibility for any loss or damage arising from the
in this email or attachments. We exclude any liability for the content
this email, or for the consequences of any actions taken on the basis of
information provided in this email or its attachments, unless that
information is subsequently confirmed in writing. If this email contains
offer, that should be considered as an invitation to treat.

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