Documentos de Académico
Documentos de Profesional
Documentos de Cultura
5. List of registered clients can be seen by use of Administration Console or from CLI.
Admin Console: BMR Administration Node -> Hosts -> BMR Clients
CLI: bmrs -o list -res [ Config | Client ]
6. Before a BMR recovery can occur, you MUST define the Boot Server environment. Use this
article for assistance:
Requirements for Bare Metal Restore (BMR) Boot Servers
http://www.symantec.com/docs/TECH87607
BMR Boot Servers are OS specific. A BMR Boot Server must exist for every OS type of
protected/registered clients. For Windows clients, a single Windows based Boot Server can be
used to recover all supported Windows OS versions, to include 32 bit or 64 bit versions. Any
NBU server or client can be designated as a Boot Server. BMR Boot Server software is part
of the client software install. The command to run is:
> bmrsetupboot -register
Once done, the Boot Server will be visible on the Master Server.:
Admin Console: BMR Administration Node -> Hosts -> BMR Boot Servers
CLI: bmrs -o list -res BootServer
All Boot Servers will register to their designated Master Server. Multiple Boot Servers are
allowed within any NBU domain. They cannot be shared by multiple Master Servers.The
running daemon process on a BMR Boot Server is 'bmrbd'..
7. See the OSCL for NBU clients that are supported by BMR:
NetBackup (tm) 7.x Operating System Compatibility List
http://www.symantec.com/docs/TECH76648
In the section for NBU Clients, look under the column for BMR Boot/Client Support. Please
note: The fact that a client is supported as a NBU client does not automatically make it a BMR
supported client. Some OS release versions of supported client may require a minimum install
release of NBU/BMR.
8. BMR client recoveries require the use of BMR specific boot images. The boot image is known
as a Shared Resource tree (SRT). Each Boot Server will create an SRT specific to its OS type. On
all Boot Servers, the command is "bmrsrtadm". For Windows you can use the GUI version
"Boot Server Assistant".
9. BMR recoveries can start from either a network boot, or a media (CD/DVD/ISO) boot. Initial
SRT creation will always be the file system based network boot SRT. Media SRT boot images
are created based on them.
For Unix/Linux SRT, the boot image information placed into the SRT is extracted from files
found in the normal OS vendor install media. Such media is required for SRT creation.
For Windows clients, the SRT makes use of a Windows WinPE image. For NBU/BMR versions
up to and including 7.6.0.X, the base "wim" file is distributed with the NBU client software.
Starting with NBU version 7.6.1.1, the initial WinPE environment needs to be downloaded from
Microsoft as part of a SDK file set. Specific instructions on how this is done will be found the
the BMR 7.6.1.1 Systems Administration Guide.
10. The BMR boot method used will always be based on the native boot method of the given OS.
For example, network based boot of Windows and Linux clients will make use of PXE boot
protocols. A Solaris environment will use JumpStart. However, Solaris Sparc servers cannot
boot Solaris x86 clients and vice versa.
At the highest level, the basic steps for this fall into three items:
1. Initialize the BMR Master (bmrd) and BMRDB: bmrsetupmaster
2. Create/Initialize BMR Boot servers (bmrbd): bmrsetupboot -register
3. Create required SRT boot images: bmrsrtadm
Some additional documentation articles that are publicly available and useful for BMR actions:
Doing a Dissimilar System Restore (DSR) to new hardware for Windows clients using Bare
Metal Restore (BMR) on NetBackup 6.X and 7.X releases.
http://www.symantec.com/docs/TECH52394
Methodology for performing Dissimilar System Restore (DSR) for UNIX/LINUX servers
http://www.symantec.com/docs/TECH62678
Restoring a BMR client image to alternate hardware while the original server is online.
http://www.symantec.com/docs/TECH87329
Performing Physical to Virtual (manual P2V) restores using BMR
http://www.symantec.com/docs/TECH211500
BMR and cluster node restores
http://www.symantec.com/docs/HOWTO84852