"SRGould41" wrote:
> Hello,
> We have a WSS 3 farm that has two WFE's. We use DocAve for backups. For some
> time now I have been fighting backup failures because of timer job intervals.
> Here is a representative error:
> --
> The job failed when backing up the site collection
> "http://site1-sharepoint".
> The interval between two jobs is longer than change log setting of this web
> application.
> Current Change Log Setting:90.00:00:00
> Current Interval between Two Jobs:103.23:59:54.8959820
> Last Job Backup Time:7/16/2009 6:00:46 PM
> Current Job Backup Time:10/28/2009 6:00:41 PM
> --
> What I have been doing is to keep increasing the change log setting, but the
> interval between jobs just keeps growing longer by the day. I don't want to
> keep
> increasing the change log setting every time this happens. We started at 10
> days and are now at 90. This DOES solve the backup failure, but the only way
> to fix it permenantly would be to never delete entries in the change log. I
> don't want to do that if I dno't have to.
> I have been hunting for information on how to resolve this, but without
> concrete results. I have read lots of information about timer jobs, but
> nothing to help me find out what jobs are causing this issue.
> Looking at the timer job status page I see current dates for one WFE and
> August dates for the other WFE. As of this morning the interval between two
> jobs has grown to 110 days. The August date isn't 110 days back so this
> doesn't seem to point at the error. Are there hidden jobs not reflected on
> this page? Today I disabled the timer service on the server with the current
> dates and I see the other server entries being updated as timer events fire
> off.
> I thought I could get all the system timer jobs to launch using
> execadmsvcjobs, but that didn't do it. I will see what happens in another day
> when the timer jobs run on their own schedule and then see if the backup
> errors continue.
> In the mean time can someone point me in the right direction? Is there a way
> to figure out which jobs are causing the errors?
> Thanks in advance
> Steve