Home > Error Code > Socket Read Failed 23 Netbackup

Socket Read Failed 23 Netbackup

Contents

Also, increasing the File List Timeout (also seen in Figure 2), can resolve issues with listing files that are available for restore. The results should display the correct hostname and IP address for the host. 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 Labels: Backup and Recovery NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! weblink

PS /tmp is not even backed up on Unix/Linux client - automatically excluded. Solution The keyfile.dat is associated with the NetBackup Encryption agent.  By default the keyfile.dat file should exist in the NetBackup\var directory for NetBackup versions 5.1 and above.    If the client is at version 5.1 or greater, the keyfile.dat file can Thanks, -Jonathan _______________________________________________ Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Wed Jun 17, 2009 1:01 pm mdonaldson Joined: 18 May 2009 Posts: 98 Restore request times out Two potential Cisco Pix firewall) and re-run the backup. https://support.symantec.com/en_US/article.TECH175412.html

Socket Read Failed 23 Netbackup

Cause Since customer wanted to restore huge amount of data. No Yes Did this article save you the trouble of contacting technical support? It is possible that updates have been made to the original version after this document was translated and published. The minimum setting is 0.

  • Standard Yes In Activity Monitor the Restore job shows in queue.
  • 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
  • No Yes How can we make this article more helpful?
  • You may also refer to the English Version of this knowledge base article for up-to-date information.
  • Find the attachment for your reference: bprd.tar.gz ‏39 KB bpdbm.tar.gz ‏21 KB 0 Kudos Reply Kindly see the latest logs Zahid_Haseeb Level 6 Partner Accredited ‎08-13-2012 12:45 AM Options Mark as
  • No Yes Did this article save you the trouble of contacting technical support?
  • What kind of backup are you trying to restore?
  • Checked the status of the netbackup client service; It must be running in order to start a restore.

See my previous explanation of the command that you have typed. http://www.symantec.com/business/support/index?page=content&id=TECH38975 http://www.symantec.com/business/support/index?page=content&id=TECH52760 Solved! No Yes How can we make this article more helpful? Clear Host Cache Netbackup Written by leading industry professionals, this blog is designed to stimulate discussion, drive thought, and suggest best practices to help readers better navigate the complex maze of federal business. © Copyright

Veritas does not guarantee the accuracy regarding the completeness of the translation. If the "Full Backup" schedule is now successful, then the firewall used has timeout values which are preventing the backup from completing successfully.  Work with the firewall manufacturer to resolve the Article:000042416 Publish: Article URL:http://www.veritas.com/docs/000042416 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in On the NetBackup system where restores are initiated, launch the NetBackup Administration Console. 2.

Database? Bpclntcmd You probably want Windows patches? The restore may or may not have initiated. Submit a Threat Submit a suspected infected fileto Symantec.

Exited With Status 23 Socket Read Failed

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 here Article:000089429 Publish: Article URL:http://www.veritas.com/docs/000089429 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in Socket Read Failed 23 Netbackup Veritas does not guarantee the accuracy regarding the completeness of the translation. Error Code 24 In Netbackup Did this article resolve your issue?

Thank You! have a peek at these guys Email Address (Optional) Your feedback has been submitted successfully! Normal Windows policy? Error Message socket read failed Solution Overview:  Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed).  Troubleshooting: Use the bpclntcmd command to test the connectivity between Netbackup Error Code 25

Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in 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 Does it get to Activity Monitor? check over here Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem General Error: Status code 23, socket read failed, during client backups or restores, or when

Don't have a SymAccount? Create/Manage Case QUESTIONS? No Yes How can we make this article more helpful?

Check the status of the Netbackup Client Service; it must be running in order to start a restore.

The following commands can be used to test the short name alias and the fully qualified long nameof the system.   # /usr/openv/netbackup/bin/bpclntcmd –hn out because for reading such data it was taking long time.

Log files:  N/A Resolution: This problem is caused by incomplete name resolution information in either the hosts file or the DNS.  Be sure the client's name and IP address are in Extract fromhttp://www.symantec.com/docs/TECH189607 WINDOWS: Note: Windows packages include fixes for Add-on products and Database Agent. Create/Manage Case QUESTIONS? http://nodatasource.com/error-code/netbackup-error-codes-pdf.html 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

A value of 100 increases the speed and efficiency of the disk cache writes. Recommended Action: A common cause for this problem is a query that has no matching images. In the General tab, set "List files timeout:" to 3600 seconds to allow one hour. 5. You may also refer to the English Version of this knowledge base article for up-to-date information.

Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Contributors About DLT Backup Central HomeMr. I also followed the following TN but nothing positive.

It is possible that updates have been made to the original version after this document was translated and published. 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 No Yes Did this article save you the trouble of contacting technical support? All SQL server databases' "Default Policy" schedules exit successfully.

On Windows master, default type (-t) is 13 - MS-Windows. The status 23 may appear in the activity monitor, or it may appear as a pop up error on the client (Figure 1).Figure 1:  A status 23 condition is seen   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 Thank You!

Those are not the only links Marianne Moderator Partner Trusted Advisor Accredited Certified ‎08-31-2012 04:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Create a SymAccount now!' Restore fails with "The server returned error code 23,more information can be found it the netbackup troubleshooting guide". If exceeded, the user receives a "socket read failed" error even if the server is still processing the user's request. You may also refer to the English Version of this knowledge base article for up-to-date information.

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 = The server returned error code 23,more information can be found it the netbackup troubleshooting guide." Error "Timed out while waiting for acknowledgement.