Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Unsuccessful BMR backup

Created: 23 Dec 2013 • Updated: 23 Feb 2014 | 4 comments
This issue has been solved. See solution.

Stream Discovery is failing with error code 26, which is resulting in partial successful backup.

Netbackup version on both master and client - 7.5.0.4
OS version on both master and client - Solaris 10
 

Detailed status:
-------------------
12/17/2013 20:28:13 - Info nbjm (pid=1005) starting backup job (jobid=120) for client atrcxb2456bkp, policy atrcxb2456bkp_FILES, schedule Weekly_Full
12/17/2013 20:28:13 - Info nbjm (pid=1005) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=120, request id:{C0CE47D8-6759-11E3-9C17-002128001016})
12/17/2013 20:28:13 - requesting resource atrcx837-bup-hcart-robot-tld-0
12/17/2013 20:28:13 - requesting resource atrcx837-bup.NBU_CLIENT.MAXJOBS.atrcxb2456bkp
12/17/2013 20:28:13 - requesting resource atrcx837-bup.NBU_POLICY.MAXJOBS.atrcxb2456bkp_FILES
12/17/2013 20:28:13 - granted resource  atrcx837-bup.NBU_CLIENT.MAXJOBS.atrcxb2456bkp
12/17/2013 20:28:13 - granted resource  atrcx837-bup.NBU_POLICY.MAXJOBS.atrcxb2456bkp_FILES
12/17/2013 20:28:13 - granted resource  6701L4
12/17/2013 20:28:13 - granted resource  HP.ULTRIUM4-SCSI.001
12/17/2013 20:28:13 - granted resource  atrcx837-bup-hcart-robot-tld-0
12/17/2013 20:28:13 - estimated 0 kbytes needed
12/17/2013 20:28:13 - begin Parent Job
12/17/2013 20:28:13 - begin Stream Discovery: Start Notify Script
12/17/2013 20:28:13 - Info RUNCMD (pid=26746) started
12/17/2013 20:28:14 - Info RUNCMD (pid=26746) exiting with status: 0
Operation Status: 0
12/17/2013 20:28:14 - end Stream Discovery: Start Notify Script; elapsed time 0:00:01
12/17/2013 20:28:14 - begin Stream Discovery: Stream Discovery
12/17/2013 20:28:14 - Info bpmount (pid=18955) started
12/17/2013 20:28:14 - Info bpmount (pid=18955) exiting with status: 0
Operation Status: 0
12/17/2013 20:28:14 - end Stream Discovery: Stream Discovery; elapsed time 0:00:00
12/17/2013 20:28:14 - begin Stream Discovery: Bare Metal Restore Save
12/17/2013 20:28:14 - started process bpbrm (pid=26779)
Operation Status: 26

12/17/2013 20:28:16 - collecting BMR information
12/17/2013 20:28:16 - connecting
12/17/2013 20:28:16 - connected; connect time: 0:00:00
12/17/2013 20:28:16 - transfering BMR information to the master server
12/17/2013 20:28:16 - connecting
12/17/2013 20:28:16 - connected; connect time: 0:00:00
12/17/2013 20:28:27 - end Stream Discovery: Bare Metal Restore Save; elapsed time 0:00:13
12/17/2013 20:28:27 - begin Stream Discovery: Policy Execution Manager Preprocessed
Operation Status: 0
12/17/2013 20:37:16 - end Stream Discovery: Policy Execution Manager Preprocessed; elapsed time 0:08:49
12/17/2013 20:37:16 - begin Stream Discovery: Validate Image
Operation Status: 0
12/17/2013 20:37:16 - end Stream Discovery: Validate Image; elapsed time 0:00:00
12/17/2013 20:37:16 - begin Stream Discovery: End Notify Script
12/17/2013 20:37:16 - Info RUNCMD (pid=28494) started
12/17/2013 20:37:17 - Info RUNCMD (pid=28494) exiting with status: 0
Operation Status: 0
12/17/2013 20:37:17 - end Stream Discovery: End Notify Script; elapsed time 0:00:01
Operation Status: 1
12/17/2013 20:37:17 - end Parent Job; elapsed time 0:09:04
the requested operation was partially successful  (1)

Attached bmrsavecfg and bpcd logs. Can anyone suggest how to get rid off this issue.

Operating Systems:

Comments 4 CommentsJump to latest comment

Riaan.Badenhorst's picture

Please check this note

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

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

Mark_Solutions's picture

The log says: The NBU client version is incompatible with the NBU master server

I assume that you do have BMR configured on the Master Server - i have seen this error when BMR is not actually configured.

Worth a look through this tech note too - just in case: http://www.symantec.com/docs/TECH58033

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Jaime_Vazquez's picture

This is a known issue for NetBackup at version 7.5.0.4.  It is described in the Late Breaking News Bulletin for NBU 7.5.

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

The errror message of incompatilble versions is a red herring, a side effect of the root cause.  The 'bpbrm' process crashed.

Request EEB for 2991238 for the patch files. The fix replaces the "bpbrm" executable. The fix code is natively part of NetBackup 7.5.0.5 and later. A more prudent plan of action would be to upgrade the Master/Media servers to later releases.

See this article link for more information:

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

SOLUTION
Jaime_Vazquez's picture

Somesh:

Any updates on last comment?  Was your problem resolved by either install of the EEB or upgrade to 7.5.0.5 or later?