Netbackup MS SQL backup Client hold (parent killed) and can’t new backup. (spawn Application-Backup jobs after the parent job was canceled by the administrator) NBU 6.5.3

** Myself
From Task manager
dbbackex.exe (child process from bp process of netbackup)


Cant’ killed

Can’t change template backup file
From Enterprise Manager See SQL process mapping one to one with Netbackup child process.

Select process -> kill process
Refresh view


Check process again
Kill process from window task

If denied kill by command

For Window 2K use kill –f <PID>    "# force kill
#kill command available with the Windows Resource Kit

Run Backup again
Document ID: 311957
http://support.veritas.com/docs/311957
Netbackup for Microsoft SQL Server backup continues to spawn Application-Backup jobs after the parent job was canceled by the administrator
To stop the MS-SQL-Server backup, end the dbbackex.exe processes on the client using Windows Task Manager:
1) Log onto the client and open Task Manager (Shift+Ctrl+Esc) 
2) Open the Processes tab, enable "show processes from all users" 
3) End all "dbbackex.exe" processes
Details:
Bug: 1411637
Exact Error Message:
No error message shown in the NetBackup logs.
Symptom(s):
During an MS SQL backup using the NetBackup 6.5.2 MS SQL Agent, if one or more of the databases in the backup list cannot be backed up due to configuration issues that prevents the database from being backed up, immediately after the SQL Server has returned an error to dbbackex.exe, the backup will stop executing and hang until either the Job is canceled or it times out, reporting a status code 41 (network connection timed out).
Log Files:
On the MS SQL Client, in the NetBackup Database Extension | File | View Status window, it can be observed that the job will have stopped executing immediately after failing to back up the Database. In the example log below, Operation #1 and #4 succeeded before Operation #5 failed. No further processing will take place subsequent to Operation #5 failing:
09:30:51 INF - Beginning backup on server sapr3 of client silver
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]12 percent processed.>.
INF - SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]21 percent processed.>
INF - SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]31 percent processed.>
INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]41 percent processed.>.
INF - SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]51 percent processed.>
INF - SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]60 percent processed.>
INF - Thread has been closed for stripe #0
ERR - Error in GetConfiguration: 0x80770003.
   CONTINUATION: - The api was waiting and the timeout interval had elapsed.
DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3002><[Microsoft][SQL Native Client][SQL Server]Cannot BACKUP or RESTORE a database snapshot.>.
DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]BACKUP DATABASE is terminating abnormally.>
ERR - Error found executing <backup database "BEDB_Snapshot_first" to VIRTUAL_DEVICE='VNBU0-10092-10012-1222244789' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.
ERR - Error in VDS->Close: 0x80770004.
   CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #5 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\YUKON_ALL.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 301(0) seconds.
09:31:44 INF - Server status = 0
INF - OPERATION #1 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\YUKON_ALL.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 333(0) seconds
INF - Thread has been closed for stripe #0
INF - OPERATION #4 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\YUKON_ALL.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 395(0) seconds
After the job has been canceled or has timed out, the dbbackex.exe process on the MS SQL Client will still be listed as running in Task Manager. If several MS SQL backups have failed, an identical number ofdbbackex.exe instances will be listed in Task Manager. These can safely be killed.
The reason for the hang is that the error message returned by the SQL Server is not being handled bydbbackex.exe.
The correct behavior in such a situation is that dbbackex.exe should skip the database and continue to back up the remaining databases.  
Workaround:
No workarounds are available.
ETA of Fix:
Symantec Corporation has acknowledged that the above-mentioned issue (Etrack 1411637)  is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers. This issue is addressed in the following patch release:
· NetBackup 6.5 Release Update 4 (6.5.4)
NetBackup 6.5.4 is released, please visit the following link for download and readme information