BE 9.1 job on hold - Veritas Backup Exec

This is a discussion on BE 9.1 job on hold - Veritas Backup Exec ; Hi all, we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6. It worked for weeks now, but since friday the backup job is put on hold permanently. We've changed nothing, the job on friday started and ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: BE 9.1 job on hold

  1. BE 9.1 job on hold

    Hi all,

    we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6. It worked for weeks now, but since friday the backup job is put on hold permanently. We've changed nothing, the job on friday started and then was aborted. The job log of this backup is empty! No message.

    The job was then put on hold and everytime we try to ready it, it is put on hold again. We tried deleting the history dir and we deleted to jobqueue. We created a new job, we restarted the server. Nothing helped, we can't get a job in ready status.

    Ideas anyone?

    Marco

  2. Re: BE 9.1 job on hold


    is the drive enabled? perhaps its showing as disconnected which would make
    it exhibit this behavior.

    "Marco =?ISO-8859-1?B?QnL8Y2s=?=" wrote:
    >Hi all,
    >
    >we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6. It worked for

    weeks now,
    >but since friday the backup job is put on hold permanently. We've changed

    nothing,
    >the job on friday started and then was aborted. The job log of this backup

    is empty!
    >No message.
    >
    >The job was then put on hold and everytime we try to ready it, it is put

    on hold again.
    >We tried deleting the history dir and we deleted to jobqueue. We created

    a new job,
    >we restarted the server. Nothing helped, we can't get a job in ready status.
    >
    >Ideas anyone?
    >
    >Marco



  3. Antw: Re: BE 9.1 job on hold

    yes, the drive is enabled

    >>> Dullo Donnerstag, 5. Mai 2005 16:32:22 >>>


    is the drive enabled? perhaps its showing as disconnected which would make
    it exhibit this behavior.

    "Marco =?ISO-8859-1?B?QnL8Y2s=?=" wrote:
    >Hi all,
    >
    >we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6. It worked for

    weeks now,
    >but since friday the backup job is put on hold permanently. We've changed

    nothing,
    >the job on friday started and then was aborted. The job log of this backup

    is empty!
    >No message.
    >
    >The job was then put on hold and everytime we try to ready it, it is put

    on hold again.
    >We tried deleting the history dir and we deleted to jobqueue. We created

    a new job,
    >we restarted the server. Nothing helped, we can't get a job in ready status.
    >
    >Ideas anyone?
    >
    >Marco





  4. Re: BE 9.1 job on hold

    Marco
    > we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6.
    > It worked for weeks now, but since friday the backup job
    > is put on hold permanently. We've changed nothing, the
    > job on friday started and then was aborted.
    > The job log of this backup is empty! No message.
    >
    > The job was then put on hold and everytime we try to ready
    > it, it is put on hold again. We tried deleting the history
    > dir and we deleted to jobqueue. We created a new job, we
    > restarted the server. Nothing helped, we can't get a job
    > in ready status.


    Is the scheduler paused at all? If you look in the NetWare
    Administration Console, what's the "Media Server Status" (top left
    corner) reported as?
    Do you have any antivirus software loaded? If so, is it set to exclude
    the \BKUPEXEC directory?

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

  5. Antw: Re: BE 9.1 job on hold

    Hi,

    don't know what the staus of the scheduler was, but the AV NLM wasn't set to exclude the BE directory. I changed that and I installed BE from scratch, because the customer didn't want to wait for an other solution. Now it runs fine, but I still wonder what caused the error...


    Marco

    >>> Michael Mittwoch, 18. Mai 2005 15:31:08 >>>

    Marco
    > we're using BE 9.1 with a Tandberg SDLT 320 on NW 5.1 SP6.
    > It worked for weeks now, but since friday the backup job
    > is put on hold permanently. We've changed nothing, the
    > job on friday started and then was aborted.
    > The job log of this backup is empty! No message.
    >
    > The job was then put on hold and everytime we try to ready
    > it, it is put on hold again. We tried deleting the history
    > dir and we deleted to jobqueue. We created a new job, we
    > restarted the server. Nothing helped, we can't get a job
    > in ready status.


    Is the scheduler paused at all? If you look in the NetWare
    Administration Console, what's the "Media Server Status" (top left
    corner) reported as?
    Do you have any antivirus software loaded? If so, is it set to exclude
    the \BKUPEXEC directory?

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *



  6. Re: Antw: Re: BE 9.1 job on hold

    Marco
    > don't know what the staus of the scheduler was, but the AV NLM
    > wasn't set to exclude the BE directory. I changed that and I
    > installed BE from scratch, because the customer didn't want to
    > wait for an other solution. Now it runs fine, but I still
    > wonder what caused the error...


    Probably the Antivirus software scanning the BE directory. It interferes
    with the jobqueue files - see:
    http://seer.support.veritas.com/docs/251332.htm

    Michael
    --
    "If it jams, force it. If it breaks, you probably
    needed a new one anyway"

    * Please post replies via the newsgroup *

+ Reply to Thread