In the master's bp.conf file.
- cheers
-----Original Message-----
From: ZIMMER, RANDY K [AG/1000] [mailto:randy.k.zimmer AT monsanto DOT com]
Sent: Friday, January 04, 2002 3:58 AM
To: 'mike.powers AT abnamro DOT com'; ferbraga AT vento.com DOT br
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Media write error
do you do that on the master or the client?
Randy Zimmer
Unix Technical Services
Office: (314) 694-3109
Pager: 800-340-8098
MonNet: 544-3109
-----Original Message-----
From: mike.powers AT abnamro DOT com [mailto:mike.powers AT abnamro DOT com]
Sent: Thursday, January 03, 2002 1:19 PM
To: ferbraga AT vento.com DOT br
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Media write error
I have received 84 error when NB is backing up a lot of large files. It
seems that NB would timout while reading a database dump file.
This was corrected by setting the CLIENT_READ_TIMEOUT in the bp.conf to a
larger number.
Mike
ferbraga AT vento.com DOT [email protected] on 01/03/2002 12:20:35 PM
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
To: veritas-bu AT mailman.eng.auburn DOT edu
cc:
Subject: [Veritas-bu] Media write error
I have sometimes a failed backup with error 84. It occurs after NBU have
done a lot of work in this class (more than 500GB). So, I don't suspect
drive error, drive configuration errors, or media type errors, like
Troubleshoot
Guide suggests. The medias are all new, and the drive is clean. This class
use a storage unit with two drives.
My master server is a Solaris8, Netbackup 3.4 with patch 34_2.
The media server, where the error occurs, is a Tru64 5.1 with the same
patch
level. The tape drive is a 9840FC. In this media server are another backups
running pretty well.
The bptm logs shows :
05:34:18 [474102] <2> bptm: INITIATING: -U
05:34:18 [474102] <2> db_byid: search for media id 000042
05:34:18 [474102] <2> db_byid: 000042 found at offset 84
05:34:18 [474102] <2> db_lock_media: unable to lock media at offset 84
(000042)
05:34:18 [474102] <2> bptm: EXITING with status 0 <----------
05:34:36 [470438] <2> signal_parent: sending SIGUSR1 to bpbrm (pid =
470410)
05:34:36 [470438] <2> write_data: attempting write error recovery, err =
5
05:34:36 [470438] <2> tape_error_rec: error recovery to block 73580
requested
05:34:36 [470438] <2> tape_error_rec: attempting error recovery, delay 3
minutes before next attempt, tries left = 5
.
.
.
05:37:36 [470438] <2> io_ioctl: command (0)MTWEOF 0 from (overwrite.c.395)
on drive index 0
05:37:36 [470438] <2> io_ioctl: MTWEOF failed during error recovery, I/O
error
05:37:36 [470438] <2> tape_error_rec: attempting error recovery, delay 3
minutes before next attempt, tries left = 4
.
.
.
05:49:36 [470438] <2> io_ioctl: command (0)MTWEOF 0 from (overwrite.c.395)
on drive index 0
05:49:36 [470438] <2> io_ioctl: MTWEOF failed during error recovery, I/O
error
05:49:36 [470438] <2> getsockconnected: host=casra-backserver2
service=bpdbm
address=172.18.100.54 protocol=tcp non-reserved port=13721
05:49:36 [470438] <2> bind_on_port_addr: bound to port 4657
05:49:36 [470438] <2> check_authentication: no authentication required
05:49:37 [470438] <16> write_data: cannot write image to media id 000042,
drive index 0, I/O error
05:49:37 [470438] <2> rewind_after_error: rewinding after EIO error
05:49:38 [475173] <2> bptm: INITIATING: -U
05:49:38 [475173] <2> db_byid: search for media id 000042
05:49:38 [475173] <2> db_byid: 000042 found at offset 84
05:49:38 [475173] <2> db_lock_media: unable to lock media at offset 84
(000042)
05:49:38 [475173] <2> bptm: EXITING with status 0 <----------
05:49:49 [470438] <2> rewind_after_error: tried 1 time(s) to perform rewind
05:49:49 [470438] <2> log_media_error: successfully wrote to error file
- 01/03/02 05:49:49 000042 0 WRITE_ERROR
05:49:49 [470438] <2> check_error_history: called from bptm line 12362,
EXIT_Status = 84
05:49:49 [470438] <2> check_error_history: drive index = 0, media id =
000042,
time = 01/03/02 05:49:49, both_match = 0, media_match = 0, drive_match =
0
05:49:49 [470438] <2> io_close: closing
/usr/openv/netbackup/db/media/tpreq/000042,
from bptm.c.10850
05:49:49 [470438] <2> tpunmount: tpunmount'ing
/usr/openv/netbackup/db/media/tpreq/000042
05:49:49 [470438] <2> bptm: EXITING with status 84 <----------
Any help will be welcome!!
Thanks in advanced
Fernando
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This message is for the named person's use only. It may contain sensitive and
private proprietary or legally privileged information. No confidentiality or
privilege is waived or lost by any mistransmission. If you are not the intended
recipient, please immediately delete it and all copies of it from your system,
destroy any hard copies of it and notify the sender. You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message
if you are not the intended recipient. CREDIT SUISSE GROUP and each legal
entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT
business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all
e-mail communications through its networks. Any views expressed in this message
are those of the individual sender, except where the message states otherwise
and the sender is authorized to state them to be the views of any such entity.
Unless otherwise stated, any pricing information given !
in this message is indicative o
nly, is subject to change and does not constitute an offer to deal at any price
quoted. Any reference to the terms of executed transactions should be treated
as preliminary only and subject to our formal written confirmation.
|
