Video Screencast Help

Error Backup MSDP (network connection broken(40))

Created: 19 Apr 2014 | 4 comments

After the first backup full completed with successfully (MSDP) the second backup finished with status (network connection broken(40))

Master-Server : 7.5.0.6 (Linux)

Media-Server : 7.5.0.6 (linux) MSDP

Client : 7.5.0.6 - HP-UX 11

17/04/2014 16:26:51 - Info bpbrm(pid=11271) starting bpbkar on client         
17/04/2014 16:26:51 - Info bpbkar(pid=28018) Backup started           
17/04/2014 16:26:51 - Info bpbrm(pid=11271) bptm pid: 11272          
17/04/2014 16:26:52 - Info bptm(pid=11272) start            
17/04/2014 16:26:52 - Info bptm(pid=11272) using 1048576 data buffer size        
17/04/2014 16:26:52 - Info bptm(pid=11272) using 64 data buffers         
17/04/2014 16:26:52 - Info bptm(pid=11272) start backup           
17/04/2014 16:26:54 - Info bptm(pid=11272) backup child process is pid 11289      
17/04/2014 16:29:47 - started process bpbrm (11271)
17/04/2014 16:29:51 - connecting
17/04/2014 16:29:52 - connected; connect time: 00:00:01
17/04/2014 16:29:54 - begin writing
17/04/2014 16:37:08 - Error bptm(pid=11272) media manager exiting because bpbrm is no longer active    
17/04/2014 16:37:09 - Info bptm(pid=11272) EXITING with status 174 <----------  
     
17/04/2014 16:37:12 - Info xxxxxx (pid=11272) StorageServer=PureDisk:xxxxxx; Report=PDDO Stats for (xxxxxx): scanned: 24917337 KB, CR sent: 26655 KB, CR sent over FC: 0 KB, dedup: 99.9%
network connection broken(40)

Operating Systems:
Discussion Filed Under:

Comments 4 CommentsJump to latest comment

Giri_S's picture

Please paste the output of bpps -x from media server. (Other backups working from same media server?)

Netbackup Admin (Unix)

msanches's picture

Hi Gary, Thanks for attention...

Below the command bpps

 

[root@brslp1pupbk01 bin]# ./bpps -x
NB Processes
------------
root      8032 21316  0 10:46 ?        00:00:00 /usr/openv/netbackup/bin/admincmd/bpstsinfo -DPSPROXY
root      8127 20756  0 10:47 ?        00:00:00 [bpcd] <defunct>
root     20747     1  0 Apr09 ?        00:00:02 /usr/openv/netbackup/bin/vnetd -standalone
root     20756     1  0 Apr09 ?        00:00:02 /usr/openv/netbackup/bin/bpcd -standalone
root     20908     1  0 Apr09 ?        00:03:33 /usr/openv/pdde/pdcr/bin/spad
pddb     21137     1  0 Apr09 ?        00:00:00 /usr/openv/pdde/pddb/bin/postmaster -D /bkp_nbu_dedup/databases/pddb/data -N 512 -B 1024 -i -p10085
root     21259     1  8 Apr09 ?        23:19:46 /usr/openv/pdde/pdcr/bin/spoold
root     21300     1  0 Apr09 ?        00:00:00 /usr/openv/netbackup/bin/bpcompatd
root     21316     1  0 Apr09 ?        00:00:30 /usr/openv/netbackup/bin/nbrmms
root     21371     1  0 Apr09 ?        00:08:25 /usr/openv/netbackup/bin/nbsl
root     21422     1  0 Apr09 ?        00:00:32 /usr/openv/netbackup/bin/nbcssc -a NetBackup
root     21446     1  0 Apr09 ?        00:00:31 /usr/openv/netbackup/bin/nbsvcmon

MM Processes
------------
root     20419 21280  0 09:38 ?        00:00:00 rdevmi -sockfd 13 -p 50 -r
root     21274     1  0 Apr09 ?        00:00:12 /usr/openv/volmgr/bin/ltid
root     21280     1  0 Apr09 ?        00:00:09 vmd
root     21312 21274  0 Apr09 ?        00:00:00 tldd
root     21368 21274  0 Apr09 ?        00:00:53 avrd

Shared Symantec Processes
-------------------------
root     19465     1  0 Apr09 ?        00:00:04 /opt/VRTSpbx/bin/pbx_exchange

[root@brslp1pupbk01 bin]# ./bpps -a
NB Processes
------------
root      8032 21316  0 10:46 ?        00:00:00 /usr/openv/netbackup/bin/admincmd/bpstsinfo -DPSPROXY
root      8127 20756  0 10:47 ?        00:00:00 [bpcd] <defunct>
root     20747     1  0 Apr09 ?        00:00:02 /usr/openv/netbackup/bin/vnetd -standalone
root     20756     1  0 Apr09 ?        00:00:02 /usr/openv/netbackup/bin/bpcd -standalone
root     20908     1  0 Apr09 ?        00:03:33 /usr/openv/pdde/pdcr/bin/spad
pddb     21137     1  0 Apr09 ?        00:00:00 /usr/openv/pdde/pddb/bin/postmaster -D /bkp_nbu_dedup/databases/pddb/data -N 512 -B 1024 -i -p10085
root     21259     1  8 Apr09 ?        23:19:49 /usr/openv/pdde/pdcr/bin/spoold
root     21300     1  0 Apr09 ?        00:00:00 /usr/openv/netbackup/bin/bpcompatd
root     21316     1  0 Apr09 ?        00:00:30 /usr/openv/netbackup/bin/nbrmms
root     21371     1  0 Apr09 ?        00:08:25 /usr/openv/netbackup/bin/nbsl
root     21422     1  0 Apr09 ?        00:00:32 /usr/openv/netbackup/bin/nbcssc -a NetBackup
root     21446     1  0 Apr09 ?        00:00:31 /usr/openv/netbackup/bin/nbsvcmon

MM Processes
------------
root     20419 21280  0 09:38 ?        00:00:00 rdevmi -sockfd 13 -p 50 -r
root     21274     1  0 Apr09 ?        00:00:12 /usr/openv/volmgr/bin/ltid
root     21280     1  0 Apr09 ?        00:00:09 vmd
root     21312 21274  0 Apr09 ?        00:00:00 tldd
root     21368 21274  0 Apr09 ?        00:00:53 avrd

SymTerry's picture

A status 174 means an abnormal condition caused a tape manager (bptm) or disk manager (bpdm) failure. 

What we will need to see is the logging from both bpbrm and bptm with the logging turned up. There is not enough information provided to determine what's going on.

msanches's picture

Hi, SymTerry

Attached logs informed for you

The backup that finished with error was started in 27 and 28/03

 

AttachmentSize
bpdm.rar 26.27 KB
bptm.rar 7.74 MB