Error Bpbrm Cannot Connect On Socket
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside netbackup error 58 can't connect to client Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In
Netbackup Error Code 59
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps
Netbackup Cannot Connect On Socket
you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX
Bptestbpcd
: Backup and Recovery : NetBackup : Problems with backup, cannot connect on socket(25) VOX : Backup and Recovery : NetBackup : Problems with backup, cannot connect on socket(25) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer bptestbpcd exit status 25 Friendly Page Solved! Go to Solution Problems with backup, cannot connect on socket(25) Eamonn Level 3 05-31-2011 02:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Master + Media servers: Netbackup 7.0.1, Windows Server 2003 R2 Clients: Netbackup 7.0.1, and 6.5.3, Windows Server 2008 (non-R2) Getting consistent failures on 3 clients lately with error 25 on the child job, cannot connect on socket(25) Happens with Full and Cumulative Incremental backups. Have tried the following: Rerun the jobs during the day (normally run at night) - Still fails Created a brand new policy (not copying the old one) - Also fails Telnet to BPCD port - Successful response from all servers to the clients Adding the required network interface - Still fails Changing the timeout connections - Still fails Pinging/NSlookup/bptestbpcd from the master/media servers - Everything a
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 netbackup error code 58 in windows client Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal netbackup port numbers Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet vnetd port number STATUS CODE 58: Can't connect to client. Troubleshooting procedures for Status 58 errors. Article:000037729 Publish: Article URL:http://www.veritas.com/docs/000037729 Support / Article Sign In Remember me Forgot Password? Don't have https://vox.veritas.com/t5/NetBackup/Problems-with-backup-cannot-connect-on-socket-25/td-p/397975 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. Troubleshooting procedures for Status 58 https://www.veritas.com/support/en_US/article.TECH68832 errors. Error Message Status Code: 58 Solution Overview: A status 58 error can occur during connections to legacy processes; bpcd, bprd, bpdbm, bpjobd, vmd, etc. typically from master or media server to client, but alsofrom master server to media server, orfrom media servers to master, orfrom client to master servers, orin very rare cases from client to media server. The cause is that either a TCP SYN request did not reach the destination host, orthe expected processes were not listening on the destination host, orthe TCP SYN+ACK returned by the destination host did not reach the source host, orthe destination host could not validate that the inbound connection was from a valid NetBackup (NB) host, orthat PBX or vnetd on the destination host could not transfer the connection the desired daemon, orin rare instances that the destination host could not create a connection to the source host - for the same reasons as noted above. The majority of these situations are due to the TCP port(s) not being open through the firewall, daemon processes not running and listening on the dest
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business https://vox.veritas.com/t5/NetBackup/Issue-25-cannot-connect-on-socket/td-p/734077 Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In 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 netbackup error instead for Do you mean VOX : Backup and Recovery : NetBackup : Issue : (25) cannot connect on socket VOX : Backup and Recovery : NetBackup : Issue : (25) cannot connect on socket Subscribe to RSS Feed Mark Topic as New Mark Topic as Read cannot connect on Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Issue : (25) cannot connect on socket amit4465 Level 3 09-03-2015 03:33 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content bash-3.2$ sudo /usr/openv/netbackup/bin/admincmd/bptestbpcd -client saaclalt1-nbu -debug 11:17:30.811 [19924] <2> bptestbpcd: VERBOSE = 0 11:17:40.849 [19924] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.666: pbxSetAddrEx/pbxConnectEx return error 62:Timer expired 11:17:40.849 [19924] <8> do_pbx_service: [vnet_connect.c:2034] vnet_pbxConnect() failed 18 0x12 11:17:40.850 [19924] <8> do_pbx_service: [vnet_connect.c:2035] save_errno 62 0x3e 11:17:40.850 [19924] <8> do_pbx_service: [vnet_connect.c:2036] use_vnetd 0 0x0 11:17:40.850 [19924] <8> do_pbx_service: [vnet_connect.c:2037] cr->vcr_service bpcd 11:17:40.850 [19924] <8> async_connect: [vnet_connect.c:1630] do_service failed 18 0x12 11:18:03.212 [19924] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3485] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 11:18:27.212 [19924] <8> do_vnetd_service: [vnet_connect.c:1955] remote host supports PBX, but PBX is not running 0 0x0 11:18:27.212 [19924] <8> vnet_vnetd_serv