Kathleen,
Thanks for the info, I agree that this is very strange.
I'm wondering if QUERY EVENT is putting the actual start date in the
scheduled start date field. For example, given:
07/14/04 23:15:00 07/14/04 01:36:34 HE2UNX108.23- HE2UNX108 Completed
15.SOL.ANY
I wonder if it should be more like this:
07/13/04 23:15:00 07/14/04 01:36:34 HE2UNX108.23- HE2UNX108 Completed
15.SOL.ANY
(i.e. should the first column show 07/13/04 instead of 07/14/04).
Can you review your activity log for early morning today (14 July) and
check whether the timestamps in the ACTUAL START field coincide with the
activity log? For example, check to see if node E2UNX108 actualy started
its scheduled backup this morning at 1:36:34 AM this morning.
Alternatively, I don't see a future event for this schedule, just the
completed event. I'm also thinking that maybe the scheduled start time of
07/14/04 23:15:00 reflects the future event (tonight) and the actual start
time of 07/14/04 01:36:34 represent last night's event, and this record is
a "melding" of last night's and tonight's events.
Let us know what your activity log shows, and if those actual start times
synch up with this mornings activity log records.
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.ibm DOT com
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 07/14/2004
15:24:58:
>
>
>
>
> Everything is below--thanks for looking at it!
>
> Kathleen
>
>
>
>
>
>
> "Andrew Raibeck"
> <storman AT US DOT IBM.C To: ADSM-L AT VM.MARIST
> DOT EDU
> OM> cc:
> Sent by: "ADSM: Subject: Re: Strange q
ev output
> Dist Stor
> Manager"
> <[email protected]
> .EDU>
>
>
> 07/14/2004 06:01
> PM
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
>
>
> Curious. No, TSM is not psychic, as far as I know.
>
> Can you post the *complete* output from the following:
>
> 1) dsmadmc -id=youradmin -pa=xxxx q ev * *
>
> (See attached file: q.ev.zip)(this one is several hundred lines
long)
>
> 2) dsmadmc -id=youradmin -pa=xxxx q sch <domain> <schedname>
>
> Specify the domain and schedule name for one of the scheduled events
> showing the goofy times.
>
>
> Domain * Schedule Name Action Start Date/Time Duration
> Period Day
> ------------ - ---------------- ------ --------------------
--------
> ------ ---
> SOL HE2UNX108.2315.- Inc Bk 01/21/04 23:15:00 1
H
> 1 D Any
> SOL.ANY
>
>
> 3) dsmadmc -id=youradmin -pa=xxxx show time
>
> Current Date and Time on the Server
> ----------------------------------------
> 07/14/04 18:23:24
> UTC (GMT) Date/Time is: 07/14/04 22:23:24
> Last Noted Date/Time is: 07/14/04 18:09:34
>
> 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.ibm DOT com
>
> 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 07/14/2004
> 14:51:41:
>
> > We've been seeing this for some time now, and haven't really done
> anything
> > about it as it doesn't seem to affect actual backup success in any
way.
> > But it is rather odd, and it's appearing more frequently now. Running
a
> q
> > ev command at around 17:40 on 7/14 (in other words, just a few minutes
> ago)
> > brings up the following:
> >
> >
> >
> > 07/14/04 23:15:00 07/14/04 01:36:34 HE2UNX108.23- HE2UNX108
> > Completed
> > 15.SOL.ANY
> > 07/14/04 23:15:00 HE2UNX109.23- HE2UNX109
> > Future
> > 15.SOL.ANY
> > 07/14/04 23:15:00 07/14/04 01:36:25 HE2UNX111.23- HE2UNX111
> > Completed
> > 15.SOL.ANY
> > 07/14/04 23:15:00 07/14/04 01:36:29 HE2UNX112.23- HE2UNX112
> > Completed
> >
> > Is TSM psychic? How does it know that these events, which are
scheduled
> > for several hours in the future, will complete successfully? We're
> running
> > TSM 5.2.2.0 on AIX 5.2, but I also used to see this intermittently on
a
> 5.1
> > version of TSM on AIX 4.3.
> >
> > Has anyone ever seen this, or heard what causes it?
> >
> > Thanks,
> >
> > Kathleen
>
>
> [attachment "q.ev.zip" deleted by Andrew Raibeck/Tucson/IBM]
|
