Bpbrm Cannot Connect Client
It could be as simple as ensuring that both hosts in question have the same configuration options for when to use VxSS.In the example above, re-adding the USE_VXSS = AUTOMATIC entry All rights reserved. Create a debug log directory on the source host and set verbose to 5. It should show the hostname and service name resolution and the outbound connection to the master server. The debug 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 navigate here
Click the name of the master server in the right pane5. Then it checks if the resolved hostname is in the server list (current server). If not, it queries the policy database to see if that hostname is used as a client in any policy Please provide all relevant info: OS version on client. Top This thread has been closed due to inactivity. her latest blog
Netbackup Cannot Connect On Socket
if windows does it have antivirus running? When executed, the command does the following. 1. telnet
NBU version on master, media server and client OS on master, media server and client Hostname lookup in your environment - DNS or hosts files? Is there any firewall software on the client? Go to Solution. Can't Connect To Client 58 Netbackup 7 On Windows client, disable Windows firewall.
No Yes How can we make this article more helpful? Netbackup Error Code 58 In Windows Client This log wil tell you how client is resolving server's incoming IP address to hostname and if this hostname can be matched with SERVER entry. Reason: Media is in use, Media server: MasterServ, Robot Type(Number): TLD(0), Media ID: N/A, Drive Name: N/A, Volume Pool: NetBackup, Storage Unit: MasterServ-hcart-robot-tld-0, Drive Scan Host: N/A, Disk Pool: N/A, Disk navigate to these guys Looking further however I can't find anything connecting on the ports being requested in the vnetd log, so again I'm left with a puzzle of why this is failing on the
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 Connect Failed Status (18) Connect_failed I have seen many times that a client belongs to another master server. 3) bpclntcmd -pn should returns the correct client hostname and IP address. 0 Kudos Reply Accepted Solution! It first does a reverse lookup of the incoming source IP address, that is the first hostname displayed on the second line of the command output. Article URL http://www.symantec.com/docs/TECH68832 Windows Bare Metal Restore (BMR) restore fails with status code 58: can't connect to client.
Netbackup Error Code 58 In Windows Client
Email Address (Optional) Your feedback has been submitted successfully! https://www.veritas.com/support/en_US/article.000024570 On serverkek3bkvnnp01, do the following: ping
On Linux client, stop and disable iptables. http://cmptp.com/cannot-connect/bcs-cannot-connect-to-the-lob-system.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 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 To test additionally I changed the setup to the following: BPCD connect back = Default Ports = Default Daemon connection port = Daemon port only Which also worked. Bptestbpcd: Exit Status = 25
Did you add separate hostnames for multiple NICs in hosts file on client itself? Status Failed (42) Connect_refused NBU client services need to be running on the client. Port 1556 open in both directions?
Waiting for resources.
Thank You! 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 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 Netbackup Port Numbers Labels: 7.1.x and Earlier Backing Up Backup and Recovery Configuring Error messages Monitoring NetBackup Troubleshooting 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution!
Then also determine the TCP port number for the daemon process on the destination host; veritas_pbx (default for NB 7.1+), vnetd (default for NB 6.0-7.0), bprd. 2. If successful you should see the No Yes Did this article save you the trouble of contacting technical support? Thank you both for the log commands, helped point me in the right direction, and find a work around until I get a solution in place. 0 Kudos Reply No Connect