The only thing I can guess is that server is trying to execute a schedule
but fails for some reason (for example lack of mount points) and retries
again, and again ... .  If the schedule had to start at 06:00 with 2
minutes retry period ?
Just guessing.
Why it retries only till 15:00 ?! Look description of Query SCHedule
command:
" ...
Start Date/Time
     Specifies the initial starting date and time for this schedule.
Duration
     Specifies the length of the startup window for this schedule.
.."
tsm: PUMBA.ACIT.BG>q sch
Domain       * Schedule Name    Action Start Date/Time      Duration Period
Day
------------ - ---------------- ------ -------------------- -------- ------
---
---
ACIT-OS2       BACK_CDRV        Inc Bk 10/02/2001 21:00:00      2 H    1 D
ACIT-OS2       BACK_CDRV        Inc Bk 10/02/2001 21:00:00      2 H    1 D
Any

Note duration field. If we have an schedule with start time 06:00 and
duration of 9 hours we can find an answer. And if the schedule was defined
with 06:00 PM in mind but got 06:00 (AM) ...


Zlatko Krastev
IT Consultant






Bruce Mitchell <bruce.mitchell AT DB DOT COM> on 10.10.2001 13:46:05
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Schedlog - revisited

All,
     Thanks for suggestions re QUERYSCHEDPERIOD, but schedmode is PROMPTED,
which we always use.
(guess I should have stated that)..

What I find extremely weird is that the sever only contacts the client from
 06:00 to 15:00???
The schedule is at 02:00 duration 9 hours, so I'd expect if it was related
that the 'polling' of the client it  would start at 11:00 at the end of
the backup window...

Any other ideas before I open a PMR.???

Tel:       +44(0) 207 547 4917
Fax        +44(0) 207 650 7917
Mobile    +44(0) 7768 361-885
email:    bruce.mitchell AT db DOT com



---------------------- Forwarded by Bruce Mitchell on 10/10/2001 10:32
---------------------------