cancel
Showing results for 
Search instead for 
Did you mean: 

I can not find NIC in IDR proccess

T_a_z
Level 3

I'm evaluating BE2010 R2.
Media Server: WS2K8 R2 with hotfix Sep 2010
Remote Agent: WS2K8 SP2 Active Directory
              WS2K8 R2 MSFC File Server
BE2010R2 HotFixed 358289

(All hosts build on Hyper-V environment)

I try to restore for WS2K8 Domain Controller with IDR.
But wizard can't find Network Interface in NIC detection process.

How can I do NIC detection?

I can restore WS2K8 R2 environments with IDR.

 

9 REPLIES 9

T_a_z
Level 3

I enabled Exchange Agent for VFF problem at evaluation time.

Currently, I'm testing for BE2010R2 disaster recovery.
I will change environment from virtual to physical after testing.

Domain Controller: WS2K8 SP2 x64
Media Server: WS2K8 R2 (x64)

I succssed IDR with WS2K8 R2 remote server.

How to enable Network interface for remote disaster recovery?


 

Kiran_Bandi
Level 6
Partner Accredited

If you change the network interface card in the computer you are recovering, you must install the necessary network drivers. Without the network drivers, you cannot access the network if you want to use a remote media server or remote backup-to-disk folders to recover the computer. After you complete the recovery, you must install new network interface card drivers that match the network card presently in the computer. The backup sets that you use to recover the computer contains the original network interface card drivers for the faulty network interface card that you replaced.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

We would need the details from the BEDRWIZ.log to prove this - but if you are using a server model where the inbuilt NIC's use Broadcom Chipsets (such as certain models from Dell and HP) then the latest Broadcom cards don't get correctly identified.

 

The fix in this instance is:

Add the following entries

 

PCI\VEN_14E4&DEV_163B
PCI\VEN_14E4&DEV_163C

 

to the ‘<BackupExec Install Path>\idr\disk4\bedrwiz.ini’ file under the [Network Bus Enumerators] section on the media server and recreate the IDR recovery CD for the Windows 2003 R2 Standard x64 remote system. After the addition the [Network Bus Enumerators] should resemble the following

 

;
; Section to list custom network bus enumerator devices
;

[Network Bus Enumerators]

; Broadcom BCM5708C  NetXtreme II GigE VBD
PCI\VEN_14E4&DEV_1639
PCI\VEN_14E4&DEV_163A
PCI\VEN_14E4&DEV_163B
PCI\VEN_14E4&DEV_163C
PCI\VEN_14E4&DEV_164A
PCI\VEN_14E4&DEV_164C
PCI\VEN_14E4&DEV_16AA
PCI\VEN_14E4&DEV_16AC

 

; NVIDIA Network Bus Enumerator

PCI\VEN_10DE&DEV_0086
PCI\VEN_10DE&DEV_00DF
PCI\VEN_10DE&DEV_0038
PCI\VEN_10DE&DEV_0057
PCI\VEN_10DE&DEV_0269

T_a_z
Level 3

Thank you, Colin!

Could you tell me how to find device ID(?) for physical environment?

I found KB similar my eval environment.
http://www.symantec.com/business/support/index?page=content&id=TECH72113&actp=search&viewlocale=en_US&searchid=1285302858914

I'll evaluate again soon !

 

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

Hmm sorry I don't understand what you are after - you don't need a device ID to implement the change I provided - and the change I provided only affects physical systems with Broadcom chipsets - virtual ssystems should not have the same problem.

T_a_z
Level 3

I am confirming the procedure of IDR with VM.

After I confirm the procedure, the procedure is confirmed in a physical environment.

When I use non-major NIC, the same processing as Broadcom might be needed. I thought.

Colin_Weaver
Moderator
Moderator
Employee Accredited Certified

OK the NICs inside of a VM should not need modification of the files to work - you will need to boot the VM off the ISO CD image created by Backup Exec after IDR

However if you have a live Hyper-V environment you might want to consider the capabilitities of the Hyper_V agemt and not use IDR at all - comment does not apply if only using Hyper-V to test processes for a Physical Installation.

T_a_z
Level 3

Thank you for your comment.

It's only using Hyper-V to test processes for a physical environment.


So I worry about using non-major NIC in a physical environment.

 

Peter_Caron
Not applicable

I am having a similar issue as the original post, when attempting to add the data provided into my bedrwiz.ini i do not see the required fields. My bedrwiz.ini is below in its entirety.

 

[Control]
TapeMode=0
NoNetwork=0
TimeZoneInfo=2C0100004500610073007400650072006E0020005300740061006E0064006100720064002000540069006D0065000000000000000000000000000000000000000000000000000B00000001000200000000000000000000004500610073007400650072006E0020004400610079006C0069006700680074002000540069006D0065000000000000000000000000000000000000000000000000000300000002000200000000000000C4FFFFFFAC