I have a NT client that is rather large.  As in 200 GB and 1-2 million
files.  We have the backups broken into 4-5 backups so that the largest
backup, backs up about 40 GB.  All of our other NT clients seem to be
backing up fine, but they may also be smaller in size.  The client is
running version 3.1.5 which probably will not be able to be upgraded since
the master server is 3.1.1 and the Operations department has put my
requested upgrade on hold.  

I have checked the problem reports and the main error message that I keep
seeing is the following:

12/04/00 06:55:45 slhbackup slhfile1_ebn from cleint slhfile1_ebn: WRN -
can't open file:
F:\FalseRoot\Shares\Associate\a43180\WINWORD\CON.DOC
(WIN32 1009: The configuration registry database is corrupt.)

The NT administrators (I'm the Unix guy, and the master/media server is
running Unix) tell me that after noticing that the backups have problems
that the CPU is pegged on their machine.  They also tell me that the
culprits are bpbkar32.exe and bpinet.d.  But I think mostly bpbkar32.exe.

I am having the NT guy add all logging possible on the client, but he had
already used bpbkar logging and the only thing that I noticed alarming there
was 
12/01/00 02:25:47 AM: [184]: FTL - tar file write error (10053)
12/01/00 02:25:47 AM: [184]: INF - EXIT STATUS 14: file write failed
12/01/00 02:25:47 AM: [184]: INF - EXIT - status = 0

Any suggestions on what might be causing the problem?  This is the only NT
client that we are having continual problems.

Thanks,
Dan