Forum Discussion

Kaio_Tonheiro's avatar
Kaio_Tonheiro
Level 4
9 years ago

CODE ERROR 13

Hello for everyone,  

       I need your help with nbu 7.6.1, code error 13.

       System of master: Windows 2008 r2 standard

       System do média server: Windows 2008 r2 Enterprise

       Version NBU: 7.6.1

 

Error LOG:.

2/2/2016 6:36:04 PM - Info nbjm(pid=5828) starting backup job (jobid=172966) for client CD170-TS, policy CDGRU_CD170-TS_DB_RFENCABIDADO_SQL_LOG, schedule Default-Application-Backup  
2/2/2016 6:36:04 PM - Info nbjm(pid=5828) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=172966, request id:{DAADCE33-368D-4E10-98E1-23D00E51A615})  
2/2/2016 6:36:04 PM - requesting resource R-CDGNETBKPPRD1-STU-DISK-DEDUP
2/2/2016 6:36:04 PM - requesting resource r-cdgnetbkpprd1.NBU_CLIENT.MAXJOBS.CD170-TS
2/2/2016 6:36:04 PM - requesting resource r-cdgnetbkpprd1.NBU_POLICY.MAXJOBS.CDGRU_CD170-TS_DB_RFENCABIDADO_SQL_LOG
2/2/2016 6:36:04 PM - granted resource r-cdgnetbkpprd1.NBU_CLIENT.MAXJOBS.CD170-TS
2/2/2016 6:36:04 PM - granted resource r-cdgnetbkpprd1.NBU_POLICY.MAXJOBS.CDGRU_CD170-TS_DB_RFENCABIDADO_SQL_LOG
2/2/2016 6:36:04 PM - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=R-CDGNETBKPPRD1-MSDP;Path=PureDiskVolume;StorageServer=r-cdgnetbkpprd1;MediaServer=r-cdgnetbkpprd1
2/2/2016 6:36:04 PM - granted resource R-CDGNETBKPPRD1-STU-DISK-DEDUP
2/2/2016 6:36:05 PM - estimated 0 Kbytes needed
2/2/2016 6:36:05 PM - Info nbjm(pid=5828) started backup (backupid=CD170-TS_1454445364) job for client CD170-TS, policy CDGRU_CD170-TS_DB_RFENCABIDADO_SQL_LOG, schedule Default-Application-Backup on storage unit R-CDGNETBKPPRD1-STU-DISK-DEDUP
2/2/2016 6:36:06 PM - started process bpbrm (10296)
2/2/2016 6:36:08 PM - Info bpbrm(pid=10296) CD170-TS is the host to backup data from     
2/2/2016 6:36:08 PM - Info bpbrm(pid=10296) reading file list for client        
2/2/2016 6:36:08 PM - connecting
2/2/2016 6:36:11 PM - Info bpbrm(pid=10296) listening for client connection         
2/2/2016 6:36:19 PM - Info bpbrm(pid=10296) INF - Client read timeout = 2100000      
2/2/2016 6:36:19 PM - Info bpbrm(pid=10296) accepted connection from client         
2/2/2016 6:36:19 PM - Info dbclient(pid=22020) Backup started           
2/2/2016 6:36:19 PM - connected; connect time: 0:00:11
2/2/2016 6:36:20 PM - Info bptm(pid=10388) start            
2/2/2016 6:36:21 PM - Info bptm(pid=10388) using 262144 data buffer size        
2/2/2016 6:36:23 PM - Info bptm(pid=10388) setting receive network buffer to 1049600 bytes      
2/2/2016 6:36:23 PM - Info bptm(pid=10388) using 32 data buffers         
2/2/2016 6:36:27 PM - Info bptm(pid=10388) start backup           
2/2/2016 6:36:38 PM - Info bptm(pid=10388) backup child process is pid 15096.6688       
2/2/2016 6:36:38 PM - begin writing
2/2/2016 6:36:39 PM - Info bptm(pid=15096) start            
2/2/2016 6:36:40 PM - Info dbclient(pid=22020) dbclient(pid=22020) wrote first buffer(size=65536)         
2/2/2016 6:39:47 PM - Error bpbrm(pid=10296) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
2/2/2016 6:40:05 PM - Info r-cdgnetbkpprd1(pid=10388) StorageServer=PureDisk:r-cdgnetbkpprd1; Report=PDDO Stats (multi-threaded stream used) for (r-cdgnetbkpprd1): scanned: 2891779 KB, CR sent: 1430 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache hits: 0 (0.0%)
2/2/2016 6:40:06 PM - Info dbclient(pid=22020) done. status: 13: file read failed       
2/2/2016 6:40:06 PM - end writing; write time: 0:03:28
file read failed (13)

 

 

My greetings for all.

7.6
Backing Up
Backup and Recovery
Configuring
Error messages
NetBackup
Windows Server (2003-2008)
  • Kaio_Tonheiro's avatar
    Kaio_Tonheiro
    9 years ago


    Find that my dns server was in error and my network was flashing , I put the server in question within the resiliency and up to date showed no more mistakes.

     

     

    thank you all for the help

     

     

    Kaio Tonheiro (Linkedin and Facebook).

     

21 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    9 years ago
    Tell us about client CD170-TS. OS? NBU version? Database type and version? Has this backup worked fine before? Do you have dbclient log on the client? And tell us about the reason for the very high Client Read timeout on the media server - 2100000 = 583.3 hours = 24 days?
  • sdo's avatar
    sdo
    Moderator
    9 years ago

    If you answer Mariiane's questions, we might be able to help you a bit more.

  • Kaio_Tonheiro's avatar
    Kaio_Tonheiro
    Level 4
    9 years ago

    The error is "socket read failed, An existing connection was forcibly closed by the remote host.  (10054)"

    Yes, this backup worked before.

    The client in 2100000 is was a test because error 13 charges latency or timeout in my network.

    I realized troubleshooting and found that the error was "socket read failed, An existing connection was forcibly closed by the remote host.  (10054)", but I do not know how to solve

     

    >>>>

    OS ?

    > 2008 R2 Enterprise
    NBU version?
    > 7.6.1
    Database type and version?
    > SQL, need to check the version with DBA's
    Has this backup worked fine before?
    > Yes
    Do you have dbclient log on the client?
    > How do I check, I believe that is

    tks a lot 

    Kaio Tonheiro

     

     

  • Marianne's avatar
    Marianne
    Level 6
    9 years ago

    dbclient log folder does not exist by default on the client.
    Create the folder under Netbackup\logs on the client.

    The backup fails within 3 minutes - increasing timeout to a very high value is not going to fix anything.
    It is hardly ever necessary to increase client connect and read timeout to more than 1800 (30 minutes ).

    In addition to checking NBU logs on the clients, it may be a good idea to logon to the client when the backup is started and see what else is running on the client during that time.

  • sdo's avatar
    sdo
    Moderator
    9 years ago

    The answers to the questions was not already above - you went back and added them afterwards.  But thank you anyway for doing so.

  • revarooo's avatar
    revarooo
    Level 6
    9 years ago

    Just a note: Don't ever change the client connect timeout, if a media server cannot connect to a client within the default 5 minutes you need to look at why that is - it's not a NetBackup problem,

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    9 years ago

    Have the opposite experience especially with database backups.

    Have "cured" multiple status 13/54/636 on Oracle & SQL backups by increasing the CLIENT_CONNECT_TIMEOUT and CLIENT_READ_TIMEOUT in busy environments.

    Actually I think that the Oracle guide suggest to reaise the CLIENT_TIME_OUT to 900 (15 minutes)

     

  • revarooo's avatar
    revarooo
    Level 6
    9 years ago

    Interesting you say that, our engineering team sent out communication a while ago saying not to change it.

    If a client cannot respond to a simple communication request within 5 minutes, there is something wrong with the system.

    Kicking the ball down the street further doesn't help matters in the long run, but I guess getting a backup is a priority. However multiple clients with the same issue will drag the backup window and potentially cause "good working clients" to fail due to resources held up etc

     

    Just passing on what we were told.

     

  • Marianne's avatar
    Marianne
    Level 6
    9 years ago

    Let us all agree that it is not NBU timeouts killing the backup.

    The backup fails 3 minutes after 1st buffer is sent by the client:

    2/2/2016 6:36:40 PM - Info dbclient(pid=22020) dbclient(pid=22020) wrote first buffer(size=65536)         
    2/2/2016 6:39:47 PM - Error bpbrm(pid=10296) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)

    It seems that something outside of NBU is killing the network connection.