Overview of restoring Windows with network boot using Netbackup Bare Metal Restore.

Article:TECH153514  |  Created: 2011-02-16  |  Updated: 2014-11-04  |  Article URL http://www.symantec.com/docs/TECH153514
Article Type
Technical Solution


Environment

Subject

Issue



Overview of Restoring Windows with network boot.

  • In a network boot, the BMR client boots from the shared resource tree on the BMR boot server.
  • Windows systems network boot uses the PXE protocol. The BMR boot server provides and manages the PXE network services, but a DHCP service is required in the environment.
  • The NIC on the client needs to be PXE compatible and enabled within the BIOS. It also needs to be the first boot device.
  • BMR require a Boot Server in the same subnet of the client in order to do network boot.
  • There needs to be an existing DHCP server within the network environment. Or else you may temporarily install and configure DHCP on the BMR Boot server and define a scope of IP addresses. This is purely Microsoft procedure and the external link below explains the procedures …

http://www.windowsnetworking.com/articles_tutorials/DHCP_Server_Windows_2003.html

  • BMR has its own PXE and TFTP service setup on BMR Boot server.
  • PXE booting process involves two steps, client first broadcast DHCP request to get IP from DHCP SERVER that is available in that subnet and then uses TFTP to download boot image and additional files (i.e. BMR SRT in BMR NW boot case).
  • The client first gets an IP from the DHCP server so that it can contact BMR master serverafter booting into BMR WinPE based restore environment. Once BMR master replies with the client configuration details, the correct intended IP will be set again by the BMR restore process.

 


Environment



Definitions of network components necessary for a network boot / restore using BMR.

BMR Boot Server            
The BMR Boot Server supports both PXE and BOOTP boot protocols, and provides service functionalities needed for network booting.
Using PXE or BOOTP, the Boot Server provides the boot ROM on the client PC with boot information from the client configuration database for that particular client PC, such as the filename of the boot image file to be downloaded. In addition, if BOOTP is used it will also provide a static IP address for the client PC; whereas, if PXE is used, the network's DHCP server provides a dynamic IP address.
               
PXE
The PXE protocol is an extension of DHCP, designed, among other things, to standardize network booting operations. It is used primarily in WfM environments where client PCs have PXE-compatible boot ROMs. Windows systems network boot uses the PXE protocol. The BMR boot server  provides and manages the PXE network services, but a DHCP service is  required in the environment. 
               
BOOTP
You can use BOOTP in place of DHCP services on Unix machines to respond to IP address requests from client PCs that have BOOTP compatible boot ROMs
               
TFTP Server
TFTP is used to transfer files between a client PC and server on a TCP/IP network. TFTP is used during network booting to transfer boot image files from the server to the client PC using the boot ROM. TFTP can also be used to provide updates to dedicated network devices, switches, routers, and print servers.

Solution



How to network boot a Windows client?

  • “Prepare to Restore” the client. For procedures, see "Preparing to restore a client" on page 54 of the Symantec NetBackup BMR Administrator's Guide
  • PXE boot the client according to the hardware vendor instructions. On  some systems, the BIOS displays a message that indicates that you can  press a key to force a PXE boot. On others, you may have to modify the  settings in the BIOS to add the network card to the default boot order. 
  • The following message  should appear: "DHCP....Press F12 for network service boot”
  • Press the Function 12 key and the system will boot and the restore  begins with no further user intervention required




Article URL http://www.symantec.com/docs/TECH153514


Terms of use for this information are found in Legal Notices