Error 23 Socket Read Failed Netbackup
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 About Corporate Profile Corporate Leadership Newsroom Research Exchange cannot connect on socket netbackup error Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 socket open failed 21 netbackup 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client backups
Netbackup Error Socket Read Failed Errno = 62 - Timer Expired
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
Read From Input Socket Failed 636 Netbackup
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 exited with status 23 socket read failed file in the
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 Investor Relations Careers
Error Code 24 In Netbackup
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español netbackup error opening the snapshot disks status 23 USA Site: Veritas Veritas PartnerNet STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed restore. netbackup error code 25 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 https://www.veritas.com/support/en_US/article.TECH57100 Please sign in to set up your subscription. Close Sign In Print Article Products 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 https://www.veritas.com/support/en_US/article.TECH38975 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 the client (Figure 1).Figure 1: A status 23 condition is seen Master Log Files: N/A Media Server Log Files: N/AClient Log Files: N/AResolution: In addition to investigating any possible network latency, change the user-directed operation timeout to a higher value by doing the following: 1. Pull up the Backup, Archive and Restore interface on the client machine in question 2. Click File | NetBackup Client Properties 3. Increase the user-directed operation timeout (Figure 2) Figure 2: Changing the user-directed operation timeout to a higher value can resolve the Status 23 error on a user-directed operation. The user-directed operation timeou
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 https://vox.veritas.com/t5/NetBackup/socket-read-failed-status-23/td-p/610704 Developers Blogs Groups Vision 2016 Sign In http://blogs.dlt.com/status-code-23-socket-read-failed/ CommunityCategoryBoardResourcesUsers 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 netbackup error : socket read failed - status 23 VOX : Backup and Recovery : NetBackup : socket read failed - status 23 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution socket read failed - status socket read failed 23 Jain_Thomas Level 3 08-07-2013 12:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All Status 23 -socket read failed Created a new policy Added the Master Server IP and hostname to /etc/hosts on master server Added the Client Ip and hostname to /etc/hosts on client Installed the client Software root @Master [/opt/openv/netbackup/bin/admincmd]#./bptestbpcd -client Aries-DC -verbose -debug 12:57:35.792 [5425] <2> bptestbpcd: VERBOSE = 5 12:57:35.792 [5425] <2> read_client: ? 12:57:35.793 [5425] <2> read_client: opendir() failed: Aries-DC: No such file or directory (2) 12:57:35.793 [5425] <2> ConnectToBPCD: db_getCLIENT(Aries-DC) failed: 227 12:57:35.793 [5425] <2> ParseConfigExA: Option (CLIENT_NAME) redefined on line 12, discarding definition on line 11. 12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.687: cached_user_name: root 12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.689: cached_user_name: :root 12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :root 12:57:35.794 [5425] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100 12:57:35.794 [5425] <2> local_bpcr_connect: bpcr.c
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 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 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. 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 ensur