Veritas-bu

[Veritas-bu] ERROR 213

2002-04-02 08:15:12
Subject: [Veritas-bu] ERROR 213
From: MarelP AT AUSTRALIA.Stortek DOT com (Marelas, Peter)
Date: Tue, 2 Apr 2002 23:15:12 +1000
It looks more like the header on the media has been
overwritten. Netbackup reports logical
errors as read/write errors which gives people the impression that
the media is bad or the drive is bad (which in my experience
is rarely the case) as opposed to the data on tape not being the
size netbackup expects or structured as netbackup expects (i.e. media
label in first block).

If you mount the tape using tpmount and dd the first block to
a file and view that file you should be able to verify whether
the header has been corrupted (overwritten with data).

Regards
Peter Marelas

-----Original Message-----
From: Daniel Teklu [mailto:DanielT AT ilx DOT com]
Sent: Tuesday, 2 April 2002 5:56 AM
To: 'larry.kingery AT veritas DOT com'
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] ERROR 213


Larry,

Yep..You are right..my drive was down..I brought it UP now..but I have
another pbm..Error 85..did my drive go bad?..I cleaned it a couple of days
ago.

Thanks

here is my bptm log:



14:34:54 [27149] <2> vmdb_query_byID_getpool: server returned:  1 21
NetBackup ANYHOST -1 -2 Main Pool

14:34:54 [27149] <2> select_media: selected media id DG0002 for backup,
backup1(rl = 1) <----------
14:34:54 [27149] <2> mount_open_media: Waiting for mount of media id DG0002
on server backup1.
14:37:26 [27149] <2> io_open: file
/usr/openv/netbackup/db/media/tpreq/DG0002 successfully opened
14:37:26 [27149] <2> write_backup: media id DG0002 mounted on drive index 0,
drivepath /dev/rmt/0mbn, drivename
 Drive0
14:37:26 [27149] <2> io_read_media_header: drive index 0, reading media
header, buflen = 32768, buff = 0x3d5dc0
14:37:26 [27149] <2> io_ioctl: command (5)MTREW 1 from (bptm.c.4691) on
drive index 0
14:38:48 [27149] <16> io_read_media_header: read error on media id DG0002,
drive index 0, reading header block,
 I/O error
14:38:48 [27149] <2> log_media_error: successfully wrote to error file -
04/01/02 14:38:48 DG0002 0 READ_ERROR
14:38:48 [27149] <2> check_error_history: called from bptm line 10939,
EXIT_Status = 85
14:38:48 [27149] <2> check_error_history: drive index = 0, media id =
DG0002, time = 04/01/02 14:38:48, both_ma
tch = 0, media_match = 0, drive_match = 0
14:38:48 [27149] <2> io_close: closing
/usr/openv/netbackup/db/media/tpreq/DG0002, from bptm.c.10202
14:38:48 [27149] <2> tpunmount: tpunmount'ing
/usr/openv/netbackup/db/media/tpreq/DG0002
14:38:48 [27149] <2> bptm: EXITING with status 85 <----------




-----Original Message-----
From: Larry Kingery [mailto:larry.kingery AT veritas DOT com]
Sent: Monday, April 01, 2002 1:54 PM
To: Daniel Teklu
Subject: Re: [Veritas-bu] ERROR 213


Have you restarted NBU after adding the storage units?

What do 

  tpconfig -l -d

  bpstulist -L

provide?

-- 
Larry Kingery 
           Proofread carefully to see if you any words out.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>