Job execute is mysteriously delayed - Veritas Backup Exec

This is a discussion on Job execute is mysteriously delayed - Veritas Backup Exec ; BE9.2 build 1391 on NW6.5/SP5. Linux agent (nls_agnt_262592.tar) running SLES 8. Job is scheduled for 11:15pm, but for some reason does not execute until about 12:45am. The job in front of it finishes well before 11:15pm. I use a different ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: Job execute is mysteriously delayed

  1. Job execute is mysteriously delayed

    BE9.2 build 1391 on NW6.5/SP5.
    Linux agent (nls_agnt_262592.tar) running SLES 8.

    Job is scheduled for 11:15pm, but for some reason does not execute
    until about 12:45am. The job in front of it finishes well before
    11:15pm.

    I use a different job for each day to direct backup to the correct
    partitions. Each day's job behaves the same way.

    Seems to have been this way for some time. Didn't notice until this
    week when I added some new servers into the mix and found their jobs
    (which follow the problem child) didn't execute on time.

    I have other SLES 8 servers that don't exhibit this problem. And it
    seems to me that this is a scheduler problem, not a remote agent
    problem.

    Ideas? Will debug give info on drive/partition reservations? I'm not
    eager to stay up and watch it myself. ;-)

    -Barry.



  2. Re: Job execute is mysteriously delayed

    Barry St.John wrote:

    > BE9.2 build 1391 on NW6.5/SP5.
    > Linux agent (nls_agnt_262592.tar) running SLES 8.
    >
    > Job is scheduled for 11:15pm, but for some reason does not execute
    > until about 12:45am. The job in front of it finishes well before
    > 11:15pm.
    >
    > I use a different job for each day to direct backup to the correct
    > partitions. Each day's job behaves the same way.
    >
    > Seems to have been this way for some time. Didn't notice until this
    > week when I added some new servers into the mix and found their jobs
    > (which follow the problem child) didn't execute on time.
    >
    > I have other SLES 8 servers that don't exhibit this problem. And it
    > seems to me that this is a scheduler problem, not a remote agent
    > problem.
    >
    > Ideas? Will debug give info on drive/partition reservations? I'm
    > not eager to stay up and watch it myself. ;-)
    >
    > -Barry.


    Hmm, sounds like a strange one..

    Can you try changing the time to 11:20pm to see if this makes any
    difference? I suspect that there is some kind of problem with this job.
    Editing it (basically refreshing it) might help.

    Chris


  3. Re: Job execute is mysteriously delayed

    I'll try changing the time. But I find it odd that I have 5 different
    jobs that all behave this way, just for this one box.

    I'll let you know...

    -Barry.



  4. Re: Job execute is mysteriously delayed

    No change. In fact I now have another remote server job exhibiting
    similar behavior.

    -Barry.



  5. Re: Job execute is mysteriously delayed

    Barry St.John wrote:

    > No change. In fact I now have another remote server job exhibiting
    > similar behavior.


    Are they both SLES 8?

    I have a test box running Novell Linux Desktop so I'll schedule a job
    to back this up to see if I see the same behavior.

    Chris

  6. Re: Job execute is mysteriously delayed

    Scratch that. The other remote server I thought was doing the same
    thing is not doing it after all. I figured out what was happening
    there.

    So we are back to this one SLES 8 box. Note that I have another SLES 8
    box that does not do this.

    Would it help diagnosis to run this in debug?

    -Barry.









  7. Re: Job execute is mysteriously delayed

    Barry St.John wrote:

    > Scratch that. The other remote server I thought was doing the same
    > thing is not doing it after all. I figured out what was happening
    > there.
    >
    > So we are back to this one SLES 8 box. Note that I have another SLES
    > 8 box that does not do this.
    >
    > Would it help diagnosis to run this in debug?


    Yes, that might help. Post back with :\bkupexec\log\ndmpd.log and
    we'll take it from there.

    Chris


  8. Re: Job execute is mysteriously delayed

    Last night, just because I really love doing it, I delete the job and
    recreated it. No joy.

    OK, I'll set it up for tonight with debug.

    -Barry.




  9. Re: Job execute is mysteriously delayed

    For anyone following this thread, I've come up with this nifty way to
    get just the one job to run in debug mode.

    This uses STUFFKEY, available free here:

    http://www.novell.com/coolsolutions/tools/13957.html

    Cut & past this StuffKey script to toggle debug mode in BE:

    #+---------------------------------------
    #| StuffKey script: BEdebug.sk
    #| Toggles the DEBUG mode in Backup Exec.
    #+---------------------------------------

    <2000 pause>

    <2000 pause>
    #
    #End


    Create BEDEBUG.NCF in SYS:\SYSTEM to run StuffKey with the above
    script:

    #+--------------------------------------------------------
    #| Toggles the debug mode of Backup Exec using StuffKey.
    #+--------------------------------------------------------
    StuffKey sys:\system\BEdebug.sk /r


    Finally, create a policy in BE. Call it DEBUG, or whatever makes sense
    for you. In the Pre/Post options, enter the command: BEDEBUG.NCF in
    both the EXECUTE BEFORE and EXECUTE AFTER command fields. The first
    one turns debug mode on when the job starts and the second turns it off
    when the job is done.

    Whenever you want to debug just one job, assign this policy to that
    backup job. That way you don't have to waste a bunch of disk space
    capturing gobs of debug data for all the rest of your jobs.

    -Barry.



  10. Re: Job execute is mysteriously delayed

    Wouldn't you know, that job ran as scheduled when debug was turned on!

    And the job that ran afterward was delay by about and hour.

    I've set tonight's jobs to turn debug on one job before the problem
    job, and turn debug off one job after. Hopefully that narrows things
    down a bit yet still catches the problem in action.

    -Barry.



  11. Re: Job execute is mysteriously delayed

    Here's NDMPD.LOG, as requested. It looks like the job cannot make a
    reservation.

    I suspect that a job on another server must be grabbing dibs on the
    drive (there are three in this library) as soon as the previous job
    finishes.

    So far I have been focusing on just this one media server. I'll have
    to do some more digging...

    -Barry.





  12. Re: Job execute is mysteriously delayed

    Barry St.John wrote:

    > Here's NDMPD.LOG, as requested. It looks like the job cannot make a
    > reservation.


    Yeah, this appears to be the problem:

    ERROR: [000009f5][08/25 23:47:54] ndmpdTapeSpecialCheat: Could Not Get
    Reservation On Device 1769474.

    > I suspect that a job on another server must be grabbing dibs on the
    > drive (there are three in this library) as soon as the previous job
    > finishes.
    >
    > So far I have been focusing on just this one media server. I'll have
    > to do some more digging...


    OK, keep us posted..

    > -Barry.








+ Reply to Thread