The "hang" can occur due to issues on the client or issues on the Master.
On the client it can be one of two things. The process 'bmrsavecfg' is spinning and not completing, or the process is having issues sending the captured bundle.dat (the client configuration file) to the waiting bpbrm process.
On the Master, the reguklar NBU backup streams will not get kicked off until teh waiting bpbrm task gets teh bundle file and sends it off to bmrd to get imported.
So, how t diagnose where the proces is failing:
1. On the client, set the DebugLevel for Orgid 121 to be 5. This is for the bmrsavecfg process.
vxlogcfg -a -p 51216 -o 121 -s "DebugLevel=5"
2. Run the bmrsavecfg process from teh command line:
bmrsavecfg -infoonly
3. If this proess runs to completion normally, then the problem is either getting the file to the Master or getting the file imported into the BMRDB
4. Copy the file "/usr/openv/netbackup/client/data/bundle.dat" to the Master Server.
5. Increase the debug level for the 'bmrd' process, OrgID 119, on the Master:
vxlogcfg -a -p 51216 -o 119 -s "DebugLevel=5"
5. Manually import the file into the BMRDB:
bmrs -o import -res config -path <path to bundle.dat file>
Again, if this completes in a normal 1-2 minutes, you are OK and the problem is some sort of communication error between the client and NBU Servers.
For failures on the client, get the log data with:
vxlogview -i 121
For failures on the Master, use:
vxlogview -i 119
Be aware that if either of the programs is caught in a loop, the debug log files will grow rather quickly.
Reset the DebugLevel back to default with:
vxlogcfg -a -p 51216 -o 121 -s "DebugLevel=1"
vxlogcfg -a -p 51216 -o 119 -s "DebugLevel=1"
In either case, I would highly recommend an upgrade to a 7.X reelase as it will allow for teh ability to open a support case for better assistance.