When using NetBackup, SharePoint Portal Server backups fail with Status Code 13: file read failed, and the error message "BEDS 0xE0000316: Unable to lock the SharePoint Portal server farm topology" in the Activity…

Overview:  
SharePoint Portal Server backups fail with a NetBackup Status Code 13 (file read failed), and the error message "BEDS 0xE0000316: Unable to lock the SharePoint Portal server farm topology" in the Activity monitor.  

Troubleshooting:
In the Activity monitor on the master server, the following is observed:
04/28/2006 09:11:53 - started process bpdm (pid=22521)
04/28/2006 09:11:52 - started process bpbrm (pid=22520)
04/28/2006 09:11:52 - connecting
04/28/2006 09:11:52 - connected; connect time: 0:00:00
04/28/2006 09:11:56 - begin writing
04/28/2006 09:12:19 - Warning bpbrm (pid=22520) from client ICE-ZS01.lly.icepoc.com: WRN - can't open object: Microsoft SharePoint Resources:\https://my-z.icepoc.com\Services DB (ICE-ZQ01/MYZ2_SERV)\MYZ2_SERV (BEDS 0xE0000316: Unable to lock the SharePoint Portal server farm topology.
04/28/2006 09:12:20 - Error bpbrm (pid=22520) from client ICE-ZS01.lly.icepoc.com: )
04/28/2006 09:12:22 - Error bpdm (pid=22521) media manager terminated by parent process
04/28/2006 09:12:26 - end writing; write time: 0:00:30 file read failed (13)

Log files:  
In the bpbkar log file on the SharePoint server, the following message will appear:

BEDS 0xE0000316: Unable to lock the Sharepoint Portal server farm topology

Resolution:
If there are multiple front end Web servers, authentication can occur on any of them.  In this instance, the topology lock was occurring because the SharePoint Hosts properties were not entered into the second front end server.

For information on how to correctly setup SharePoint permissions, see the article under related documents.