OK, there are several tings in here that are problematic For starts, the environment is 6.5.6, which has been EOSL for quite a while now.
Need some more details for the Master/Client environment. What version of Solaris is the Master? What version/release is the Linux client?
When performing an NBU backup with the BMR feature enabled, you should get an initial job on the Admin Console that shows the BMR portion of the process. Do you see that? If so can you share the job details as shown for it?
The BMR portion is there to create, capture and insert the client configuration into the BMRDB. The NBU job manager performs two functions for this:
1.It sends a START_NOTIFY to the client with appropriate option information which causes the client system to run "bmrsavecfg" locally. This process creates the client information in a file called "bundle.dat".
2. It creates a bpbrm process which starts up and waits for the client to send it the client configuration file. This becomes the "master job" and stays resident until the entire NBU back is completed.
3. When the client process completes, it sends the bundle file to bpbrm for insertion into the BMRDB.
4. The bpbrm process forwards the file to the bmrd process on the Master for DB insertion and waits for a response when complete.
5. The bmrd process, using database services, insert the information into the BMRDB and when complete, returns either a zero or a one to bpbrm as the status code.
6. The bpbrm gets the response and then starts firing off the normal NBU backup streams noted in the policy. Those become their own jobs and get their own job id.
7. Normal NBU backup occurs and when the last stream completes, the "master job" captures the highest status code of all of the job and terminates with that status code.
With all of this, please tell me where you are seeing the "hang"?
You can emulate the BMR portion of this by doing the following (all commands are in /usr/openv/netbackup/bin):
On the Linux client, run the command "/bmrsavecfg -infoonly". This creates the file "/usr/openv/netbackup/baremetal/client/data/bundle.dat". Run "echo $?" immediately after that to get the return code.
If the return code on the client was zero, copy this file to the Master at any directory. As an example, create the file "/tmp/bundle.dat".
Manually import the configuration into the BMRDB by running "bmrs -o import -res config -path /tmp//bundle.dat". Again run "echo $?" to get its return code.
If all of this worked with no errors (rc=0) then BMR is not the culprit. Try the backup with the BMR option disabled but with the "True Image" and "With move detection" enabled. Setting the BMR option on automatically enables both.
Please let us know your results for all of this.