Video Screencast Help

BMR error "Unable to Verify Backup"

Created: 21 Dec 2012 | 6 comments
Andre_Torres's picture

Hello my friends,

I was trying to perform a BMR, but it gives me the error "Unable to Verify Backup". Looking for it, I found this TECH:

while looking in it, identified the problem as error 135 described in the TECH. Tried the solutions (putting an entry in hosts in Master Server; adding in Host Properties -> Master Server -> Client Attributes) but it keeps giving me the same error.

I'm trying to BMR an Windows 2k3, the policy backup was configured ok, I have the image ok. The Master is in

The Target where I'm trying to restore is a raw machine, and I'm using a boot disk created by the boot server.

Anyone with BMR experience can help me solve this problem?

Comments 6 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

I'm not sure bpclntcmd is included in BMR recovery environment, but if exist, run "bpclntcmd -pn" and "bpclntcmd -self" on the recovery target machine and tell us how it shows.
Also run "bpclntcmd -ip <ip_address_of_client>" on the master server.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Andre_Torres's picture

bpclntcmd -ip on master:

aliases:     MININT-LKAA9FB
in the client, trying to run bpclntcmd give me the following error:
"This application has failed to start because libnbccl.dll was not found. Re-installing the application may fix this problem."
Remembering that I'm using a boot disc, so reinstall is not an option.
Yasuhisa Ishikawa's picture

Please check following points intead.

  • Hostname displayed in "bpclntcmd -ip <ipaddress_of_client>" on the master is same with client name in backup policy configured for BMR backup.
  • IP address displayed in "bpclntcmd -hn <hostname of client in policy>" on the master is same with IP address configured while BMR recovery. Run "ipconfig /all" in command prompt on BMR recovery environment.
  • Master server's IP address displayed in "req query HKLM\Software\Veritas\NetBackup\CurrentVersion\Config /V Server"  on BMR recovery environment is same with that of master server.
  • Client hostname displayed in "req query HKLM\Software\Veritas\NetBackup\CurrentVersion\Config /V Client_Name" is same with client name in backup policy.
  • IP address displayed in "ping <client_name>" on BMR revocery environment is same with IP address configured on BMR recovery environment.

Also check in bprd log to determine what requests are issued from client while recovery.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Andre_Torres's picture

The name will not be the same, because I'm trying to make a dissimilar restore.

I've made a copy of the current configuration of the client. Also, made a backup yesterday to make sure I have a valid image, with all local drives and system state.

The machines source and target of the BMR are exactly the same, the only changes are MAC Address and IP (which I inserted in the copy of the configuration).

mandar_khanolkar's picture

In BMR restore environment, open hosts file in notepad.

1. open command prompt in recovery env using open file and locate cmd.exe in x:\windows\system32 folder.

2. from command prompt cd into x:\windows\system32\drivers\etc\ folder and open notepad hosts file.

3. confirm if your nb master server ip-hostname is correctly configured.

4. sometimes it happens you register client name in backup policy with short name where your client always get resolved with ip with fqdn. in this case also backup verification fails.

you may want to add short and fqdn both for your client and master server name in this hosts file.

5. without rebooting client try verify backup step again. it may work.



Yasuhisa Ishikawa's picture

Client host name must be same because target host is configured as so so that same client request resore.

 the only changes are MAC Address and IP

It sounds like you delete original IP address and add new one. From server perspective, client that is different from original client is requesting restore. Master server expect that client A(original client) request client A's data, but client B request client A's data.

if you want to change IP, it should be done after completing successful recovery.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan