cancel
Showing results for 
Search instead for 
Did you mean: 

NBSL is crashing during DNS resolution

pkatakdound
Level 5
Partner Accredited

Hi Team,

Approximately after 72 hrs I could not login into NetBackup Console. Facing Java and PBX related errors . We need to reboot master server and everything works fine till @72 hrs. Veritas Support concluded that we have 111 servers which are now not currently in the network causing this issue during their DNS resolution. DNS queries  associated with them crashing NBSL. Kindly suggest workaround OR solution regarding same.

 Check error in file attached

 

Regards

Prajyot Katakdound

 

 

 

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Tell us more about the "111 servers which are now not currently in the network".

What are their roles in NBU?
Media servers or clients?
Or a mix of both?

Don't think you can solve this in Netbackup as it sounds more like a DNS server/OS issue.

You maybe can migate part of the problem by setting Reverse Hostname Lookup to Prohibited under master server properties Network Settings

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

sdo
Level 6
Partner    VIP    Certified

Thiago_Ribeiro
VIP
Partner    VIP    Accredited

Hi

 

Can you check if some of then, may be applied in your case?

Is your environment in cluster?

https://www.veritas.com/support/en_US/article.000080775 - BUG REPORT: In all versions of NetBackup 7.7, nbsl may core dump if an invalid application cluster reference exists in the database

Are you trying to open NBU Console from Media Server?

https://www.veritas.com/support/en_US/article.000099899 - An Emergency Engineering Binary (EEB) is available for NetBackup 7.7.1 which resolves nbsl communication issues in the Java GUI

 

Regards,

 

Thiago

Mike_Gavrilov
Level 6
Partner    VIP    Accredited Certified

>Veritas Support concluded that we have 111 servers which are now not currently in the network causing this issue during their >DNS resolution. DNS queries  associated with them crashing NBSL.

What's the  reason to keep this "army of the dead"? Did you tune them off and planing to return them back? In your case workaround would take more time that actual deleting of all these records.