Netbackup Error Socket Open Failed
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 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 : Error code 21-Socket open failed in NetBackup VOX : Backup and Recovery : NetBackup : Error code 21-Socket open failed in NetBackup 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 Error code 21-Socket open failed in NetBackup Raz_Sam Level 3 10-23-2013 03:26 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, I was facing error code 21- Scoket open failed issue from long back. While trouble shooting, I have restarted NetBackup Client Service. Still am facing same issue. Can any one suggest on this and provide solution for this to fix it. OS: Windows NetBackup version: 6.5 Thanks in Advance, Sam. Solved! Go to Solution. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Have you confirmed that Marianne Moderator Partner Trusted Advisor Accredited Certified 10-23-2013 09:48 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Have you confirmed that Windows firewall is disabled on the client? If there is a company firewall, confirm that vnetd (port 13724) is open in both directions. Status 21 is normally client unable to connect back. Please create bpcd log folder on the client under ...\veritas\netbackup\logs and run the following from cmd on master and/or media server: bptestbpcd -client
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 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 : 21-Socket open failed VOX : Backup and Recovery : NetBackup : 21-Socket open failed Subscribe to https://vox.veritas.com/t5/NetBackup/Error-code-21-Socket-open-failed-in-NetBackup/td-p/583806 RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page 21-Socket open failed madhuri Level 4 11-13-2014 01:42 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, I was facing error code 21- Scoket open failed issue. https://vox.veritas.com/t5/NetBackup/21-Socket-open-failed/td-p/643985 I have executed the above command "bptestbpcd -client
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision https://vox.veritas.com/t5/NetBackup/21-socket-open-failed/td-p/431249 2016 Developers Blogs Groups Vision 2016 Sign In https://vox.veritas.com/t5/NetBackup/Randomly-getting-status-21-socket-open-failed-for-backups/td-p/736598 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 error NetBackup : (21) socket open failed VOX : Backup and Recovery : NetBackup : (21) socket open failed Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page (21) socket open failed stevenfoo Level 4 10-24-2011 06:05 AM Options Mark netbackup error socket as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content master/media server: NB 7.1.0.2 (windows 2008 R2) client: hp-ux 11.23 (with NB client 6.5) while trying to connect we encounter (21) socket open failed. we taken several forum steps to resolved the issue but could not. at last we remove the client and other the other stuff of veritas and the reinstall again. it was working after that after more than half a day. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Troubleshooting 0 Kudos Reply 9 Replies This is usually a host name Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified 10-24-2011 06:22 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content This is usually a host name comparision error connected to DNS or similar. Perhaps when you re-installed the Server list in th
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 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 : Randomly getting status: 21: socket open failed fo... VOX : Backup and Recovery : NetBackup : Randomly getting status: 21: socket open failed fo... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Randomly getting status: 21: socket open failed for backups Noor_Toorabally Level 4 07-08-2015 12:55 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I have been getting errors as follows randomly for both standard and oracle (RMAN) backups on my netbackup master server. The version of the server is 7.5.0.7 running on RHEL 5.11 The version of the clients are 7.5.0.4 (SAN Clients) Ther version of the Media servers are 7.5.0.4 (SAN Media). The logs shows the following, I would like to know if there is any way to start digging for the cause of this issue: 07/05/2015 00:00:37 - Info nbjm (pid=9601) starting backup job (jobid=1635947) for client seprdu01, policy RMAN_SEPRDU01_BD, schedule Default-Application-Backup 07/05/2015 00:00:37 - Info nbjm (pid=9601) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1635947, request id:{64B718AC-22CA-11E5-8292-439B8376C6B8}) 07/05/2015 00:00:37 - requesting resource sesegx2x-hcart3-robot-tld-1 07/05/2015 00:00:37 - requesting resource sesegx10.sagir.qc.NBU_CLIENT.MAXJOBS.seprdu01 07/05/2015 00:00:37 - requesting resource sesegx10.sagir.qc.NBU_POLICY.MAXJOBS.RMAN_SEPRDU01_BD 07/05/2015 00:00:37 - Waiting for scan drive stop HP.ULTRIUM4-SCSI.002, Media server: sesegx27 07/05/2015 00:00:38 - granted resource sesegx10.sagir.qc.NBU_CLIENT.MAXJOBS.seprdu01 07/05/2015 00:00:38 - granted resource sesegx10.sagir.qc.NBU_POLICY.MAXJOBS.RMAN_SEPRDU01_BD 07/05/2015 00:00:38 - granted resource S00830 07/05/2015 00:00:38 - granted resource H