Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Media\s+write\s+error\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Veritas\-bu\]\s+Media\s+write\s+error\s*$/: 12 ]

Total 12 documents matching your query.

1. [Veritas-bu] media write error (score: 1): Author: kumar appan <kumarav100 AT gmail DOT com> (kumar appan); Date: Tue, 7 Jun 2005 09:47:41 +0400; Hi, We got the error as media write failed while backing up the client m/c .Looking at the the medialist summary , that media state is frozen .Is there anyway to recover the data from that media and; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-06/msg00074.html (10,376 bytes)
2. [Veritas-bu] media write error (score: 1): Author: Mark.Donaldson AT cexp DOT com (Mark.Donaldson AT cexp DOT com); Date: Tue, 7 Jun 2005 10:06:33 -0600; Frozen means that no further writes will go to the tape. It's still readable (unless the mechanism is trashed). First check if there's images on it: "bpimmedia -mediaid <tapenum>". No images? No worr; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2005-06/msg00080.html (11,678 bytes)
3. [Veritas-bu] Media Write Error (score: 1): Author: Simon.WEAVER AT astrium-space DOT com (WEAVER, Simon); Date: Wed, 7 Aug 2002 06:55:47 +0100; Guys As you may know, my Master Server blue screened yesterday. Firstly thanks for the fix on removing the killed job - worked seamlessly :) I am a little concerned that I am now getting media write; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-08/msg00078.html (11,371 bytes)
4. [Veritas-bu] Media Write Error (score: 1): Author: begrn AT wmdata DOT no (Grønås Bengt); Date: Wed, 7 Aug 2002 09:15:05 +0200; I am recirculating some previous answer: bpexpdate -d 0 -ev XXXXXX (the tape is erased of images) bpexpdate -deassignempty -ev XXXXXX (force return tapes that are deleted of images to available statu; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-08/msg00081.html (12,580 bytes)
5. [Veritas-bu] Media Write Error (score: 1): Author: Simon.WEAVER AT astrium-space DOT com (WEAVER, Simon); Date: Wed, 7 Aug 2002 11:51:19 +0100; Peter Ok an update for you: I am still getting STATUS 84 errors. Still unable to use bplabel command, but I did try a theory of mine to see if it would work. Here goes.... I removed the Barcode ID 08; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-08/msg00082.html (11,710 bytes)
6. [Veritas-bu] Media write error (score: 1): Author: ferbraga AT vento.com DOT br (ferbraga AT vento.com DOT br); Date: Thu, 3 Jan 2002 18:20:35 +0000; 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; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00024.html (14,291 bytes)
7. [Veritas-bu] Media write error (score: 1): Author: mike.powers AT abnamro DOT com (mike.powers AT abnamro DOT com); Date: Thu, 3 Jan 2002 13:18:44 -0600; 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.; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00027.html (14,964 bytes)
8. [Veritas-bu] Media write error (score: 1): Author: mike.powers AT abnamro DOT com (mike.powers AT abnamro DOT com); Date: Thu, 3 Jan 2002 15:34:03 -0600; Master/media server. Whoever controls the drives. Mike "ZIMMER, RANDY K [AG/1000]" <randy.k.zimmer AT monsanto DOT com> on 01/03/2002 01:57:52 PM do you do that on the master or the client? Randy Zim; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00032.html (16,016 bytes)
9. [Veritas-bu] Media write error (score: 1): Author: randy.k.zimmer AT monsanto DOT com (ZIMMER, RANDY K [AG/1000]); Date: Thu, 3 Jan 2002 13:57:52 -0600; 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 I have received 84 error when NB is backing up a lot of la; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00058.html (15,662 bytes)
10. [Veritas-bu] Media write error (score: 1): Author: bhalchandra.kelkar AT csfb DOT com (Kelkar, Bhalchandra); Date: Sun, 6 Jan 2002 17:19:38 +0800; In the master's bp.conf file. - cheers 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 I have received 84; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00065.html (17,516 bytes)
11. [Veritas-bu] Media write error (score: 1): Author: pawilhelm AT davidson DOT edu (Wilhelm, Patrick); Date: Fri, 18 Jan 2002 15:00:18 -0500; Perhaps you've solved your problem by now, but I was receiving 84 errors on our LTO drives that could not be isolated. Veritas indicated that an 84 error meaning that communication with the drive was; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00326.html (12,344 bytes)
12. [Veritas-bu] Media write error (score: 1): Author: briandiven AT northwesternmutual DOT com (briandiven AT northwesternmutual DOT com); Date: Fri, 18 Jan 2002 14:34:58 -0600; --openmail-part-39b0f579-00000002 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline ;Creation-Date="Fri, 18 Jan 2002 14:34:58 -0600" Content-Transfer-Encoding: quoted-printable; /usr/local/webapp/mharc-adsm.org/html/Veritas-bu/2002-01/msg00328.html (17,264 bytes)

Current List: 1 - 12
Page: [1]