Video Screencast Help

Parent job of SAP Backup failing with status code 6

Created: 07 Sep 2013 | 2 comments
Jecintha's picture

Hello,

We have our master server running on Windows 2008 and the version of Netbackup is 7.5.0.5 For a particular client server, a linux machine (Linux 2.6.32-220.el6.x86_64) with the Netbackup version of 7.5, the parent job of SAP DB backup is failing with status code 6. All the child jobs are getting completed successfully.  Previously, we encounted backup failure in this server and the cause was error in the brtools.  Now, we see some log updates in bpbrm and suspect that to be the cause, but not sure of the action that needs to be taken.  The log entries are as under:

09:45:36.650 [2312.4904] <2> logparams: -backup -S hydesm001 -c PGERPDEV -ct 17 -ru root -cl TCS_HYD_PGCIL_19.147 -sched Daily -bt 1378527336 -dt 0 -st 0 -b PGERPDEV_1378527336 -mediasvr hydesm001 -jobid 74950 -jobgrpid 74950 -masterversion 750000 -maxfrag 0 -bpstart_time 1378527636 -p 0 -use_ofb -use_otm -jm -secure 1 -kl 90 -rg other -nfsok -hadb -connect_options 16974338
09:45:36.650 [2312.4904] <2> verify_client: bpbrm.c.37873: *connect_opts: 16974338 16974338 0x01030202
09:45:36.650 [2312.4904] <2> read_client: ?
09:45:36.650 [2312.4904] <2> read_client: opendir() failed: PGERPDEV: No such file or directory (2)
09:45:36.650 [2312.4904] <2> read_client: ?
09:45:36.650 [2312.4904] <2> read_client: opendir() failed: PGERPDEV: No such file or directory (2)
09:45:36.650 [2312.4904] <2> verify_client: bpbrm.c.37939: db_getCLIENT failed for CLIENT: PGERPDEV
09:45:36.650 [2312.4904] <2> verify_client: bpbrm.c.38105: db_getCLIENT failed: 227 227 0x000000e3
09:45:36.650 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\146\fb3d7f46+0,1,a,0,1,0+pgerpdev.txt
09:45:36.650 [2312.4904] <2> bpbrm start_bpcd_stat: bpbrm.c.22003: bpcd_client: PGERPDEV
09:45:36.650 [2312.4904] <2> bpbrm start_bpcd_stat: bpbrm.c.22006: bpcd_client_hostname: PGERPDEV
09:45:36.650 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\146\fb3d7f46+veritas_pbx,1,400,2,1,0+pgerpdev.txt
09:45:36.650 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\08d\e505688d+0,1,a,0,1,0+10.11.19.147.txt
09:45:36.650 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\146\fb3d7f46+vnetd,1,400,2,1,0+pgerpdev.txt
09:45:36.666 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\146\fb3d7f46+bpcd,1,400,2,1,0+pgerpdev.txt
09:45:37.961 [2312.4904] <2> vnet_pbxConnect: pbxConnectEx Succeeded
09:45:37.976 [2312.4904] <2> logconnections: BPCD CONNECT FROM 10.11.11.201.63087 TO 10.11.19.147.1556 fd = 796
09:45:37.976 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\08d\e505688d+veritas_pbx,1,400,2,1,0+10.11.19.147.txt
09:45:37.976 [2312.4904] <8> file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\08d\e505688d+vnetd,1,400,2,1,0+10.11.19.147.txt

I have also attached the logs for any further information.  Request you to help me and guide me how to proceed here.

Regards,

Jecintha

Operating Systems:

Comments 2 CommentsJump to latest comment

Nicolai's picture

Take a look at the severity level of the messages

<2> debug info

<8> Warning

<16> Error

<32>  Severe Error 

Normal <16> and <32> are event where Netbackup will fail - but the bpbrm snippet you provided does not show any error or severe errors.

The output from brtool did show :

Backup of </oracle/PED/sapdata2/sr3_11/sr3.data11> is failed due to <Error 150 : Server Status: termination requested by administrator>.

Status 150 usually mean the Netbackup administrator killed the backup.

The "BRBACKUP completed successfully with warnings" is normal if the previous backup failed.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Jecintha's picture

My apologies... I had uploaded a wrong attachment.   I have now attached the bpbrm logs and I can see the errors posted in my orginal post here. 

AttachmentSize
090713.txt 8.14 MB