Forum Discussion

LEE6's avatar
LEE6
Level 3
6 years ago

socket read failed: errno = 62 - Timer expired

I have encounter backup issue, below is the error

08/27/2019 12:40:18 - Info bptm (pid=71011) start backup
08/27/2019 12:40:19 - Info bptm (pid=71011) backup child process is pid 71012
08/27/2019 12:41:31 - Info bpbkar (pid=5644) will attempt to use change journal data for <N:\>
08/27/2019 12:44:12 - Info bpbkar (pid=5644) not using change journal data for <N:\>: no previous track log
08/27/2019 13:41:18 - Info bptm (pid=71011) waited for full buffer 21451 times, delayed 215032 times
08/27/2019 13:41:34 - Info bptm (pid=71011) EXITING with status 0 <----------
08/27/2019 13:41:35 - Info BKM001 (pid=71011) StorageServer=PureDisk:BKM001; Report=PDDO Stats for (BKM001): scanned: 26818556 KB, CR sent: 18348440 KB, CR sent over FC: 0 KB, dedup: 31.6%, cache disabled
08/27/2019 13:45:39 - end writing; write time: 1:06:17
08/27/2019 13:46:35 - Error bpbrm (pid=71006) socket read failed: errno = 62 - Timer expired
08/27/2019 13:46:35 - Error bpbrm (pid=71006) could not send server status message
08/27/2019 13:46:36 - Info bpbkar (pid=5644) done. status: 13: file read failed
08/27/2019 13:46:38 - Info bpbrm (pid=103343) Starting delete snapshot processing
08/27/2019 13:46:39 - Info bpfis (pid=5060) Backup started
08/27/2019 13:46:39 - Warning bpbrm (pid=103343) from client AADDCC.LOCAL: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.AADDCC.LOCAL_1566880752.1.0
08/27/2019 13:46:39 - Info bpfis (pid=5060) done. status: 4207
08/27/2019 13:46:39 - Info bpfis (pid=5060) done. status: 4207: Could not fetch snapshot metadata or state files
file read failed (13)

7.7
windows server 2012
  • sdo's avatar
    sdo
    Moderator
    6 years ago

    There can be many reasons why an error 62 and status 13 and status 4207 might be generated.  No-one here will have an immediate answer for you.

    Have you searched and researched and tried anything at all yourself yet ?

    I googled, and found this :

    https://www.veritas.com/support/en_US/article.100043604

    • LEE6's avatar
      LEE6
      Level 3
      6 years ago

      Have tried the suggested article solution, to adjust the CLIENT_READ_TIMEOUT but it does not resolved the issue

  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    I think this is the real error:

    Info bpfis (pid=5060) done. status: 4207: Could not fetch snapshot metadata or state files 
    file read failed (13)

    Have you checked bpfis log on the client?

    I have experienced this issue when the client could not connect to the master server at the end of the backup to update snapshot info.
    Windows client needs connectivity to the Master server when WOFB (snapshot backup) is needed.
    If connectivity is not possible, then WOFB in Master Server's Client Attributes for this client name must be disabled. 

    • LEE6's avatar
      LEE6
      Level 3
      6 years ago

      Hi Marianne

      I have look through the bpfis logs as attached. Still unable to identify what is the issue with the snapshot

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        LEE6 

        I was hoping to see more in bpfis log.
        There is no more than what we see in Job Details:
        bpfis: INF - EXIT STATUS 4207: Could not fetch snapshot metadata or state files

        Connection to the master server seems to be fine:
        11:35:10.939 [4368.3468] <2> vnet_pbxConnect: pbxConnectEx Succeeded
        11:35:10.939 [4368.3468] <2> logconnections: BPRD CONNECT FROM 192.168.10.140.50216 TO 192.168.10.8.1556 fd = 764

        I guess logging level is at the default of 0?
        Can you you try to increase it to 3?

        Please also check the client for VSS errors.