Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SAP Backup exit status 6 & 25

Created: 04 Oct 2013 | 17 comments

Hi all,

There was a SAP backup failure in our environment with status code 6 for the parent job and one of the child job failed with status code 25. 

But when looking at the bphdb logs in the client, it showed the below errors:

BR0278E Command output of '/usr/sap/XX1/SYS/exe/run/backint -u XX1 -f backup -i /oracle/XX1/sapbackup/.bemfwyis.lst -t file_online -p /oracle/XX1/11202/dbs/initXX1.utl -c':

[12582] Error detected while reporting backup ids.
 
PFA the logs of bphdb. 
 
Operating Systems:

Comments 17 CommentsJump to latest comment

cs3472's picture

The job details log shows the below message for status code 25:

05-oct-2013 2:42:55 - Error bpbrm (pid=6528) listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1380927630.12582.prog.3

huanglao2002's picture

please check  /usr/openv/netbackup/logs/user_ops/ directory permission.

please reference 

http://www.symantec.com/docs/TECH8420

http://www.symantec.com/docs/TECH52446

cs3472's picture

The backups were running fine till yesterday and no modifications were done to this folder... Please find the permissions below:

drwxrwxrwx 5 root bin 96 Apr 12 2011 user_ops

Marianne's picture

Check bpbrm log on the media server. It could be a timeout. 

Client Connect and Client Read Timeouts on the media server should be at least 1800 (30 min) for large databases.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

cs3472's picture

Hi Marianne,

Both are set to already set to default and no changes made to those values...

Client read timeout =1800 

Marianne's picture

The default is 300 (5 min).  Timeout was just one possibility.

Please check media server bpbrm log as per my previous post.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

huanglao2002's picture

If database more and more large,the backup total time  large than the firewall time out.

cs3472's picture

Hi Marianne,

Sorry for the delay in repsonse. I see the below error message in the bpbrm log file in the master server

02:42:55.323 [6528] <2> bpcr_disconnect_rqst: bpcr failed reading disconnect message from client
02:42:55.323 [6528] <2> bpbrm send_info_via_progress_file: could not disconnect from bpcd on <client machine>
02:42:55.323 [6528] <2> bpbrm send_info_via_progress_file: could not close CLIENT_CMD_SOCK (9)
02:42:55.323 [6528] <16> bpbrm listen_for_client: listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1380927630.12582.prog.3

Marianne's picture

You did not mention exact NBU versions. Have a look at this TN that describes similar issue during restore:

http://www.symantec.com/docs/TECH125637

This TN also mentions TECH 164991 for the same situation during a backup, but that TN does not seem to exist.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

cs3472's picture

NBU master server version is 7.0.1

Client machine also same version

Marianne's picture

Have you had a look at the TN?

This issue was scheduled to be addressed in the following release:

NetBackup 7.1.0.3
NetBackup 7.5

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

cs3472's picture

Still I have this issue... Even though it will be addressed in NetBackup 7.1.0.3 & NetBackup 7.5

Is there a temp fix for this issue???

03:04:06.848 [205] <5> :  Backup of </oracle/XXX/sapdata2/sr3_7/sr3.data7> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3_12/sr3.data12> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3_15/sr3.data15> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3701_1/sr3701.data1> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata1/sysaux_1/sysaux.data1> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/origlogA/cntrl/cntrlXXX.dbf> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata2/sr3_7/sr3.data7> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3_12/sr3.data12> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3_15/sr3.data15> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata3/sr3701_1/sr3701.data1> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/sapdata1/sysaux_1/sysaux.data1> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.
03:04:06.849 [205] <5> :  Backup of </oracle/XXX/origlogA/cntrl/cntrlXXX.dbf> is failed due to <Error 0 : Server Status:  the requested operation was successfully completed>.

Error in the Job details log:

Error bpbrm (pid=28448) listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1381539701.205.prog.5.pcb_std

What details should I need to check in the bpbrm log file?

Marianne's picture

Look for <8> Warnings, <16> Error or <32> Severe Error, in bpbrm log for PID specific to this client's backup job(s).

Your other option is to log a call with Symantec Support and submit all relevant logs.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

cs3472's picture

These are the logs which are found in bpbrm folder at that particular moment is this:

03:03:56.221 [28448] <16> common_signal: Invalid parameters.
 

***************************

03:03:57.899 [28448] <16> bpbrm listen_for_client: listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1381539701.205.prog.5.pcb_std

***************************

03:03:57.902 [28448] <2> job_connect: Connected on port 59130
03:03:57.902 [28448] <2> set_job_details: Tfile (296321): LOG 1381539837 16 bpbrm 28448 listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1381539701.205.prog.5.pcb_std
03:03:58.040 [28448] <2> job_monitoring_exex: ACK disconnect
03:03:58.040 [28448] <2> job_disconnect: Disconnected
03:03:58.040 [28448] <4> db_error_add_to_file: listen for client protocol error - couldn't write necessary information on /usr/openv/netbackup/logs/user_ops/dbext/logs/vxbsa.1381539701.205.prog.5.pcb_std
03:03:58.042 [28448] <2> Bpbrm_siginfo_print: 0: delay 1 signo SIGUSR1:16 code -1 pid 28204
03:03:58.051 [28204] <2> Bpbrm_siginfo_print: 0: delay 0 signo SIGCHLD:18 code 1 pid 28448
03:03:58.052 [28204] <2> bpbrm brm_sigcld: bpbrm child 28448 exit_status = 25, signal_status = 0
03:03:58.052 [28204] <2> bpbrm brm_sigcld: child 28448 exited with status 25: cannot connect on socket

Marianne's picture

Full logs will be needed on media server and client to confirm if this is the same issue or not.

It will be best if you log a Support call with Symantec.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

CRZ's picture

I think Marianne nailed it above.

If this is a multiplexed backup, you could disable multiplexing.  That's about all you can do at the revision you're running, though, and it may take a lot longer (although that might be preferable to it not working at all).

Bottom line is you need to upgrade - there is no 7.0.1 EEB which will work around the issue described in the TechNotes.  This issue is resolved in 7.1.0.3 and above.  May I recommend 7.5.0.6? :)


bit.ly/76LBN | APPLBN | 75LBN