cancel
Showing results for 
Search instead for 
Did you mean: 

BMR Backups Failing

Hello all,

 

i'm setting up a test environment in our company and i'm running into some issues with BMR Backups here.

 

I'm using NBU 7.1.0.2 on a Windows Server 2008R2 Backup Server.

 

This is the detailed Job Status:

22.11.2011 10:37:46 - Info nbjm(pid=4660) starting backup job (jobid=76) for client bu-server02.ardasi.local, policy BMR, schedule MANUAL_FULL  
22.11.2011 10:37:46 - Info nbjm(pid=4660) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=76, request id:{BB72A357-0DDB-4174-B606-A859BEB7B1CA})  
22.11.2011 10:37:46 - requesting resource StorageUnit1_Pool1
22.11.2011 10:37:46 - requesting resource bu-dasi.ardasi.local.NBU_CLIENT.MAXJOBS.bu-server02.ardasi.local
22.11.2011 10:37:46 - requesting resource bu-dasi.ardasi.local.NBU_POLICY.MAXJOBS.BMR
22.11.2011 10:37:46 - Info nbrb(pid=3068) Limit has been reached for the logical resource bu-dasi.ardasi.local.NBU_CLIENT.MAXJOBS.bu-server02.ardasi.local    
22.11.2011 10:37:50 - granted resource bu-dasi.ardasi.local.NBU_CLIENT.MAXJOBS.bu-server02.ardasi.local
22.11.2011 10:37:50 - granted resource bu-dasi.ardasi.local.NBU_POLICY.MAXJOBS.BMR
22.11.2011 10:37:50 - granted resource MediaID=@aaaac;DiskVolume=\\bu-filer01\AdvancedDisk;DiskPool=Pool1;Path=\\bu-filer01\AdvancedDisk;StorageServer=bu-dasi.ardasi.local;MediaServer=bu-dasi.ardasi.local
22.11.2011 10:37:50 - granted resource StorageUnit1_Pool1
22.11.2011 10:37:50 - estimated 0 Kbytes needed
22.11.2011 10:37:50 - begin Parent Job
22.11.2011 10:37:50 - begin Bare Metal Restore, Start Notify Script
22.11.2011 10:37:50 - Info RUNCMD(pid=5088) started            
22.11.2011 10:37:50 - Info RUNCMD(pid=5088) exiting with status: 0         
Status 0
22.11.2011 10:37:50 - end Bare Metal Restore, Start Notify Script; elapsed time: 00:00:00
22.11.2011 10:37:50 - begin Bare Metal Restore, BMR Save
22.11.2011 10:37:50 - started process bpbrm (5000)
22.11.2011 10:37:54 - collecting BMR information
22.11.2011 10:37:54 - connecting
22.11.2011 10:37:56 - connected; connect time: 00:00:02
22.11.2011 10:37:56 - transferring BMR information to the master server
22.11.2011 10:37:56 - connecting
22.11.2011 10:37:56 - connected; connect time: 00:00:00
22.11.2011 10:37:57 - Error bpbrm(pid=5000) BMRERR: Received BMR error: Errors were encountered while discovering disk configuration. (1)
22.11.2011 10:38:01 - Error bpbrm(pid=5000) BMRERR: Received BMR error: Send of discovery not attempted. (1)   
22.11.2011 10:38:01 - Error bpbrm(pid=5000) BMRERR: Received BMR error: BMR information discovery failed. (1)    
22.11.2011 10:38:01 - Error bpbrm(pid=5000) BMRERR: Did not receive bmr client request from bu-server02.ardasi.local, status = -1
22.11.2011 10:38:01 - end writing
Status 26
22.11.2011 10:38:01 - end Bare Metal Restore, BMR Save; elapsed time: 00:00:11
22.11.2011 10:38:01 - begin Bare Metal Restore, Policy Execution Manager Preprocessed
22.11.2011 10:38:06 - Info bmrsavecfg(pid=0) done. status: 26: client/server handshaking failed       
Status 1
22.11.2011 10:56:07 - end Bare Metal Restore, Policy Execution Manager Preprocessed; elapsed time: 00:18:06
22.11.2011 10:56:07 - begin Bare Metal Restore, End Notify Script
22.11.2011 10:56:07 - Info RUNCMD(pid=2416) started            
22.11.2011 10:56:07 - Info RUNCMD(pid=2416) exiting with status: 0         
Status 0
22.11.2011 10:56:07 - end Bare Metal Restore, End Notify Script; elapsed time: 00:00:00
Status 1
22.11.2011 10:56:07 - end Parent Job; elapsed time: 00:18:17
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.

 

Content of bmrsavecfg:

$Header 65543,51216,121,1321953059,-3600,bu-dasi
0,51216,128,121,1,1321953059157,2912,1180,0:,42:Invalid input parameters, exiting, line=50,30:stringManipulation.cpp:Split(),1
0,51216,128,121,2,1321953059173,2912,1180,0:,152:The cable connect status for NIC \\.\{63F3A66C-1E36-4A81-9F4A-F36F945D2329} is found as: 1, Retrying Cable Connect Status check after a delay of 300ms..,36:WinNetwork.cpp:IsNicCableConnected(),1
0,51216,128,121,3,1321953059485,2912,1180,0:,152:The cable connect status for NIC \\.\{63F3A66C-1E36-4A81-9F4A-F36F945D2329} is found as: 1, Retrying Cable Connect Status check after a delay of 300ms..,36:WinNetwork.cpp:IsNicCableConnected(),1
0,51216,128,121,4,1321953059797,2912,1180,0:,152:The cable connect status for NIC \\.\{63F3A66C-1E36-4A81-9F4A-F36F945D2329} is found as: 1, Retrying Cable Connect Status check after a delay of 300ms..,36:WinNetwork.cpp:IsNicCableConnected(),1
0,51216,128,121,5,1321953067316,2912,1180,0:,59:Did not find the system volume even with alternative flags.,47:CWindowsVdsFacade.cpp:verifySystemVolumeFound(),1
0,51216,121,121,1,1321953067379,2912,1180,0:,36:diskAgent->discover failed, rc=10004,23:CBmrSaveCfg::discover(),1
2,51216,121,121,2,1321953067379,2912,1180,0:,0:,0:,2,(16|)
1,51216,128,121,6,1321953067457,2912,1180,0:,0:,33:regutils.cpp:GetRegistryString2(),1,(754|A18:HKEY_LOCAL_MACHINE|A25:SOFTWARE\VERITAS\VCS\Base|A13:HomeDirectory|i32:2|)
1,51216,128,121,7,1321953067457,2912,1180,0:,0:,26:CSaveCfgFile.cpp:execute(),2,(128|u32:66|A15:haclus -display|A18:.\CSaveCfgFile.cpp|i32:137|i32:1|i32:2|)
1,51216,128,121,8,1321953067457,2912,1180,0:,0:,26:CSaveCfgFile.cpp:execute(),2,(128|u32:66|A14:hasys -display|A18:.\CSaveCfgFile.cpp|i32:137|i32:1|i32:2|)
1,51216,128,121,9,1321953067457,2912,1180,0:,0:,26:CSaveCfgFile.cpp:execute(),2,(128|u32:66|A14:hagrp -display|A18:.\CSaveCfgFile.cpp|i32:137|i32:1|i32:2|)
1,51216,128,121,10,1321953067457,2912,1180,0:,0:,26:CSaveCfgFile.cpp:execute(),2,(128|u32:66|A14:hares -display|A18:.\CSaveCfgFile.cpp|i32:137|i32:1|i32:2|)
1,51216,128,121,11,1321953067457,2912,1180,0:,0:,26:CSaveCfgFile.cpp:execute(),2,(128|u32:66|A10:hares -dep|A18:.\CSaveCfgFile.cpp|i32:137|i32:1|i32:2|)
0,51216,128,121,12,1321953073088,2912,1180,0:,63:QLogic-Faserkanal-Adapter is incompatible with Windows 1.6 PE .,33:winpackage.cpp:FillOutPackageDb(),1
0,51216,128,121,13,1321953073291,2912,1180,0:,91:Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) is incompatible with Windows 1.6 PE .,33:winpackage.cpp:FillOutPackageDb(),1
0,51216,128,121,14,1321953073291,2912,1180,0:,91:Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) is incompatible with Windows 2.1 PE .,33:winpackage.cpp:FillOutPackageDb(),1
0,51216,128,121,15,1321953073510,2912,1180,0:,65:Could not determine running HAL. Returning the first hardware id.,33:deviceutils.cpp:GetRunningHalId(),1
1,51216,128,121,16,1321953073790,2912,1180,0:,0:,33:regutils.cpp:GetRegistryString2(),1,(754|A18:HKEY_LOCAL_MACHINE|A45:SYSTEM\CurrentControlSet\Services\MSSQLSERVER|A9:ImagePath|i32:2|)
0,51216,121,121,3,1321953073915,2912,1180,0:,19:Send not attempted.,23:CBmrSaveCfg::discover(),1
2,51216,121,121,4,1321953073915,2912,1180,0:,0:,0:,2,(57|)
2,51216,121,121,5,1321953073931,2912,1180,0:,0:,0:,2,(35|)

 

It seems like BMR is having trouble with the NIC of the System it sould backup...

And backed up systems are not showing up in the bmr restore clients list as they should do.

 

Any ideas?

 

Thanks in advance!

6 Replies

Hi

Here is the failure point

>>0,51216,128,121,5,1321953067316,2912,1180,0:,59:Did not find the system volume even with alternative flags.,47:CWindowsVdsFacade.cpp:verifySystemVolumeFound(),1

Is this a GPT system disk by any chance ?

If so, BMR doesn't support GPT disks as of now. This is our roadmap for future.

thanks

Suchitra

0,51216,128,121,5,13219530673

0,51216,128,121,5,1321953067316,2912,1180,0:,59:Did not find the system volume even with alternative flags.,47:CWindowsVdsFacade.cpp:verifySystemVolumeFound(),1
0,51216,121,121,1,1321953067379,2912,1180,0:,36:diskAgent->discover failed,

Looks like disk discovery job failed during bmrsavecfg execution at client.

1. Do you have GPT/EFI based system?

BMR as of yet does not support GPT/EFI based client system backup.

2. Do you have cluster environment or any specific volume configuration on client?

bmrsavecfg debug level 6 logs would help here.

Also try running below command if it works. This is a simulation of discovering bmr config but it will not send this details to master server and saves at client side only.

bmrsavecfg -infoonly

check if this works. I believe this would fail as there are some issues with disk discovery.

Thanks.

-mandar

Thanks for your

Thanks for your answers!

 

It's a single physical System using a mounted LUN from a NetApp System where the OS is installed into and it's indeed EFI based.

 

I can back up the Master Server partially successfull and it uses a mounted LUN too.

 

I've run the bmrsavecfg -infoonly and it failed.

http://www.symantec.com/busin

http://www.symantec.com/business/support/index?page=content&id=TECH127933

 

 

NetBackup Bare Metal Restore (BMR) unable to restore or recognize Extensible Firmware Interface (EFI) labeled disks.

As well as the excellent

As well as the excellent advice above and just going back to basics for a moment here, in your posts you have posted and have said:

22.11.2011 10:38:06 - Info bmrsavecfg(pid=0) done. status: 26: client/server handshaking failed      
 Status 1

It seems like BMR is having trouble with the NIC of the System it sould backup...
 
And backed up systems are not showing up in the bmr restore clients list as they should do.

So point 1 - we have client server handshaking not working and point 2 you say client do not show up in the console as they should.

Do you have any clients that do collect their BMR data successfully and do any appear in the console at all?

If not we need to make sure you have run the BMR Master Server setup successfully and also the bmrsetupboot -register

After that there are BMR further fixes in 7.1.0.3 so you may want to upgrade anyway - release notes here:

http://www.symantec.com/docs/DOC4886

Important when upgrading

Important when upgrading NBU:

For BMR to be successful, NBU versions on Master, Media and Client(s) must match.