Requirements for Bare Metal Restore (BMR) Boot Servers

Details:

For Bare Metal restore (BMR) Boot Servers the following are the requirements:

1. The Boot Server must be of the same OS as the clients that are being recovered. The Master and Boot Server can reside on the same server without issue. You can have multiple Boot Servers of the same OS registered to the Master Server.

2. The Boot Server can only support clients at the same OS release 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 Boot Server can support all 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 Note 323877.

Windows 2003 Boot Server can do all supported Windows client versions (Windows 200, XP, 2003). It is considered the highest OS release version. A Windows 2000 Boot Server can only support Windows 2000 clients. A Windows XP server can not be a BMR Boot Server.

A Windows 2003 64-bit Boot Server can support 64 and 32 bit clients. This requires NetBackup patch 6.5.4 and later. A Windows 2003 32-bit Boot Server at NetBackup release 6.5.4 and later will also support both 32 and 64 bit Windows clients. Windows Boot Servers at patch release 6.5.3 and earlier are only supported on 32 bit OS releases and only support 32 bit clients.

Red Hat Linux Version 5 can support Red Hat Versions 4 and 3 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.

4. Solaris clients can only network boot to a Solaris Boot Server on the same sub-net. All other clients do not have this restriction.

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. However, when using such media, 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).

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.

Related Documents:

http://support.veritas.com/docs/322801

http://support.veritas.com/docs/323877

http://support.veritas.com/docs/329993

Products Applied:
NetBackup Enterprise Server 6.0, 6.0 MP4, 6.0 MP5, 6.0 MP6, 6.0 MP7, 6.5, 6.5.1, 6.5.2, 6.5.3, 6.5.3 .1, 6.5.4
NetBackup with the BMR option 6.0, 6.0 MP4, 6.0 MP5, 6.0 MP6, 6.0 MP7, 6.5, 6.5.1, 6.5.2, 6.5.3, 6.5.3 .1, 6.5.4

Last Updated: August 18 2009 11:36 PM GMT
Expires on: 08-18-2010

Subscribe to receive critical updates about this document

Subjects:
AIX
   Application: Installation
HP-UX
   Application: Configuration, Installation
Linux
   Applications: Configuration, Installation
NetBackup Enterprise Server
   Application: Configuration, Installation
   Nbu Add-Ons And Options: Bare Metal Restore
   Options: Bare Metal Restore
NetBackup with the BMR option
   Application Configuration: Installation
   Configuration: Server
   Installation: Product
Solaris
   Application: Configuration, Installation
Windows 2000
   Information Development: Configuring, Installing
Windows Server 2003
   Information Development: Configuring, Installing

Languages:
English (US)

Operating Systems:
Windows 2000

Advanced Server, Server

AIX

5.1, 5.2, 5.3

HP-UX

11.0., 11.11

Solaris

10, 8.0, 9.0

Linux

RHEL 3.0 (ES), RHEL 4.0, RHEL 5, SLES 8, SLES 9

Windows Server 2003

Enterprise (x64), Enterprise Server, Standard Server, Standard Server(x64)

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.