08-07-2017 10:15 PM
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
08-07-2017 11:45 PM
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?
08-08-2017 01:35 AM
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
08-08-2017 05:07 AM
08-08-2017 06:16 AM
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
08-09-2017 02:44 PM
>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.