Netbackup Error 636

Question

Hi All,&nbsp;I have backup failure on my Oracle DB. Please let me know what all the things i need to check.07/17/2017 23:12:07 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:12:51 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:13:30 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:14:01 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:14:30 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:15:56 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:21:43 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:26:25 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:33:59 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:36:37 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:39:04 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:41:29 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:42:42 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/17/2017 23:53:13 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:03:33 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:13:53 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:24:18 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:34:44 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:45:08 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 00:55:28 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 01:05:43 - Error bpbrm (pid=24538) could not write PING message to OUTSOCK07/18/2017 01:08:44 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:09:18 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:03 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:09 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:14 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:19 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:36 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:41 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:10:46 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:13:21 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:14:39 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:14:44 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:14:49 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:14:54 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:15:00 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:15:05 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:15:10 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:02 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:07 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:35 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:40 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:45 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:51 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:16:56 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:01 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:08 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:14 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:20 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:25 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK07/18/2017 01:17:35 - Error bpbrm (pid=24538) could not write FILE ADDED message to OUTSOCK&nbsp;Thanks,Nayab&nbsp;

thiago_ribeiro · Answer

Hi,For now, take a look this articles. Please tell us more about your environment.NBU version: Master/Media and ClientOS versionOracle versionhttps://vox.veritas.com/t5/NetBackup/Oracle-backups-failing-with-status-code-636/td-p/604262https://www.veritas.com/support/en_US/article.000018102&nbsp;Regards,&nbsp;Thiago

mr_shaik · Answer

NBU versionNBU Master:- 7.7.2NBU&nbsp; Media:-&nbsp;7.7.2&nbsp;( Media Server is client itself)OS version:- Linux 2.6.18-308.eI5 (Master &amp; Media)Oracle version:- 11g

marianne · Answer

Status 636 is most of the time caused by a firewall timeout between master and media server.
In addition to the links posted by&nbsp;Thiago_Ribeiro, have a look at these TNs for tcp_keepalive_time setting on Linux servers. This setting must be changed on master and media server.
https://www.veritas.com/support/en_US/article.TECH125896
https://www.veritas.com/support/en_US/article.TECH202675

Forum Discussion

Netbackup Error 636

3 Replies

Related Content

Error 636

Backup failure with error code 636

Error 636 only on FULL

Inactive TCP session - error 636 (firewall)

Backup failure with error code 636

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date