cancel
Showing results for 
Search instead for 
Did you mean: 

Error 0 General Ping of nbjm failed, communication lost

Gerald_W__Gitau
Level 6
Certified
Hi everyone,
 
I have got this problem now on its 3rd debut "General ping of nbjm failed, communication lost". It happens just after midnight when Full backups are running or about to run. The jobs that were already running hung, and other jobs that are supposed to run do not kick off. I have on previous occassion extracted nbsupport logs and sent them to Veritas but no satisfactory answer as to why it happens, what causes it and how to prevent it. Anybody who has experienced this??
 
NBU ver 6.0 MP4
Servers - WK3 STD Edition SP1
Clients - Mixed WK2, W3K, Unix, Linux
 
Note: Removal Storage Service has been disabled on master and media servers. The problem has never happened when only incrementals backups are running!!
 
 
 
 
 
2 REPLIES 2

nathan_Schmidt
Level 4
to fix this you will need post MP4 Binaries from backline engineering. I had the same problems with jobs ending with a status 50.
 
Check this out:
 
And let me know if this helps!
 
 
 

VERITAS NetBackup Enterprise Server

Release 6.0 MP4

DATE: February 2007

Contents

========

File Name Destination cksum

--------- -------------- -----

(x86)

nbpem.exe \netbackup\bin\ 3486007163

nbproxy.exe \netbackup\bin\ 1282748167

nbproxyreq.exe \netbackup\bin\admincmd\ 1659948976

nbjm.exe \netbackup\bin\ 2988885938

libVcnbac.dll \netbackup\bin\ 945268661

libnborb.dll \netbackup\bin\ 3450950604

" " \netbackup\bin\admincmd\ 3450950604

" " \volmgr\bin\ 3450950604

 

Installation process:

=====================

(only needs to occur on master server)

1) stop the NetBackup services

2) make a copy of the existing files that are being replaced

3) install the files listed above into the proper destination directory

NOTE: the new files must have the same permissions as the original ones!

(e.g. executable by root)

4) start the NetBackup services

New in this Fix:

================

(1) jobs continue to wait for resources even after the window is closed

(ET 858810)

(2) nbpem stops processing manual backup jobs when housekeeping is

running (bptm delete_expired)

(ET 857531)

(3) nbpem terminates after failing to get last backup image

(ET 860294)

(4) status 50 and 200 followed by a chain of hundreds of 200s

(ET 860273)

(5) Backup job failed with status 805 after nbpem coredumped - Post MP4.

(ET 860266)

(6) Jobs not running after upgrading to 6.0 MP4

(ET 857531)

(7) bperror reporting large number of bogus error messages

wrt scheduling even though jobs are finishing successfully

(ET 860790)

(8) Jobs are not kicking off when scheduled

(ET 933564)

(9) Jobs do not retry until all jobs associated with the parent complete

(ET 834130)

(10) nbpem memory leak when there are immediate backups and a high density

of clients per policy

(ET 846190)

(11) Msg queue 0x52455051 (pem reply queue) fills up when running

user backups that reports one error in pem

(ET 856242)

(12) nbpem core dump after successful backup

(ET 863109)

(13) differential backup of windows clients on multi-stream policy

performs full backup

(ET 915270)

(14) When the policy lists the client name in upper case, windows

backup uses WOFB even though clientDB entry disables WOFB.

(ET 922389)

(15) Multiple NetBackup binaries core dump after upgrading to 6.0 MP4

(ET 915879)

(16) bptm is stuck waiting for a resource request from nbjm,

nbjm is stuck waiting on a CORBA request

(ET 897092)

(17) nbpem core dump due to non thread-safe call to strcmp

(ET 936732)

(18) status 805 failures for resubmitted multistream jobs

using snapshots

(ET 899380)

(19) Hot Catalog Backup schedule never runs although due

(ET 970785)

===============================================================

Users of NetBackup should have a working knowledge of the following topics:

o NetBackup client and server software

 

System Prerequisites:

NetBackup Server and local client 6.0 MP4

Gerald_W__Gitau
Level 6
Certified
Thanks, will try it out. But it might be a while before I confirm if its working. The problem has occurred 3 times only since MP4 ugrade in December last year.