09-12-2016 03:44 AM
NBU Master: Win 2012 R2 / 64 Bit
Master Version: 7.7.1
Java Console Version: 7.7.1
Location from where java console accessing : Locally on Master.
I am facing issue with NBU jave console. Cannot make new policy and alos cannot make changes to existign policies. Everting it showing error "Time out" " In the background service requesting is runnning". But after a long time 2 to 4 minutes the modification are applying followed by timeout error.
java console is accessed with same name mentioned in the bp.conf file.
NBSL logs not showing any timeout . But some trust errors are showing. unfortunately i dont have the logs to paste here.
The issue happened quite recently before that it was fine.
Did a server reboot but not worked.
Other thing noticed are:
When ping with server name it returns with IP VER 6 status. it is not resolving to name. returns the mac id of the NIC.
A local host file entry mentioned with master IP and corresponding FQDN and without FQDN.
No server patches applied in between these days. or any other Netbackup changes.
The prior java console versions are found in the start menu location under seperate folder.
Please help...
Solved! Go to Solution.
09-26-2016 05:38 AM
The issue resolved after settign TCPIP registry value "KeepAliveTime" set to to 240000 on master/media. we have a firwall between master and media.
This fix is a gift when try to resolve the SQL backup failure which was failing with status code 636.
09-12-2016 05:24 AM
Hi,
Follow this technote to do some performance improvements.
http://www.veritas.com/docs/000036374
Also,can you try install the Java console on other Client and try to do some operation.
Regards
09-12-2016 06:14 AM
Hi rfdalgo,
Forgot to metion earlier i already tried tuning the bp.setconf but not helped with parametres mentioned the technote. Also tried accessign using the java console of a media server in the same netbackup domain but was givig same problem.
09-26-2016 05:38 AM
The issue resolved after settign TCPIP registry value "KeepAliveTime" set to to 240000 on master/media. we have a firwall between master and media.
This fix is a gift when try to resolve the SQL backup failure which was failing with status code 636.