Normally I run my AO configuration M-F evenings after COB based the measurement interval of 8am-6pm for a maximum of 6 hours. After tuning a bunch of VVs to CPGs in the AO config the amount of work to do often exceeds what can be done in 6 hrs. It being the weekend I figured I would give AO a jump on Monday and run on Sunday the config using a sampling interval of 8-6 on *Friday* (about 51 hours ago). I carefully backed into the -btsecs and -etsecs but when the task runs it errors out saying "Not enough samples in the requested time interval". It appears as if the systems does not retain granular enough data back that far 48+ hours. Does anyone know if this retention period is adjustable? Is anyone successfully running AO configs based on historical data of this age? I have a 7400 running 3.1.2 MU2.
Ken
Are there limitations to -btsecs and -etsecs with AO?
-
spencer.ryan
- Posts: 35
- Joined: Tue Feb 11, 2014 11:33 am
Re: Are there limitations to -btsecs and -etsecs with AO?
Take a look at this: viewtopic.php?f=18&t=621
Why not just set two schedules, one that runs M-Th, and another for Friday that has the maxruntime set to 12 or 18 hours.
Why not just set two schedules, one that runs M-Th, and another for Friday that has the maxruntime set to 12 or 18 hours.