below mentioned are the details for bprd process...

bprd responds to administrative and client requests for the restores, backups, archives, lists of archived/backed up files and manual immediate backups.

Started by: Initiate Request Daemon in the Netbackup admin interface.

Stopped by: Terminate Request Daemon in the Netbackup admin interface.

Activity log: /usr/openv/netbackup/logs/bprd/bprd.log on client.

you can also refer to the NBU Administrator's Guide I for more details on other NBU daemons...

with backups or restores failing due to bad tapes or some such?

It may be a carry over from that & 'simply' be a hung process. If you stop all NetBackup services is it still there? If it's still there when services are stopped it may be wise just to 'kill' it off.

As it's not a command that you 'run', but a process that is initiated by NetBackup daemon, unfortunately I couldn't advise on the exact meaning of the "options" - maybe someone else could help there. ;-)

Also I have came through one of the TN which was below mentioned details... TN link is also mentioned below...

The second option is to touch the NON_MPX_RESTORE file on the master server. This disables multi-plexed restores and prevents the "bprd -mpxmain" function from ever starting.
# touch /usr/openv/netbackup/NON_MPX_RESTORE

http://seer.entsupport.symantec.com/docs/272836.htm

That means option -mpxmain is used for multi-plexed restoration.

Now the option left is -dontfork, for which details are not avaiable (or either I don have that :) )

You can get the synatex of the COMMANDS and not the PROCESSES from the NBU Commands Guide

Also there are brief details of the bprd process options in the said guide which is not matching with the options we are talking about ...

Also one more thing as said by Andy, there are commands available for troubleshooting the bprd as sometimes it may hung.

Thats all from my side ... :)