Netbackup Error 23 A Read Operation From A Socket 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 Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal
Error Code 24 In Netbackup
Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: netbackup error opening the snapshot disks status 23 Veritas Veritas PartnerNet STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed restore. Article:000029399 Publish: Article netbackup error code 25 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
Bpcd On Client Exited With Status 23 Socket Read Failed
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 order to start a restore.The
Clear Host Cache Netbackup
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 timeout is the number of seconds to wait for a respo
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 bpclntcmd -pn Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch
Bpclntcmd Pn
Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet General Error: Status code 23, socket read failed, during client backups 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 https://www.veritas.com/support/en_US/article.TECH38975 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 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 https://www.veritas.com/support/en_US/article.TECH57100 Cause The keyfile.dat file in the
reset by peer An netbackup error 23 error condition occurred while reading data from the network. Please retry your request. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 04:30:31 GMT by s_wx1126 (squid/3.5.20)
Netbackup Status Code No Comments A read operation from a socket failedThere are several clues on Status Code 23 escalation error on Netbackup. The error itself raised depends on the several triggers, i.e : the corrupt of binaries files, OS patches or service pack (on Windows) issues, caches for concurrent disk writes, connectivity between master and media or client, etc.In my environment, there is a database oracle server where the backup was going smootlhy but suddently the backup was terminated and raised the status "23".Before I was going to check it deeply, I tried to check the server's environment first at the time of error raised, and I found if the CPU's idle was zero ('0'), because the oracle daemon had taken out all of the CPU and memory resources for processing data.I had tried to wait, until the processing was end and re-start the backup job. Finally the job was going succeded.From the experiences, I reached to the conclussion if the system (CPU and memory) resources busy could lead the netbackup status 23 (Socket Read Failed), beside the status code "134". I think it will be varry in every netbackup environment. Email This BlogThis! Share to Twitter Share to Facebook Newer Post Older Post Home 0 comment(s): Post a Comment Ads Popular Tags Recents Popular Posts Symantec Netbackup 7.5 Status Codes 0 the requested operation was successfully completed 1 the requested operation was partially successful 2 none of the requested files were b... bp.conf file The bp.conf is the master configuration file for the backup client software. With it the allowed servers and other options are ... Status Code 191 -- (NetBackup Error 191: no images were successfully processed) Error 191 raised when relocation of images to tape or duplication processes is get trouble. For Example when the duplication is going in pro... Status Code (196) : Client Backup was NOT Attempted Because Backup Windo