Error 23 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 netbackup error 23 Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate netbackup status 23 socket read failed Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français
Socket Read Failed Errno = 104 - Connection Reset By Peer
Deutsch Italiano 日本語 한국어 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 Errno = 62 - Timer Expired
(socket read failed). 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 socket read failed errno = 62 - timer expired vmware 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 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
Socket Read Failed Errno = 119 - System Call Timed Out
Success Licensing Programs Licensing Process ABOUT About Corporate Profile socket read failed tomcat Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français exited with status 23 socket read failed Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed https://www.veritas.com/support/en_US/article.TECH54563 restore. Article:000029399 Publish: Article URL:http://www.veritas.com/docs/000029399 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 https://www.veritas.com/support/en_US/article.TECH38975 Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed restore. Error Message Socket Read FailedTimed out waiting for acknowledgement.The restore may or may not have initiated.Check the status of the NetBackup Client Service;it must be running in order to start a restore.The server returned error code 23. 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 network connection between the client and the master server. It can also be seen if the backup set in question contains a very high file count, as in excess of 1 million files. The status 23 may appear in the activity monitor, or it may appear as a pop up error on t
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 http://blogs.dlt.com/status-code-23-socket-read-failed/ 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 http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/symantec-netbackup-18/bpbackup-and-socket-read-error-23-108335/ 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. socket read 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. 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 socket read failed 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 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 Linked
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central Forums Forum Index » Symantec NetBackup » bpbackup and socket read error (23) The time now is Mon Oct 10, 2016 3:00 pm View previous topic | View next topic Page 1 of 1 bpbackup and socket read error (23) Author Message Andy Braithwaite Joined: 05 Oct 2010 Posts: 3 bpbackup and socket read error (23) Hi, I'm having some problems with a client initiated backup. I hope you can help. 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 and are supposed to be almost identical. Server scheduled backups work on both clients. However on one client bpbackup fails: [root@xxxxx bin]# ./bpbackup -w /etc/group EXIT STATUS 23: socket read failed Also, the clients properties in the admin console show v6.5 only. I've definately installed 6.5.6 on this client. I even reinstalled the client from scratch and still get the same result. Where can I start looking? Many thanks Andy Tue Oct 05, 2010 5:04 am Andy Braithwaite Joined: 05 Oct 2010 Posts: 3 I'd like to add that the client is a virtual box on esx 4.0 Hi, I'm having some problems with a client initiated backup. I hope you can help. 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 and are supposed to be almost identical. Tue Oct 05, 2010 6:18 am Len Boyle Guest bpbackup and socket read erro