The same success is shown for the the NEW_DATA and DATA sockets. Notice that there is only a 0.8 second delay before receiving the ipc and hash1 strings for use by bpcd.ġ4:34:49.872 logconnections: BPCD CONNECT FROM 2.2.2 TO 3.3.4ġ4:34:49.874 vnet_connect_to_vnetd_extra. The bpbrm debug log shows that some forwarding sockets can be created to the client host successfully.
Starting with NetBackup 7.0.1, this problem may cause vnetd -standalone to also be delayed before accepting inbound connections. When this problem occurs, vnetd on the remote host may experience delays returning the connection information to other NetBackup processes which will timeout and fail the operation with a variety of different status codes status 13, status 25, status 54, etc.
Stream-based database extensions (DB2, Informix, Oracle, SAP, SQL-Server, Sybase, Teradata, XBSA/DataStore) create additional forwarding connections from the master and media servers. When vnetd is in use (which is the default configuration), any backup or restore will create one or more vnetd forwarding connections to the client host from the media server.