Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

NBU 6.5.4 - Synthetic Backup failing BMR Errors

Updated: 21 May 2010 | 1 comment
Trevor_Jackson's picture
Trevor_Jackson
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi all,

We have a Solaris 10 server running NBU 6.5.4 which we are testing out different features on. We are trying to create a backup which reduces the size, and the duration of each nightly backup. Effectively only securing the delta information. However, each time we perform the backup we get the following error: - [Note: Systems we are trying to backup are Windows 2003 servers]

0/08/2009 04:00:02 - begin Snapshot: Bare Metal Restore Save
10/08/2009 04:00:03 - started process bpbrm (pid=1535)
10/08/2009 04:00:51 - Error bpbrm (pid=1535) BMRERR: Received BMR error: Failed to import Config file. (1)
10/08/2009 04:00:51 - Error bpbrm (pid=1535) BMRERR: Received BMR error: Failed sending the discovery. (1)
10/08/2009 04:00:51 - Error bpbrm (pid=1535) BMRERR: Received BMR error: BMR information discovery failed. (1)
10/08/2009 04:00:54 - begin Create Snapshot
10/08/2009 04:00:51 - end writing
Operation Status: 1

10/08/2009 04:00:51 - end Create Snapshot; elapsed time 8759:59:57 

The errors would seem to indicate that the BMR client cannot be communicated with. 

Under 'BMR Management' the servers are not listed in the BMR Client list, which is also odd...

Can anyone advise?

Also, does anyone know how to add a new BMR client, can't seem to find the information to do this?

Thanks

Trevor

discussion Filed Under:
,

Comments

Trevor_Jackson's picture
08
Oct
2009
0 Votes 0
Login to vote
Trevor_Jackson

I believe this is resolved...

Hi people,

I checked the bprd log and it pointed me to the error 'status = client is not validated to use the server (131)' which turns out to be related to the name used by the server we are backing up, when it translates name to IP and IP to name again.

There is now a DNS server with servername.support.local which has been added.

Therefore I went into Backup, Archive and Restore and added a new Server. (http://seer.entsupport.symantec.com/docs/269612.htm)

The server now exists and I can see the restore data. However, I believe I need to add the server name to the bp.conf on the master server to allow this to occur properly.

Hope it work, fingers crossed!!

Trevor

SOLUTION

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
258,911