[Veritas-bu] Fault in "bpschedreq -predict" ??
2002-09-27 02:28:31
I think this is how it is supposed to work. When you ask for it to predict
for a date, it is predicting for that date, not up to that date...
e.g. for using -predict with a date 2 weeks out, think of it as predicting
what would happen if I stopped bprd for 2 weeks and then started it? you
wouldn't run all the jobs to catch up to that time. you would have missed
those.
Try passing it a time as well for some time during the day when all your
windows are closed. You won't get anything back.
- Scott
"Donaldson, Mark"
<[email protected] To: "Veritasbu
(E-mail)" <veritas-bu AT mailman.eng.auburn DOT edu>
om> cc:
Sent by: Subject:
[Veritas-bu] Fault in "bpschedreq -predict" ??
veritas-bu-admin AT mailman DOT eng.
auburn.edu
09/24/2002 06:07 PM
Based on a recent thread on this list, I've been looking into bpschedreq
-predict.
It seems that it'll report only the next occurance of a client & class for the
given supplied date. If I set a date out a couple of days, the list is almost
no different than the date set for the end of tomorrow.
Once a Class/client combination is discovered, the bpschedreq command looks no
further for repeat instances. My hourly archived-redo log incrementals are
reported once.
This is v3.4. Does v4.5 work the same? Anybody have a work-around?
-M
|
|
|