Create/Manage Case QUESTIONS? Solution Overview: When attempting a NetBackup (tm) SQL backup, the attempt fails with NetBackup Status Codes 2 and 25. Troubleshooting:Master Log Files: N/A Media Server Log Files: The following appears In Note that this level of the NetBackup for SQL Server extension will automatically create DSNs as required.Install patch MP2 for NetBackup updates and DB Agent updates since version 4.5 Terms of You may also refer to the English Version of this knowledge base article for up-to-date information. Source
And where do these different hostnames fit in the picture? You may also refer to the English Version of this knowledge base article for up-to-date information. Sorry, we couldn't post your feedback right now, please try again later. Do you by any chance have anything on TCP tuning? 0 Kudos Reply The failure occurs to quickly RiaanBadenhorst Moderator Partner Trusted Advisor Accredited Certified 01-14-2014 10:56 AM Options Mark as
No Yes How can we make this article more helpful? Thank You! Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
I tried to decrease tcp_time_wait_interval, but it didn't help....RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of backup plus archivelog command at 02/14/2008 15:19:20ORA-19506: failed to create sequential file, Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 25 NetBackup SQL backups fail with Status Code 25 - cannot connect Email Address (Optional) Your feedback has been submitted successfully! VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a 14:34:52.759  <2> vnet_vnetd_connect_forward_socket_begin: ...
I have seen in the past issues with too many CLOSE_WAIT and TIME_WAIT connections. Below is output from backup session. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? https://www.veritas.com/support/en_US/article.000007046 So - this is why I asked for both.
We have seen in a similar forum discussion that TCP error 10038 went away after a reboot. Request VN_REQUEST_CONNECT_FORWARD_SOCKET(10) ... update request from nbjm on master server ...05:37:31.390 [1888.1268] <2> process_requests: open for write file name = C:\Program Files\Veritas\NetBackup\Logs\user_ops\dbext\logs\2236.0.1400881046... Please ensure that all of the logs exist as suggested above.
We normally reccommend Client Connect and Client Read Timeout of 1800 (30 min) on the media server. https://www.veritas.com/support/en_US/article.000087047 No Yes This does not apply to 7.x. errno = 22: Invalid argument...
And I am curious about the path selectionC:\Program Files\VERITAS\PwC_SQL_all_TxLgbu_script.bch , in the policy backup selection isC:\Program Files\VERITAS\PwC_SQL_all_bu_script.bch which is a full backup script. this contact form status: 25: cannot connect on socket 7/30/2012 10:41:13 PM - Error bpbrm(pid=4452) client restore EXIT STATUS 25: cannot connect on socket 7/31/2012 12:45:06 AM - restored image Server1_1343169693 - (cannot connect Thanks 0 Kudos Reply Firstly check thatuser Marianne Moderator Partner Trusted Advisor Accredited Certified 01-14-2014 11:09 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to ipc_string: /tmp/vnet-... 14:34:52.762  <2> vnet_vnetd_connect_forward_socket_begin: ...
Does seem somehow related to comms, or maybe the comms processes. Create/Manage Case QUESTIONS? vnet_push_string failed: 12 0x0000000c 14:40:25.296  <2> ProcessRequests: vnetd.c.364: status: 12 0x0000000c 14:40:25.300  <2> vnet_push_string: vnet.c.236: errno: 32 0x00000020 14:40:25.300  <2> vnet_push_string: vnet.c.238: Function failed: 12 0x0000000c 14:40:25.300  have a peek here Go to Solution Getting error 25 socket connect errors restoring files MelB Level 4 07-31-2012 05:12 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to
It is possible that updates have been made to the original version after this document was translated and published. Sorry, we couldn't post your feedback right now, please try again later. status: 25: cannot connect on socket 7/31/2012 2:45:21 AM - Error bpbrm(pid=4276) client restore EXIT STATUS 25: cannot connect on socket 7/31/2012 4:49:12 AM - restored image Server1_1343172259 - (cannot connect msg: VNETD CONNECT FROM 220.127.116.11.42542 TO 18.104.22.168.13724 fd = 9 14:34:54.367  <2> vnet_vnetd_connect_forward_socket_begin: ...
I have just seen too many CLOSE_WAIT and TIME_WAIT connections. dbclient.txt 18 KB 0 Kudos Reply Here is dbclient log Harsha_rao Level 4 05-14-2015 03:55 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a I had to follow this technote in order to adjust TCP/IP stack so to fix the status 2850 with the restore. Check This Out This looks like a connectivity issue between Server2 (media server) and Server1 (SQL client).
Backup type : user directed. Email Address (Optional) Your feedback has been submitted successfully! Is there some port setting in NBU that has to be open for both backups and restores? 0 Kudos Reply NBU uses the same ports for Marianne Moderator Partner Trusted Advisor I will keep you posted on what my future actions are.
dbclient.txt) and upload as File attachment. CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical minor delay 10540/1: 284.9916 bind(6, 0xFFBFEDDC, 110, 3) = 0 10540/1: AF_UNIX name = /tmp/vnet-10540289946940226105000000000-cnaGLu 10540/1: 284.9923 chmod("/tmp/vnet-10540289946940226105000000000-cnaGLu", 0666) = 0 ...snip... 10540/1: 284.9936 write(4, " 1 4 : 4 0 It looks that problem was really with network card.
It loks like network issue, not enough open tcp sockets or something like this.