Requirements for Bare Metal Restore (BMR) Boot Servers

Article:TECH87607  |  Created: 2009-01-19  |  Updated: 2013-08-23  |  Article URL
Article Type
Technical Solution





Requirements for Bare Metal Restore (BMR) Boot Servers


 For Bare Metal restore (BMR) Boot Servers the following are the requirements:
1.   The Boot Server services are considered client services. As such a BMR Boot Server does not have to reside on a Master Server. The Master and Boot Server can reside on the same server without issue. The Boot Server must be of the same OS as the clients that are being recovered.  A Windows OS based Boot Server of any supported platform can support recovery of any BMR supported Windows based clients. A Solaris 10 X86 Boot Server only supports Solaris 10 X86 clients.  It does not support SPARC hardware systems and vice-versa.  You can have multiple Boot Servers of the same OS registered to the Master Server. You can have multiple Boot Servers of any supported OS registered to the Master Server.  You should only have a single Boot Server of any given OS variant per subnet. 
2.    The Boot Server can only support clients at the same OS release/maintenance level or lower than it is. Examples are:
  • A Solaris 9 Boot Server can do Solaris 9 and Solaris 8 clients, but not Solaris 10.  A Solaris 10 (SPARC) Boot Server can support all currently supported versions of Solaris clients (Sparc hardware only).  However if you wish to support clients at Solaris 10 Update 6 or higher, you must have a Solaris 10 Update 6 or higher Boot Server in order to create the proper Shared Resource Tree (SRT) data. See related Tech Note 329993 for further information. Restoring Solaris 10 Update 6 or higher clients requires installation of NBU release 6.5.2 or higher and related EEB files.  See related Tech article TECH73669. The Maintenance/Update level (kernel version) of the Boot Server must also be at the highest level for any client it supports.  The kernel version also sets the highest level of Shared Resource Tree (SRT) that can be created on the given Boot Server. As an example, a Solaris 10 Boot Server with kernel version "Generic_144488-06" cannot create or host an SRT of kernel version "Generic_147440-01", which is numerically higher. BMR Solaris (SPARC) Boot Servers emulate the actions of a normal Solaris JumpStart server. If there is a pre-existing JumpStart server on the same sub-net, the network boot mechanism may have unpredictable results.
  • Windows Boot Servers at NBU/BMR patch release 6.5.3 and earlier are only supported on 32 bit OS releases and only support 32 bit clients.
  • Starting with NetBackup 6.5.4, Windows 2003 64-bit client support was added. A Windows 2003 Boot Server at 32 or 64 bit can support both 32 and 64 bit Windows 2003 clients. 
  • A Windows 2000 Boot Server can only support Windows 2000 clients. Windows 2000 support is restricted to NetBackup 6.X releases only.
  • Windows XP clients are not supported as BMR Boot Servers.
  • Netbackup 7.0.1 introduced the support for Windows 2008/2008 R2 Boot servers and clients.  Support exists for both 32 and 64 bit Windows 2008/2008R2 clients. 
  • On Netbackup 7.0.1, a Windows 2003 Boot Server (both 32 and 64 bit) supports restoration of all supported Windows client versions (Windows XP, 2003, Vista, Windows 7, Windows 2008 / 2008 R2). The Windows WinPE SRT images are generic and will work with ANY version of supported Windows clients. The SRT used for client restores must match the architecture (32 or 64 bit) of the client backup image. A 32 bit SRT must be used to restore a 32 bit Windows OS backup image and a 64 bit SRT must be used for 64 bit images. 
  • Support for Windows 2000 is dropped in Netbackup 7.0.  A Windows 2000 client needs to remain at release 6.5.X and will require a 6.5.X Boot Server in order to be restored using BMR. They must be recovered using a 6.5.X SRT.
  • Red Hat Linux Version 6 can support Red Hat Versions 5 and lower supported releases.  The Red Hat maintenance update level must be as high or higher than the clients it supports and the SRT versions it can create.
  • Suse Linux Version 11 supports restoring Version 10 and supported lower versions clients. SRT creation rules are the same. The update (MP) level restrictions also apply.  
  • Not all OEM vendor released maintenance levels are supported by BMR.  See the OS Compatibility List, TECH76648, for a listing of clients that can be BMR Boot Servers and clients.
3.  Boot Server should be updated to the same NBU patch level as the Master Server. It can not be at a patch level higher than what the BMRDB is initialized to. The Boot Server must be at the same NBU patch level or higher than the clients it supports.  For NBU 7.X, Boot Server software is installed with client software installs. As such, any patch updates will automatically update both the client and Boot Server software.
4.  AIX network booting is the only OS that can cross subnets.  All other OS variants supported by BMR require a Boot Server in the subnet of the client in order to do network boot. If one is not available, the use of BMR Bootable Media is required.
5.  You must have a BMR Boot Server to create BMR bootable restore media.  The ISO image created is always based on an existing NFS based SRT which must be created first. However, when using a media SRT for BMR recoveries, a Boot Server is not required and is not part of the restore process. To make use of the boot media, the BMR process Prepare To Restore must specify the CDFS based Shared Resource Tree (SRT) in order to have the correct restore files created in the BMR database (BMRDB). Failure to do so will cause restore time errors.
       NBU 6.5.X environments:  The installation of the Boot Server software is separate from the installation of the other NBU/BMR components. In all cases the software must initially make use of install media, not update media.  For Windows installations, the software is part of the Additional Software section. For Unix installs a separate BMR install CD is used. Windows based BMR Master and Boot Server software is updated by the single patch file.  Unix Master and Boot Servers each have their own update patch files. A Boot Server must be registered with the Master Server before it is operational.  The command 'bmrsetupboot' will perform this task.  The server name used for the registration will be the NBU client name of the system.
       NBU 7.X environments:  Boot Server software is automatically installed with client software installs.  The software is updated along with client software updates. Boot Servers at this release register to the Master Server using "bmrsetupboot -register".  The server name will always be the NBU client name. 
      In some rare instances, the NBU version of the Boot Server will not be accurately reflected in the BMRDB.  To refresh this, simply run the same 'bmrsetup' boot command used to initially register the client.  This will only update the key value in the BMRDB and has no other side-effects. If this fails to properly update on the Master Server, please contact Symantec NetBackup Support for assistance.

A complete output of registered Boot Servers can be displayed by running, on the Master Server, either of these commands: 

            bmrs -o query -res BootServer

            bmrs -o list -res database -table BootServer


Legacy ID


Article URL

Terms of use for this information are found in Legal Notices