bpbkar32.exe faults on DFSR backup jobs of NetBackup 7.5.0.x Windows clients.

  • Modified Date:
  • Article ID:000087564


This problem has been observed on NetBackup 7.5.0.x Windows clients.

Full backups of the DFSR content finish successfully, but Incrementals fail with status code 13 (file write failed) reported once bpbkar32.exe produces an application fault on the client.


Error Message

The Activity Monitor will show the job failed with Status Code 13 - with job details similar to these:

11/6/2012 8:42:14 PM - Error bpbrm(pid=12152) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
11/6/2012 8:42:22 PM - Info MyClient(pid=2856) StorageServer=PureDisk:MyServer; Report=PDDO Stats for (MyServer): scanned: 2050069 KB, CR sent: 84510 KB, CR sent over FC: 0 KB, dedup: 95.9%
11/6/2012 8:42:22 PM - Error bpbrm(pid=12152) could not send server status message
11/6/2012 8:42:25 PM - end writing; write time: 00:03:17
file read failed(13)

The Windows Client will show an Application Event Log message similar to the following:

Tue Nov 6 2012 20:42:12 Application Error E1000 Faulting application name: bpbkar32.exe, version: 7.500.412.916, time stamp: 0x5055e1c4
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0x40000015
Fault offset: 0x00000000000761c9
Faulting process id: 0x1200
Faulting application start time: 0x01cdbc910bc18678
Faulting application path: C:\Program Files\VERITAS\NetBackup\bin\bpbkar32.exe
Faulting module path: C:\Windows\system32\MSVCR100.dll



When the combination of DFSR, Shadow Copy Components and True Image Restore with Move Detection are used together, it can cause a problem with how the TIR stream attempts to register itself in the NetBackup catalog.  There is an unexpected result which causes bpbkar32.exe to produce an application fault.



The formal resolution for this issue (Etrack 2985558) is included in the following release:

  • NetBackup 7.5 Maintenance Update 6 (

NetBackup is now available - please access the Related Article below for more information.

A workaround for this issue is to discontinue the use of TIR with Move Detection within the Policy backing up DFSR data.

If the workaround is not acceptable, please contact Symantec Support, referencing this document and Etrack 2985395 to obtain an Emergency Engineering Binary (EEB) replacement library containing a fix for this issue.

Applies To

This problem may occur if either the ALL_LOCAL_DRIVES or Shadow Copy Components:\ entries are specified in the Backup Selections of the policy AND Enable TIR with Move Detection is enabled in the Policy Attributes.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)