Table of Contents
PC running slow?
It appears that some readers have encountered an error with Symantec Netbackup error code 23. There are a number of factors that can cause this issue. Let’s discuss some of them below. g.STATUS CODE: 23 A socket read error occurs when attempting to perform a user-guided backup or restore. Troubleshooting: This type of behavior can be considered if there is latency in your network connection between the client and the primary master server.
g.
Overview: Document
describes how to fix backups that fail with status 23 “Socket error with read error.” The backup may fail in state 23 if the client is unable to resolve the IP address of a specific Connectivity Media Server. A
Client protocol Files:
Examine the client type Bpcd protocol for details on hostname or address image resolution:
12: 44: 38,619 [4804.5184] <2> enable connection log: accept BPCD DE 10.1.2.3.47204 TO 10.1.2.37.13724
12: 44: 38,619 [4804.5184] <2> principal: bpcd setup_sockopts completed
12: 44: 43.134 [4804.5184] <8> Error bpcd peer_hostname: gethostbyaddr: The requested name will be valid, but the requested data type could not be found.
(0)
12: 44: 43.134 [4804.5184] <16> bpcd gethostbyaddr peer_hostname: error on King peer host, herrno = 0
12: 44: 43.134 [4804.5184] <16> principal: failed to get hostname of peer bpcd
Repair:
In the above case, the actual connection is established from the media server (IP = 10.1.2.3) to the client (IP = 10.1.2.37). The very first sign of a mailbox error is a line with the following personal message:
<8> bpcd peer_hostname: gethostbyaddr failed
This indicates that many clients will not be able to resolve the IP address of the media server in this case, 10.1.2.3. In this case, it is very likely that nslookup from 10.1.2.3 will fail due to the execution of ‘bpclntcmd -ip 10.1.2.3’
Start name resolution and check with ‘bpclntcmd -hn [hostname]’ to make sure the hostname is resolved correctly.
PC running slow?
ASR Pro is the ultimate solution for your PC repair needs! Not only does it swiftly and safely diagnose and repair various Windows issues, but it also increases system performance, optimizes memory, improves security and fine tunes your PC for maximum reliability. So why wait? Get started today!
Permission: Correct hostname resolution is disadvantageous neither in the DNS server nor in the corresponding host file record on the master server on the client.
The hosts files were found:
– in your feed % SystemRoot% system32 drivers etc directory (Windows)
– As part of / Etc directory (UNIX / Linux)
Dear good Samaritans!
I need help solving from time to time.The recurring dilemma of an assumed storage policy (with some storage profiles configured) that sometimes fails when using status code 23: Failed to read socket. I am using Netbackup 5.1 on Solaris Seven 64 bit. The configured master server and media server were still in the server box. I tried to find technical notes for you, but I never found out.
Based on the recommendation of the troubleshooter, this idea might be related to a malicious bptm binary, but I don’t think so because all backups that can be swapped from DSSU to FDSU (tape) n have no problem. I’m trying to directly check for Readline errors “get_num_avail_drives: was unsuccessful: socket read failed (23) and get_stunits: get_num_avail_drives successfully with stat 23” in some bpsched logs but not found.
08: 02: 17.324 [1287] <2>? : ————————————
08: 02: 17.325 [1287] <2>? : << CLIENT: kgsainss054 (root) BIRTH: 1269216098 PRIORITY: 0
08: 02: 17,328 [1287] <2>? : POLICY: Offsite_Weekly_Policy SCHEDULE: Weekly_Offisite_Schedule (0) PART 2 JOBID 353864 353864
08:02:17 grpid.328 [1287]? : <2> STUNITE: NO (Hideout) (kgsainss054)
08: 02: 17.329 [1287] <2>? : PID: 29796 STATUS: 23 TEST: 1 SPID: (REG)
08:02:17 29006.329 [1287] <2>? : ————————————
08: 02: 17.329 [1287] <2>? : Kgsainss054 left state at 23 (failed to read take)
08: 02: 17.355 [1287] <2>? : / Usr / openv / netbackup / bin / backup_exit_notify kgsainss054 Offsite_Weekly_Policy Weekly_Offisite_Schedule FULL 23 &
08:02:17 0. [1287] 931 <2> add_to_failure_history: successfully written to the error history file -> 22.03.10 08:02:17 kgsainss054 Offsite_Weekly_Policy Weekly_Offisite_Schedule 23. * NULL * 0 1269216137
08:02:17. [1287] 935 <2> set_job_details: Send jobData job id (353864)
08:02:17. [1287] 942 <2> send_structure_data: value of index field 9 m_nStatus <23>
08: 02: 17.943 [1287] <2> Index send_structure_data: 21 Value of the field m_nState <2>
08: 02: 17.943 [1287] <2> Index send_structure_data: 43 Field m_nRestartable Value <1>
08: 02: 17.946 <2> [1287] send_structure_data: m_nDataMovement value of index field 48 <0>
08: 02: 17.947 [1287] <2> send_structure_data: Index field 45 m_nFrozenImage <0>
08:02:17 Value. 948 [1287] <2> send_structure_data: Index 46 field m_szBackupID
08:02:17 Value 951 [1287] <2> set_job_details: JobRunData purchase Jobid (353864)
08: 02: 17.952 [1287] <2> send_structure_data: Index field 55 m_nSuspendable <0>
The value is 08:02:17. [1287] 954 <2> send_structure_data: index field 56 m_nResumable Value <0>
08: 02: 17.956 [1287] <2> set_job_details: Done
08: 02: 17.958 [1287] <2> job_end_try: Done
08: 02: 17.961 [1287] <16> log_in_errorDB: Save client kgsainss054 in addition to exit status 23 (failedread socket)
08: 02: 17.962 [1287] <2> Send set_job_details: Tfile jobid (353864)
08: 02: 17.963 [1287] <2> set_job_details: LOG 1269216137 16 bpsched 1287 The kgsainss054 client write completed with 23 reads (socket failure)
08: 02: 17.965 [1287] <2> set_job_details: Done
–
Best regards, CCWK Normal Kalvick 15 8 2004-05-05T07: 12: 00Z 2007-08-09T03: 35: 00Z 1 55 317 SSS 2 389 1 9.4402
[b] Sarawak Information Systems Sdn 3, bhd,
Horizontal lot 352, Lorong Rubber 12,
Jalan Gummi, 93400 Kuching,
Sarawak, Malaysia.
[/ B]
[b] Email: [i] calvincwk
Website: [i] [url = http: //www.sains.com.my/] www.sains.com.my [/ url] [/ i]
Telephone. : [i] 012 8830928
082 410522 dia. 227 [/ i]
Fax: [i] 082 236971 [/ i] [/ b]
Improve the speed of your computer today by downloading this software - it will fix your PC problems.
La Mejor Forma De Resolver El Estilo De Error 23 De Symantec Netbackup
Il Modo Migliore Per Risolvere Il Valore Di Errore Di Symantec Netbackup 23
Лучший способ определить код ошибки Symantec Netbackup 23
Le Principal Moyen De Résoudre La Procédure D’erreur Symantec Netbackup 23
Der Einfache Weg Zur Behebung Von Symantec Netbackup-Fehlerprogrammierung 23
Det Bästa Sättet Att Lösa Symantec Netbackup Felkod 23
A Maneira Ideal De Resolver A Senha 23 De Erro Do Symantec Netbackup
Najlepszy Sposób Radzenia Sobie Z Kodem Błędu Symantec Netbackup 23
De Beste Manier Om Symantec Netbackup-foutcode 23 Op Te Lossen
Symantec Netbackup 오류 코드 23을 처리하는 가장 좋은 방법
