Error V-126-3 bmrprep could not complete the requested operation

AnthonyD's picture
 
Everytime we try to perform a "Prepare to Restore" operation on our NetBackup 6.0 MP3 clients, we receive the message:
 

Error V-126-3 bmrprep could not complete the requested operation.

Please see logs for additional information.

The SRT Solaris9_905 could not be shared by the Boot Server hosting it. Please verify that the required confirguration in the Boot Server is correct. The nfs daemons and configuration files need to be properly working for this operation to work.

 

Does anyone know how I can troubleshoot this problem?

 

Servet's picture

Hi,

 

I have just experienced the same problem;

 

I've fixed the issue to adding hostnames and IPs to /usr/openv/netbackup/bpconf and /etc/hosts files for each server (master,boot server and client). Try it.

 

And see the teschnote that is published by Symantec.

 

http://seer.entsupport.symantec.com/docs/284762.htm 

 

FYI

 

 

claudio.veronezi@consteltecnologia.com's picture

I've done it but partially

I've done it to /etc/hosts

at the bp.conf  there is another sintaxe or something?

could U send me an example please?

Att.

Cláudio Veronezi Mendes
Eng Computação
Londrina - PR - Brazil
EMC / Solaris / Veritas

Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil

claudio.veronezi@consteltecnologia.com's picture

Generate image again

I've solved the problem creating a new image (iso)  in server

thanks a lot

Cláudio Veronezi Mendes
Eng Computação
Londrina - PR - Brazil
EMC / Solaris / Veritas

Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil

Zahid.Haseeb's picture

See this below post also, it

See this below post also, it may help you more

http://www.symantec.com/connect/blogs/error-v-126-3-bmrprep-could-not-complete-requested-operation

Thanks in Advance
Zahid Haseeb

Armin Sievers's picture

HiI faced this problem also

Hi

I faced this problem also and got it solved.
The problem was not IP related, instead the / directory was full and so nothing could be written to the /tftpboot directory.
Maybe it is a usefull hint.

kr
Armin