Home > Cannot Create > Cannot Create Data Socket The Operation Completed Successfully
Cannot Create Data Socket The Operation Completed Successfully
Marianne Moderator Partner Trusted Advisor Accredited Certified 10-12-2010 12:09 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Highest possible Then, retry the operation and check the resulting debug logs. * The following information applies only to Sun Solaris: Verify that all operating system patches are installed. VOX : Backup and Recovery : NetBackup : Restoration Fails with message cannot create data ... The bpcd log is full of ERRNO=2 messages. have a peek here
Go to Solution Issue : (25) cannot connect on socket amit4465 Level 3 09-03-2015 03:33 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Issue : (25) cannot connect on socket VOX : Backup and Recovery : NetBackup It seems that client is receiving incoming connections, but is unable to connect back on 1556, 13724 or13782. The netsh takes effect instantly, the registry keys require a reboot.
I had one client error out with status 13 on the system state, but when I reran the job it completed sucesfully. See the Operating Notes section of the NetBackup Release Notes. * The following information applies only to Windows systems: Verify that the recommended service packs are installed. ****************************************************** You might want On which port? If connecting to the client takes that long then something is going amiss so may be a DNS issue - try using the hosts file on the client and adding the
Check that the server is not running out of disk space, especially on its system drive which could be affecting its performance and VSS capabilities 3. As they are IIS servers you may need to exclude or stop the web catalogs during the backups (if that is possible in your environment) - see this tech note: http://www.symantec.com/docs/TECH19904 Failures are typically 21, 23, 25 (changes each time, and one drive's job might fail with a 21, while another with 23 or 25) Happens with Full and Cumulative Incremental backups. Reverse lookup enabled on DNS?
Consider the below scenario where bpbrm wants to fork bpbkar in client. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem NetBackup has been using the PBX port for communication between unified processes Rais logging level up to get more details if needed. No need to perform any further troublehooting from NBU side.
try to telnet
bpcd from the master just to be sure.How are the tape drives? https://vox.veritas.com/t5/NetBackup/Constant-errors-21-23-and-25/td-p/431800 Labels: AIX Backup and Recovery Error messages NetBackup 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! It looks like I have to create some folders and turn on logging from the master server. bash-4.2$ uname -a AIX saaclalt1 1 6 000076FBD400 bash-4.2$ cat /usr/openv/netbackup/bin/version NetBackup-AIX53 184.108.40.206 bash-4.2$ ps -ef | grep bpcd root 13762766 1 0 Sep 03 - 0:02 /usr/openv/netbackup/bin/bpcd -standalone
Create/Manage Case QUESTIONS? http://skimwp.org/cannot-create/cannot-create-data-socket-error-0-0.php Check output of 'ps -ef' on client and look for these processes: /usr/openv/netbackup/bin/bpcd -standalone /usr/openv/netbackup/bin/vnetd -standalone /opt/VRTSpbx/bin/pbx_exchange Before you test again with bptestbpcd, create bpcd log folder on the client. Handy NetBackup Links 0 Kudos Reply Refer this Mahesh_Roja Level 6 10-13-2010 05:09 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Troubleshooting 0 Kudos Reply 9 Replies Error bpbrm(pid=5736) Marianne Moderator Partner Trusted Advisor Accredited Certified 10-12-2010 08:56 AM Options Mark as
For detail, check Troubleshooting Guide. A couople of weeks ago 2 of the 35 servers this machine backs up starting having this error. Another odd issue with these clients is when the jobs start up they take a very long time to start attempting to back up data (vs how long it takes job Check This Out No Yes How can we make this article more helpful?
Handy NetBackup Links 0 Kudos Reply Thanks, I will look at mrtba Level 4 10-12-2010 11:23 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Anyone run in to anything similar that might be able to shed some light on how to resolve this? For first, enable debug logging Yasuhisa_Ishika Level 6 Partner Accredited Certified 10-25-2011 05:21 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report
What makes this more confusing is the errors are intermittent.
Handy NetBackup Links 0 Kudos Reply sorry if there was confusion Daryl_Kinnaird Level 4 10-12-2010 12:15 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Did you add separate hostnames for multiple NICs in hosts file on client itself? Also have a look at the client's bpbkar log around the same time period. How does media server resolve client hostname and IP for backup NIC?
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 For first, enable debug logging Yasuhisa_Ishika Level 6 Partner Accredited Certified 10-25-2011 05:21 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report The jobs fail more often than they succeed. this contact form 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
NBU is not going to work if network connection at TCP-level is unsuccessful. BPBRM_VERBOSE = 6 0 Kudos Reply Level 6? No Yes Did this article save you the trouble of contacting technical support? Email Address (Optional) Your feedback has been submitted successfully!
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 I do not recommend starting with level 5 logging (only when requested by Tech Support) - something between 1 and 3 should give good enough indication. Error bpbrm(pid=5736) cannot create data socket, The operation completed successfully. (0) The job then terminates with a status 21. Can you telnet from the client to the master and/or media server on port 1556 and 13724?
Just on a hunch. 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. In which direction is telnet unsuccessful? As well when I try to load host properities on either of the clients it can take upwards to 15 minutes to bring up the information, where as our other clients
The same error can be seen for connect-back attempts for all 3 ports: 17:28:33.370  <16> get_vnetd_socket: vnet_end_connect_back failed: 10 17:28:33.370  <16> process_requests: get_vnetd_socket failed: 25 Handy NetBackup Links 0 Host properties loaded with in a minute or two on both clients, which is a lot better than in the past. This means that if the backup is still failing with the same error, the problem is not with host cache. 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
DNS for resolution of hostnames. In addition, check following points. * DNS is stable * UAC is disabled * firewall is disabled, or port 1556 is open View solution in original post 0 Kudos Reply 6 And sorry for late response. Which NBU version on client?
On which port?