Open File

[belse]

Hello All,

I am using Veritas Netbackup 6.5.6. I have enabled VSS for open file backup whenever backup gets finished I  get two job IDs one is always with 0 success and other one is (1) partially sucess. 

Why does this happen? is backup successful?. Sharing the logs for both job ids and screenshot as well. let met tell you its disk based backup.

(1)  Successfull.

2/15/2013 5:08:25 PM - estimated 0 kbytes needed

2/15/2013 5:08:25 PM - started

2/15/2013 5:08:28 PM - started process bpbrm (920)

2/15/2013 5:08:33 PM - connecting

2/15/2013 5:08:34 PM - connected; connect time: 00:00:01

2/15/2013 5:08:56 PM - begin writing

2/15/2013 5:09:34 PM - end writing; write time: 00:00:38

the requested operation was successfully completed(0)

(2) Partial.

2/15/2013 5:07:51 PM - requesting resource A00001

2/15/2013 5:07:51 PM - requesting resource master.NBU_CLIENT.MAXJOBS.slave

2/15/2013 5:07:51 PM - requesting resource master.NBU_POLICY.MAXJOBS.abelwal

2/15/2013 5:07:52 PM - granted resource master.NBU_CLIENT.MAXJOBS.slave

2/15/2013 5:07:52 PM - granted resource master.NBU_POLICY.MAXJOBS.abelwal

2/15/2013 5:07:52 PM - granted resource MediaID=@aaaac;Path=E:\A00001;MediaServer=master

2/15/2013 5:07:52 PM - granted resource A00001

2/15/2013 5:07:54 PM - estimated 0 kbytes needed

2/15/2013 5:07:54 PM - begin Parent Job

2/15/2013 5:07:54 PM - begin Bare Metal Restore, Start Notify Script

2/15/2013 5:07:54 PM - started process RUNCMD (3896)

2/15/2013 5:07:54 PM - ended process 0 (3896)

Status 0

2/15/2013 5:07:54 PM - end Bare Metal Restore, Start Notify Script; elapsed time: 00:00:00

2/15/2013 5:07:54 PM - begin Bare Metal Restore, BMR Save

2/15/2013 5:07:54 PM - started process bpbrm (2524)

2/15/2013 5:07:59 PM - collecting BMR information

2/15/2013 5:07:59 PM - connecting

2/15/2013 5:08:00 PM - connected; connect time: 00:00:01

2/15/2013 5:08:00 PM - transferring BMR information to the master server

2/15/2013 5:08:00 PM - connecting

2/15/2013 5:08:01 PM - connected; connect time: 00:00:01

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: Failed to import Config file. (1)   

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: Failed sending the discovery. (1)    

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)

2/15/2013 5:08:25 PM - end writing

Status 1

2/15/2013 5:08:25 PM - end Bare Metal Restore, BMR Save; elapsed time: 00:00:31

2/15/2013 5:08:25 PM - begin Bare Metal Restore, Policy Execution Manager Preprocessed

Status 0

2/15/2013 5:09:34 PM - end Bare Metal Restore, Policy Execution Manager Preprocessed; elapsed time: 00:01:09

2/15/2013 5:09:34 PM - begin Bare Metal Restore, End Notify Script

2/15/2013 5:09:34 PM - started process RUNCMD (2560)

2/15/2013 5:09:34 PM - ended process 0 (2560)

Status 0

2/15/2013 5:09:34 PM - end Bare Metal Restore, End Notify Script; elapsed time: 00:00:00

Status 1

2/15/2013 5:09:34 PM - end Parent Job; elapsed time: 00:01:40

the requested operation was partially successful(1)

The job was successfully completed, but some files may have been

busy or unaccessible. See the problems report or the client's logs for more details.

[RamNagalla · Accepted solution]

the job that got failed is a Parent job

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: Failed to import Config file. (1)   

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: Failed sending the discovery. (1)    

2/15/2013 5:08:24 PM - Error bpbrm(pid=2524) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)

and its trying to say that the Client version is not compatiable with Master server. 

and it has BMR enabled?

are you trying to do the BMR backup? if not Please disalbe it from policy attributes and try again?

if you are trying to do the BMR backup, then let us know the Version of netbackup Master and Clients.

[belse]

Hi Nagalla....... Thanks so much for reply so nice of you......You are right in Policies Collect disaster recovery for bmr was by default checked. Is it the culprit? If yes why is it saying " Client version is not compatiable with Master server" and when should we use BMR enabled option.

[Marianne]

Is it the culprit?

Yes

If yes why is it saying " Client version is not compatiable with Master server"

You need to tell us.
Tell us exact version, patch level, bit version of:
Master server OS
Master server NBU version
Client OS
Client NBU version
 

and when should we use BMR enabled option.

When BMR is a Business requirement in your organization

**** NB **** You NEED to upgrade your environment. NBU 6.x is no longer supported.

[belse]

Thanks for reply Marianne...

Pls find....

Tell us exact version, patch level, bit version of:
Master server OS Win2003
Master server NBU version 6.5.6
Client OS win2003 
Client NBU version 6.5

[Marianne]

I remember that NBU 6.5 needed master and clients to be on exact same patch level for bmr to work.
So, you need to patch client to 6.5.6.

Even better: Upgrade your entire environment to 7.5.0.4.

[mandar_khanolka]

Actually client can be less than 6.5.6 master. BMR master server log would reveal root cause. Can you check the log with 119 id.

First confirm if you need BMR protection (server level DR protection) to your client.

If not then you can disable BMR from your backup policy.

And as Marianne suggested better to go with 7.5.x.

Thanks.

Mandar

[Marianne]

I had 1st-hand experience where a customer patched 6.5 master first and BMR backups stopped working.

Status 0 after clients were upgraded.