Backup job causing CPU pin. - Veritas Backup Exec

This is a discussion on Backup job causing CPU pin. - Veritas Backup Exec ; Our scheduled backup jobs are pinning our cpu, the job starts but never writes to the media and just keeps spinning while consuming the cpu to %100. The only way to stop this is to stop the Server service and ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Backup job causing CPU pin.

  1. Backup job causing CPU pin.


    Our scheduled backup jobs are pinning our cpu, the job starts but never writes
    to the media and just keeps spinning while consuming the cpu to %100. The
    only way to stop this is to stop the Server service and it's dependant services.
    When this happens we have gotten a dr watson error, here are the cliff notes;
    scheduler_servi.exe causing a stack overflow c00000fd. I have looked all
    over for any info on this and have found none. Interesting piece to this
    puzzle is the fact that when I stop the service to abort the job and get
    my cpu back the job history doesn't even log a thing and their are no event
    logs entries, yipee. We are running NT 4 on SP 6a with Backup exec 8.0. Any
    help would be greatly appreciated.

    Regards,
    Todd



  2. Re: Backup job causing CPU pin.

    What build of v8.0?

    If it's not 3316, grab that from
    http://seer.support.veritas.com/docs/230827.htm and upgrade.

    Todd Day wrote:

    >Our scheduled backup jobs are pinning our cpu, the job starts but never writes
    >to the media and just keeps spinning while consuming the cpu to %100. The
    >only way to stop this is to stop the Server service and it's dependant services.
    >When this happens we have gotten a dr watson error, here are the cliff notes;
    >scheduler_servi.exe causing a stack overflow c00000fd. I have looked all
    >over for any info on this and have found none. Interesting piece to this
    >puzzle is the fact that when I stop the service to abort the job and get
    >my cpu back the job history doesn't even log a thing and their are no event
    >logs entries, yipee. We are running NT 4 on SP 6a with Backup exec 8.0. Any
    >help would be greatly appreciated.
    >
    >Regards,
    >Todd
    >
    >
    >
    >



  3. Re: Backup job causing CPU pin.


    Thanks Ken.. We are running 3315, what does 3316 fix that's related to our
    issue?
    Ken Putnam wrote:
    >What build of v8.0?
    >
    >If it's not 3316, grab that from
    >http://seer.support.veritas.com/docs/230827.htm and upgrade.
    >
    >Todd Day wrote:
    >
    >>Our scheduled backup jobs are pinning our cpu, the job starts but never

    writes
    >>to the media and just keeps spinning while consuming the cpu to %100. The
    >>only way to stop this is to stop the Server service and it's dependant

    services.
    >>When this happens we have gotten a dr watson error, here are the cliff

    notes;
    >>scheduler_servi.exe causing a stack overflow c00000fd. I have looked all
    >>over for any info on this and have found none. Interesting piece to this
    >>puzzle is the fact that when I stop the service to abort the job and get
    >>my cpu back the job history doesn't even log a thing and their are no event
    >>logs entries, yipee. We are running NT 4 on SP 6a with Backup exec 8.0.

    Any
    >>help would be greatly appreciated.
    >>
    >>Regards,
    >>Todd
    >>
    >>
    >>
    >>

    >



  4. Re: Backup job causing CPU pin.

    Dunno specifically, but it's the last build for that release, and I've
    not heard of this kind of problem with v8.0 before. (7.0 and 7.2 yes,
    but not 8.0)

    Rather than just re-installing what you have, you may as well get the
    latest and greatest.

    Or if you want, you can grab the latest v8.5 build. Won't support SQL
    /Exchange 2000, but the base code will still work and you can backup
    SQL v7 and Exch v5.5

    Todd Day wrote:

    >Thanks Ken.. We are running 3315, what does 3316 fix that's related to our
    >issue?
    >Ken Putnam wrote:
    >
    >
    >>What build of v8.0?
    >>
    >>If it's not 3316, grab that from
    >>http://seer.support.veritas.com/docs/230827.htm and upgrade.
    >>
    >>Todd Day wrote:
    >>
    >>
    >>
    >>>Our scheduled backup jobs are pinning our cpu, the job starts but never
    >>>
    >>>

    >writes
    >
    >
    >>>to the media and just keeps spinning while consuming the cpu to %100. The
    >>>only way to stop this is to stop the Server service and it's dependant
    >>>
    >>>

    >services.
    >
    >
    >>>When this happens we have gotten a dr watson error, here are the cliff
    >>>
    >>>

    >notes;
    >
    >
    >>>scheduler_servi.exe causing a stack overflow c00000fd. I have looked all
    >>>over for any info on this and have found none. Interesting piece to this
    >>>puzzle is the fact that when I stop the service to abort the job and get
    >>>my cpu back the job history doesn't even log a thing and their are no event
    >>>logs entries, yipee. We are running NT 4 on SP 6a with Backup exec 8.0.
    >>>
    >>>

    >Any
    >
    >
    >>>help would be greatly appreciated.
    >>>
    >>>Regards,
    >>>Todd
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>

    >
    >
    >



+ Reply to Thread