Error Bpbrm Client Restore Exit Status 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 Success socket read failed 23 netbackup windows Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership
Netbackup Error Code 24
Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano netbackup error opening the snapshot disks status 23 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket
Netbackup Error Code 25
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 Article Products netbackup socket write failed 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. %
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 In CommunityCategoryBoardResourcesUsers
Bpclntcmd
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : socket read failed (23) VOX : Backup and Recovery : NetBackup : socket read failed (23) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the https://www.veritas.com/support/en_US/article.TECH54563 Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution socket read failed (23) mantu2a Level 3 01-13-2013 06:50 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, We are facing issue with a media server. Many jobs running on various client servers for that media server are failing with error : 01/13/2013 19:51:27 - Error bpbrm https://vox.veritas.com/t5/NetBackup/socket-read-failed-23/td-p/525966 (pid=5551) bpcd on client exited with status 23: socket read failed 01/13/2013 19:51:28 - Error bpbrm (pid=5551) cannot send mail because BPCD on client exited with status 23: socket read failed 01/13/2013 19:51:29 - end writing socket read failed (23) We checked and found : bptestbpcd -client client name Command is working when we try it from master for media server but not for client Again , when we try vmoprcmd, vmoprcmd -d -h (media server) The Media Manager device daemon (ltid) is not active on host (media server). Again,for media server : netstat -a |grep bp *.bpcd *.* 0 0 49152 0 LISTEN *.bpjava-msvc *.* 0 0 49152 0 LISTEN 30054418cd8 stream-ord 300211cf480 00000000 /usr/openv/var/vnetd/bpcompatd.uds When we try bpclntcmd from media server for client, we get : bpclntcmd -hn client host cleint: client at 199.37.184.185 (0xc725b8b9) aliases: From master for media: master: bpclntcmd -hn media host media: media at 135.153.168.80 aliases: media 135.153.168.80 From media for master : bpclntcmd -hn master host master: master at 135.53.28.54 (0x87351c36) host master: master at 135.53.28.53 (0x87351c35) aliases: Please advice, Regards Samrat Chowdhury Solved! Go to Solution. Labels: 7.1.x and Earlier Backup and Recovery NetBackup 1 Kudo Reply 1 Solut
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 http://blogs.dlt.com/status-code-23-socket-read-failed/ 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 http://symantec697.rssing.com/chan-4200978/all_p41.html 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 netbackup error 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 occur during a restore to a Novell socket read failed 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 Linkedin Youtube About Technically Speaking Technically Speaking is a blog dedicated to providing the latest
contact us about this channel Embed this content in your HTML Search confirm cancel Report adult content: click to rate: Account: (login) More Channels Showcase RSS Channel Showcase 6422343 RSS Channel Showcase 9004547 RSS Channel Showcase 9214052 RSS Channel Showcase 5021410 Channel Catalog Subsection Catalog Articles on this Page (showing articles 801 to 820 of 8873) 01/12/13--23:02: _backup exec 2012 fo... 01/13/13--02:27: _Netbackup Licenses 01/13/13--18:13: _VADP Restore - Cann... 01/13/13--18:50: _socket read failed ... 01/13/13--23:16: _Backup Exec 2012 R1... 01/13/13--23:20: _System Recovery 201... 01/14/13--00:45: _How to restore data... 01/14/13--00:57: _BESR 2010 Events No... 01/14/13--00:59: _Using auth.conf fil... 01/14/13--01:55: _backup process 01/14/13--02:00: _backup exec 2012 no... 01/14/13--02:44: _Backup Exec 12.5 li... 01/15/13--09:34: _Restore a Backup Se... 01/15/13--12:00: _EC 25 01/15/13--12:51: _MSSQL 2008 server s... 01/15/13--13:01: _Deletion of informa... 01/15/13--13:11: _BackupExec 12.5 and... 01/15/13--14:13: _Can't connect to BE... 01/15/13--14:23: _I think my LTO driv... 01/15/13--14:27: _Problem with a Sola... (showing articles 801 to 820 of 8873) Browse the Latest Snapshot Browsing All Articles (8873 Articles) Live Browser older | 1 | .... | 38 | 39 | 40 | (Page 41) | 42 | 43 | 44 | .... | 444 | newer 0 0 01/12/13--23:02: backup exec 2012 for sql server 2008 Contact us about this article I need a solution Hi Guys, Need your advise here. Let's say currently I have the below backup strategy: 1. Daily full db backup to filesystem via SQL Maintenance Plan