Netbackup Restore Error 23
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT socket read failed 23 netbackup windows About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers
Exited With Status 23 Socket Read Failed
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas
Error Code 24 In Netbackup
PartnerNet STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed). Article:000089429 Publish: Article URL:http://www.veritas.com/docs/000089429 Support / Article Sign In
Netbackup Error Opening The Snapshot Disks Status 23
Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 23: Schedule netbackup error code 25 initiated Client backups fail with a NetBackup Status Code 23 (socket read failed). 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 the master server and the client. Specifically, be sure to use the bpclntcmd -pn command. The following commands can be run to test both forward and reverse hostname lookups in Windows & Unix The following commands can be used to test the short name alias and the fully qualified long name of the system. %
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange clear host cache netbackup Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 bpclntcmd 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client backups bpclntcmd pn or restores, or when loading client properties. 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 https://www.veritas.com/support/en_US/article.TECH54563 First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. 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 loading client properties. Error Message Status code 23, socket read failed Cause The keyfile.dat https://www.veritas.com/support/en_US/article.TECH57100 file in the
Read Failed” Juan Maldonado September 21, 2010 No Comments Facebook Twitter LinkedIn I am sure you have run into a status code 23 “Socket Read Failed”. This stinks because the code can lead you to troubleshooting a multiple of things in your http://blogs.dlt.com/status-code-23-socket-read-failed/ environment. Let’s see the recommended action by Symantec would you check the NetBackup problems report http://www.adminbytes.com/2009/06/netbackup-error-23-socket-read-failed.html for clues on where and why the failure occurred. If you cannot determine the cause from the Problem report, then you are to create a debug log directory for the process that could have returned this status code (YAY for Legacy Logging!!) Then, retry the operation and check the resulting debug log. Also corrupt binaries are one possible cause socket read for this error. So make sure you load a fresh “bptm” from the install media to try to resolve the problem. On Sun Solaris systems you must first verify that all operating systems patches are installed. See the Operating Notes sections of the NetBackup Release Notes. For Windows you need to verify that the recommended service packs are installed. Also this error can occur during a restore to a Novell client. The following may be socket read failed a possible action to take: • By default, the value for Novell “Maximum Concurrent Disk Cache Writes” may be too low (for example, 50); Novell recommends setting it to 100. A value of 100 increases the speed and efficiency of the disk cache writes. 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 = 4000SET Maximum Directory Cache Buffers = 4000 SET Maximum Concurrent Disk Cache Writes = 2000SET Maximum Concurrent Directory Cache Writes = 2000SET Maximum Physical Receive Packet Size = 1514 On Windows master servers, check the LIST_FILES_TIMEOUT value and ensure that this value is at least 1800. 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 6 Steps to Giving Data Backup the Respect It Deserves June 28, 2016 All-Flash Storage Goes Mainstream, but Only Some Offer Enterprise-Grade Parity June 17, 2016 Don’t Miss: Feds Discuss Forward Thinking Approach to Data Backup and Recovery June 16, 2016 Follow DLT Facebook Twitter Linkedin Youtube About Technically Speaking Technically Speaking is a blog dedicated to providing the latest public sector IT industry news. Written by leading in