Error bptm (pid=129776) media manager terminated by parent process

[Jeff10]

 I am getting multiple backups failing with the following error message.

03/07/2017 08:57:45 - Info nbjm (pid=12473) no response from BPCD on client=dhs-scom-sql2, jobid=2016553

03/07/2017 09:08:17 - Error bpbrm (pid=43679) socket read failed: errno = 110 - Connection timed out

03/07/2017 09:08:17 - Error bptm (pid=43709) system call failed - Connection timed out (at child.c.1306)

03/07/2017 09:08:17 - Error bptm (pid=43709) unable to perform read from client socket, connection may have been broken

03/07/2017 09:08:17 - Error bptm (pid=43685) media manager terminated by parent process

03/07/2017 09:08:47 - Info dhs-lmdc-nb01 (pid=43685) StorageServer=PureDisk:dhs-lmdc-nb01; Report=PDDO Stats for (dhs-lmdc-nb01): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled

03/07/2017 09:08:47 - Info dbclient (pid=3884) done. status: 13: file read failed

03/07/2017 09:08:47 - end writing; write time: 0:16:02

file read failed  (13)

I cna't find any solutions, any help or ideas would be appriecated.

Jeff 

[Tousif]

Hello,

It seems to be network issue. Enable the bpbrm (Media) and bpbkar (client) verbose 5 logging and system log.

Rerun the backup and review the log for more information.

Also you can do the below test:

Check VSS writer status on client (Windows)

Run the bpbkar null test against backup selection.

Increase the client read timeout to 7200 - 9200

Run the small file backup for that client check if it work.

Try to take backup from alternate media server.

Some time this kind of issue get resolved by reboot the client server.

Thanks & Regards,

[Marianne]

bpbrm timed out and terminated bptm as a result.
So, the actual error is bpbrm that reported status 13.

Increase client connect and client read timeouts on the media server to 1800.

Create log folders for further troubleshooting.
On media server: bptm and bpbrm
On SQL client: bpcd and dbclient

[BVshet]

Hi,

This failure is impacting only teh SQL agent based backups or even the file system backups ?

If the File system backups are working I would suggest checking both forward and reverse name resolution and check if the media server can communicate with the client.

Try bptestbpcd -debug -verbose.

[Jeff10]

this is happening on the file system backups also.

[Jeff10]

silly question but what kind of errors or failures am i looking for in the logs?  

[Marianne]

I would start with bpbrm log for the 7th and trace PID 43679.

Here is a post where I explained how I read logs:

https://vox.veritas.com/t5/NetBackup/How-to-use-logs/m-p/447331#M98462

If you want to, you can copy logs to .txt files (e.g. bpbrm.txt) and upload as attachments.

If you want to hide actual hostnames and IPs, you may want to do a search and replace, e.g:
replace <master-server-name> with Master, <master-server-IP> with 10.10.10.1
replace <media-server-name> with Media1, <media-server-IP> with 10.10.10.2
replace <SQL-client-name> with Client1, <SQL-client-IP> with 10.10.10.3

If you upload a new bpbrm file, then please post ALL text in Details tab of failed job.