Rob, 

We do have regular filesystem backups made for the nbu db, so we're
covered there.  To get these 2 classes 
Well, I went ahead and deleted the zero-length files that NBU was
cacking on, and I was able to run successful backups with no 'bad image
header' error messages.  I'll see if there is any difference in what is
there now in the /usr/openv/netbackup/db/(hostname)/...  directory that
I modified and the last good backup before the incident.  Otherwise
everything appears fine now.

Thanks much,

RCA

Rob Worman wrote:
> 
> Ryan-
> 
> the bad news:
> As you have probably already concluded, you have database corruption - it
> happened because your NBU database filesystem filled up while NBU was trying 
> to
> write catalog data about ongoing backups.  It even appears as if this 
> corruption
> is preventing ongoing backups from working?
> 
> the good news:
> It's not hard to fix, it just might take awhile to track down the corrupted
> files.
<snip>
> 
> So fixing the corruption means tracking down the hosed files and restoring 
> them
> (if possible) or deleting them (and if indeed your current corruption is 
> causing
> problems in getting backups to run, then I'd first get those corrupted files 
> out
> of your images DB, get your backups to run, and then tackle the restoration
> process)
> 
> does this make sense?
> 
> rob