The Netbackup Legacy Client Service (bpinetd) terminates unexpectedly.
This can be problematic if Accelerator is configured for use. This will cause Accelerator jobs to fail the Accelerator piece of the job. The job as a whole will continue to run, but without the benefit of Accelerator.
The problem can be observed in the Application Event Log.
08/05/2013 14:06:12 - Info bpbkar (pid=7800) change journal enabled for <D:\>
08/05/2013 14:06:12 - Info bpbkar (pid=7800) NOT using change journal data for <D:\>: unable to locate journal data
Application Event log:
Tue Aug 5 2013 14:03:03 Windows Error Reporting I1001 Fault bucket ,
Event Name: APPCRASH
Response: Not available
Cab Id: 0
bpinetd is crashing while cleaning up VSS snapshots that were created by NetBackup as part of a backup. Since it was crashing, it might not have cleaned them up. No serious problems will happen if they are not cleaned up but this could be a waste of disk space and/or slow down VSS. This will, however interfere with proper Accelerator driven logic and such jobs will conclude without the benefit of Accelerator.
The formal resolution for this issue (Etrack 3199748) is included in the following releases:
- NetBackup 7.5 Maintenance Release 7 (18.104.22.168)
- NetBackup 7.6.Maintenance Release 2 (22.214.171.124)
NetBackup 126.96.36.199 is now available - download links and information can be found in the Related Article linked below.
NetBackup 188.8.131.52 is now available - download links and information can be found in the Related Article linked below.
If this issue is experienced, please contact Symantec technical support, referencing this document and Etrack 3289848 to obtain an Emergency Engineering Binary (EEB) replacement for bpinetd.exe for NetBackup 184.108.40.206 containing a fix for this issue.