Job Status Failed - Veritas Backup Exec

This is a discussion on Job Status Failed - Veritas Backup Exec ; BE7.01. Backup worked fine, verify seemed to work fine, but job status showed FAILED. Backup log file also says failed, but doesn't say why....

+ Reply to Thread
Results 1 to 3 of 3

Thread: Job Status Failed

  1. Job Status Failed


    BE7.01. Backup worked fine, verify seemed to work fine, but job status showed
    FAILED. Backup log file also says failed, but doesn't say why.

  2. Re: Job Status Failed

    The following is the list I use to determine the cause of a "FAILED" status. If
    you have an editor that suports macros, set one up that you can use scan any
    failed job log.

    Access Denied
    Corrupt File
    Unable to Attach
    Job was Aborted
    Insufficient Memory
    The Media Operations was Aborted
    Drive Not Responding
    Lost Connection

    Ray Zorz wrote:

    > BE7.01. Backup worked fine, verify seemed to work fine, but job status showed
    > FAILED. Backup log file also says failed, but doesn't say why.



  3. Re: Job Status Failed


    I am also having the same error as mentioned. But this error
    just started showing up about 2 weeks ago, and it's here ever since.
    I am aware of the log file that shows "Access Denied" on certain
    files. But previous back-up schedules show "Successful" on the job status
    field. This is the same back-up schedule that's been running in
    our server, and as far as I know, nothing has been changed in our
    server. Which raised another question, the logs on the Alert tab.
    had disappeared. At this point I am not getting any alerts postings
    at all.

    Troubleshoot:
    -I've looked at the scheduled job compared it to the previous
    successful jobs, and they seemed to look identical.
    -I've erased the contents of the tape before running the backup.
    -I've re-booted the server.

    Ken Putnam wrote:
    >The following is the list I use to determine the cause of a "FAILED" status.

    If
    >you have an editor that suports macros, set one up that you can use scan

    any
    >failed job log.
    >
    > Access Denied
    > Corrupt File
    > Unable to Attach
    > Job was Aborted
    > Insufficient Memory
    > The Media Operations was Aborted
    > Drive Not Responding
    > Lost Connection
    >
    >Ray Zorz wrote:
    >
    >> BE7.01. Backup worked fine, verify seemed to work fine, but job status

    showed
    >> FAILED. Backup log file also says failed, but doesn't say why.

    >



+ Reply to Thread