pops out from that output.
Have you requested that logging be turned up on the system? Is this something the system SA can do? I've seen some of your posts before and I'm sure you're aware of what to do, but just in case, the SA will need to create a bpcd directory under <install_path>/openv/netbackup/logs, and should add the verbose entry to the bp.conf file located under <install_path>/openv/netbackup
Have the SA send you back any logs that are generated from a backup, and post them here.
If you want to sift through large logfiles, the bpcd on the master could have something that complains about not being able to connect to "blackfin"
Also, we just nailed down a case here where we could telnet to a solaris 10 server to vnetd and bpcd no problems from the master, and we could telnet to 13724 locally on the client, however when we ran a backup, no bpcd logs were generated, nor were there any vnetd logs generated after we created a vnetd log directory. We checked inetd and it was running also, so everything was telling us the backup should work, but it was not.
We enabled vnetd in standalone mode, and the backups are working - this is a workaround for now until the SA can pin down why inetd is acting funny. Below is the technote that pointed us in that direction - its for older versions of NBU, but it worked. I dont know if that is your issue or not, we wont know until you can see if bpcd logs are being generated.
If logs are not being generated from backups that initiate from the master server, have the SA run <install_path>/openv/netbackup/bin/bpcd locally on the machine, and it should generate a bpcd log. This will let you know that something is not communicating between vnetd and inetd.
Hope this helps.
