NetWorker: BMR wizard is unavailable after Host and Network step while detecting disks
Summary: NetWorker: Bare Metal Recovery (BMR) wizard stops responding after 'Host and Network' step while detecting disks.
Symptoms
BMR wizard stops responding after 'Host and Network' step while detecting disks.
Eventually the disk detection may time-out with error:
Error trying to initialize 'X:/Program Files/EMC NetWorker/nsr/bin/winpe_nw_support.dll'Cause
Disk or controller (or SAN) fault.
In the DOS window, try running 'diskpart' - it should come up with a 'DISKPART>' prompt within a few seconds.
If it does not, this confirms that the system cannot communicate with the disks correctly.
Command 'list disk' should show all available disks.
'list disk' Resolution
Disable the SAN-attached drives and re-run the BMR wizard:
The BMR wizard only recovers critical volumes which means the Windows boot drive (usually C:\) and any drives that services depend on.
If there are other drives to recover, this can be performed with the NetWorker User program once the server has rebooted post recovery.
If the critical drives are local to the server, and it also has SAN-attached drives, it is possible to disconnect the SAN-attached drives and complete the recovery without issue.
This can be achieved by either disconnecting the FC port, disabling the HBA slot, or temporarily changing the SAN zoning so that no drives are presented.
Even if the SAN-attached drives are needed for recovery, disabling the SAN-attached drives by one of the above methods is a useful test to check if the SAN or HBA is responsible for the unavailability at the disk detection stage.
Reboot the BMR system after disabling and run the wizard again to confirm it now gets to step 4, 'Available Disks'.