jobs pending for 100+ hours and not timing out - Veritas Backup Exec

This is a discussion on jobs pending for 100+ hours and not timing out - Veritas Backup Exec ; Our backups have been quite reliable recently, without getting any errors etc. However the problem has arisen that for some reason the backups wouldn't run on Thursday night (I think the drive locked up or something), but rather than the ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: jobs pending for 100+ hours and not timing out

  1. jobs pending for 100+ hours and not timing out

    Our backups have been quite reliable recently, without getting any errors
    etc. However the problem has arisen that for some reason the backups
    wouldn't run on Thursday night (I think the drive locked up or something),
    but rather than the jobs timing out when they reached the end of the alloted
    time frame (all jobs scheduled using advanced), they continued to run in a
    pending state, with more and more jobs joining the queue.

    I've been busy recently, so haven't had time to check on it each day, and
    assumed that since I hadn't received any messages from BENT that all was
    well, but checked the system just now, and found no backup has run since
    that point, with the earliest jobs sitting there on 114hours of runtime.

    I had thought that the time window option (running BENT 8.5 Rev 3571, on
    NT4) would stop jobs going past that time, but obviously not. Is there any
    way to get BENT to cancel/fail the job if it takes too long to complete, so
    I at least get a failure notification to tip me off to the problem?

    Keith



  2. Re: jobs pending for 100+ hours and not timing out

    Hi
    I had a similar problem to this. Ken Putnam very kindly sent me this link,
    which might be of interest.
    http://seer.support.veritas.com/docs/192055.htm

    "Keith Langmead" wrote in message
    news:3ce12470$3@hronntp01....
    > Our backups have been quite reliable recently, without getting any errors
    > etc. However the problem has arisen that for some reason the backups
    > wouldn't run on Thursday night (I think the drive locked up or something),
    > but rather than the jobs timing out when they reached the end of the

    alloted
    > time frame (all jobs scheduled using advanced), they continued to run in a
    > pending state, with more and more jobs joining the queue.
    >
    > I've been busy recently, so haven't had time to check on it each day, and
    > assumed that since I hadn't received any messages from BENT that all was
    > well, but checked the system just now, and found no backup has run since
    > that point, with the earliest jobs sitting there on 114hours of runtime.
    >
    > I had thought that the time window option (running BENT 8.5 Rev 3571, on
    > NT4) would stop jobs going past that time, but obviously not. Is there any
    > way to get BENT to cancel/fail the job if it takes too long to complete,

    so
    > I at least get a failure notification to tip me off to the problem?
    >
    > Keith
    >
    >




  3. Re: jobs pending for 100+ hours and not timing out

    Cheers, but I'm not getting any error messages or anything appear, something
    seems to periodically stop the backups from starting properly, so they all
    sit in a pending state, they never complete, fail, generate an error or
    anything, they just sit there.

    Need a way to force the backup to fail if it runs more than x number of
    hours.

    "Steve Barningham" wrote in message
    news:3ce12ce3@hronntp01....
    > Hi
    > I had a similar problem to this. Ken Putnam very kindly sent me this link,
    > which might be of interest.
    > http://seer.support.veritas.com/docs/192055.htm
    >
    > "Keith Langmead" wrote in message
    > news:3ce12470$3@hronntp01....
    > > Our backups have been quite reliable recently, without getting any

    errors
    > > etc. However the problem has arisen that for some reason the backups
    > > wouldn't run on Thursday night (I think the drive locked up or

    something),
    > > but rather than the jobs timing out when they reached the end of the

    > alloted
    > > time frame (all jobs scheduled using advanced), they continued to run in

    a
    > > pending state, with more and more jobs joining the queue.
    > >
    > > I've been busy recently, so haven't had time to check on it each day,

    and
    > > assumed that since I hadn't received any messages from BENT that all was
    > > well, but checked the system just now, and found no backup has run since
    > > that point, with the earliest jobs sitting there on 114hours of runtime.
    > >
    > > I had thought that the time window option (running BENT 8.5 Rev 3571, on
    > > NT4) would stop jobs going past that time, but obviously not. Is there

    any
    > > way to get BENT to cancel/fail the job if it takes too long to complete,

    > so
    > > I at least get a failure notification to tip me off to the problem?
    > >
    > > Keith
    > >
    > >

    >
    >




  4. Re: jobs pending for 100+ hours and not timing out

    Pending isn't Running. They were waiting to run, and you're right, since there
    were no prompts (they weren't running yet) the tweaks mentioned in the other
    response won't help

    Not even the first job was running? or had an alert or prompt?

    That window is the time during which BENT will release the jobs (from scheduled
    to pending) if for some reason BackupExec isn't running at the scheduled
    execution time.



    Keith Langmead wrote:

    > Our backups have been quite reliable recently, without getting any errors
    > etc. However the problem has arisen that for some reason the backups
    > wouldn't run on Thursday night (I think the drive locked up or something),
    > but rather than the jobs timing out when they reached the end of the alloted
    > time frame (all jobs scheduled using advanced), they continued to run in a
    > pending state, with more and more jobs joining the queue.
    >
    > I've been busy recently, so haven't had time to check on it each day, and
    > assumed that since I hadn't received any messages from BENT that all was
    > well, but checked the system just now, and found no backup has run since
    > that point, with the earliest jobs sitting there on 114hours of runtime.
    >
    > I had thought that the time window option (running BENT 8.5 Rev 3571, on
    > NT4) would stop jobs going past that time, but obviously not. Is there any
    > way to get BENT to cancel/fail the job if it takes too long to complete, so
    > I at least get a failure notification to tip me off to the problem?
    >
    > Keith



  5. Re: jobs pending for 100+ hours and not timing out

    From the logs of the failed jobs, each of the jobs had gone through and
    completed the backup scan, but none had started the actual backup job and
    were sitting in a pending state.

    I think it's being caused by something that's still running when our ISP
    change the tapes over in the server, thus stopping the scheduled inventory
    job from running successfully (I think the inventory job was also pending,
    but it doesn't keep canceled inventory jobs in the Job Monitor), and
    apparently having a knock on effect to the other jobs.

    I'm sure with some investigation I can find what is causing that, but I'm
    more concerned if this or anything else causes this to happen again, I won't
    get alerted to the problem, and sods law says it'll happen when I've got a
    lot on, and no time to check myself.

    Keith

    "Ken Putnam" wrote in message
    news:3CE1D9A0.D5863826@nospam_usa.net...
    > Pending isn't Running. They were waiting to run, and you're right, since

    there
    > were no prompts (they weren't running yet) the tweaks mentioned in the

    other
    > response won't help
    >
    > Not even the first job was running? or had an alert or prompt?
    >
    > That window is the time during which BENT will release the jobs (from

    scheduled
    > to pending) if for some reason BackupExec isn't running at the scheduled
    > execution time.
    >
    >
    >
    > Keith Langmead wrote:
    >
    > > Our backups have been quite reliable recently, without getting any

    errors
    > > etc. However the problem has arisen that for some reason the backups
    > > wouldn't run on Thursday night (I think the drive locked up or

    something),
    > > but rather than the jobs timing out when they reached the end of the

    alloted
    > > time frame (all jobs scheduled using advanced), they continued to run in

    a
    > > pending state, with more and more jobs joining the queue.
    > >
    > > I've been busy recently, so haven't had time to check on it each day,

    and
    > > assumed that since I hadn't received any messages from BENT that all was
    > > well, but checked the system just now, and found no backup has run since
    > > that point, with the earliest jobs sitting there on 114hours of runtime.
    > >
    > > I had thought that the time window option (running BENT 8.5 Rev 3571, on
    > > NT4) would stop jobs going past that time, but obviously not. Is there

    any
    > > way to get BENT to cancel/fail the job if it takes too long to complete,

    so
    > > I at least get a failure notification to tip me off to the problem?
    > >
    > > Keith

    >




+ Reply to Thread