Home > Error Code > Error Bpbrm Cannot Connect Status 58

Error Bpbrm Cannot Connect Status 58

Contents

Covering Symantec NetBackup, EMC Avamar and EMC DataDomain.. If you are using hosts files, you should have entries in /etc/hosts for clients on the server, and hosts entries on the client for master and media server(s). Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. http://megavoid.net/error-code/error-bpbrm-cannot-connect-to.html

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 When I attempt to do a backup, I get the followingin the Admin Console on the master server: Error bpbrm (pid=21078) cannot connect to filer3, Operation now in progress (150) can't There is no bpbrm messages on the master but on the media server, the bpbrm log contains: job_disconnect: Disconnected ConnectionCache::connectAndCache: Acquiring new connection for host alabama, query type 1 vnet_pbxConnect: pbxConnectEx Click the name of the master server in the right pane5.

Error Bpbrm Cannot Connect Status 58

kuldeep singh replied Aug 7, 2014 -Go the registry of client HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\Curr entVersion\Config -Check for the registry name SERVER -This registry should contain entry of master and media server -It should Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Please do the following test: Create bpcd log folder on the client. Client needs to connect back on same port. 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 Error Code 58 In Netbackup No Yes How can we make this article more helpful?

Email Address (Optional) Your feedback has been submitted successfully! Bptestbpcd Exit Status 25 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. To do so, from the Administration Console:1. No Yes Did this article save you the trouble of contacting technical support?

Just simply click apply and okay to commit those changes. Netbackup Error Code 58 In Windows Client No Yes Did this article save you the trouble of contacting technical support? Sorry, we couldn't post your feedback right now, please try again later. Backups fail with status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC).

Bptestbpcd Exit Status 25

Logs are below. 09/11/2013 22:20:36 - granted resource CA5548 09/11/2013 22:20:36 - granted resource HP.ULTRIUM3-SCSI.000 09/11/2013 22:20:36 - granted resource kek3bkvnnp01-hcart3-robot-tld-0 09/11/2013 22:20:36 - estimated 0 kbytes needed 09/11/2013 22:20:36 - https://www.veritas.com/support/en_US/article.000008622 How can we resolve? Error Bpbrm Cannot Connect Status 58 Did you remember to create bpcd folder on the client? Netbackup Cannot Connect On Socket Labels: 7.1.x and Earlier Backing Up Backup and Recovery Error messages Federal Government NDMP Option NetBackup Solaris 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution!

Thank You! navigate here philip_wernberg replied Aug 7, 2014 Can you ping the client? If so, please post. Then compares the resolved hostname to the server list ...16:52:46.092 [1160.5436] <2> bpcd valid_server: comparing hal.veritas.com and hal.veritas.com ... Status Failed 42 Connect_refused

If it exceeds that timeout then try using a host file entry to avoid DNS latency.If the client had been working at NBU 5.x release but now fails after upgrading to 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 You may also refer to the English Version of this knowledge base article for up-to-date information. Check This Out The client sees the incoming connection from source IP address 10.82.105.254 ...16:52:46.077 [1160.5436] <2> logconnections: BPCD ACCEPT FROM 10.82.105.254.44554 TO 10.82.110.6.13782  16:52:46.077 [1160.5436] <2> bpcd main: setup_sockopts complete ...

Troubleshooting procedures for Status 58 errors. Connect Failed Status (18) Connect_failed Solution Make sure the NetBackup media server is allowed access to the client at the following ports: 1556 (pbx)13724 (vnetd)13782 (bpcd) To limit the number of open ports 1556 is the When using the VMware agent and the error "can't connect to client" is encountered this indicates a failure internal to NetBackup communications.  This is not a failure between NetBackup and the VMware vCenter server,

Add the name of the client in question if it isn't listed 7.

Do you have, in client propoeties, the master and media servers inserted in SERVERS TAB? 0 Kudos Reply Hi Andy, Wow, what a quick RickyB Level 3 ‎11-23-2011 08:46 AM Options Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2016 (1) ► Apr (1) ► 2015 (3) ► Jun (3) ► 2014 (7) ► Sep (7) ► Sorry, we couldn't post your feedback right now, please try again later. Netbackup Port Numbers Handy NetBackup Links 0 Kudos Reply NetBackup Client software Will_Restore Level 6 ‎08-28-2013 01:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend

Netbackup - Error '(58) Can't Connect to Client" olakunleoj asked Aug 7, 2014 | Replies (3) I was using netbackup for my backup, the netbackup was on Solaris 10 and I If it's not there could be a firewall blocking connectivity - check this out. The majority of the causes of this issue are due to the client not listening on the BPCD or VNETD ports, the master server unable to resolve the client by hostname, this contact form See the example below- In this example the client hostname is dotto.veritas.com and the master server is hal9000.veritas.com-C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -pnexpecting response from server hal9000.veritas.comdotto.veritas.com dotto.veritas.com 10.82.110.63412 Creating a bplist log on

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 Just looked like the errors you get when the client s/w isn't installed on the client (which obviously it isn't on a filer!). Sathisp83 Level 3 Certified ‎08-26-2013 11:33 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I'm getting the below error Launch the NetBackup Administration Console, connecting to the master server2.

Sorry, we couldn't post your feedback right now, please try again later. Click the name of the master server in the right pane 5. You may also refer to the English Version of this knowledge base article for up-to-date information. status: 58: can't connect to clientcan't connect to client  (58)  Cause The NetBackup media server is unable to connect to the NetBackup client at the required ports.

For Linux clients, if they are missing a library file required by bpcd or vnetd, you would get this type of error message:telnet localhost 13782Trying 127.0.0.1...Connected to clientname.domainname.comEscape character is '^]'.bpcd: