BMR backup is partially successful without any errors, no errors/warnings found

[tyadagiri]

Please look at the log and could not see any errors/warnings so not sure where the backup shows as partially successful:

Here is the Child job log:

03/02/2015 20:45:59 - Info bpbrm (pid=28033) starting bptm
03/02/2015 20:45:59 - Info bpbrm (pid=28033) Started media manager using bpcd successfully
03/02/2015 20:45:59 - Info nbjm (pid=2702) starting backup job (jobid=1016732) for client ausu596a, policy u_os_bmr_np, schedule Full
03/02/2015 20:45:59 - estimated 0 kbytes needed
03/02/2015 20:45:59 - Info nbjm (pid=2702) started backup (backupid=ausu596a_1425350759) job for client ausu596a, policy u_os_bmr_np, schedule Full on storage unit ausu130a-hcart3-robot-tld-0
03/02/2015 20:45:59 - started process bpbrm (pid=28033)
03/02/2015 20:46:00 - Info bpbrm (pid=28033) ausu596a is the host to backup data from
03/02/2015 20:46:00 - Info bpbrm (pid=28033) telling media manager to start backup on client
03/02/2015 20:46:00 - Info bptm (pid=28036) using 262144 data buffer size
03/02/2015 20:46:00 - Info bptm (pid=28036) using 32 data buffers
03/02/2015 20:46:00 - Info bptm (pid=28036) start backup
03/02/2015 20:46:00 - Info bptm (pid=28036) Waiting for mount of media id B08903 (copy 1) on server ausu130a.
03/02/2015 20:46:00 - Info bpbrm (pid=28033) spawning a brm child process
03/02/2015 20:46:00 - Info bpbrm (pid=28033) child pid: 28051
03/02/2015 20:46:00 - Info bpbrm (pid=28033) sending bpsched msg: CONNECTING TO CLIENT FOR ausu596a_1425350759
03/02/2015 20:46:00 - mounting B08903
03/02/2015 20:46:00 - connecting
03/02/2015 20:46:00 - Info bpbrm (pid=28033) start bpbkar on client
03/02/2015 20:46:00 - Info bpbkar (pid=11345) Backup started
03/02/2015 20:46:00 - Info bpbrm (pid=28033) Sending the file list to the client
03/02/2015 20:46:00 - connected; connect time: 0:00:00
03/02/2015 20:46:27 - Info bptm (pid=28036) media id B08903 mounted on drive index 6, drivepath /dev/nst16, drivename TLD000-IBMhcart3-17-0007838675, copy 1
03/02/2015 20:46:28 - mounted B08903; mount time: 0:00:28
03/02/2015 20:46:28 - positioning B08903 to file 493
03/02/2015 20:47:34 - positioned B08903; position time: 0:01:06
03/02/2015 20:47:34 - begin writing
03/02/2015 20:47:43 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/usr/openv] is in a different file system from [/usr]. Skipping
03/02/2015 20:48:00 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/usr/openv/var/vnetd/bpcd.uds] is a socket special file. Skipping
03/02/2015 20:48:00 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/usr/openv/var/vnetd/terminate_bpcd.uds] is a socket special file. Skipping
03/02/2015 20:48:00 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/usr/openv/var/vnetd/terminate_vnetd.uds] is a socket special file. Skipping
03/02/2015 20:48:10 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/crash] is in a different file system from [/var]. Skipping
03/02/2015 20:48:11 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/log] is in a different file system from [/var]. Skipping
03/02/2015 20:48:11 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/opt/OV/tmp/ovcd.sock] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/acpid.socket] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/rpcbind.sock] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/abrt/abrt.socket] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/dbus/system_bus_socket] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/nscd/socket] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/run/nslcd/socket] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/anvil] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/bounce] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/defer] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/discard] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/error] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/lmtp] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/local] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/proxymap] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/proxywrite] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/relay] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/retry] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/rewrite] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/scache] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/smtp] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/tlsmgr] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/trace] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/verify] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/private/virtual] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/public/cleanup] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/public/flush] is a socket special file. Skipping
03/02/2015 20:48:12 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var/spool/postfix/public/showq] is a socket special file. Skipping
03/02/2015 20:48:13 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/boot] is in a different file system from [/]. Skipping
03/02/2015 20:48:13 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/dev] is in a different file system from [/]. Skipping
03/02/2015 20:48:14 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/home] is in a different file system from [/]. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/opt] is in a different file system from [/]. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/proc] is on file system type PROC. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/sys] is on file system type sysfs. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/tmp] is in a different file system from [/]. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/usr] is in a different file system from [/]. Skipping
03/02/2015 20:48:17 - Info bpbrm (pid=28051) from client ausu596a: TRV - [/var] is in a different file system from [/]. Skipping
03/02/2015 20:48:29 - Info bpbrm (pid=28033) media manager for backup id ausu596a_1425350759 exited with status 0: the requested operation was successfully completed
03/02/2015 20:48:29 - end writing; write time: 0:00:55
the requested operation was successfully completed  (0)

Parent Job log:

03/02/2015 20:45:56 - Info nbjm (pid=2702) starting backup job (jobid=1016731) for client ausu596a, policy u_os_bmr_np, schedule Full
03/02/2015 20:45:56 - Info nbjm (pid=2702) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1016731, request id:{6ACCEC1C-C14F-11E4-8350-54B64447C31E})
03/02/2015 20:45:56 - requesting resource ausu130a-hcart3-robot-tld-0
03/02/2015 20:45:56 - requesting resource ausu130a.NBU_CLIENT.MAXJOBS.ausu596a
03/02/2015 20:45:56 - requesting resource ausu130a.NBU_POLICY.MAXJOBS.u_os_bmr_np
03/02/2015 20:45:56 - granted resource  ausu130a.NBU_CLIENT.MAXJOBS.ausu596a
03/02/2015 20:45:56 - granted resource  ausu130a.NBU_POLICY.MAXJOBS.u_os_bmr_np
03/02/2015 20:45:56 - granted resource  B08903
03/02/2015 20:45:56 - granted resource  TLD000-IBMhcart3-17-0007838675
03/02/2015 20:45:56 - granted resource  ausu130a-hcart3-robot-tld-0
03/02/2015 20:45:56 - estimated 0 kbytes needed
03/02/2015 20:45:56 - begin Parent Job
03/02/2015 20:45:56 - begin Bare Metal Restore: Start Notify Script
03/02/2015 20:45:56 - Info RUNCMD (pid=28017) started
03/02/2015 20:45:56 - Info RUNCMD (pid=28017) exiting with status: 0
Operation Status: 0
03/02/2015 20:45:56 - end Bare Metal Restore: Start Notify Script; elapsed time 0:00:00
03/02/2015 20:45:56 - begin Bare Metal Restore: Bare Metal Restore Save
03/02/2015 20:45:57 - collecting BMR information
03/02/2015 20:45:57 - connecting
03/02/2015 20:45:57 - connected; connect time: 0:00:00
03/02/2015 20:45:57 - transfering BMR information to the master server
03/02/2015 20:45:57 - connecting
03/02/2015 20:45:57 - connected; connect time: 0:00:00
03/02/2015 20:45:57 - started process bpbrm (pid=28024)
Operation Status: 26
03/02/2015 20:45:59 - end Bare Metal Restore: Bare Metal Restore Save; elapsed time 0:00:03
03/02/2015 20:45:59 - begin Bare Metal Restore: Policy Execution Manager Preprocessed
Operation Status: 0
03/02/2015 20:48:29 - end Bare Metal Restore: Policy Execution Manager Preprocessed; elapsed time 0:02:30
03/02/2015 20:48:29 - begin Bare Metal Restore: End Notify Script
03/02/2015 20:48:30 - Info RUNCMD (pid=28259) started
03/02/2015 20:48:30 - Info RUNCMD (pid=28259) exiting with status: 0
Operation Status: 0
03/02/2015 20:48:30 - end Bare Metal Restore: End Notify Script; elapsed time 0:00:01
Operation Status: 1
03/02/2015 20:48:30 - end Parent Job; elapsed time 0:02:34
the requested operation was partially successful  (1)

[katlamudi]

Hi Yadagiri,

Please check bmrd log on master server (ORIG ID: 119),  if possible attach here.

Share your NB version and Client OS version as well.

regards,

Katlamudi

[mnolan · Accepted solution]

The BMR config transfer to the master server seems to be having issues.

03/02/2015 20:45:57 - transfering BMR information to the master server
03/02/2015 20:45:57 - connecting
03/02/2015 20:45:57 - connected; connect time: 0:00:00
03/02/2015 20:45:57 - started process bpbrm (pid=28024)
Operation Status: 26

This is why the parent ended in status 1, but the backup itself was status 0.

Here is a technote that shows one of many issues we could be having, as well as the logging used for this type of error.

http://www.symantec.com/docs/TECH200322

[tyadagiri]

Thank you for the Technote, this weekend we are applying the patch to 7.5.0.7, hope this will resolve the BMR issue.