Welcome to the wonderful world of NetBackup vs. Emulex! Try the following touch file, which fixed our issue.
< install_dir >\ Volmgr\ database\ NO_SIXTEEN_BYTE_CDB See this technote for details (It didn't directly apply to our environment either, but it did fix the problem...) http://seer.support.veritas.com/docs/281312.htm Good luck, Kent Eagle MTS Infrastructure Engineer II, MCP, MCSE Tech Services / SMSS ---------------------------------------------------------------------- Message: 1 Date: Wed, 21 Mar 2007 14:11:00 -0400 From: "Hall, Christian N." <[EMAIL PROTECTED]> Subject: [Veritas-bu] Return code 84 To: "NB List Mail" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" All, Environment: Media server: Host: Windows 2003 SP1 Hardware HP DL380 G4 HBA TYPE: Emulex LP9802-E Emulex LightPulse LP9802 2 Gigabit PCI Fibre Channel Adapter WWN: 20:00:00:00:C9:3F:48:52 Diver version : 5-1.30A6; HBAAPI v2.2.b, 02-17-05 Firmware version: 1.91A5 Driver Name: elxstor STK Tape T9940B tape drive: Drive Type: sktt9940b Code Version: 1.35.412/4.08 Interface: Fiber STK Windows 2003 tape driver: Mfg: StorageTek Driver date: 2/26/2003 Driver version: 6.0.0.1 Veritas Netbackup 5.1MP6 Fabric: Silkworm 3800 code version Kernel: 5.4 Fabric OS: v3.2.1a Made on: Fri May 12 15:20:59 PDT 2006 Flash: Fri May 12 15:21:57 PDT 2006 BootProm: Tue Oct 30 10:24:38 PST 2001 I have a Windows 2003 media server that is getting constant 84s' when it attempts to write to media. The media is new, and other hosts can write to it. The Emulex drivers are storport with the required Microsoft hot fix but it still fails repeatedly. I have opened many cases with VERITAS, STK, SUN, Emulex but thay all seemed puzzled. Suggestions, or help would be greatly appreciated. Here is an excerpt from the BPTM log 01:14:45.188 [5628.1504] <2> write_data: absolute block position prior to writing backup header(s) is 2, copy 1 01:14:45.188 [5628.1504] <2> io_write_back_header: drive index 1, adc-enf-sls1_1174453694, file num = 1, mpx_headers = 0, copy 1 01:14:45.188 [5628.1504] <2> write_data: completed writing backup header, start writing data when first buffer is available, copy 1 01:14:45.188 [5628.1504] <2> write_data: first write, twin_index: 0 cindex: 0 dont_process: 1 wrote_backup_hdr: 1 finished_buff: 0 01:14:45.188 [5628.1504] <2> write_data: received first buffer (65536 bytes), begin writing data 01:14:50.312 [5628.1504] <2> write_data: write of 65536 bytes indicated only 0 bytes were written, err = 1 01:14:50.312 [5628.1504] <2> logconnections: bpdbm CONNECT FROM 172.19.5.41.3920 TO 172.29.2.14.13721 01:14:50.312 [5628.1504] <2> logconnections: BPDBM CONNECT FROM 172.19.5.41.3920 TO 172.29.2.14.13721 01:14:50.766 [5628.1504] <4> write_data: WriteFile failed with: Incorrect function. (1); bytes written = 65536; size = 0 01:14:50.766 [5628.1504] <2> is_possible_recoverable_error: not attempting error recovery, errno = 1 01:14:50.766 [5628.1504] <2> set_job_details: Done 01:14:50.766 [5628.1504] <2> logconnections: bpdbm CONNECT FROM 172.19.5.41.3921 TO 172.29.2.14.13721 01:14:50.766 [5628.1504] <2> logconnections: BPDBM CONNECT FROM 172.19.5.41.3921 TO 172.29.2.14.13721 01:14:51.203 [5628.1504] <16> write_data: cannot write image to media id HA0671, drive index 1, Incorrect function. 01:14:51.203 [5628.1504] <2> log_media_error: successfully wrote to error file - 03/21/07 01:14:51 HA0671 1 WRITE_ERROR 01:14:51.203 [5628.1504] <2> check_error_history: called from bptm line 17599, EXIT_Status = 84 01:14:51.203 [5628.1504] <2> check_error_history: drive index = 1, media id = HA0671, time = 03/21/07 01:14:51, both_match = 0, media_match = 0, drive_match = 0 01:14:51.203 [5628.1504] <2> io_close: closing C:\Program Files\VERITAS\NetBackup\db\media\tpreq/HA0671, from bptm.c.15695 01:14:51.203 [5628.1504] <2> tpunmount: tpunmount'ing C:\Program Files\VERITAS\NetBackup\db\media\tpreq/HA0671 01:14:51.203 [5628.1504] <2> get_tape_path: drive index 1, DOS name: \\.\Tape2, PnP name: \\?\scsi#sequential&ven_stk&prod_t9940b&rev_1.35#6&3 072439b&0&000300#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b} Thanks, Chris Hall Visit our website at www.wilmingtontrust.com Investment products are not insured by the FDIC or any other governmental agency, are not deposits of or other obligations of or guaranteed by Wilmington Trust or any other bank or entity, and are subject to risks, including a possible loss of the principal amount invested. This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
