Backup job doesn't start - Veritas Backup Exec

This is a discussion on Backup job doesn't start - Veritas Backup Exec ; Job was running ok for a long time then it failed because the drive required cleaning. I ran a cleaning tape then cancelled the Active Alert. From then on it hasn't run a backup although the job says "Ready". I ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Backup job doesn't start

  1. Backup job doesn't start


    Job was running ok for a long time then it failed because the drive required
    cleaning. I ran a cleaning tape then cancelled the Active Alert. From then
    on it hasn't run a backup although the job says "Ready". I haven't had a
    backup for 3 days so I am really concerned. Can Someone please help. Thanks

  2. Re: Backup job doesn't start

    Things to check:

    Make sure the scheduler is enabled in the BE Admin Console.

    Make sure the server time is correct and that the job is scheduled
    correctly (AM vs PM).

    Look to see if your drive is disabled or paused in the BE Admin
    Console.

    See if you can insert a tape then use the Utilities menu to eject it.
    That will confirm you can still communicate with the drive.

    If none of that pans out, if the drive is external and there only one
    instance of the SCSI driver loaded, shut down BE, unload the SCSI
    driver, power-cycle the tape drive, then reload the SCSI driver and
    restart BE.

    If you have more than one instance of the SCSI driver loaded, you can
    still do this but you need to be sure to unload the correct instance of
    the driver. LIST STORAGE ADAPTERS at the server console. Note the
    adapter instance that has the tape drive listed under it. The output
    will look some like:

    0x11 [V512-A0-D0] Adaptec Controller in slot

    Note the 'A0' in the brackets. That's the adapter instance ID. If you
    have the same driver loaded re-entrantly, you will see A1 for the
    second instance, A2 for the third, etc.

    To unload a specific instance of the driver, REMOVE STORAGE ADAPTER Ax
    (where 'x' is the number of the driver instance). Then power-cycle
    your tape drive, etc.

    This method can sometimes get your tape drive talking again without
    having to resort to a reboot. Having said that, if this method doesn't
    work, your next step is to power down both the server and the tape
    drive, then restart.

    If a complete restart still doesn't let your jobs run, then the problem
    is within BE.

    -Barry.



+ Reply to Thread