BMRERR errors

[LucSkywalker195]

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

[mandar_khanolka]

DO you have VxVM, VxFS configured on your NB client?

What is NB client version? What is RHEL version?

Thanks.

Mandar

[thesanman]

I have a similar issue at the moment.  v7.5.0.5 Master, Media and Client on RHEL v6.3.  3 servers build from same OS "build image", 2 work fine (bmr save config) but the 3rd fails.  I has much larger disk volumes (2.4TB) and is running Oracle but that's about it.  I have even moved to the v7.5.0.6 client with no luck.

I do not appear to have VxVM or VxFS installed or configured.

I have a case open with Symantec about it.

[mandar_khanolka]

Thanks for contacting symantec support for your issue. Hopefully the issue will be trivial to solve.

Thanks.

Mandar

[LucSkywalker195]

This is running: 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 Netbackup Client version: 7.5.0 Veritas file system is not installed or configured.

[LucSkywalker195]

I think this has to do with Red Hat virtualization technology. Their Netbackup 7.5 guide carefully states how to backup a VM client and restore it and they explcitly left out BMR as an option. It is possible on the virtualization server, but not the clients. I'll update with any more information I can find. Interesting stuff.

[mandar_khanolka]

Are you using Linux KVM based guest VM and trying to protect it using BMR enabled policy?

Thanks.

Mandar

[thesanman]

In my case I suspect not; it's been escalated to backline where they have found a disk info command is not being run or failing.  I am awaiting an update.

[LucSkywalker195]

Yes

[LucSkywalker195]

I think this article might be related to my problem which might have a fix for it in 7.5.0.5.

I'm currently at 7.5.0.3 on my master and media servers.

http://www.symantec.com/business/support/index?page=content&id=TECH199940&actp=search&viewlocale=en_...

I've opened a support case with Red Hat also to see if they are aware of it also.

Please share your opinions. Thanks!

[mandar_khanolka]

Yet BMR does not support RHEL protection running on KVM based guest VM.

To know more on BMR virtualization support, please refer below link containing the SCL PDF document:

http://www.symantec.com/business/support/index?page=content&id=TECH127089

Thanks.

Mandar

[thesanman]

Not as simple as it seemed.  Seems like my RHEL OS build was built using GUID Partition Table (GPT) due to the server having disk volumes on it > 2TB.  Thus the output from fdisk is incorrect and bmrsaveconfig is failing.

It seems like BMR doesn't support GPT as yet.  Just waiting to here when.

[rishi_raj_gupta]

Yes. BMR currently doesn't support GPT on Linux.

BMR support for GPT on Linux is being considered, but the release vehicle is not yet planned and it would be post 7.6 release.

Thanks,

Rishi Raj

[dracula_lucas]

Hi, Mandar_khanolkar,

"Yet BMR does not support RHEL protection running on KVM based guest VM.".  I didn't find related declaration in the link "http://www.symantec.com/business/support/index?pag..." you provided. There are several VM types mentioned in this document but KVM excluded. 

Does it only mean Netbackup7.5 BMR does not support KVM based guest VM officially? While we can still try BMR on KVM based guest VM, right?

Or it is not feasible to apply BMR function on KVM based guest VM.

Thanks,

Lucas

[Jaime_Vazquez]

The article noted above reports those virtual environments that are offiially supported.  If the environment in question is not on the list, it is not officially supported. Simple as that.  Whether or not the BMR function works is a totally different story.  You might get lucky, you migh not.  The fact that you get it to work will not make it supported.

A BMR enabled backup job will cause a RC=1 error for the backup job itself for one of two major operations; the 'bmrsavecfg' process failed on the client or the configuration import failed on the Master Server. This article helps diagnose this:

BMR enabled backup jobs fail with status code 1
http://www.symantec.com/docs/TECH207639
 

Disregard the error messages "Failed to configure VxVM" as they are for the most part just a red herring. If the "bmrsavecfg -infoonly" completed with RC=0 and no error messages displayed, the issue will be on the Master Server (bmrd) for the import into the BMRDB.

You can view the return code of the 'bmrsavecfg' command (actually, any command) by running, as the next command:

echo %ERRORLEVEL% (Windows)

echo $?   (Unix/Linux)

The function of the above command invocation is to display the status return code of whatever command was immediately previously executed.

[dracula_lucas]

Jaime,

Thanks for your information.

I tried 2 KVM based VM client for BMR. One succeeded, anther one failed with same error with LucSkywalker1957's

Netbackup Version: 7.5.0.5

Client1:

Host:Redhat 6.3, 2.6.32-279.19.1.el6.x86_64

VM:2.6.18-348.1.1.el5

Client2:

Host: redhat 5.8 2.6.18-300.el5

VM:2.6.18-348.1.1.el5

I also followed the procedure in http://www.symantec.com/docs/TECH207639

[root@pcm-g8-rms-ext ~]# /usr/openv/netbackup/bin/bmrs -o import -res config -path /tmp/bundle120.dat

[Error] V-123-49 Operation failed.

I googled V-123-49 with no luck. I suspect it is caused by the Redhat6.3.

thanks,

Lucas

Thanks,

Lucas

[Jaime_Vazquez]

Lucas:

The error code V-123-49 is a generic "I failed" code. The Technical article (which I wrote) was specific on how to see the cause of the import error by displaying the debug log for the ORGID 119 (bmrd) which is resposible for the actual import activity.

vxlogview -i 119 

In the NetBackup OS Compatibility List document (http://www.symantec.com/docs/TECH76648) it reads for RHEL 6.3 (page 41):

Red Hat Enterprise Linux 6 Update 3 requires NetBackup 7.5.0.5 or later.

If your client truly is RHEL 6.3 and this is a NBU 7.5.0.5 environment, then that alone will not cause the import failure. If this is because of the partitioning table (GPT disk), these commands should show it:

parted --script $disk_path  --script    (specify individual disk paths for each invocation)

fdisk -lu

Try this and see what your results are.

[LucSkywalker195 · Accepted solution]

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.