status 84 The request could not be performed because of an I/O device error. (1117 - Veritas Net Backup

This is a discussion on status 84 The request could not be performed because of an I/O device error. (1117 - Veritas Net Backup ; Hi Guys, I have a problem i am facing with backups failing with status code 84, i have a NB 6.0 Ent server (windows) connected on SAN, and an HP Library also 6XXX series also on SAN, backing up HP-Unix ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: status 84 The request could not be performed because of an I/O device error. (1117

  1. status 84 The request could not be performed because of an I/O device error. (1117


    Hi Guys,


    I have a problem i am facing with backups failing with status code 84, i
    have a NB 6.0 Ent server (windows) connected on SAN, and an HP Library also
    6XXX series also on SAN, backing up HP-Unix servers file backups.

    All the connections are working fine, when setting up policies the first
    jobs succeeds but after that the same jobs starts failing with status 84...........then
    when i remove backup selections from the policy and then renter backup selections
    and re-run job it completes....very strange behaviour ...anyone have an idea
    if this is a known bug???? i have MP2 on master and v 6.0 basic on clients....


    here is what i got from bptm logs.... any response would be aprreciated:


    12:18:43.671 [1436.2864] <2> io_ioctl: command (0)MTWEOF 0 from (overwrite.c.249)
    on drive index 0
    12:18:43.671 [1436.2864] <2> get_drive_path: SCSI coordinates {3,0,2,1},
    dos_path \\.\Tape0, pnp_path ---
    12:18:43.671 [1436.2864] <2> io_close: closing C:\Program Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000,
    from overwrite.c.264
    12:18:43.671 [1436.2864] <2> openTpreqFile: tpreq_file: C:\Program Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000,
    serial_num: HU10617HM7
    12:18:43.671 [1436.2864] <2> get_drive_path: SCSI coordinates {3,0,2,1},
    dos_path \\.\Tape0, pnp_path ---
    12:18:43.671 [1436.2864] <2> check_serial_num: serial number match for drive
    with SCSI coordinates {3,0,2,1}, dos_path \\.\Tape0, drive serial number
    HU10617HM7, expected serial number HU10617HM7
    12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates {3,0,2,1})
    configured with blocksize 0
    12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates {3,0,2,1})
    has compression enabled
    12:18:43.703 [1436.2864] <2> io_open: SCSI RESERVE
    12:18:43.703 [1436.2864] <2> io_open: file C:\Program Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000
    successfully opened (mode 2)
    12:18:43.703 [1436.2864] <2> tape_error_rec: spacing to EOD for error recovery
    12:18:43.718 [1436.2864] <2> tape_error_rec: absolute block position at EOD
    is 456545
    12:18:43.718 [1436.2864] <2> tape_error_rec: locating to absolute block number
    456544 for error recovery
    12:18:43.734 [1436.2864] <2> tape_error_rec: absolute block position after
    read position is 456544
    12:18:43.734 [1436.2864] <2> signal_parent: set bpbrm media ready event (pid
    = 2656)
    12:18:43.750 [1436.2864] <2> write_data: write of 65536 bytes indicated only
    0 bytes were written, err = 1117
    12:18:43.750 [1436.2864] <2> db_error_add_to_file: dberrorq.c:midnite = 1162321200
    12:18:43.750 [1436.2864] <4> write_data: WriteFile failed with: The request
    could not be performed because of an I/O device error. (1117); bytes written
    = 65536; size = 0
    12:18:43.750 [1436.2864] <2> signal_parent: set bpbrm media ready event (pid
    = 2656)
    12:18:43.750 [1436.2864] <2> write_data: attempting write error recovery,
    err = 1117
    12:18:43.750 [1436.2864] <2> tape_error_rec: error recovery to block 456544
    requested
    12:18:43.750 [1436.2864] <2> tape_error_rec: attempting error recovery, delay
    3 minutes before next attempt, tries left = 3
    12


  2. Re: status 84 The request could not be performed because of an I/O device error. (1117

    Hello,

    Did I have the same problem at a customer, how solve it?

    Thanks,

    nova a pensé très fort :
    > Hi Guys,
    >
    >
    > I have a problem i am facing with backups failing with status code 84, i
    > have a NB 6.0 Ent server (windows) connected on SAN, and an HP Library also
    > 6XXX series also on SAN, backing up HP-Unix servers file backups.
    >
    > All the connections are working fine, when setting up policies the first
    > jobs succeeds but after that the same jobs starts failing with status
    > 84...........then when i remove backup selections from the policy and then
    > renter backup selections and re-run job it completes....very strange
    > behaviour ...anyone have an idea if this is a known bug???? i have MP2 on
    > master and v 6.0 basic on clients....
    >
    >
    > here is what i got from bptm logs.... any response would be aprreciated:
    >
    >
    > 12:18:43.671 [1436.2864] <2> io_ioctl: command (0)MTWEOF 0 from
    > (overwrite.c.249) on drive index 0
    > 12:18:43.671 [1436.2864] <2> get_drive_path: SCSI coordinates {3,0,2,1},
    > dos_path \\.\Tape0, pnp_path ---
    > 12:18:43.671 [1436.2864] <2> io_close: closing C:\Program
    > Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000, from
    > overwrite.c.264 12:18:43.671 [1436.2864] <2> openTpreqFile: tpreq_file:
    > C:\Program Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000,
    > serial_num: HU10617HM7 12:18:43.671 [1436.2864] <2> get_drive_path: SCSI
    > coordinates {3,0,2,1}, dos_path \\.\Tape0, pnp_path ---
    > 12:18:43.671 [1436.2864] <2> check_serial_num: serial number match for drive
    > with SCSI coordinates {3,0,2,1}, dos_path \\.\Tape0, drive serial number
    > HU10617HM7, expected serial number HU10617HM7
    > 12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates
    > {3,0,2,1}) configured with blocksize 0
    > 12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates
    > {3,0,2,1}) has compression enabled
    > 12:18:43.703 [1436.2864] <2> io_open: SCSI RESERVE
    > 12:18:43.703 [1436.2864] <2> io_open: file C:\Program
    > Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000
    > successfully opened (mode 2) 12:18:43.703 [1436.2864] <2> tape_error_rec:
    > spacing to EOD for error recovery 12:18:43.718 [1436.2864] <2>
    > tape_error_rec: absolute block position at EOD is 456545
    > 12:18:43.718 [1436.2864] <2> tape_error_rec: locating to absolute block
    > number 456544 for error recovery
    > 12:18:43.734 [1436.2864] <2> tape_error_rec: absolute block position after
    > read position is 456544
    > 12:18:43.734 [1436.2864] <2> signal_parent: set bpbrm media ready event (pid
    > = 2656)
    > 12:18:43.750 [1436.2864] <2> write_data: write of 65536 bytes indicated only
    > 0 bytes were written, err = 1117
    > 12:18:43.750 [1436.2864] <2> db_error_add_to_file: dberrorq.c:midnite =
    > 1162321200 12:18:43.750 [1436.2864] <4> write_data: WriteFile failed with:
    > The request could not be performed because of an I/O device error. (1117);
    > bytes written = 65536; size = 0
    > 12:18:43.750 [1436.2864] <2> signal_parent: set bpbrm media ready event (pid
    > = 2656)
    > 12:18:43.750 [1436.2864] <2> write_data: attempting write error recovery,
    > err = 1117
    > 12:18:43.750 [1436.2864] <2> tape_error_rec: error recovery to block 456544
    > requested
    > 12:18:43.750 [1436.2864] <2> tape_error_rec: attempting error recovery, delay
    > 3 minutes before next attempt, tries left = 3
    > 12




  3. Re: status 84 The request could not be performed because of an I/O device error. (1117


    My forte is giving inexact answers. Having stated that, here's what you can
    try.

    Check networking. Stop-and-go (ie. networking errors) can show up as SCSI
    errors. Check using ftp or copying files and verify that the speed is what
    you'd expect for your speed.

    2) Check your SCSI drive outside of NBU and make sure it's writing at full
    speed. Replace cartridge before doing it.

    3) MP4


    Eric Hartmann wrote:
    >Hello,
    >
    >Did I have the same problem at a customer, how solve it?
    >
    >Thanks,
    >
    >nova a pensé très fort :
    >> Hi Guys,
    >>
    >>
    >> I have a problem i am facing with backups failing with status code 84,

    i
    >> have a NB 6.0 Ent server (windows) connected on SAN, and an HP Library

    also
    >> 6XXX series also on SAN, backing up HP-Unix servers file backups.
    >>
    >> All the connections are working fine, when setting up policies the first
    >> jobs succeeds but after that the same jobs starts failing with status


    >> 84...........then when i remove backup selections from the policy and

    then
    >> renter backup selections and re-run job it completes....very strange
    >> behaviour ...anyone have an idea if this is a known bug???? i have MP2

    on
    >> master and v 6.0 basic on clients....
    >>
    >>
    >> here is what i got from bptm logs.... any response would be aprreciated:
    >>
    >>
    >> 12:18:43.671 [1436.2864] <2> io_ioctl: command (0)MTWEOF 0 from
    >> (overwrite.c.249) on drive index 0
    >> 12:18:43.671 [1436.2864] <2> get_drive_path: SCSI coordinates {3,0,2,1},
    >> dos_path \\.\Tape0, pnp_path ---
    >> 12:18:43.671 [1436.2864] <2> io_close: closing C:\Program
    >> Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000, from


    >> overwrite.c.264 12:18:43.671 [1436.2864] <2> openTpreqFile: tpreq_file:


    >> C:\Program Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000,


    >> serial_num: HU10617HM7 12:18:43.671 [1436.2864] <2> get_drive_path: SCSI


    >> coordinates {3,0,2,1}, dos_path \\.\Tape0, pnp_path ---
    >> 12:18:43.671 [1436.2864] <2> check_serial_num: serial number match for

    drive
    >> with SCSI coordinates {3,0,2,1}, dos_path \\.\Tape0, drive serial number
    >> HU10617HM7, expected serial number HU10617HM7
    >> 12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates
    >> {3,0,2,1}) configured with blocksize 0
    >> 12:18:43.687 [1436.2864] <2> init_tape: \\.\Tape0 (SCSI coordinates
    >> {3,0,2,1}) has compression enabled
    >> 12:18:43.703 [1436.2864] <2> io_open: SCSI RESERVE
    >> 12:18:43.703 [1436.2864] <2> io_open: file C:\Program
    >> Files\VERITAS\NetBackup\db\media\tpreq\drive_HP.UL TRIUM3-SCSI.000
    >> successfully opened (mode 2) 12:18:43.703 [1436.2864] <2> tape_error_rec:


    >> spacing to EOD for error recovery 12:18:43.718 [1436.2864] <2>
    >> tape_error_rec: absolute block position at EOD is 456545
    >> 12:18:43.718 [1436.2864] <2> tape_error_rec: locating to absolute block


    >> number 456544 for error recovery
    >> 12:18:43.734 [1436.2864] <2> tape_error_rec: absolute block position after
    >> read position is 456544
    >> 12:18:43.734 [1436.2864] <2> signal_parent: set bpbrm media ready event

    (pid
    >> = 2656)
    >> 12:18:43.750 [1436.2864] <2> write_data: write of 65536 bytes indicated

    only
    >> 0 bytes were written, err = 1117
    >> 12:18:43.750 [1436.2864] <2> db_error_add_to_file: dberrorq.c:midnite

    =
    >> 1162321200 12:18:43.750 [1436.2864] <4> write_data: WriteFile failed with:


    >> The request could not be performed because of an I/O device error. (1117);


    >> bytes written = 65536; size = 0
    >> 12:18:43.750 [1436.2864] <2> signal_parent: set bpbrm media ready event

    (pid
    >> = 2656)
    >> 12:18:43.750 [1436.2864] <2> write_data: attempting write error recovery,
    >> err = 1117
    >> 12:18:43.750 [1436.2864] <2> tape_error_rec: error recovery to block 456544
    >> requested
    >> 12:18:43.750 [1436.2864] <2> tape_error_rec: attempting error recovery,

    delay
    >> 3 minutes before next attempt, tries left = 3
    >> 12

    >
    >



+ Reply to Thread