Error 23 Server Status Socket Read Failed
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
Socket Read Failed Netbackup
Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom exited with status 23 socket read failed Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 netbackup error code 24 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed).
Netbackup Error Opening The Snapshot Disks Status 23
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 to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article
Netbackup Error Code 25
Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 23: Schedule 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. % Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign bpclntcmd -pn In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. clear host cache netbackup Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : SQL backup are failing with error 23 (socket read ... VOX : https://www.veritas.com/support/en_US/article.TECH54563 Backup and Recovery : NetBackup : SQL backup are failing with error 23 (socket read ... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page SQL backup are failing with error 23 (socket read failed ) lovy Level 4 02-11-2015 01:38 PM Options Mark as https://vox.veritas.com/t5/NetBackup/SQL-backup-are-failing-with-error-23-socket-read-failed/td-p/703563 New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, File system backup are working fine but SQL backups are failing with error code 23 socket read failed . Things i already checked: 1.I checked SQL server and netbackup clientservices. 2. registry entries. pls provide me a solution. job detail: 02/11/2015 21:39:05 - Error bpbrm (pid=1690) bpcd on 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 http://blogs.dlt.com/status-code-23-socket-read-failed/ the code can lead you to troubleshooting a multiple of things in your environment. Let’s see the recommended action by Symantec would you check the NetBackup problems report 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 socket read 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 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. socket read failed 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 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 Bpclntcmd Pn