Forum Discussion

LucSkywalker195's avatar
12 years ago
Solved

BMRERR errors

I have a Linux VM that I have to backup within the VM and I'm trying to collect BMR data for it. Any help you can give me I really appreciate. Thanks eveyone!

OS: Linux 2.6.18-348.6.1.el5 #1 SMP Fri Apr 26 09:21:26 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux

Client version: NetBackup-RedHat2.6.18 7.5

PID job details:

7/16/2013 3:41:53 PM - begin Stream Discovery, BMR Save

7/16/2013 3:41:55 PM - started process bpbrm (6765)

7/16/2013 3:41:58 PM - collecting BMR information

7/16/2013 3:41:58 PM - connecting

7/16/2013 3:41:58 PM - connected; connect time: 00:00:00

7/16/2013 3:41:58 PM - transferring BMR information to the master server

7/16/2013 3:41:58 PM - connecting

7/16/2013 3:41:58 PM - connected; connect time: 00:00:00

7/16/2013 3:42:02 PM - Error bpbrm(pid=6765) BMRERR: Received BMR error: Failed to import Config file. (1)

7/16/2013 3:42:02 PM - Error bpbrm(pid=6765) BMRERR: Received BMR error: Failed sending the discovery. (1)

7/16/2013 3:42:02 PM - Error bpbrm(pid=6765) BMRERR: Received BMR error: BMR information discovery failed. (1)

7/16/2013 3:42:02 PM - Info bmrsavecfg(pid=0) done. status: 1: the requested operation was partially successful

7/16/2013 3:42:02 PM - end writing Status 1

 

vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6

bmrsavecfg -infoonly

vxlogview -p 51216 -i 121 -d all -t 00:10:00

07/19/2013 10:45:02.832 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [fileAttribsCommon.cpp:IsFileReadableCommon()] Could not do stat on file /usr/openv/netbackup/baremetal/client/data/ClientCustomFiles

07/19/2013 10:45:04.564 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24023 exited with non-zero status=1

07/19/2013 10:45:04.564 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.332 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24075 exited with non-zero status=1 07/19/2013 10:45:05.332 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.341 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24076 exited with non-zero status=1

07/19/2013 10:45:05.341 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.790 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24131 exited with non-zero status=1

07/19/2013 10:45:05.790 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.794 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24132 exited with non-zero status=1

07/19/2013 10:45:05.794 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.799 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24133 exited with non-zero status=1

07/19/2013 10:45:05.799 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.804 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24134 exited with non-zero status=1

07/19/2013 10:45:05.804 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.809 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24135 exited with non-zero status=1

07/19/2013 10:45:05.809 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.814 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [bmrSystemCommon.cpp:BmrSystemCommon()] Child process pid=24136 exited with non-zero status=1

07/19/2013 10:45:05.814 [Diagnostic] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 2 V-128-128 [CSaveCfgFile.cpp:execute()] Failed to configure VxVM.

07/19/2013 10:45:05.814 [Debug] NB 51216 bmrcommon 128 PID:23317 TID:1 File ID:121 [No context] 1 [fileAttribsCommon.cpp:IsFileExecutableCommon()] Could not do stat on file /opt/VRTSvcs/bin/hares

  • Answer is from Scott Austin at Symantec. Hopefully they'll find a way to address this in version 7.6!

    The client is using /dev/vda for it's disk or virtual disk alpha. BMR does not support the use of virtual disk objects. We need XEN to use /dev/sda for BMR to work as intended.

    Issue

    Backups fail for BMR RedHat client due to a failure with the importing of the client collected information (bundle.dat).

    Error

    Job Details:

    2/15/2013 15:31:20 - Error bpbrm (pid=4791) BMRERR: Received BMR error: Failed to import Config file. (1)

    2/15/2013 15:31:20 - Error bpbrm (pid=4791) BMRERR: Received BMR error: Failed sending the discovery. (1)

    2/15/2013 15:31:21 - Error bpbrm (pid=4791) BMRERR: Received BMR error: BMR information discovery failed. (1)

    bmrd (OID 119) log:

    2/15/2013 15:31:05.446 [stringManipulation.cpp:GetFieldFromLine()] Exiting, line=275 field=/dev/vda: rc=0

    2/15/2013 15:31:05.524 [ParseFdisk.cpp:ParseFdisk()] Unable to find the disk object for disk /dev/vda

    2/15/2013 15:31:05.524 [ParseFdisk.cpp:ParseFdisk()] Exiting, line=201

    2/15/2013 15:31:05.524 V-128-22 [ParseClientInformation.cpp:ParseClientInformation()] Parser returned with non-zero return code = 1, OutputType = FDISK_NUM

    2/15/2013 15:31:05.555 [ParseClientInformation.cpp:ParseClientInformation()] Critical function failed. OutputType = FDISK_NUM.

    2/15/2013 15:31:05.555 [ParseClientInformation.cpp:ParseClientInformation()] Exiting in ../ParseClientInformation.cpp at 695.

    2/15/2013 15:31:05.555 V-128-18 [ImportCfg.cpp:ImportConfig()] unable to parse client information

    Environment

    NetBackup BMR 7.5.X Master

    NetBackup BMR 7.5.x RedHat client

    Cause

    The behavior listed up top is caused by the device paths (/dev/vda) configured on the RedHat client being backed up to collect BMR information. NetBackup BMR is not able to handle this devcie path, resulting in failure.

    TECH203050

    Again with the log file We where able to find out exactly why this was failing. It's not that we do not support the use of XEN it's the way it's emulating hardware is the issue.

17 Replies