cancel
Showing results for 
Search instead for 
Did you mean: 

Warning bptm cannot update image database to add completed fragment

Titus_Bandugula
Level 4
Certified
Hello All,
 
Since the past two days most of our backups fail with Status 13 - file read failed.
Symantec TSE is unable to figure out the issue. They blame the N/W for this.
We use 1GB N/W ports on our master (Solaris 10) and media (Netbackup Appliance 5520/media server).
We had ran the SAS network analyzer which showed that the N/W is being higly utilized but no packet loss.
We use single Ethernet Card and dedicated N/W ports for the Netbackup Servers.
I couldn't find anything helpful to resolve this issue.
NBU version : - 7.5.06 on Master/Media and Most clients
Please HELP !!
 
DETAILED JOB STATUS: -
 
03/19/2014 11:18:07 - Info nbjm (pid=1509) starting backup job (jobid=1941780) for client WTHTMGSR02.KAUST.EDU.SA, policy PRD_HV20, schedule PRD_HV20_INCR
03/19/2014 11:18:08 - estimated 68675742 kbytes needed
03/19/2014 11:18:08 - Info nbjm (pid=1509) started backup (backupid=WTHTMGSR02.KAUST.EDU.SA_1395217087) job for client WTHTMGSR02.KAUST.EDU.SA, policy PRD_HV20, schedule PRD_HV20_INCR on storage unit stu_disk_bthpat5p10
03/19/2014 11:18:09 - started process bpbrm (pid=1866)
03/19/2014 11:18:11 - Info bpbrm (pid=1866) WTHTMGSR02.KAUST.EDU.SA is the host to backup data from
03/19/2014 11:18:11 - Info bpbrm (pid=1866) reading file list from client
03/19/2014 11:18:11 - Info bpbrm (pid=1866) starting bpbkar on client
03/19/2014 11:18:11 - connecting
03/19/2014 11:18:11 - connected; connect time: 0:00:00
03/19/2014 11:18:33 - Info bpbkar (pid=13292) Backup started
03/19/2014 11:18:33 - Info bpbrm (pid=1866) bptm pid: 1889
03/19/2014 11:18:34 - Info bpbkar (pid=13292) CONTINUE BACKUP received.
03/19/2014 11:18:34 - Info bptm (pid=1889) start
03/19/2014 11:18:34 - Info bptm (pid=1889) using 262144 data buffer size
03/19/2014 11:18:34 - Info bptm (pid=1889) using 30 data buffers
03/19/2014 11:18:35 - Info bptm (pid=1889) start backup
03/19/2014 11:18:36 - Info bptm (pid=1889) backup child process is pid 1897
03/19/2014 11:18:36 - begin writing
03/19/2014 11:22:57 - Info bptm (pid=1889) waited for full buffer 3225 times, delayed 14981 times
03/19/2014 11:24:28 - Warning bptm (pid=1889) cannot update image database to add completed fragment, error = file read failed
03/19/2014 11:24:29 - Info bptm (pid=1889) EXITING with status 13 <----------
03/19/2014 11:24:30 - Error bpbrm (pid=1866) db_flist_complete failed: no entity was found (227) WTHTMGSR02.KAUST.EDU.SA PRD_HV20 1 1395217087
03/19/2014 11:24:30 - Info bthpat5p10 (pid=1889) StorageServer=PureDisk:bthpat5p10; Report=PDDO Stats for (bthpat5p10): scanned: 2874379 KB, CR sent: 235593 KB, CR sent over FC: 0 KB, dedup: 91.8%
03/19/2014 11:24:31 - Critical bpbrm (pid=1866) unexpected termination of client WTHTMGSR02.KAUST.EDU.SA
03/19/2014 11:24:31 - Info bpbkar (pid=0) done. status: 13: file read failed
03/19/2014 11:24:31 - end writing; write time: 0:05:55
file read failed  (13)
 
1 ACCEPTED SOLUTION

Accepted Solutions

Titus_Bandugula
Level 4
Certified

Hello All,

 

The issue is resolved.

There was a Network problem in out environment which caused the Status 13.

View solution in original post

5 REPLIES 5

Marianne
Level 6
Partner    VIP    Accredited Certified

Seems nobody wanted to attempt a reply....

My guess is that the answer should be in one (or more) of the following logs:

bpbkar on client
bptm and bpbrm on media server (appliance).

My guess is that you have already provided level 5 logs to Symantec engineer.
I am not going to offer to sift through these logs as level 5 logs are normally massive and difficult to open on a Windows laptop with 'normal' text editors.

If this case has not yet been resolved and you want to upload zipped files, I am sure one of our Connect friends may be willing to have a look the logs.

revarooo
Level 6
Employee

What's the case number?

 

Deb_Wilmot
Level 6
Employee Accredited Certified

I'm curious - did you ever get a solution to this?  If so- what was it?  If not - what's the case ID?

 

Titus_Bandugula
Level 4
Certified

Hello All,

 

The issue is resolved.

There was a Network problem in out environment which caused the Status 13.

Deb_Wilmot
Level 6
Employee Accredited Certified

Thanks for the follow-up!  Hopefully the resolution will help others.