Backups Failing With Error 58
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 netbackup error 58 can't connect to client Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体)
Netbackup Error 59
English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 58: "Can't connect
Bptestbpcd
to client". Backups fail with status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC). Article:000027851 Publish: Article URL:http://www.veritas.com/docs/000027851 Support / Article Sign In Remember me
Netbackup Cannot Connect On Socket
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 Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 58: "Can't connect to client". Backups fail with bptestbpcd exit status 25 status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC). Error Message can't connect to client Solution Overview: A Status 58 will occur when the server cannot connect to the client. This can occur for standard backups when there are problems with hostname resolution or network routing. This can also occur during catalog backups when the master server cannot make a network connection to a media server in order to read the catalog data. This can also happen when NetBackup Access Control (NBAC) is configured incorrectly.Troubleshooting:Verify the forward and reverse hostname lookups are working for the client. Also verify the network path is valid for the host. From the media server run the command:# telnet
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 netbackup status code 13 In CommunityCategoryBoardResourcesUsers turn netbackup port numbers on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. vnetd port number Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Backup failing with error code 58 VOX : Backup and Recovery : NetBackup https://www.veritas.com/support/en_US/article.000027851 : Backup failing with error code 58 Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup failing with error code 58 Jecintha Level 4 Certified 07-29-2012 09:13 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend https://vox.veritas.com/t5/NetBackup/Backup-failing-with-error-code-58/td-p/456483 Report Inappropriate Content Hello, I see that backup for a particular windows host is failing with error code 58. The server is reachable, however, in host properties, I see that the status of the server is Cannot connect to Socket (25). I tried stopping and restarting the services running bpdown and bpup. This has also not been of much help. Appreciate any help in this regard. Regards, Jecintha Labels: Backing Up Backup and Recovery NetBackup Troubleshooting 3 Kudos Reply 10 Replies Hi, K33 Level 4 07-29-2012 09:17 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi Kindly look the technote http://www.symantec.com/business/support/index?page=content&id=TECH68832 Check this fourms. https://www-secure.symantec.com/connect/forums/backup-failing-server-error-code-58 0 Kudos Reply Hello Kashish, Thanks for the Jecintha Level 4 Certified 07-29-2012 09:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello Kashish, Thanks for the reply. I went through the forum link attached. There was an update that the below mentioned services should be running
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 https://www.veritas.com/support/en_US/article.TECH45551 Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 25, 41, 58, and 160: Oracle RMAN backups fail intermittently http://nayabrasools.blogspot.com/2013/05/troubleshooting-netbackup-error-code-58.html Article:000030664 Publish: Article URL:http://www.veritas.com/docs/000030664 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 error 58 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 STATUS CODE 25, 41, 58, and 160: Oracle RMAN backups fail intermittently Solution Overview: Oracle RMAN backups fail intermittently with status codes 25, 41, 58, and 160. Troubleshooting: The intermittent nature of the failure presents difficulty in pinpointing backups failing with the cause of the problem. In this case, review the dbclient log file (on the Oracle server) and the bpsched log (on the master server) for any of the error messages listed under the log file section. Log files: The above listed error messages are seen in various master and client server log files outlined below. Status Code 25 is seen in the dbclient log file on the Oracle server. <16> serverResponse: ERR - server exited with status 25: cannot connect on socketStatus Code 41is seen in the dbclient log file on the Oracle server. <16> check_comm_file_for_error: ERR - server exited with status 41: network connection timed outStatus Code 58 is seen in the bpsched log file on the master server. <16> log_in_errorDB: failure logging message to client nbuclient in log /usr/openv/netbackup/logs/user_ops/dbext/logs/3657934.0.1132178989: can't connect to client (58)Status Code 160is seen in the dbclient log file on the Oracle server. <16> bsa_checkFeatureId: Server exit status = 160: authentication failedAdditionally, the bpsched log file shows the following error message:<2> logconnections: getsockname(7) failed: 22<8> bpcr_setup_sockopts: setsockopt TCP_NODELAY failed on fd 7Resolution: The connection between the Oracle client server and the other Veritas NetBackup (t
enabled Please turn of and check else try to add the bpcd, vnetd, and pbx port to firewall exceptiton rules. and check. if that does not work.. please proceed with the below troubleshooting steps From Master :- --> ping