Home > Cannot Connect > Cannot Connect On Socket Netbackup Linux
Cannot Connect On Socket Netbackup Linux
What could be the problem Antivirus ?(i use the same AV for the other servers but it is working fine). The following information applies only to UNIX, Linux, and Macintosh systems: The master server is the first SERVER entry in the bp.conf file. And only one network card is used on this server as well as the Netapps. Register now while it's still free! https://vox.veritas.com/t5/NetBackup/new-Linux-client-25-cannot-connect-on-socket/td-p/148043
Netbackup Error 25 Cannot Connect On Socket
thing.The linux client is not in domain; its in workgroup.we had just added the entry in the host file in both the servers, through which its communicating.So nslookup doesnt work in Can you ping the server? Make sure that the /usr/openv/volmgr/database/3pc.conf file exists. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on
If necessary, stop and restart NetBackup. PBX??? 0 Kudos Reply Re: cannot connect a linux client Andy_Welburn Moderator Trusted Advisor 12-05-2008 01:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to You may also refer to the English Version of this knowledge base article for up-to-date information. Netbackup Error Code 25 The following information applies only to UNIX and Linux systems: Verify that the /etc/services file (and NIS services if NIS is used) has entries for the NetBackup services: bpcd, bpdbm, and
The script is in /usr/openv/netbackup/bin/goodies. Bpcd Port Number Thanks for posting this. We made a dedicated subnet and that helped 50% of the problems go away. Thanks.
Netbackup Cannot Connect On Socket 25 Windows
If the backup fails again, run the bptpcinfo manually to generate the file 3pc., then try the backup again. Article:000008360 Publish: Article URL:http://www.veritas.com/docs/000008360 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 Netbackup Error 25 Cannot Connect On Socket These errors are Recommended Action: Do the following, as appropriate: Verify that bpcompatd, vnetd, and Private Branch Exchange (PBX) are running. Netbackup Cannot Connect To Client 58 WHAT is with this service????
There are no firewalls active anywhere. navigate to this website If you have received this communication in error, please notify us immediately by email reply. With NetBackup database extensions: Make sure that the applicable database product has the correct permissions allowing NetBackup to write to the progress log on the client. See www.veritas.com for ordering information (161)Linux is just a client in our env.Thanks in advance 0 Kudos Reply Re: new Linux client - 25 cannot connect on socket sdo Moderator Partner Bptestbpcd Cannot Connect On Socket
Check the services file. On NetWare target clients: The master server name is the first SERVER entry in the bp.ini file. Click Here to join Tek-Tips and talk with other members! http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-status-25-netbackup-linux.html But .... 0 Kudos Reply Re: cannot connect a linux client Andy_Welburn Moderator Trusted Advisor 12-04-2008 06:51 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print
Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : cannot connect a linux client VOX : Backup and Recovery : NetBackup : cannot
In fact we get a serious amount of EZ24 errors from our L700 --- No resonse from server.As far as I know there really is little beyond bumping maxuprcs, that you Thanks. On a Windows master server, verify that the NetBackup Request Manager and NetBackup database manager services are running. Bpcd Log 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
Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature. OKI have write in host file (server and client) the IP+hostname+simplename. This problem can occur in the following situation: when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running. click site Red Flag This Post Please let us know here why this post is inappropriate.
Enable SAR and then you can see if you may be swapping (We were) and out of CPU resource. If these processes are not running, start them. from master (can also do this from the client to master)bpclntcmd -pnbpclntcmd -ip client_ip_addbpclntcmd -hn client_hostnamenslookup client_ip (do this twice - should give same result)nslookup client_hostname (do this twice - should By joining you are opting in to receive e-mail.
Check the following &CompanyName; support Web site to ensure that all recommended NetBackup patches are installed: www.symantec.com/business/support/ Then select "NetBackup" followed by "files and updates." If failure occurs when you run If you run multiple backups concurrently to Netbackup from Oracle on Linux, you may receive intermittent failures with the following error message: serverResponse: ERR - server exited with status 25: cannot But the ping comand works for both IP & hostname.One more interesting thing is that...when we ran bpgetconfig comand in client ...we are getting the error asEvaluation software has expired. RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 15 Sep 09 01:18 Hi Aix,NDMP protocol version 4.
RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 23 Sep 09 11:55 Hi santhas,Yes, the filers credentials are verified, and I have added it as NDMP host. You need at least one licence for each client type.You may be able to get a temporary licence from your reseller - or possibly from Symantec Sales if you ask nicely.Message