Home > Connect To > Connect Failed Status (18) Connect_failed Netbackup

Connect Failed Status (18) Connect_failed Netbackup

Contents

Error Message 1: (58) can't connect to client 2: (58) can't connect to client 3: (58) can't connect to client 4: (58) can't connect to client From job details:02/12/2015 06:16:46 - Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may Job details show that connection was attempted first on PBX (port 1556), then vnetd (port 13724), then bpcd (13782). Required fields are marked * Name * Email * Website Comment You may use these HTML tags and attributes:
his comment is here

Go to Solution cannot connect to client madhuri Level 4 ‎02-18-2014 10:35 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate enable the bpcd log in the client with Verobse 5 and try the backup again and attach the log. Job details show that connection was attempted first on PBX (port 1556), then vnetd (port 13724), then bpcd (13782). 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 https://www.veritas.com/support/en_US/article.000024722

Connect Failed Status (18) Connect_failed Netbackup

status: 58: can't connect to client  Cause A NetBackup VMware agent backup using the VMware policy type makes use of a NetBackup server identified as the VMware backup host.  The VMware backup host Veritas does not guarantee the accuracy regarding the completeness of the translation. Stop & Restart Netbackup.  Check Policy again if it shows Policy Select Type as "NDMP" Test backups.    Terms of use for this information are found in Legal Notices.

Related Articles Article URL http://www.symantec.com/docs/TECH130453 0 Kudos Reply Follow the above suggestions watsons Level 6 ‎04-28-2014 01:45 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a

For more information on NetBackup port requirements see the NetBackup firewall port requirements documentation link below.Applies ToNetBackup 7.5.0.x Terms of use for this information are found in Legal Notices.

Related Client host properties shows cannot connect to socket. If the command has a failure, look at the reported NBU status code with "echo %ERRORLEVEL%" on Windows, and "echo $?" on Unix/Linux. 0 Kudos Reply Cannot be too much of Bptestbpcd White Papers & Webcasts Concur SMB Expense Policy Template Engaging the New IT Buyer: 4 Social Media Trends and How Marketers Should Adjust Gaining and Executing a Smarter Understanding of Customers

Go to Solution. Status: 58: Can't Connect To Client If not, check that firewall software on client is disabled. Bookmark the permalink. « Backup Exchange 2010 DAG using Symantec Netbackup Microsoft Exchange 2013 Deployment Assistant available » Leave a Reply Cancel reply Your email address will not be published. You may also refer to the English Version of this knowledge base article for up-to-date information.

Veritas does not guarantee the accuracy regarding the completeness of the translation. Bpclntcmd -clear_host_cache Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Cannot connect to client VOX : Backup and Recovery : NetBackup : Cannot connect Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Vmwar Backups Fail with Status 58  Or " connect failed STATUS (18) CONNECT_FAILED   " 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

Status: 58: Can't Connect To Client

Toolbox for IT My Home Topics People Companies Jobs White Paper Library Collaboration Tools Discussion Groups Blogs Follow Toolbox.com Toolbox for IT on Twitter Toolbox.com on Twitter Toolbox.com on Facebook Topics Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup of Windows client failing with Status 58. Connect Failed Status (18) Connect_failed Netbackup Therefore, restore job finish with error. Status Failed (42) Connect_refused what is the output of bptestbpcd -client -verbose -debug from the Media server?

Handy NetBackup Links 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and this content The media server will attempt to connect to the client bpcd port via the following port numbers: 1556 (pbx) 13724 (vnetd) 13782 (bpcd) The NetBackup media server will try connecting to Still facing issues for few clients with status 58. blocking operation is currently executing.... Info Bpbkar(pid=0) Done. Status: 58: Can't Connect To Client

  1. Veritas does not guarantee the accuracy regarding the completeness of the translation.
  2. Are you backing up other client's properly or are you having issues across the board? 0 Kudos Reply Please tell us all relevant Marianne Moderator Partner Trusted Advisor Accredited Certified ‎08-28-2013
  3. Top This thread has been closed due to inactivity.
  4. NetBackup 6.x and 7.x firewall port requirements http://www.symantec.com/docs/TECH136090 Handy NetBackup Links 0 Kudos Reply Solved thanq madhuri Level 4 ‎06-11-2014 12:33 AM Options Mark as New Bookmark Subscribe Subscribe to
  5. No Yes Did this article save you the trouble of contacting technical support?
  6. I was expecting to see the port number and IP address that is used to connect to the client.

Also on the Master can you run: bptestbpcd -client does that fail too? Go to Solution Status 58 = can't connect to client. Use hostnames to test - not IP addresses (Your policy seems to be using IP address 172.24.131.244 and not client hostname). weblink No Yes How can we make this article more helpful?

Check the Policy which failed , If it does not show Policy Select Type as "NDMP"; This will confirm your Netbackup NDMP License is Expired.  Apply New License on NDMP host. Port 1556 open in both directions? This is normal behavior for restore to connect to CAS Array first and then to Mailbox role server.

Handy NetBackup Links 0 Kudos Reply « Previous 1 2 3 Next » Contact Privacy Policy Terms & Conditions Log In E-mail or User ID Password Keep me signed in

Please do the following test: Create bpcd log folder on the client. That would be "bpcd -standalone" and "vnetd -standalone". Thank You! If it's not there could be a firewall blocking connectivity - check this out.

Client needs to connect back on same port. Thanks! status: 58: can't connect to client can't connect to client (58) 0 Kudos Reply NBU version is 7.1.0.1 will Marianne Moderator Partner Trusted Advisor Accredited Certified ‎09-12-2013 02:57 AM Options http://haywirerobotics.com/connect-to/can-39-t-connect-to-camera-fix.html Labels: Backup and Recovery Error messages NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

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 NBU version on master, media server and client OS on master, media server and client Hostname lookup in your environment - DNS or hosts files? On Windows client, disable Windows firewall. The backup host is a stand-alone NetBackup client, so separate from the NetBackup media server that will be writing backup images to storage unit.

If it's not there could be a firewall blocking connectivity - check this out. Thank You! olakunleoj replied Aug 7, 2014 Please, how can I rectify it? So, it seems that there is either a firewall between the media server and the client, or else OS firewall on the client is blocking port connections.

You may also refer to the English Version of this knowledge base article for up-to-date information.