We are using DLT 7000 drive, but the errors below are related to the
images in the NBU database.  Its been two days since this happened now,
and the two classes affected with this problem haven't backed up
anything in their incrementals, although I know they have new data in
them--but they return a status code 0.  As of this morning, I'm getting
the same errors as my previous post.

Thanks,

RCA


"Humphries; Douglas" wrote:
> 
>  What type of drives are you using?  We had problems doing restores from
> backups which seemed to have run successfully but got bad image header
> errors when doing the restores.  We are using STK9840 drives.  I never had
> this problem with DLT7k drives.  I got zero help from either Veritas or STK
> on this issue.
> 
> -----Original Message-----
> From: McMurphy, Tim
> To: Veritas NBU
> Sent: 10/18/00 5:29 PM
> Subject: RE: [Veritas-bu] NBU database problem/bad image header
> 
> How is your db backup? You may have to use it.
> 
> -----Original Message-----
> From: RYAN C. ANDERSON [mailto:ryan_anderson AT udlp DOT com]
> Sent: Wednesday, October 18, 2000 3:19 PM
> To: Veritas NBU
> Subject: [Veritas-bu] NBU database problem/bad image header
> 
> I have a problem relating to the previous thread about the NBU
> database.  Below is the output of bpadm --> reports --> problems.
> Unbeknownst to me, an admin had tried a restore on a very large server
> with many small files yesterday.  He had chosen a large range of dates
> and the filesystem where the NBU db filled up.  Its otherwise just fine
> being in a more compressed state.  We recompressed the files, but now,
> I've gotten these errors below and am not sure what to make of it.  I
> searched through the mailing list archives and NBU newsgroup on this
> issue, and didn't find too much, but someone had suggested using '#
> bpdbm -consistency' might fix the problem.
> 
> The files its cacking on are all 0 length and were created at the time
> the filesystem filled up.  Any thoughts?
> 
> Thanks,
> 
> RCA
> 
> ===================================================================
> 
> info.../usr/openv/netbackup/db/images/faithful/0932000000/tyr_therest_09
> 3221
> 6789_FULL
> 10/17/00 23:59:40 faithful -  cannot get image
> 
> info.../usr/openv/netbackup/db/images/faithful/0971000000/heimdall_P_int
> eg_0
> 971500172_FULL
> 10/17/00 23:59:40 faithful -  cannot get image
> 
> info.../usr/openv/netbackup/db/images/faithful/0971000000/heimdall_P_int
> eg_0
> 971500172_FULL
> 10/17/00 23:59:43 faithful -  cannot get image
> 
> info.../usr/openv/netbackup/db/images/faithful/0932000000/tyr_therest_09
> 3221
> 6789_FULL
> 10/18/00 03:16:01 faithful -  Bad image header:
> tyr_therest_0932216789_FULL
> 10/18/00 03:16:06 faithful -  Bad image header:
> heimdall_P_integ_0971500172_FULL
> 10/18/00 05:13:17 faithful -  Bad image header:
> tyr_therest_0932216789_FULL
> 10/18/00 05:13:23 faithful -  Bad image header:
> heimdall_P_integ_0971500172_FULL
> 10/18/00 10:24:45 faithful -  Bad image info in
> 
> /usr/openv/netbackup/db/images/faithful/0971000000/heimdall_P_integ_0971
> 5001
> 72_FULL
> 
> Ryan C. Anderson        |   United Defense L.P.
> Unix Administrator      |   763.572.6684 (desk)
> ryan_anderson AT udlp DOT com  |   612.235.9936 (pager)