Highlighted
kem80
1 Copper

Avamar 7.5.1 BMR restore error message

We have recently upgraded our EMC Avamar envirornment to 7.5.1. We now have Data Domains that hold the avamar backups with virtual Avamar servers managing the backup/restores of virtual and physical machines.

We are currently doing some DR exercises with the new settup, but we are getting errors/issues with doing client recoveries of physical machines. Whether they are  Win 2008 or 2012, recovering to similar hardware or even to a virtual overspeced machine we get the same error message.. During the recovery we are booting off the Avamar BMR disk, connecting to the Avamar server, and it will correclty present all the backups available. Which ever image/backup you choose to restore from  it just returns with the error below:-

Critical Volume Error - Error retrieving the list of critical volumes using a backup label of 'xxx' and command line option of "; Critical volume mapping XML error. miscellaneous error (536870919) "

Unfortunately not much out there with this issue, anybody shed any light?

0 Kudos
10 Replies
rishi8419
1 Nickel

Re: Avamar 7.5.1 BMR restore error message

Use Avamar_Windows_BMR_Wizard_x64_WinPE10-7.4.101-58.iso to make this work . It will atleast start it

0 Kudos
Pawan_Kumawat
2 Bronze

Re: Avamar 7.5.1 BMR restore error message

Hi,

Please make sure vss/system state backup is completed with no exceptions.

I faced this issue when had issue with system state backups.

Regards,

Pawan Kumawat

0 Kudos
Pawan_Kumawat
2 Bronze

Re: Avamar 7.5.1 BMR restore error message

Found a EMC KBA for this-

Avamar BMR is failing with error "Error retrieving the list of critical volumes using a backup label "<NUMBER>" and command line options of ": critical volumes mapping xml error miscellaneous error (536870919?)"

Retrieving system_info for the backup from WINPE is failing:

avtar FATAL <0000>: failed to load and initialize Data Domain library (libDDBoost)
avtar FATAL <10536>: Failed to initialize DDR communications manager, DDR result code: 5031 desc:
avtar Error <10512>: Problem logging into the DDR server index:1

Syntax retrieving system_info area files:
avtar.exe -x --server=<Avamar server> --id=<MC user> --ap=<MC user's password> --path=<domain>/<client name> --labelnum=<Label number> --target=<Path at local disk> ".system_info" --internal



Bug in Avamar 7.5.101-101 WinPE code.


Apply HF#296330

Workaround:
Use Avamar Windows BMR Wizard 7.4.101-58 ISO


0 Kudos
CyberJoeIT
1 Nickel

Re: Avamar 7.5.1 BMR restore error message

Does this issue apply to Avamar_Windows_BMR_Wizard_x64_WinPE10-7.5.101-101.iso?  I was testing our BMR process and Avamar barfed for: 

"Error retrieving the list of critical volumes using a backup label "<NUMBER>" and command line options of ": critical volumes mapping xml error miscellaneous error (536870919?)"

0 Kudos
Santhosh_Arjun
1 Copper

Re: Avamar 7.5.1 BMR restore error message

Hi, Can you share KB article please Also, Did anyone found workaround for Avamar 7.5.0 . I am having similar issues where BMR initiates fine but fails with error "Error retrieving the list of critical volume"
0 Kudos
pablo56321
1 Copper

Re: Avamar 7.5.1 BMR restore error message

where can we download the 7.4 winpe ISO ? thanks
0 Kudos
pablo56321
1 Copper

Re: Avamar 7.5.1 BMR restore error message

i got the same error , where can we download this iso ? "Use Avamar Windows BMR Wizard 7.4.101-58 ISO"  thanks
0 Kudos
ionthegeek
4 Ruthenium

Re: Avamar 7.5.1 BMR restore error message

The hotfix is a patched version of the 7.5.1-101 ISO which you can retrieve from here:

ftp://avamar_ftp:anonymous@ftp.emc.com/software/hotfixes/296330/WIN64/AvamarWindowsBMRWizard_x64_WinPE10-7.5.101-101.iso

0 Kudos
pablo56321
1 Copper

Re: Avamar 7.5.1 BMR restore error message

thanks for your reply , even with this avamar version I still got "  Critical Volume Error - Error retrieving the list of critical volumes using a backup label of 'xxx' and command line option of "; Critical volume mapping XML error. miscellaneous error (536870919) " 

can it be a problem with the drive size of my computer ? 

0 Kudos