Down tape drive at 80% - Veritas Net Backup

This is a discussion on Down tape drive at 80% - Veritas Net Backup ; What does the "all logs" report when the drive is down'd? create /usr/openv/netbackup/logs/bptm and check that log too. also stopltid and then restart with ltid -v and then check system logs. Tom Buskey wrote: >everytime I try to do a ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Down tape drive at 80%

  1. Re: Down tape drive at 80%


    What does the "all logs" report when the drive is down'd?
    create /usr/openv/netbackup/logs/bptm and check that log too.
    also stopltid and then restart with ltid -v and then check system logs.

    Tom Buskey wrote:
    >everytime I try to do a backup, the tape drive gets downed.
    >
    >I'm using NB Datacenter 3.4 on Solaris 8 with a ADIC Scalar 220 with a
    >sony AIT-2 drive.
    >
    >Any clues?
    >



  2. Down tape drive at 80%

    everytime I try to do a backup, the tape drive gets downed.

    I'm using NB Datacenter 3.4 on Solaris 8 with a ADIC Scalar 220 with a
    sony AIT-2 drive.

    Any clues?


  3. Re: Down tape drive at 80%

    Bob Stump wrote:
    > What does the "all logs" report when the drive is down'd?
    > create /usr/openv/netbackup/logs/bptm and check that log too.
    > also stopltid and then restart with ltid -v and then check system logs.
    >


    /usr/openv/netbackup/logs/bptm:

    16:30:01 [4110] <16> io_terminate_tape: FREEZING media id 000284, too
    many data
    blocks written, check tape/driver block size configuration


    16:30:01 [4110] <2> log_media_error: successfully wrote to error file -
    05/28/03 16:30:01 000284 0 WRITE_ERROR
    16:30:01 [4110] <2> check_error_history: called from bptm line 13536,
    EXIT_Status = 84
    16:30:02 [4110] <2> check_error_history: drive index = 0, media id =
    000284, time = 05/28/03 16:30:01, both_match = 0, media_match = 0,
    drive_match = 4
    16:30:02 [4110] <2> tpunmount: tpunmount'ing
    /usr/openv/netbackup/db/media/tpreq/000284
    16:30:02 [4110] <2> TpUnmountWrapper: SCSI RELEASE
    16:30:02 [4110] <2> getsockconnected: host=babel service=bpdbm
    address=xx.xx.xx.xx protocol=tcp non-reserved port=xxxxx
    16:30:02 [4110] <8> check_error_history: DOWN'ing drive index 0, it has
    had at least 5 errors in last 12 hour(s)
    16:30:02 [4110] <2> bptm: EXITING with status 84 <----------


  4. Re: Down tape drive at 80%

    lucky you

    http://seer.support.veritas.com/docs/248548.htm

    --
    Ramzaidi Abdul Rahaman
    Sn System Engineer
    Ruhas Technology Sdn Bhd
    03 7660 7540 / 012 284 5121
    "Tom Buskey" wrote in message news:3ed51bc2@hronntp01....
    > Bob Stump wrote:
    > > What does the "all logs" report when the drive is down'd?
    > > create /usr/openv/netbackup/logs/bptm and check that log too.
    > > also stopltid and then restart with ltid -v and then check system logs.
    > >

    >
    > /usr/openv/netbackup/logs/bptm:
    >
    > 16:30:01 [4110] <16> io_terminate_tape: FREEZING media id 000284, too
    > many data
    > blocks written, check tape/driver block size configuration
    >
    >
    > 16:30:01 [4110] <2> log_media_error: successfully wrote to error file -
    > 05/28/03 16:30:01 000284 0 WRITE_ERROR
    > 16:30:01 [4110] <2> check_error_history: called from bptm line 13536,
    > EXIT_Status = 84
    > 16:30:02 [4110] <2> check_error_history: drive index = 0, media id =
    > 000284, time = 05/28/03 16:30:01, both_match = 0, media_match = 0,
    > drive_match = 4
    > 16:30:02 [4110] <2> tpunmount: tpunmount'ing
    > /usr/openv/netbackup/db/media/tpreq/000284
    > 16:30:02 [4110] <2> TpUnmountWrapper: SCSI RELEASE
    > 16:30:02 [4110] <2> getsockconnected: host=babel service=bpdbm
    > address=xx.xx.xx.xx protocol=tcp non-reserved port=xxxxx
    > 16:30:02 [4110] <8> check_error_history: DOWN'ing drive index 0, it has
    > had at least 5 errors in last 12 hour(s)
    > 16:30:02 [4110] <2> bptm: EXITING with status 84 <----------
    >




+ Reply to Thread