Ben Kokenge wrote:
>
> Here is what I am up against.  We have a UNIX box that wants to
> backup most of it's data nightly, and it's *.log files weekly.  No
> problem, I have the standard mgnt. class backing up nightly and
> a weekly mgnt. class for weekly log files.  In the incl/excl file I have:
>
> include *
> exclude /.../*.log
> include /.../*.log   weekly
>
> So far so good.  Here is my problem (or lack of understanding).
> This machine needs to be rebooted every now and again (this part
> is out of my hands), and when that happens the WEEKLY mgnt.
> class resets it self (I believe).  If we have a  .LOG file backedup
> yesterday, then you reboot, it seems to backup again the next
> night.  If we don't reboot the UNIX box, it will only backup the
> .LOG files once a week.
>
> This can't be right.  I believe I am employing something wrong here.
>
I agree that the behaviour you are seeing does not seem right.  The
"frequency" parameter in a backup copy group does say that that many
days must elapse before a new incremental backup is taken (ok a file in
that management class, one presumes).  That should be relative to the
insertion date of the current active version.  It shouldn't depend on
the history of when the scheduler started.

Why do you have the exclude statement?  It is superfluous since the
include below it has the exact same pattern.  I wonder if, however, it
is related to the cause of the buggy behaviour...

Bruce