I am backing up an HP-UX v3 machine and am getting the same issue as mentioned in this post:
The client version is 220.127.116.11. Does the mentioned issue still persist in the newer version?
Solved! Go to Solution.
Is the HP client a virtual server ?
There are many many reasons for this issue, would have to see the logs.
This enables the -o 121 log - bmrsavecfg
vxlogcfg -a --prodid 51216 -o 121 -s DebugLevel=6 -s DiagnosticLevel=6
This runs on the client, and creates the bundle.dat file
The bmrd process runs on the master, and imports the dundle.dat into the DB
vxlogcfg -a --prodid 51216 -o 119 -s DebugLevel=6 -s DiagnosticLevel=6
These commands turn the logs 'up'
Use vxlogview to gather the logs
Issue got resolved after updating client binaries to 7.5. The only issue I percieve is maybe 7.1.x did not have support for ASM or this maybe a bug in 18.104.22.168.
Thanks anyway for everyones input.
This issue was in 7102 patch version and was BMRDB upgrade specific. This issue would impact devices to their driver packages association. So if BMR master is running with 7102 version (even though client is at 7103) then this issue may hit. Where mentioned EEB needs to be applied on 7102 or move to later patch/major version to resolve.