β01-12-2012 12:31 AM
please anyone tell me solution of Netbackup Problem.
My question is : Why did BMR fail?
Environment
Server : windows storage server 2008
server software version : Netbackup 7.1
clietnt : Redhat Enterprise Linux 5.2 i686
Clietnt software version : Netbackup 6.5
follow is server report.
Info 5 Backup started backup job for client xxx, policy LinuxMBR, schedule full on storage unit NBUstorage
Error 5 Backup BMRERR: Received BMR error: Failed to discover System. (1)
Error 5 Backup BMRERR: Received BMR error: BMR information discovery failed. (1)
Error 5 Backup BMRERR: Did not receive bmr client request from xxx, status = 0
Info 6 Backup started backup job for client xxx, policy LinuxBMR, schedule full on storage unit NBUstorage
Info 6 Backup client xxx handling path ALL_LOCAL_DRIVES
Info 6 Media Device begin writing backup id xxx_1326344978, copy 1, fragment 1, destination path C:\NBU_storage
Info 6 Backup from client xxx: TRV - /var/lib/nfs/rpc_pipefs is in a different file system from /var. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/acpid.socket is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/audispd_events is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/pcscd.comm is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/sdp is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/avahi-daemon/socket is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/cups/cups.sock is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var/run/dbus/system_bus_socket is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /boot is in a different file system from /. Skipping.
Info 6 Backup from client xxx: TRV - /dev is in a different file system from /. Skipping.
Info 6 Backup from client xxx: TRV - /misc is in a different file system from /. Skipping.
Info 6 Backup from client xxx: TRV - /net is in a different file system from /. Skipping.
Info 6 Backup from client xxx: TRV - /proc is on file system type PROC. Skipping.
Info 6 Backup from client xxx: TRV - /sys is in a different file system from /. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/mapping-root is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/.ICE-unix/6279 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/.font-unix/fs7100 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-1887-0-5e36e0d44d254 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18d2-0-5963f498b9e9e is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18e7-0-4cce4014220dd is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18e9-0-4cce40142a40f is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18eb-0-16ac945839996 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18ee-0-71174e9224cf6 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18f7-0-4cce4014abd85 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-18fd-0-7e445a0faf3a1 is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-1903-0-728bcf9d37abf is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /tmp/orbit-root/linc-1917-0-4cce40151199f is a socket special file. Skipping.
Info 6 Backup from client xxx: TRV - /var is in a different file system from /. Skipping.
Info 6 Backup successfully wrote backup id xxx_1326344978, copy 1, fragment 1, 5688576 Kbytes at 7009.010 Kbytes/sec
Info 6 Backup Status the requested operation was successfully completed
Info 5 Backup Status the requested operation was partially successful
Error 5 Backup backup of client xxx exited with status 1 (the requested operation was partially successful)
please some one help...
Solved! Go to Solution.
β01-12-2012 10:20 PM
01/13/2012 23:21:40.360 [Diagnostic] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 V-128-312 [bmrSystem.cpp:SetOsInfo()] Unsupported Linux release: Red Hat Enterprise Linux Server release 5.2 (Tikanga)
01/13/2012 23:21:40.372 [Debug] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 [CSystemAgent.cpp:discover()] Failed verifying OS support for .
Your NB client (6.5) does not support BMR for RHEL 5. You need to upgrade client to 6.5.4 level where BMR support for 5.x RHEL started.
Thanks.
-Mandar
β01-12-2012 01:06 AM
>> Error 5 Backup BMRERR: Received BMR error: BMR information discovery failed. (1)
>> Error 5 Backup BMRERR: Did not receive bmr client request from xxx, status = 0
This indicates that the client setup probably is not supported by BMR or that particular BMR client version.
To know exact failure, please check bmrsavecfg log generated on your client machine being backed up. You may need to enable debug log with level 6 on client and re-run backup in case the root cause log message is not clear.
Thanks.
Mandar
β01-12-2012 05:43 AM
This technote explains how to set up the logs.
http://www.symantec.com/docs/TECH75805
On the client, run
vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6
β01-12-2012 06:00 AM
Please upgrade your client netbackup version and see....
β01-12-2012 10:01 PM
Thank you for your kind reply.
I did as you said.
#vxlogcfg -a -p 51216 -o 111 -s DebugLevel=6 -s DiagnosticLevel=6
#bmrsavecfg -infoonly
follow is bmrsavecfg.txt
01/13/2012 23:21:40.322 [Debug] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 [fileAttribsCommon.cpp:FileExistsCommon()] Could not do stat on file /usr/openv/netbackup/baremetal/client/data/bundle.dat
01/13/2012 23:21:40.323 [Debug] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 [fileAttribsCommon.cpp:FileExistsCommon()] Could not do stat on file /usr/openv/netbackup/baremetal/client/data/bmrcli.xml
01/13/2012 23:21:40.360 [Diagnostic] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 V-128-312 [bmrSystem.cpp:SetOsInfo()] Unsupported Linux release: Red Hat Enterprise Linux Server release 5.2 (Tikanga)
01/13/2012 23:21:40.372 [Debug] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 [CSystemAgent.cpp:discover()] Failed verifying OS support for .
01/13/2012 23:21:40.373 [Debug] NB 51216 bmrsavecfg 121 PID:7892 TID:1 File ID:121 [No context] 1 [CBmrSaveCfg::discover()] sysAgent->discover failed, rc=4
01/13/2012 23:21:40.373 [Application] NB 51216 bmrsavecfg 121 PID:7892 TID:1 File ID:121 [No context] [Error] V-121-12 Failed to discover System.
01/13/2012 23:21:40.376 [Application] NB 51216 bmrsavecfg 121 PID:7892 TID:1 File ID:121 [No context] [Error] V-121-35 BMR information discovery failed.
I dont know exactly. But, according to this log,
Clients Pc is not supported for BMR??
I tried to install Netbackup 7.1 to Client PC, but 7.1 seems not to support Unix 32bit OS,
so, I got Netbackup 6.5 and install to this Client.
I wanna do BMR for this Clietnt.
Is there way to do BMR for this Client? or no way?
β01-12-2012 10:20 PM
01/13/2012 23:21:40.360 [Diagnostic] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 V-128-312 [bmrSystem.cpp:SetOsInfo()] Unsupported Linux release: Red Hat Enterprise Linux Server release 5.2 (Tikanga)
01/13/2012 23:21:40.372 [Debug] NB 51216 bmrcommon 128 PID:7892 TID:1 File ID:121 [No context] 1 [CSystemAgent.cpp:discover()] Failed verifying OS support for .
Your NB client (6.5) does not support BMR for RHEL 5. You need to upgrade client to 6.5.4 level where BMR support for 5.x RHEL started.
Thanks.
-Mandar