Labels: 7.1.x and Earlier Backup and Recovery Error messages NetBackup Windows 7 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! ... Most likely firewall software of some sort; see the Firewall topics above for some possibilities.Checking for Name Resolution DelaysWhen testing connections to bpcd and other daemons be sure to check the time difference delta 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: No Yes Did this article save you the trouble of contacting technical support? Source
Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! status: 58: can't connect to client 08/06/2014 09:08:17 - end writing can't connect to client (58) Join this group Popular White Paper On This Topic The Difference Between Microsoft Azure & RE: cannot connect on socket Gaskin69 (IS/IT--Management) (OP) 14 Jan 04 08:24 Master server (Netbackup 4.5 Datacenter) is Win 2k not Unix and it is on a SSO environment, it acts Go to Solution Status 58 = can't connect to client.
Backups fail with status code 58 after enabling Veritas Security Services (VxSS) and NetBackup Access Control (NBAC). Solved! Host-resident Firewalls Typically, any conflicting firewalls are located within the network cloud. However, they can also reside on the end-stations and cause problems. For NB 6.x and earlier UNIX hosts, check the Make sure the media server can resolve the host name of the backup host to the correct IP address. 3.
status: 48: client hostname could not be found 2013-02-08 09:54:11 - Error bpbrm(pid=7200) client restore EXIT STATUS 48: -Your data has been truncated. No Yes How can we make this article more helpful? Create/Manage Case QUESTIONS? Netbackup Error Code 58 In Windows Client Performs a successful reverse lookup of the incoming IP address and gets the hostname ...16:52:46.092 [1160.5436] <2> bpcd peer_hostname: Connection from host hal.veritas.com (10.82.105.254) port 44554 ...
These servers are all NT4 or 2000.They backup with no errors. Netbackup Cannot Connect On Socket Close this window and log in. Join UsClose ExchangeBlog Blog technologii MS Exchange Server Skip to content Home Exchange Updates Lync Updates Tools Sites HelpDeskTop SharePointBlog ITinUse Authors Contact ExchangeBlog » Tips » Exchange 2010 GRT restore https://www.veritas.com/support/en_US/article.000024722 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
Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem STATUS CODE 58: "Can't connect to client". Status Failed (42) Connect_refused 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 Job details show that connection was attempted first on PBX (port 1556), then vnetd (port 13724), then bpcd (13782). RE: cannot connect on socket bpBlade (TechnicalUser) 14 Jan 04 02:05 I am getting error 57 messages, client connection refused in attempting to backup File shares in a SAN environment.specs are
No Yes Log In E-mail or User ID Password Keep me signed in Recover Password Create an Account Blogs Discussions CHOOSE A TOPIC Business Intelligence C Languages Cloud Computing Communications NetBackup 6.x and 7.x firewall port requirements http://www.symantec.com/docs/TECH136090 Handy NetBackup Links View solution in original post 0 Kudos Reply 4 Replies Be convinced that Windows ipmanyak Level 4 04-27-2014 11:19 PM Netbackup Error Code 59 Use hostnames to test - not IP addresses (Your policy seems to be using IP address 172.24.131.244 and not client hostname). Bptestbpcd Exit Status 25 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
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 ... It is possible that updates have been made to the original version after this document was translated and published. 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 have a peek here Create/Manage Case QUESTIONS?
Go to Solution Cannot connect to client madhuri Level 4 04-27-2014 10:53 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Connect Failed Status (18) Connect_failed Are you aComputer / IT professional?Join Tek-Tips Forums! You may also refer to the English Version of this knowledge base article for up-to-date information.
You're now being signed in. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Email Address (Optional) Your feedback has been submitted successfully! Netbackup Port Numbers Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters.
On UNIX hosts: netstat -a -p | grep LISTEN *.vnetd *.* 0 0 49152 0 LISTEN 7326/vnetd*.1556 *.* 0 0 49152 0 LISTEN 1839/pbx_exchange*.bpcd *.* 0 0 49152 0 LISTEN 2748/bpcd...snip... Note: Use the 'netstat -n' option to suppress service name resolution and display the TCP port numbers 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. Check This Out NBU version on master, media server and client OS on master, media server and client Hostname lookup in your environment - DNS or hosts files?
Some articles for help: Troubleshooting procedures for Status 58 errors. Client software already installed and even i restarted the services, again its failing. In this specific case the NetBackup media server is separate from the NetBackup VMware backup host and the NetBackup media server is unable to reach the standard NetBackup ports on the Error Message can't connect to client Solution Overview: A Status 58 will occur when the server cannot connect to the client. This can occur for standard backups when there are problems
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, RE: cannot connect on socket PGPhantom (IS/IT--Management) 12 Jan 04 14:42 What error??Specifics?? Note the NetBackup daemon running and listening check and the bpps check in section three.On Windows, verify that the %SystemRoot%system32driversetcservices file has the correct entries for bpcd, bpdbm, and bprd.Also, verify If these services are not running, start them.If the above processes or services are running, examine the All Log Entries report for the time of the failure to determine where the
Create/Manage Case QUESTIONS? Sorry, we couldn't post your feedback right now, please try again later. It is possible that updates have been made to the original version after this document was translated and published. Make sure that the /usr/openv/volmgr/database/3pc.conf file exists.
RE: cannot connect on socket Gaskin69 (IS/IT--Management) (OP) 12 Jan 04 15:13 Cannot connect on socket error(25) RE: cannot connect on socket PGPhantom (IS/IT--Management) 12 Jan 04 15:53 To provide good Client needs to connect back on same port. 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.