Once this is done, then further troubleshooting can be done to isolate the failure to a specific function, network configuration, performance issue, machine resources, etc. 1.1 Verify NetBackup Server processes are Engaged tech support, turn VxMS logging on etc. Logs produced look similar to this: Detailed Status (from Activity Monitor): 10/23/2012 10:45:07 PM - Error bpbrm(pid=8764) from client
hash_str1: 709103... 14:35:39.191  <2> vnet_generate_hashes: ... ipc_string: /tmp/vnet-... 14:34:52.762  <2> vnet_vnetd_connect_forward_socket_begin: ... Windows: netstat -a > c:\netstat.txt UNIX: netstat -a > /tmp/netstat.txt The netstat.txt file that gets created should list the listening processes that are running (bpcd, vnetd, vopied, bpjava-msvc). Remove the old (renamed) file folder which should contain only the vmx, nvram and log files [house cleaning] The client was then able to backup successfully.0 0 11/09/12--12:18:
hash_str1: 901ff61c13eccdf2857499342888fbed 14:40:25.139  <2> vnet_generate_hashes: ... lesser delay 10540/1: 283.1897 unlink("/tmp/vnet-10540289946940226105000000000-cnaGLu") = 0 10540/1: 283.1903 so_socket(PF_UNIX, SOCK_STREAM, 0, "", 1) = 6 10540/1: 283.1904 setsockopt(6, SOL_SOCKET, SO_REUSEADDR, 0xFFBFEE4C, 4, 1) = 0 10540/1: 283.1906 unlink("/tmp/vnet-10540289946940226105000000000-cnaGLu") Err#2 ENOENT Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem If there are connectivity problems to other clients that are included in the same Such a mismatch is a third potential cause for a status 54 on a database client backup or restore.
Check the NetBackup System Administrator Guide (for UNIX or Windows) for firewall and port information. msg: VNETD CONNECT FROM 184.108.40.206.42533 TO 220.127.116.11.13724 fd = 8 14:34:50.301  <2> vnet_vnetd_connect_forward_socket_begin: ... I am running Red-Hat 5. Error Bpbrm Could Not Send Server Status Message One of my media server is down for patching.
telnet: Unable to connect to remote host: Connection refused The telnet session will end automatically and return to the prompt. I have opened case with symantec and did not find any solution yet. If telnet is unsuccessful you will get a message similar to: # telnet nbclient bpcd Trying x.x.x.x... https://www.veritas.com/support/en_US/article.TECH138071 Today where all communication is passed thru 13724, more meaningful messages may be masked as sockets errors because of vnetd. 0 Kudos Reply I set the read timeout to the bsb
No Yes How can we make this article more helpful? VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a 14:34:52.759  <2> vnet_vnetd_connect_forward_socket_begin: ... hash_str2: dee028... 14:35:39.191  <2> process_connect_forward_socket: ... I've read that you can move the database from one opscenter to another copying the data under /db/data, but i don't want to replace the info in the new opscenter, I
Can I redirect where NetBackup can extract the files to another directory with more disk space?0 0 11/08/12--10:32: NET BACKUP ON TERADATA Contact us about this article I need http://www.symantec.com/connect/fr/forums/error-bpbrm-listen-client-timeout-during-accept-data-listen-socket-after-60-seconds Opening session--attempting with NDMP protocol version 4... Error Bpbrm No Worklist Items Returned From Bpresolver On Client Logging in using MD5 method... Error Bpbrm Cannot Connect To Client Be aware that re-issuing the command properly will return the file list pretty quick since the list is in the file cache.
Which led us to wonder if it was a config issue on the VMware side (VMX file?). this contact form Example from a UNIX client /usr/openv/netbackup/logs/bpcd/log.
status: 150: termination requested by administrator 11/08/2012 14:53:06 - Error ndmpagent (pid=29764) connection 0x12f6fc0 ndmp_message_process_one failed, status = 18 (NDMP_XDR_DECODE_ERR) 11/08/2012 14:53:06 - Error ndmpagent (pid=29764) connection 0x12f9790 ndmp_message_process_one failed, status Does anyone have any idea about how to do this? Kind regards, Juan0 0 11/08/12--07:02: Sql database completed with status code 1, as per dbclient error log, its Sorry, we couldn't post your feedback right now, please try again later. have a peek here I do not see any realted to how long a file takes to write.
We implemented a workaround suggested by symantec about using account other than SYS, but it didnt help. Phil Weber IT Infrastructure Unix Systems Engineer Phone: 01384 26 4136 Mobile: n/a -----Original Message----- From: Weber, Philip [mailto:Philip.Weber AT egg DOT com] Sent: 04 April 2002 10:28 To: 'larry.kingery AT This is also a very good test for firewall issues to see if a path is open through the firewall.
Are you sure you want to continue?CANCELOKWe've moved you to where you read on your other device.Get the full title to continueGet the full title to continue reading from where you Create/Manage Case QUESTIONS? The key to success is to isolate which socket is not being established. Email Address (Optional) Your feedback has been submitted successfully!
First, three connections to the client occur from the master and then the media server. Waiting for connect notification message... Sorry, we couldn't post your feedback right now, please try again later. Check This Out All members of the Egg group are registered in England and Wales.
Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error bpbrm: listen for client timeout during accept data_ipc: /tmp/vnet-... 14:34:53.949  <2> bpbrm listen_for_client: ...