ANR2576W An attempt was made to update an event record for a scheduled
operation
         which has already been executed - multiple client schedulers
may be
         active for node ________.
        Can occur in a scenario where the scheduler is started through
CAD, but
        there is a lingering/stuck scheduler running, from a prior
invocation:
        in this case, kill off the defective scheduler process.
However, the
        Events table will likely contain a status of Completed for that
node's
        schedule, for an earlier day, rather than Pending, for today,
and a
        scheduler reattempt by that client's CAD will thus again fail on
the
        ANR2576W.  An alternative in this case is to define and
associate a
        special schedule to do the work.
        Check to see if you have any restartable restores going on for
the
        client in question via the server command: 'Query RESTore'.
Cancel the
        restartable restore session number if you do, and see if that
makes the
        problem go away.

"kill off the defective scheduler process"

How is this accomplished?  Can this be done on the TSM server, or is
this the process running on the node?

I've read that this may occur if the queryschedperiod and the Backup
Window are the same size or if the queryschedperiod is smaller than the
Backup window.  Is this a possibility?

This seems to be occurring intermittently, but on the same nodes most of
the times.

Thanks again.  Eric


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, May 20, 2009 2:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANR2576W

On May 20, 2009, at 5:22 PM, Eric Thompson wrote:

>
> Does anyone have any experience w/ this, have any ideas?

Eric - Yes.
See that message in http://people.bu.edu/rbs/ADSM.QuickFacts for my
findings. If you find any other cause, let me know.

    Richard Sims