Home > Cannot Connect > Veritas Netbackup Cannot Connect On Socket Status 25

Veritas Netbackup Cannot Connect On Socket Status 25

Contents

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical I uninstalled and reinstalled the client. You may also refer to the English Version of this knowledge base article for up-to-date information. Thanks, Randy Tue Jan 29, 2008 10:15 am Jeff Lightner Guest Status 25 - Cannot Connect On Socket You had a hard boot. check over here

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... No Yes Did this article save you the trouble of contacting technical support? Create/Manage Case QUESTIONS? No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities

Netbackup Cannot Connect On Socket Linux

Thanks 0 Kudos Reply After making the hosts file epsilon22222 Level 4 ‎01-31-2013 05:31 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Thanks, Randy ---------------------------------- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). VOX : Backup and Recovery : NetBackup : Error Status 25: cannot connect on socket (status ... Why would telnet fail with Marianne Moderator Partner Trusted Advisor Accredited Certified ‎10-18-2015 06:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend

  1. Email Address (Optional) Your feedback has been submitted successfully!
  2. No Yes Did this article save you the trouble of contacting technical support?
  3. Error Message Exit Status 25 - cannot connect on socket.
  4. Regarding the command being fired, it is normal bprestore command which is being executed with all the parameters required. /usr/openv/netbackup/bin/bprestore -r -L -R -C masterserver -Dmaster-server -S master-server -p
  5. No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES
  6. You might want to see if all the components are still there (e.g.
  7. All other types of communication are fine except for the actual attempt to backup data. 1.
  8. Step 3: If the master server can not connect to the client when trying to access the client host properties, below are steps you can take to further troubleshoot this issue:

if yes, from where you are actually trying to do the restore? I have in fact resolved 25 socket timeout on a system in the last month simply by doing a reboot after eliminating all other possibilities. As you have experienced -S wrong-name produced status 25. -Cwrong-namewill cause status 227 (no entity found). -Dwrong-name will cause some sort of connection error. Netbackup Bpclntcmd Can you show us output of traceroute?

Which of 33 services Netbackup installs do you recommend restarting? Netbackup Cannot Connect On Socket 25 Windows Step 4: A very useful command to help with testing client and server resolution is the command bpclntcmd -pn when run from a NBU client or media server. Anyone have any secrets I don't know about to resolve the issue? telnet: connect to address 10.28.1.236: No route to host telnet: Unable to connect to remote host: No route to host [email protected]# telnet s56upapp620-bak vnetd s56upapp620-bak/vnetd: Servname not supported for ai_socktype [email protected]#

Thank You! Bptestbpcd Main: Function Connecttobpcd Failed: 25 Backup BlogProduct DirectoriesEdit These Directories!Backup SoftwareBackup and Archive HardwareBackup Book WikiMiscellaneous ResourcesBackup Service ProvidersMailing ListsFAQsEdit These FAQs!NetBackup FAQNetWorker FAQTSM FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec What is the BPCD log saying on the master and client for the transaction? No Yes Did this article save you the trouble of contacting technical support?

Netbackup Cannot Connect On Socket 25 Windows

NB Processes ------------ root 8573 1 0 Jan 6 ? 4:44 /usr/openv/netbackup/bin/nbevtmgr root 8580 1 0 Jan 6 ? 2:41 /usr/openv/netbackup/bin/nbaudit root 8686 1 0 Jan 6 ? 3:46 /usr/openv/netbackup/bin/bprd root Create/Manage Case QUESTIONS? Netbackup Cannot Connect On Socket Linux Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Netbackup Error 58 Can't Connect To Client I even typed in a fake server name along with the other Media Server names and the installation recognized that the server name was bad. 5. I uninstalled 6.0 and

Email Address (Optional) Your feedback has been submitted successfully! check my blog Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The master server is getting a status code 25 (cannot connect on Labels: 7.1.x and Earlier Backup and Recovery NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Guest Status 25 - Cannot Connect On Socket Randy, Have you tired doing a telnet from the client to the master server? Bppllist -l Cannot Connect On Socket (25)

I've rebooted, uinstalled, reinstalled, lit a few candles and organized an all night vigil and still no luck. VOX : Backup and Recovery : NetBackup : bptestbpcd: EXIT status = 25 cannot connect on soc... CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical this content Article:000012138 Publish: Article URL:http://www.veritas.com/docs/000012138 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

Email Address (Optional) Your feedback has been submitted successfully! Error Code 25 In Netbackup It is possible that updates have been made to the original version after this document was translated and published. No Yes How can we make this article more helpful?

Handy NetBackup Links 0 Kudos Reply Contact Privacy Policy Terms & Conditions Backup Central HomeMr.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? netstat -a |grep bp tcp 0 0 *.bpdbm *.* LISTEN tcp 0 0 *.bpjobd *.* LISTEN tcp 0 0 *.bprd *.* LISTEN tcp 0 0 *.bpcd *.* LISTEN 0 Kudos Reply Labels: Backup and Recovery Linux NetBackup Troubleshooting 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Bptestbpcd Exit Status 25 It is possible that updates have been made to the original version after this document was translated and published.

If it had been working try to determine what changes may have been made to the client server's OS or the network links. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! I've added fqdn names to the host files as you mentioned on both the media server and the client and still get cannot connect on socket = 25 error when http://bovbjerg.net/cannot-connect/veritas-server-status-cannot-connect-on-socket.php I uninstalled the clients and pushed the install from the Master to verify communication and the install was successful. 7.

See screenshot attached, I have not been able to restart the services on the media server as backup to take library it is still running. I cannot backup any data and I cannot connect to the client via Client Properties on the Master Server GUI. Step 5: Ensure the client server has the bpcd and vnetd port in listening mode using the command netstat -a: On Windows:    TCP    dotto:vnetd       dotto.veritas.com:0  LISTENING TCP    dotto:bpcd        dotto.veritas.com:0  LISTENING   in case anything else is blocking communications 0 Kudos Reply Thanks for the replies guy.

I will have to wait until the current queued jobs finish to restart services... The source server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server. 0 Kudos Reply Thanks everybody for your alisdad Level For UNIX clients you can try removing the BPCD port from inetd.conf and run the command "bpcd -standalone" to see if that gets the port listening. Figure 1.   Media Server Log Files:  \volmgr\debug\daemon log13:10:27.432 [14832.14532] <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference implies that EMM could not be initialized via the PBX componentbptm log03:55:58.955

Go to Solution Error Status 25: cannot connect on socket (status 25) ver_65 Level 2 ‎02-09-2009 02:46 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email