02-21-2008 02:23 AM
02-21-2008 03:59 AM
02-21-2008 07:52 AM
02-21-2008 08:56 AM
02-21-2008 11:54 AM
07-29-2008 06:12 AM
I just upgraded from 6.5 to 6.5.2A and had the same problem with my clients caching and taking a long time to load in the right pane. I made the changes in nbj.conf, but still have to wait 2 or 3 minutes for them to appear. Here is my nbj.conf file settings. I remarked the original settings. Any suggestions?
BPJAVA_PORT=13722
VNETD_PORT=13724
NBJAVA_CONNECT_OPTION=1
NBJAVA_CLIENT_PORT_WINDOW=0 0
INSTALL_PATH=/usr/openv/java
#INITIAL_MEMORY=36M
INITIAL_MEMORY=256M
#MAX_MEMORY=256M
MAX_MEMORY=1024M
MEM_USE_WARNING=80
#FORCE_IPADDR_LOOKUP=1
FORCE_IPADDR_LOOKUP=0
USE_NBJAUTH_WITH_ENHAUTH=0
NBJAVA_CORBA_DEFAULT_TIMEOUT=60
NBJAVA_CORBA_LONG_TIMEOUT=1800
07-29-2008 03:50 PM
you can try this:
Increase memory buffers on java client
Open the java folder and find "Setconf.bat" RIGHT click and edit this file. Find the set of lines as shown below. (Yours may look a little different but the same lines will exist)
SET INITIAL_MEMORY=36M
SET MAX_MEMORY=256M
SET MEM_USE_WARNING=80
SET NBJAVA_CONNECT_OPTION=1
SET NBJAVA_CLIENT_PORT_WINDOW=0 0
SET FORCE_IPADDR_LOOKUP=0
SET USE_NBJAUTH_WITH_ENHAUTH=0
SET BPJAVA_PORT=13722
SET VNETD_PORT=13724
REM SET NBJAVA_CORBA_DEFAULT_TIMEOUT=60
REM SET NBJAVA_CORBA_LONG_TIMEOUT=1800
SET NBJDIR=%INSTALL_PATH%
SET VXSSATLIBPATH=%VXSSAT_INSTALL_PATH%\bin
SET JAVALIBPATH=%NBJDIR%;%VXSSATLIBPATH%
Now Change the Following lines :
OLD
SET INITIAL_MEMORY=36M
SET MAX_MEMORY=256M
SET FORCE_IPADDR_LOOKUP=1
NEW
SET INITIAL_MEMORY=128M
SET MAX_MEMORY=512M
SET FORCE_IPADDR_LOOKUP=0
Save and Close the file. Now reopen Netbackup Java 6.5 and enjoy loading the client list in a minute or two tops.
09-21-2008 10:26 AM
Hi All,
I am facing the same issue but not via Java console but it's the NBU Admin Console...
Anyone has solution to this issue?
Cheers,
Bclee
09-22-2008 10:09 PM
my issue has been resolved!!! it's due to a decommissioned media server which did not properly decommissioned... Hence during console startup, it's trying to hunt for the decommissioned server... that's y it's taking a long time.
09-23-2008 11:23 AM