Forum Discussion

soeheinhtut's avatar
soeheinhtut
Level 4
6 years ago

Info bpbkar32(pid=6172) done. status: 52: timed out waiting for media manager to mount volume

Please help to check below failed job and how can i resolved and prevent in future?

==========================================================================================

12/21/2019 2:41:33 AM - Info nbjm(pid=4068) starting backup job (jobid=23613) for client abcoai-bkup01p, policy DATA-ACC-lto-17, schedule Full
12/21/2019 2:41:33 AM - Info nbjm(pid=4068) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=23613, request id:{771DE47C-20ED-4A45-BC58-C194575575CD})
12/21/2019 2:41:33 AM - requesting resource abcoai-LTO-OA
12/21/2019 2:41:33 AM - requesting resource abcoai-bkmg01p.NBU_CLIENT.MAXJOBS.abcoai-bkup01p
12/21/2019 2:41:33 AM - requesting resource abcoai-bkmg01p.NBU_POLICY.MAXJOBS.DATA-ACC-lto-17
12/21/2019 2:41:33 AM - granted resource abcoai-bkmg01p.NBU_CLIENT.MAXJOBS.abcoai-bkup01p
12/21/2019 2:41:33 AM - granted resource abcoai-bkmg01p.NBU_POLICY.MAXJOBS.DATA-ACC-lto-17
12/21/2019 2:41:33 AM - granted resource CBMA17
12/21/2019 2:41:33 AM - granted resource HP.ULTRIUM6-SCSI.001
12/21/2019 2:41:33 AM - granted resource abcoai-LTO-OA
12/21/2019 2:41:33 AM - estimated 0 Kbytes needed
12/21/2019 2:41:33 AM - Info nbjm(pid=4068) started backup (backupid=abcoai-bkup01p_1576872693) job for client abcoai-bkup01p, policy DATA-ACC-lto-17, schedule Full on storage unit abcoai-LTO-OA
12/21/2019 2:41:46 AM - started process bpbrm (7888)
12/21/2019 2:42:04 AM - Info bpbrm(pid=7888) abcoai-bkup01p is the host to backup data from
12/21/2019 2:42:09 AM - Info bpbrm(pid=7888) reading file list for client
12/21/2019 2:42:09 AM - connecting
12/21/2019 2:42:23 AM - Info bpbrm(pid=7888) starting bpbkar32 on client
12/21/2019 2:42:23 AM - Info bpbkar32(pid=6172) Backup started
12/21/2019 2:42:23 AM - Info bpbkar32(pid=6172) change time comparison:<disabled>
12/21/2019 2:42:23 AM - Info bpbkar32(pid=6172) archive bit processing:<enabled>
12/21/2019 2:42:23 AM - connected; connect time: 0:00:14
12/21/2019 2:42:23 AM - Info bptm(pid=7720) start
12/21/2019 2:42:45 AM - Info bptm(pid=7720) using 65536 data buffer size
12/21/2019 2:42:45 AM - Info bptm(pid=7720) setting receive network buffer to 263168 bytes
12/21/2019 2:42:45 AM - Info bptm(pid=7720) using 30 data buffers
12/21/2019 2:42:59 AM - Info bptm(pid=7720) start backup
12/21/2019 2:42:59 AM - Info bptm(pid=7720) Waiting for mount of media id CBMA17 (copy 1) on server abcoai-bkup01p.
12/21/2019 2:42:59 AM - mounting CBMA17
12/21/2019 2:44:14 AM - Info bptm(pid=7720) media id CBMA17 mounted on drive index 1, drivepath {4,0,0,0}, drivename HP.ULTRIUM6-SCSI.001, copy 1
12/21/2019 2:44:19 AM - mounted; mount time: 0:01:20
12/21/2019 2:44:23 AM - positioning CBMA17 to file 1
12/21/2019 2:47:12 AM - positioned CBMA17; position time: 0:02:49
12/21/2019 2:47:12 AM - begin writing
12/21/2019 2:52:28 AM - Info bpbkar32(pid=6172) done. status: 52: timed out waiting for media manager to mount volume
12/21/2019 2:52:28 AM - end writing; write time: 0:05:16
timed out waiting for media manager to mount volume(52)

7.6
windows server 2012

31 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    I believe this is another type of timeout, not a media mount timeout.
    We see that the media was mounted, positioned and even 'begin writing'. The tape was waiting for data to arrive from the client.

    Please tell us what all the timeout values are on master, media server, client.
    It looks like a timeout value of 5 minutes (300) kicked in and incorrectly reported the error as media mount timeout.

    To troubleshoot, you need the following logs:
    On media server: bptm and bpbrm
    On the client: bpbkar

    These log folders do not exist by default, they need to be created.
    I suggest that you increase logging level to 3 on media server and client.

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        I see network errors in bptm log - so, status 52 is incorrect error message. 

        It seems that it should have been Client Read timeout, but because all timeouts are the same, this old NBU version reported on the wrong timeout. 

        We really need the client bpbkar log as well to see generation of datastream and what was sent to media server, plus higher level bpbrm and bptm logs - this will show us every time data buffer and metadata is received from the client.

        Please increase media mount timeout to something like 15 minutes, and Client read timeout to 10 minutes (600).
        Increase logging level to 3 for media server and client. 

        Please try to upload logs as .txt files, as this makes it easier to open files online.