Home > Error Code > Exited With Status 23 Socket Read Failed

Exited With Status 23 Socket Read Failed

Contents

Also, increasing the File List Timeout (also seen in Figure 2), can resolve issues with listing files that are available for restore. This problem can occur during a backup or a restore. Reinitializing and attempting to use IPv4. 12:25:03.413 [4248.8424] <2> NdmpMoverSession[0]: ndmp_mover_set_window(0, 18446744073709551615) 12:25:03.428 [4248.8424] <2> NdmpMoverSession[0]: Attempting to create server to which remote host san1 can connect - IPv4 12:25:03.444 [4248.8424] This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. navigate here

Recently we received a call from customer who was backing up databases from Azure VM to Azure blob storage.  The... This error indicates that the client and server were able to initiate communications, but encountered difficulties and the communications did not complete. Here is a screenshot of that setting.  It allows you to configure various things like auto backup, patching or... The default is 60 seconds.

Exited With Status 23 Socket Read Failed

Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscriptions Search Again Situation Customer told he is trying to restore 1.4 tb of data which Close the NetBackup Administration Console.Applies ToNetbackup 7.1 Terms of use for this information are found in Legal Notices. JackLiUnable to connect to SQL Server on azure VM due to an extra NSG applied to subnet September 18, 2016If you need to open up your SQL Server on an Azure Categories AlwaysON (13) Backup/Restore (20) Blocking (2) Cloud (19) Cluster Shared Volumes (3) ColumnStore Index (1) Connectivity (13) Database Engine (86) Database File Gorw/Shrink (4) Database Mail (1) Database Mirroring (2)

I even reinstalled the client from scratch and still get the same result. Close Login Didn't find the article you were looking for? Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support Connect Communities Security Center Find a Partner Events Webcasts Contact Us About Bpclntcmd Solution Overview: STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed backup or restore.Troubleshooting:This sort of behavior can be seen when there is a latency in the

These errors are caused either by network connectivity issues or if a required process such as pbx_exchange is not running. Determine the client and server that had the handshake failure. Server scheduled backups work on both clients. If exceeded, the user receives a "socket read failed" error even if the server is still processing the user's request.

Create/Manage Case QUESTIONS? Email Address (Optional) Your feedback has been submitted successfully! No Yes Did this article save you the trouble of contacting technical support? Submit a Threat Submit a suspected infected fileto Symantec.

  • No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
  • Contributors About DLT Subscribe Toggle navigation Subscribe ContributorsAbout DLT Subscribe scroll down for more Recent Cloud Cybersecurity Data & Storage IT Perspective Digital Design Open Source Data & Storage Status Code
  • It is possible that updates have been made to the original version after this document was translated and published.
  • Checked the status of the netbackup client service; It must be running in order to start a restore.

Error Code 24 In Netbackup

I went through quite a few things before doing a reverse lookup from the master server to the client - which failed. weblink Create/Manage Case QUESTIONS? Exited With Status 23 Socket Read Failed Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Netbackup Error Code 25 Reinitializing and attempting to use MoverListen method. 12:25:03.663 [4248.8424] <2> NdmpMoverSession[0]: ndmp_mover_set_window(0, 18446744073709551615) 12:25:03.678 [4248.8424] <2> NdmpMoverSession[0]: ndmp_mover_listen failed, status = NDMP_CONN_TYPE_UNCONFIGURED_ERR 12:25:03.678 [4248.8424] <16> NdmpMoverSession[0]: ERROR Start failed 12:25:03.678 [4248.8424]

NetBackup status code: 23 Message: socket read failed Explanation: A read operation from a socket failed. check over here October 18, 2016Recently we got a call from customer who was trying to enable stretch database but repeatedly got errors like below: Oct 14 2016 13:52:05 [Informational] TaskUpdates: Message:Task : ‘Configure July 9, 2016In the past few weeks, I saw this error come across quite a bit and thought I will provide an explanation for the reasons why we generate this error. The restore may or may not have initiated. Clear Host Cache Netbackup

It is very possible that you came across either one of the flavors of the two error messages shown below: 2016-07-08 23:53:59.63 Logon       Error: 18456, Severity:... Veritas does not guarantee the accuracy regarding the completeness of the translation. NetBackup status code: 26 Message: client/server handshaking failed Explanation: Aprocess on the server encountered an error when it communicated with the client. http://nodatasource.com/error-code/psexec-cmd-exited-with-error-code-0.html NetBackup Share This: Facebook Twitter LinkedIn Previous AutoCAD for Mac Next Open Source in the DoD Juan Maldonado Related Posts Smart Records Retention for Government Social Media Content July 20, 2016

It increases the number of write requests to be run at one time •  Change to or add the following settings in the Novell sys:system\autoexec.ncf file:SET Maximum Packet Receive Buffers = I've definately installed 6.5.6 on this client. Also Created DBMto file under \VERITAS\NetBackup\bin with the value of 120 4.

I hope you can help.

Thank you for your feedback! I have a 6.5.6 windows 2003 x64 master server and two Red Hat linux (2.6.18-164.el5) client - there are many more clients, however these two were built at the same time Email Address (Optional) Your feedback has been submitted successfully! Recommended Action: Determine which activity encountered the handshake failure by examining the All Log Entries report for the appropriate time period.

Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. Create/Manage Case QUESTIONS? weblink 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

Error Message Status code 23, socket read failed Cause   The keyfile.dat file in the \NetBackup\bin\ directory resulted in bpcd issuing the prompt and waiting for a passphrase, and remaining as a NetBackup status code: 24 Message: socket write failed Explanation: A write operation to a socket failed. Where can I start looking? The server returned error code 23,more information can be found it the netbackup troubleshooting guide".

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? NDMP_DATA_CONNECTION_HOST_NAME= 3.