NetBackup AdminGuide BMR

NetBackup_AdminGuide_BMR.
book Page 1 Thursday, May 24, 2007 1:02 PM
Veritas NetBackup™
Bare Metal Restore™
Administrator’s Guide
UNIX, Windows, and Linux
Release 6.5
12308286
NetBackup_AdminGuide_BMR.book Page 2 Thursday, May 24, 2007 1:02 PM
Veritas NetBackup Bare Metal Restore

Administrator’s Guide
Copyright © 2007 Symantec Corporation. All rights reserved.
NetBackup 6.5
Symantec, the Symantec logo, NetBackup, and Bare Metal Restore are trademarks or
registered trademarks of Symantec Corporation or its affiliates in the U.S. and other
countries. Other names may be trademarks of their respective owners.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-
Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights
reserved.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON
INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be “commercial computer

software” and “commercial computer software documentation” as defined in FAR
Sections 12.212 and DFARS Section 227.7202.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com
Printed in the United States of America.

Third-party legal notices
Third-party software may be recommended, distributed, embedded, or bundled

with this Veritas product. Such third-party software is licensed separately by its
copyright holder. All third-party copyrights associated with this product are
listed in the accompanying release notes.
Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide
for license installation instructions.
Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone
or email support. Use the Knowledge Base search feature to access resources
such as TechNotes, product alerts, software downloads, hardware compatibility
lists, and our customer email notification service.
Contents
Chapter 1 Introducing Bare Metal Restore

How BMR Works ..................................................................................................11
What's new in NetBackup BMR 6.5 ...................................................................12
Bare Metal Restore Management window .......................................................13
Terminology .........................................................................................................13
Chapter 2 Installing Bare Metal Restore

Before installing BMR .........................................................................................15
Identifying the systems to protect ............................................................16
Cluster environments ..................................................................................16
UNIX and Linux systems ....................................................................................16
BMR master server on UNIX and Linux systems ....................................16
Installation prerequisites for UNIX and Linux systems ................16
Installing the BMR master server on a UNIX or Linux system .....17
Uninstalling the BMR master server from a UNIX or Linux system 18
BMR boot server on UNIX and Linux systems .........................................20
Boot server installation prerequisites for UNIX and Linux systems 20
BMR boot server in a UNIX cluster ...................................................22
Installing a BMR boot server on a UNIX or Linux system .............23
Uninstalling a BMR boot server from a UNIX or Linux system ....24
BMR client software on UNIX and Linux systems ..................................25
Microsoft Windows systems ..............................................................................26
BMR master server on Windows systems ................................................26
Licensing prerequisites for Windows systems ................................26
Licensing the BMR master server on a Windows system ..............27
Uninstalling the BMR master server from a Windows system .....28
BMR boot server on Windows systems .....................................................30
Boot server installation prerequisites for Windows systems .......30
BMR boot server in a Windows cluster .............................................30
Installing a BMR boot server on a Windows system ......................31
Uninstalling a BMR boot server from a Windows system .............36
BMR client software on Windows systems ..............................................37
Upgrading and migrating from older BMR versions ......................................38
Steps for migrating to NetBackup BMR 6.5 .............................................38
Stopping and starting the BMR 4.7 server daemon ........................39
Converting external procedures ................................................................ 40
Modify the external procedure scripts ............................................. 40
Adding external procedures to the BMR database ......................... 41
Decommissioning BMR 4.7 ......................................................................... 41
Uninstalling BMR 4.7 clients ............................................................. 42
Chapter 3 Monitoring Bare Metal Restore activity

Monitoring backup jobs ...................................................................................... 43
Monitoring BMR restore tasks ........................................................................... 44
Viewing BMR logs ................................................................................................ 46
BMR logging originator IDs ....................................................................... 47
Configuring and using logging .................................................................. 48
Restore logs .................................................................................................. 49
Chapter 4 Protecting clients

Back up the client ................................................................................................ 51
Configuring policies to back up BMR clients ........................................... 52
Perform complete backups ......................................................................... 53
Perform a full backup after a restore ....................................................... 53
Ensure successful backups ......................................................................... 54
Save custom files ......................................................................................... 54
Monitor backups .......................................................................................... 55
Use the ALL_LOCAL_DRIVES directive ................................................... 55
Use the same client name in multiple policies ........................................ 55
Solaris Zone support ................................................................................... 55
Configure NetBackup properties ....................................................................... 57
Chapter 5 Setting up restore environments

Install boot server software ............................................................................... 59
Create shared resource trees ............................................................................. 60
Add client resources ............................................................................................ 60
Create boot media ................................................................................................ 61
Verify the protection ........................................................................................... 61
Chapter 6 Restoring clients

Restore process overview ................................................................................... 64
Preparing to restore a client .............................................................................. 66
Prepare to Restore Client dialog box ........................................................ 67
Understanding BMR disk recovery behavior .................................. 69
Restoring clients .................................................................................................. 72
Restoring BMR clients using network boot ............................................. 73
AIX network boot .................................................................................73
HP-UX network boot ............................................................................74
Linux network boot ..............................................................................75
Solaris network boot ............................................................................76
Windows network boot .......................................................................77
Restoring BMR clients using media boot .................................................77
AIX media boot .....................................................................................77
HP-UX media boot ................................................................................78
Linux media boot ..................................................................................79
Solaris media boot ................................................................................80
Windows media boot ...........................................................................80
Restoring to a specific point in time .................................................................81
Understanding the point in time restore process ...................................81
When to use point in time restore .............................................................82
Creating a point in time restore configuration .......................................82
Restoring to dissimilar disks ..............................................................................83
Understanding the dissimilar disk restore process ................................83
When to use dissimilar disk restore ..........................................................84
Restoring to dissimilar disks ......................................................................84
Creating a restore configuration for DDR ........................................84
Restoring to dissimilar disks ..............................................................85
Restoring to a dissimilar system .......................................................................86
When to use dissimilar system restore ....................................................86
Restoring to a dissimilar system ...............................................................87
Discovering a configuration ...............................................................88
Creating an editable DSR configuration ...........................................88
Adding NIC and MSD drivers .............................................................88
Changing network interfaces .............................................................89
Mapping disks .......................................................................................89
Creating boot media .............................................................................89
Restoring the client .............................................................................90
First logon .............................................................................................90
Restoring NetBackup media servers .................................................................90
Configuring an alternate media server ....................................................91
Configuring automatic media server failover .................................91
Overriding the original media server manually ..............................92
Restoring the media server ........................................................................92
Restoring BMR boot servers ...............................................................................93
Using external procedures .................................................................................93
External procedure points and names ......................................................94
Client-specific external procedure names .......................................95
Operating system specific external procedures names .................95
Managing external procedures ..................................................................95
Running external procedures .................................................................... 96
External procedure data transfer .............................................................. 96
Interaction with external procedures ....................................................... 97
External procedure logging ........................................................................ 97
External procedure operational states ..................................................... 98
External procedure exit codes ................................................................... 99
External procedure error handling ........................................................... 99
External procedure environment variables ........................................... 100
UNIX and Linux environment variables ........................................100
HP-UX environment variables .........................................................101
Solaris environment variables .........................................................102
Windows environment variables .................................................... 102
Storage area network support ......................................................................... 103
SANs and dissimilar disk restores ..........................................................103
SANs and dissimilar system restores ..................................................... 103
Multiple network interface support ............................................................... 104
Client configuration using gateways ...................................................... 104
Port usage during restores ...............................................................................106
Chapter 7 Managing shared resource trees

Shared resource tree overview ........................................................................ 107
Shared resource trees view ..............................................................................109
Creating a shared resource tree ...................................................................... 111
Creating an SRT for UNIX or Linux ........................................................ 112
Creating an AIX SRT .......................................................................... 113
Creating an HP-UX SRT .................................................................... 114
Creating a Solaris SRT ...................................................................... 116
Creating a Linux SRT ........................................................................ 118
Creating an SRT for Windows ................................................................. 121
Adding software in a shared resource tree .................................................... 121
Adding software to a UNIX or Linux SRT .............................................. 122
Adding NetBackup maintenance packs .......................................... 123
Adding Veritas Volume Manager and Veritas File System ......... 124
Adding Veritas Security Services .................................................... 125
Adding other software ...................................................................... 125
Patches, packages, and Solaris SRTs .............................................. 126
Installing device drivers into Linux SRTs ......................................126
Adding software to a Windows SRT ....................................................... 126
Using a shared resource tree exclusively ...................................................... 127
Copying a shared resource tree ....................................................................... 129
Copying an SRT on UNIX and Linux ....................................................... 129
Copying an SRT on Windows ................................................................... 130
Repairing a damaged shared resource tree ................................................... 130
Breaking a stale shared resource tree lock ....................................................132
Deleting a shared resource tree .......................................................................133
Deleting an SRT on UNIX and Linux .......................................................133
Deleting an SRT on Windows ...................................................................134
Chapter 8 Managing boot media

Boot media overview .........................................................................................135
About writing a CD or DVD ..............................................................................136
Creating boot media for UNIX and Linux .......................................................137
Creating boot media for AIX .....................................................................138
Creating boot media for HP-UX ...............................................................138
Creating boot media for Linux .................................................................139
Creating boot media for Solaris ...............................................................139
Creating boot media for Windows ...................................................................139
Chapter 9 Managing Windows driver packages

Packages overview .............................................................................................141
Packages view .....................................................................................................142
Adding a Windows driver package ..................................................................143
Finding the correct driver ........................................................................143
Deleting a Windows driver package ................................................................144
Chapter 10 Managing clients and configurations

Client configuration overview .........................................................................145
Bare Metal Restore Clients view ......................................................................146
Discovered Configurations view ......................................................................148
Copying a configuration ...................................................................................150
New configuration dialog box ..................................................................150
Discovering a configuration .............................................................................152
Prepare to Discover dialog box ................................................................152
Modifying a configuration ................................................................................155
Deleting a configuration ...................................................................................156
Deleting a client .................................................................................................156
Change Configuration dialog box ...................................................................157
Configuration summary ............................................................................158
Devices and Drivers ...................................................................................160
Discovered Windows signed driver .................................................161
Hosts ............................................................................................................163
Network interfaces ....................................................................................165
Importing and mapping interfaces .................................................166
Changing interfaces manually .........................................................167
UNIX and Linux boot interface ........................................................168
10
Network routes ........................................................................................... 169
Volumes ............................................................................ 171
Mapping and unmapping volumes .................................................. 172
Understanding the views .................................................................. 174
Chapter 11 Managing boot servers

Boot server requirements ................................................................................. 179
General boot server requirements ..........................................................179
AIX boot server requirements ................................................................. 180
HP-UX boot server requirements ............................................................ 180
Linux boot server requirements .............................................................. 180
Solaris boot server requirements ............................................................ 180
Windows boot server requirements ........................................................ 181
Boot servers view ............................................................................................... 181
Removing a boot server .................................................................................... 182
Chapter 12 Troubleshooting
Problems booting from CD or DVD ................................................................. 183
Long restore times ............................................................................................. 184
Legacy restore fails on Windows client with multiple identical NICs ....... 184
Networking problems at DOS phase during legacy restore ........................ 185
DSR troubleshooting ......................................................................................... 186
Solaris media boot network parameters issue .............................................. 187
To recover from deleting a client accidentally ............................................. 187
Appendix A Legacy Windows restore procedures

Creating a legacy shared resource tree ..........................................................190
Creating legacy boot media ..............................................................................190
Creating a legacy boot CD ......................................................................... 190
Creating a legacy boot floppy .................................................................. 191
Rewriting an archived boot floppy ..........................................................192
Archived Boot Floppies view ............................................................................ 192
Restoring a system with legacy procedures .................................................. 194
Booting the legacy restore media ............................................................ 194
Entering client information ............................................................. 194
Verifying the boot disk and saving a vendor partition ................ 195
BMR Restore Utility ........................................................................... 197
Restoring to dissimilar disks for Windows clients ............................... 197
Bootable Windows drivers ........................................................................ 198
Index 199
Chapter 1
Introducing Bare Metal
Restore
Bare Metal Restore (BMR) is the Server Recovery option of NetBackup. BMR
automates and streamlines the server recovery process, making it unnecessary
to manually reinstall operating systems or configure hardware. With simple
commands, complete server restores can be accomplished in a fraction of the
time without extensive training or tedious administration.
How BMR Works

Bare Metal Restore works with normal NetBackup backups. Clients are backed
up to NetBackup servers as always. However, an additional procedure
automatically runs before every scheduled backup to record the state of the
machine configuration, including disk layouts and TCP/IP configuration. BMR
automatically captures and records any changes to a machine’s configuration at
the next scheduled backup.
BMR software recovers a server easily and automatically. The user issues a
“Prepare to Restore” command from the BMR node in the NBU Administration
Console, or from a command line on the NetBackup Master Server.
The following are standard features of Bare Metal Restore:
■ Support of Windows, Solaris, AIX, HP-UX, and Linux platforms
■ Dissimilar System Restore for Windows. This integrated feature enables
recovery to target Windows systems with completely different hardware
configurations. These differences can be network interface adapters, mass
storage devices, video adapters, motherboards, and CPUs. This feature also
supports migration to systems from a different hardware vendor.
■ Point-in-Time Restore. Restore systems back to the point of the last
successful backup—full or incremental—or to previous backup images.
12 Introducing Bare Metal Restore
What's new in NetBackup BMR 6.5
■ External Procedures. Insert custom scripts within the restore process to

help automate operations such as database recovery or application recovery.
■ Machine Configuration Recovery. Automatically record and update disk
configuration and TCP/IP settings every scheduled backup. Recovery is
ensured to the precise prefailure state of all system configurations.
■ Rapid-Fire Recovery. Execute multiple server restores in parallel to
accomplish mass recovery.
The BMR master server must be installed and licensed so that clients can be
protected. For procedures, see:
■ “Installing Bare Metal Restore” on page 15
For information about how to protect clients, see:
■ “Protecting clients” on page 51
After clients are protected, you can set up the restore environment necessary to
restore them:
■ “Setting up restore environments” on page 59
You can restore clients by using the procedures documented in the following:
■ “Restoring clients” on page 63

Related Topics
■ “What's new in NetBackup BMR 6.5” on page 12
■ “Bare Metal Restore Management window” on page 13
■ “Terminology” on page 13
What's new in NetBackup BMR 6.5

NetBackup BMR 6.5 includes the following set of new features:
■ Windows Fast Restores. BMR 6.5 allows restoration of Windows system in as
little as 15 minutes. The older DOS-based boot infrastructure is retained in
this release to support the few systems that do not meet the requirements to
use the Fast Restore mechanism. For information on the requirements for
the new Fast Restore process, refer to the NBU 6.5 Release Notes.
■ Windows Network Booting. Windows Boot Servers now install the network
services that are required to support Network booting of PC hardware. When
you perform a Prepare To Restore operation on a Windows system, the Boot
Server will automatically be configured to boot a fully automated Fast
Restore image.
Introducing Bare Metal Restore 13

Bare Metal Restore Management window
■ Platform proliferations. BMR now supports the following OS versions:

Solaris 10, AIX 5.3, Red Hat Linux 4, and SUSE 9.
Bare Metal Restore Management window

The Bare Metal Restore Management view of the NetBackup Administration
Console shows the following: the protected clients, the restore environment that
rebuild protected clients, and the restore tasks. Use the Refresh option to update
the details pane with new information retrieved from the master server. If an
item is selected, only that item is updated.
Figure 1-1 Bare Metal Restore management window
Terminology
The following terminology is used in Bare Metal Restore.

boot server
14 Introducing Bare Metal Restore

Terminology
A server that contains the resources to boot a client, to rebuild the client system, and to
begin a restore or a discovery.
client configuration
A collection of information about the system. This information includes the following: the
number of disk drives, volume and file system information, number and type of network
adapters, network properties, drivers, and other system software components. Most BMR
operations are performed on configurations; a configuration is the template used to rebuild
a protected system.
discovery boot
A non-intrusive boot that collects device and disk layout information.
dissimilar disk restore (DDR)
The capability to restore to a machine that has a different disk configuration than the
original machine.
dissimilar system restore (DSR)
The capability to restore a machine into a complete different hardware (Windows only).
media boot
The process of booting a client using a CD or a DVD that contains the shared resource tree.
prepare to discover
Operation that runs on the master server and prepares all the resources necessary to do a
discovery boot of a client.
prepare to restore
Operation that runs on the master server and prepares all the resources necessary to
restore the client.
protection domain
A logical grouping of Bare Metal Restore servers and clients that includes the following:
one BMR master server, one or more BMR boot servers, and one or more protected clients.
restore configuration
The client configuration that is used to restore a client. You may have to modify the restore
configuration so you can restore to dissimilar disks or to a different system.
shared resource tree (SRT)
A source of system resources, including the means to rebuild the client system and restore
all system files.
Chapter 2
Installing Bare Metal
Restore
Bare Metal Restore includes the following software components:
■ A master server that controls the operation of BMR.
■ Boot server software that manages and provides the resources that are used
to rebuild systems.
■ Client software that is installed when the NetBackup client software is
installed. No special installation or configuration is required.
This chapter contains instructions for installing and for uninstalling BMR and
information about how to migrate from previous BMR releases.
■ “Before installing BMR” on page 15
■ “UNIX and Linux systems” on page 16
■ “Microsoft Windows systems” on page 26
■ “Upgrading and migrating from older BMR versions” on page 38
Before installing BMR

Before installing BMR software, read the NetBackup Release Notes, which
contains information about dependencies, limitations, and operating system
installation prerequisites for BMR.
Also, you need to do the following: identify the systems to protect, determine
shared resource tree requirements, select boot servers, and, if applicable,
identify your cluster environment.
16 Installing Bare Metal Restore

UNIX and Linux systems
Identifying the systems to protect

You can include the systems that run specific levels of the AIX, HP-UX, Solaris,
Linux, or Windows operating systems as clients in your BMR installation. A BMR
client can be a server for other applications or processes.
For information about supported systems, see Supported Platforms and
Peripherals > Other NetBackup Compatibility Lists > NetBackup Bare Metal
Restore in the NetBackup Release Notes.
Cluster environments
For information about supported cluster environments, see the following in the
NetBackup Release Notes: Supported Platforms and Peripherals > Other
NetBackup Compatibility Lists > NetBackup Bare Metal Restore.

For information about how to install the BMR components, see the following:
■ “BMR master server on UNIX and Linux systems” on page 16
■ “BMR boot server on UNIX and Linux systems” on page 20
■ “BMR client software on UNIX and Linux systems” on page 25
BMR master server on UNIX and Linux systems

To install the Bare Metal Restore master server, see the following instructions.
Install the BMR master server before you install BMR boot servers.
After you install and license the BMR master server and configure NetBackup so
that back ups can occur, you can protect clients.
■ “Installation prerequisites for UNIX and Linux systems” on page 16

■ “Installing the BMR master server on a UNIX or Linux system” on page 17
■ “Uninstalling the BMR master server from a UNIX or Linux system” on
page 18
Installation prerequisites for UNIX and Linux systems

The following are installation prerequisites:
■ Install the BMR master server on the same system as the NetBackup master
server in your environment. Install the same version of BMR as NetBackup.
Do not install the BMR master server on a NetBackup media server or on a
NetBackup client.
Installing Bare Metal Restore 17

■ Install the NetBackup master server before the BMR master server. For
instructions on how to install NetBackup, see the NetBackup Installation
Guide for UNIX and Linux.
■ You must have a valid BMR license key.
■ For information about operating system installation prerequisites for BMR,
see the NetBackup Release Notes.
■ The compat-libstdc++ library is required on RedHat Linux 3.0 systems.
Refer to your Linux distribution documentation to locate this library.
■ If a BMR main server daemon (bmrd) from BMR 4.7 is running on the
system, stop it before you install the new BMR master server. After you
install the new BMR master server, you can restart the BMR 4.7 daemon.
For procedures, see “Stopping and starting the BMR 4.7 server daemon” on
page 39.
Installing the BMR master server on a UNIX or Linux system

Use this procedure to install the BMR master server on a UNIX or Linux system.
In a cluster environment, install and run the BMR master server on all systems
in the cluster where the NetBackup master server is installed.
To install the BMR master server on a UNIX or Linux system
Note: If you install BMR in a cluster environment, freeze the active node before
you begin the installation so that migrations do not occur during installation.
For information about how to freeze a service group, see the NetBackup High
Availability Administrator’s Guide.
1 Log in as the root user on the system where the NetBackup master server is
installed.
2 Insert the CD that contains the BMR software into the CD-ROM drive.
3 Change the working directory to the CD-ROM directory.
cd /cd_rom_directory
Where cd_rom_directory is the path to the directory where you can access
the CD-ROM. On some platforms, you may need to mount this directory. For
instructions on how to mount the directory, see the NetBackup Installation
4 Enter the following command:
./install
5 Select the NetBackup Add-On Product Software option.


6 In the menu of NetBackup product options that appears, select NetBackup

Bare Metal Restore.
7 Enter q to quit the menu.
8 In the message that asks if the list is correct, click y.
The installation process begins.
9 When installation completes, the Installation Options menu appears. Enter
q to quit the menu.
10 In a cluster environment, complete step 1 through step 9 for each node
where a NetBackup master server is installed.
Note: If you install BMR in a cluster environment, unfreeze the active node after
the installation completes. For information about how to unfreeze a service
group, see the NetBackup High Availability Administrator’s Guide.
Note: The BMR master server product releases a patch whenever the NetBackup
server releases a patch. If you install BMR for the first time on a NetBackup
server that has already been patched, the BMR daemon does not start. Instead,
install the matching BMR patch first, then start the BMR daemon.
Uninstalling the BMR master server from a UNIX or Linux

system
The following instructions describe how to remove the BMR master server
permanently from a UNIX system without uninstalling NetBackup. These
procedures remove BMR completely, including the BMR database and log files.
Before you uninstall BMR, delete all BMR-specific items from NetBackup such as
client configurations, SRTs, archived boot floppies, and so on. Although all BMR
program components are removed when BMR is uninstalled, the configuration
items that relate to NetBackup are not.
All BMR components and configuration information are removed when you use
one of the following procedures:
■ To remove the BMR master server from a Solaris system
■ To remove the BMR master server from a non-Solaris system

To remove the BMR master server from a Solaris system
Note: If you remove BMR in a cluster environment, freeze the active node before
you begin so that migrations do not occur during the removal process. For
information about how to freeze a service group, see the NetBackup High
1 Log in as root to the system where the BMR master server is installed.
2 Do one of the following:
■ If you intend to uninstall the BMR master server for a version of
NetBackup earlier than 6.5, enter the following command to uninstall:
pkgrm VRTSnbbmr
Do you want to remove this package?
■ If you intend to uninstall the BMR master server for NetBackup 6.5,
enter the following command to uninstall:
pkgrm SYMCnbbmr
3 In the following message that appears, enter y to remove the BMR master
server:
4 If a message about superuser permissions appears that asks if you want to

continue, enter y.
Messages that show the progress of the removal process appear.
5 To remove the BMR master server completely and not upgrade to a newer
version, enter n in the following message:
Are you doing this pkgrm as a step in an upgrade process?
[y,n,?,q]
6 In the messages that ask if you want to remove BMR files, enter y in each
prompt to remove the BMR files.
7 In a cluster environment, complete step 1 through step 6 for each node
where the BMR master server is installed.
Note: In a cluster environment, unfreeze the active node after removing BMR
from all systems. For information about how to unfreeze a service group, see the
NetBackup High Availability Administrator’s Guide.
To remove the BMR master server from a non-Solaris system
you begin so that migrations do not occur during the removal process. For
information about how to freeze a service group, see the NetBackup High
1 Log in as root to the system where the BMR master server is installed.
2 Run the following command:
/usr/openv/netbackup/bin/install_bmr -d
3 In a cluster environment, complete the previous steps for each node where
BMR is installed.
Note: In a cluster environment, unfreeze the active node after removing BMR
from all systems. For information about how to unfreeze a service group, see the
BMR boot server on UNIX and Linux systems

To install boot server software, see the following tasks and related topics:
■ “Boot server installation prerequisites for UNIX and Linux systems” on
page 20
■ “BMR boot server in a UNIX cluster” on page 22
■ “Installing a BMR boot server on a UNIX or Linux system” on page 23
■ “Uninstalling a BMR boot server from a UNIX or Linux system” on page 24
■ “Boot server requirements” on page 179
Boot server installation prerequisites for UNIX and Linux

systems
The following are the BMR boot server installation prerequisites for UNIX and
Linux systems.
All systems
■ Install NetBackup master server, NetBackup media server, or NetBackup
client software on the system where the boot server software is installed.
Install it before the boot server software is installed. To install the
NetBackup software, see the NetBackup Installation Guide for UNIX and
Linux.

■ Maintain the same version of BMR on the BMR master and boot servers that
are installed on the same system.
■ Install and configure the BMR master server for the environment before you
install and configure BMR boot servers.
UNIX systems
■ The tftp and the bootp services must be available. On some operating
systems, these services are commented out of the /etc/inetd.conf file.
They must be uncommented and inetd needs to be refreshed for the BMR
boot server to function.
■ NFS services are required (unless the boot server is used only to create local
SRTs for media boot). NFS server services are required to support a network
boot of BMR clients. NFS client and server services are required to copy
SRTs between boot servers. No /etc/exports configuration is required;
Bare Metal Restore adds and removes specific export permissions as
required.
Look for the nfsd process in the process table. If it is not present, make
sure the NFS server is installed and configured. (Solaris automatically
starts the NFS server if it is installed normally.)
Red Hat Linux systems

Install the following RPM packages (unless already installed):
■ compat-libstdc++
■ tftp-server
■ dhcp
Enable the tftp service by doing the following:
1 Edit the /etc/xinetd.d/tftp file and change disable = yes to

disable = no.
2 Start the service by running the following command:
/etc/init.d/xinetd restart
Create an /etc/dhcpd.conf file and configure it to define the networks it
serves. You do not have to define host information; hosts are added and removed
as needed by the BMR software. The following is an example configuration:
log-facility local7;
ddns-update-style none;
ignore unknown-clients;
subnet 10.10.5.0 netmask 255.255.255.0 {
default-lease-time 600;
max-lease-time 7200;
option domain-name "example.com";
option broadcast-address 10.10.5.255;
option domain-name-servers 10.10.1.4,10.88.24.5;
option routers 10.10.5.1;
To verify the /etc/dhcpd.conf file syntax, restart the daemon and ensure it
starts successfully by running:
/etc/init.d/dhcpd restart
SuSE Linux systems

Install the following RPM packages (unless already installed):
■ nfs-utils
■ dhcp-base
■ dhcp-server
■ inetd
■ tftp
Enable the tftp service by doing the following:
1 Edit the /etc/inetd.conf file and uncomment the tftp line.
2 Start the service by running the following command:
/etc/init.d/inetd restart
Modify the /etc/dhcpd.conf file to define the networks it serves. You do not
have to define host information; hosts are added and removed as needed by the
Bare Metal Restore software. The following is an example configuration:
log-facility local7;
ddns-update-style none;
ignore unknown-clients;
subnet 10.10.5.0 netmask 255.255.255.0 {
default-lease-time 600;
max-lease-time 7200;
option domain-name "example.com";
option broadcast-address 10.10.5.255;
option domain-name-servers 10.10.1.4,10.88.24.5;
option routers 10.10.5.1;
To verify the /etc/dhcpd.conf file syntax, restart the daemon and ensure it
starts successfully by running:
/etc/init.d/dhcpd restart
BMR boot server in a UNIX cluster

For information about the systems on which BMR boot servers can be clustered,
see the following in the NetBackup Release Notes: Supported Platforms and
Restore .

The following are general instructions for installing and using a BMR boot
server in a clustered environment.
1 In the clustering application, set up a virtual IP address on the nodes that
provides the BMR boot server functionality.
2 Install the NetBackup client software on each node.
3 On each node, configure the NetBackup client name to be the name that
resolves to the virtual IP address. Use that name for the last CLIENT_NAME
entry in the bp.conf file on the system.
4 Install the BMR boot server software on each node. Switch the virtual
address to each node before you install the boot server software.
5 Create a cluster application resource that calls the start and stop scripts for
the boot server daemon:
/usr/openv/netbackup/bin/rc.bmrbd start
/usr/openv/netbackup/bin/rc.bmrbd stop
6 When you create SRTs, choose a location on a file system on the shared disk.
7 If a boot server fails over and it has restore tasks that are pending, perform a
new prepare-to-restore operation for each pending restore task.
Installing a BMR boot server on a UNIX or Linux system

Use this procedure to install a BMR boot server on a UNIX or Linux system.
Note: This procedure registers the boot server with the BMR master server using
the last CLIENT_NAME entry in the /usr/openv/netbackup/bp.conf file on
the boot server. That name must be resolvable to an IP address. The IP address
must be the IP address of one of the network interfaces (except for the loop back)
address, on the boot server. If the bp.conf file does not have a CLIENT_NAME
entry or if it does not meet these criteria, do the following: add an entry or fix
the bp.conf file before you install the boot server. If you do not follow these
guidelines, the boot server does not function.
To install a BMR boot server on a UNIX or Linux system

1 Log in as the root user.
2 Insert the CD that contains the BMR boot server software into the CD-ROM
drive.
3 Change the working directory to the CD-ROM directory.
cd /cd_rom_directory
Where cd_rom_directory is the path to the directory where you can access
the CD-ROM. On some platforms, you may need to mount this directory. For

instructions on how to mount the directory, see the NetBackup Installation

./install
5 Select NetBackup Add-On Product Software.
6 In the menu of NetBackup product options, select NetBackup Bare Metal
Restore Boot Server.

7 Enter q to quit the menu.
8 In the message that asks if the list is correct, click y.
The installation process begins.
9 When the installation completes, the Installation Options menu appears.
Enter q to quit the menu.
Note: The BMR boot server product releases a patch whenever the NetBackup
server releases a patch. If you try to install the BMR boot server for the first time
on a NetBackup server that has already been patched, the BMR daemon does not
start. Instead, install the matching BMR boot server patch first, then start the
BMR boot server daemon.
Uninstalling a BMR boot server from a UNIX or Linux system

The following instructions describe how to remove a BMR boot server
permanently from a UNIX or Linux system. Use one of the following procedures:
■ To remove a BMR boot server from a Solaris system
■ To remove a BMR boot server from a non-Solaris system
To remove a BMR boot server from a Solaris system
Caution: The following procedure removes the BMR boot server software and all
of the shared resource trees on that server.
1 Log in as root to the system where the BMR boot server is installed.
2 Delete all of the SRTs on the boot server by using the bmrsrtadm command.
3 On the NetBackup master server, run the following command to delete the
boot server name from the BMR database:
/usr/openv/netbackup/bin/bmrs -o delete -r bootserver -name
bootservername
4 Do one of the following:


■ If you intend to uninstall the BMR master server for a version of

NetBackup earlier than 6.5, enter the following command to uninstall:
pkgrm VRTSnbbmr
■ If you intend to uninstall the BMR master server for NetBackup 6.5,
enter the following command to uninstall:
pkgrm SYMCnbbmr
5 When the following message appears, click y to remove the BMR boot
server:
6 If a message about superuser permissions appears that asks if you want to

continue, enter y.
Messages that show the progress of the removal process appear.
7 When the following message appears, enter n to remove the BMR boot
server completely and not upgrade to a newer version:
Are you doing this pkgrm as a step in an upgrade process?
[y,n,?,q]
8 In the messages that ask if you want to remove BMR files, enter y to each
prompt.
To remove a BMR boot server from a non-Solaris system

You must log in as root when you run the commands in the following procedure.
1 Log in as the root user.
2 On the BMR boot server, delete all of the SRTs by using the bmrsrtadm
command.
3 On the NetBackup master server, run the following command to delete the
boot server name from the BMR database:
/usr/openv/netbackup/bin/bmrs -o delete -r bootserver -name
bootservername
To see a list of boot server names, run the following command:

/usr/openv/netbackup/bin/bmrs -o list -r bootserver
4 On the BMR boot server, run the following command:

/usr/openv/netbackup/bin/install_bmrboot -d
BMR client software on UNIX and Linux systems

The BMR client software installs automatically when the NetBackup client
software is installed. For information about how to install NetBackup client
software, see the NetBackup Installation Guide for UNIX and Linux.

Microsoft Windows systems
For information on how to install the BMR components, see the following:
■ “BMR master server on Windows systems” on page 26
■ “BMR boot server on Windows systems” on page 30
■ “BMR client software on Windows systems” on page 37
BMR master server on Windows systems

The Bare Metal Restore master server installs on a Windows system when the
NetBackup master server is installed; no separate installation procedure is
required. However, you must enter a license key to use BMR.
■ Your license key may be a single key for the base NetBackup product and all
NetBackup add-ons that you install, including BMR. If you already installed
NetBackup and entered the license key, BMR is already licensed.
■ You may have a separate license key specifically for the BMR option. If so,
you must enter the BMR license key before you can use BMR
See “Licensing the BMR master server on a Windows system” on page 27.
After you license BMR, you must run a wizard to set up the BMR master server.
If you install and run the BMR master server in a cluster environment, you must
do the following: license BMR on all systems in the cluster where NetBackup
master servers are installed.
For information on how to license and configure NetBackup, see the following
tasks and related topics:
■ “Licensing the BMR master server on a Windows system” on page 27
■ “Uninstalling the BMR master server from a Windows system” on page 28
■ “Licensing prerequisites for Windows systems” on page 26
After you license the BMR master server and configure NetBackup so that
backups can occur, you can protect clients.
For more information, see “Protecting clients” on page 51.
Licensing prerequisites for Windows systems

■ The NetBackup master server must be installed and in operation on the
Windows computer.
■ You must have a valid BMR license key.

Licensing the BMR master server on a Windows system
Note: If you license and set up BMR in a cluster environment, freeze the active
node before you begin so that migrations do not occur. For information about
how to freeze a service group, see the NetBackup High Availability System
Administrator’s Guide.
To add the BMR license key

If you install and run the BMR master server in a cluster environment, perform
this procedure on systems where the NetBackup master server is installed.
If the license key for BMR was included in the license key for the base NetBackup
product, you do not have to perform this procedure.
1 On the NetBackup Administration console, click Help > License Keys.
2 In the NetBackup License Keys dialog box, click New.
3 In the Add a new License Key dialog box, enter the BMR license key.
4 Click Add.
5 In the NetBackup License Keys dialog box, click Close.

You do not have to enter any information; the wizard performs the required
steps to set up the master server.
Note: If you license and set up BMR in a cluster environment, unfreeze the active
node after you complete this process. For information on how to unfreeze a
service group, see the clustering section in the NetBackup High Availability
Administrator’s Guide for your cluster software.
Uninstalling the BMR master server from a Windows system

The BMR master server software is not uninstalled. Rather, you deactivate the
BMR master server by deleting the license key from the list of current
NetBackup licenses. When the license key is deleted, BMR is no longer available
for use. You can delete the BMR license key only if BMR was licensed with its
own key, separate from the base NetBackup product license key.
Before you delete the BMR license key from NetBackup, you should remove the
BMR database.

you remove BMR so that migrations do not occur during removal. For
information on how to freeze a service group, see the NetBackup High
To remove the BMR database

If you are running BMR in a cluster environment, perform the following
procedure on the active node.
1 Open a Windows command window.
C:\Program Files\Veritas\NetBackup\bin>bmrsetupmaster -undo
3 In the following prompt, enter y to remove the BMR database.

The current BMR database is about to be deleted. Do you want to
continue? (y/n)
To delete the BMR license key

If you run BMR in a cluster environment, delete the BMR license key on every
system in the cluster with the BMR master server installed.
1 On the NetBackup Administration Console, click Help > License Keys.
2 In the NetBackup License Keys dialog box, select the BMR license key from
the list.
Caution: If BMR was included as part of the base product key and you perform
the following step, you delete your base key. You cannot use NetBackup. If you
do not want to delete the NetBackup license key, do not continue.
3 Click Delete.
The BMR license key is deleted from the Current Licenses dialog box. Bare
Metal Restore Management is no longer appears in the NetBackup
Administration Console.
Note: In a cluster environment, unfreeze the active node after deactivating BMR
from all systems. For information on how to unfreeze a service group, see the
BMR boot server on Windows systems

To install boot server software, see the following tasks and related topics:
■ “Boot server installation prerequisites for Windows systems” on page 30
■ “BMR boot server in a Windows cluster” on page 30
■ “Installing a BMR boot server on a Windows system” on page 31
■ “Uninstalling a BMR boot server from a Windows system” on page 36
Boot server installation prerequisites for Windows systems

■ Install NetBackup master server, NetBackup media server, or NetBackup
client software on the system where the boot server software is installed. It
must be installed before the boot server software is installed. To install the
NetBackup software, see the NetBackup Installation Guide for Windows.
■ Maintain the same version of BMR on the BMR master and boot servers that
are installed on the same system.
■ Install and configure the BMR master server for the environment before you
install and configure the BMR boot servers.
■ Disable any PXE and TFTPD services that are running on the system before
you install the Boot Server package.
■ If the Boot Server is to be installed on an Active Directory Server, set the
following two security settings as shown. This allows the legacy (DOS)
restore method to share SRTs with restoring clients:
■ Microsoft network server: Digitally sign communications (always) -
Disabled
■ Microsoft network server: Digitally sign communications (if client
agrees) -- Enabled
BMR boot server in a Windows cluster

For information about the systems where BMR boot servers can be clustered, see
the following in the NetBackup Release Notes: Supported Platforms and
Restore.
The following are general instructions for installing and using a BMR boot
server in a clustered environment.
1 In the clustering application, set up a virtual IP address on the nodes that
provide the BMR boot server functionality.

2 Install the NetBackup client software on each node.

3 On each node, configure the NetBackup client name to be the name that
resolves to the virtual IP address: Start the Backup, Archive, and Restore
interface. Enter that name as the client name in the Specify NetBackup
Machines and Policy Type dialog box. Then make it the current client.
4 Install the BMR boot server software on each node. Switch the virtual
address to each node before you install the boot server software.
5 Create a cluster application resource that calls the start and stop script for
the boot server services:
net start "NetBackup Bare Metal Restore Boot Server"
net stop "NetBackup Bare Metal Restore Boot Server"
6 When you create SRTs, choose a location on a file system on the shared disk.
7 If a boot server fails over with restore tasks to be done, perform a new
prepare-to-restore operation for each pending restore task.
Installing a BMR boot server on a Windows system

The following are the installation options:
■ Local installation: install to the same computer where the installer runs
■ Remote installation: install to a different computer than the one where the
installer runs
To begin installing a boot server, follow the procedures in “To install a BMR boot
server on Windows” on page 31. Those procedures direct you to an additional
procedure for remote installation if necessary.
To install a BMR boot server on Windows

1 Log on as Administrator on the server where you plan to install the BMR
boot server. Or log on to the server from where you plan to push the
installation.
2 Insert the NetBackup installation CD in the drive.
■ On Windows systems with AutoPlay enabled for CD-ROM drives, the
Veritas NetBackup installation browser starts automatically.
■ On Windows systems that have AutoPlay disabled, run Launch.exe
in the top-level directory on the CD.
3 The NetBackup installation browser appears:
4 Click Additional Products in the Main Menu.
5 Click Additional Product Installations.
6 Click BMR Boot Server.
7 In the welcome screen, click Next to continue.
8 In the License screen, select I accept the terms of the license agreement.
Then click Next.

9 In the Install Choice screen, do the following:
■ Select either Install to this computer only or Select from available
computers on the network.
■ Select Typical installation.
■ Click Next to continue.
If you select Select from available computers on the network, go to “To use
the remote installation option” on page 34.

If you selected a typical installation, the Install screen appears.
10 On the Install screen, click Install.

11 After the installation completes, click Finish in the Installation Complete
screen.
12 To exit the NetBackup installation browser, click Exit.

To use the remote installation option

After you select Select from available computers on the network, click Next to
continue. Now you can use the NetBackup Remote Features window to install
the boot server software on a remote computer:
1 In the Destination System window, right-click Windows Destination

Computers and select one of the following from the shortcut menu:
■ Add Remote Computer—to select a computer from a list of computers
in your Microsoft Windows network.
■ Add Remote Computer Manually—to enter the name of a computer.

Depending on your selection, one of the following pop-up windows appears:
2 If you select Add Remote Computer, select a computer from the Available
Systems window and then click Next. If you select Add Remote Computer
Manually, enter the domain and computer in the Manual Remote Computer
Selection window. Then click Next.
The NetBackup Remote Features window refreshes and displays the Remote
Computer Login Credentials window.
3 Enter your user name, password, and domain and then click OK. To add
more remote computers, check the Remember User Name and Password
checkbox.

The NetBackup Remote Features window refreshes, and the remote

machine appears in the Destination Systems window.
4 Click Next.
5 In the Install screen, click Install.
6 After the installation completes, click Finish in the Installation Complete
screen.
7 To exit the NetBackup installation browser, click Exit.
Uninstalling a BMR boot server from a Windows system
Caution: The following procedure removes the BMR boot server software and all
of the shared resource trees on that server.
To remove the shared resource trees from the boot server

1 Log on as Administrator on the boot server.
2 On the Start menu on the Windows BMR boot server, click Programs >
Veritas NetBackup > Bare Metal Restore Boot Server Assistant.
3 In the Bare Metal Restore Boot Server Assistant, click Shared Resource Tree
Administration Wizard.
4 In the Shared Resource Tree Administration wizard welcome screen, click
Next.

5 In the Create or Add Software to a Shared Resource Tree screen, select the
option to delete a shared resource tree and click Next.
6 Follow the prompts to delete a shared resource tree.

7 Repeat until all shared resource trees are removed.
To remove the boot server software

1 On the Windows Start menu, click Settings > Control Panel > Add/Remove
Programs.
2 Select Veritas Bare Metal Restore Boot Server.
3 Click Remove.
4 Follow the prompts to remove the boot server software.
5 In the NetBackup Administration Console, delete the boot server from the
list of available boot servers.
BMR client software on Windows systems

The BMR client software installs automatically when the NetBackup client
software is installed. For information about how to install NetBackup client
software, see the NetBackup Installation Guide for Windows.

Upgrading and migrating from older BMR versions
You can upgrade to NetBackup 6.5 only from NetBackup 6.0. The older
standalone BMR product (BMR 4.7) cannot be directly upgraded to NBU 6.5, but
it can be migrated to NBU 6.5 in a deliberate fashion.
BMR 4.7 clients can operate with NetBackup 6.5 servers. So you can install
NetBackup BMR 6.5 while your 4.7 version of BMR continues to protect your
clients.
To migrate from BMR 4.7, perform the following tasks:
■ “Steps for migrating to NetBackup BMR 6.5” on page 38
■ “Converting external procedures” on page 40
■ “Decommissioning BMR 4.7” on page 41
Steps for migrating to NetBackup BMR 6.5

The following is a high level description of the migration process.
Note: On a system that already hosts a BMR 4.7 master server, file server, or
boot server, you must do the following: stop the BMR 4.7 server daemon (bmrd)
before you install (or uninstall) BMR 6.5 master or boot server software.
For more information on upgrading from BMR 4.7, see “Stopping and
starting the BMR 4.7 server daemon” on page 39.
1 Upgrade the NetBackup master server to NetBackup 6.5. For instructions,
see the NetBackup Installation Guide for UNIX and Linux or the NetBackup
Installation Guide for Windows.
The NetBackup master server must be on a system that supports the BMR
master server. For information about supported systems, dependencies,
limitations, and operating system installation prerequisites for BMR, see
the NetBackup Release Notes.
Your existing BMR environment now works with the NetBackup 6.5 master
server.
2 Upgrade the NetBackup media servers to NetBackup 6.5. For instructions,
see the NetBackup Installation Guide for UNIX and Linux or the NetBackup
Installation Guide for Windows.
Your existing BMR environment now works with the NetBackup 6.5 media
servers.
3 Install and license the BMR 6.5 master server software on the NetBackup 6.5
master server machine.
For instructions, see “Installing Bare Metal Restore” on page 15.

The NetBackup master server must be on a system that supports the BMR
master server. For information about supported systems, dependencies,
limitations, and operating system installation prerequisites for BMR, see
the NetBackup Release Notes.
Your existing BMR environment continues to work.
4 Upgrade the clients to NetBackup 6.5. For instructions, see the NetBackup
Installation Guide for UNIX and Linux or the NetBackup Installation Guide
for Windows.
Because the BMR client is part of the NetBackup client code, no additional
installation is needed for BMR clients. After you upgrade to the NetBackup
6.5 client code, the old BMR 4.7 client code is disabled but is not removed.
5 On the NetBackup 6.5 master server, configure a policy for BMR protection
and back up the clients you want to protect with BMR.
For instructions, see “Protecting clients” on page 51.
The BMR agent on the client runs and saves the client configuration before
the backup starts. You can view the BMR job in the NetBackup
Administration Console Activity Monitor.
If the backup is successful, the client is protected and appears in the Bare
Metal Restore Clients view in the NetBackup Administration Console. To
restore a client, first install a boot server and create a shared resource tree
for that client type.
If the backup fails or the BMR agent on the client fails, the NetBackup BMR
6.5 environment does not protect the client.
6 Set up the restore resources in your NetBackup BMR 6.5 environment.
For more information, see “Setting up restore environments” on page 59.
The NetBackup BMR 6.5 environment restores your clients.
7 Perform test restores onto different hardware. UNIX and Linux must restore
to similar hardware, and Windows can restore to any x86 hardware.
After successful test restores, you can decommission your BMR 4.7
environment.
Stopping and starting the BMR 4.7 server daemon

UNIX and Linux only.
On a system that runs a BMR 4.7 master server, file server, or boot server, do the
following: stop the BMR 4.7 server daemon (bmrd) before you install (or
uninstall) the BMR 6.5 server software. After you install or uninstall the BMR
6.5 server software, you can restart the BMR 4.7 bmrd daemon. For procedures,
see the following:

To stop the bmrd daemon

1 Edit the /etc/inittab file on the BMR 4.7 server and comment out the
line that starts the BMR daemon.
2 Run the following command to refresh initd:
kill -1 1
3 Determine the process ID of the BMR 4.7 bmrd process and then end the
bmrd process.
To start the bmrd daemon

1 Edit the /etc/inittab file and uncomment the line that starts the BMR
daemon.
2 Run the following command to refresh initd:
kill -1 1
Converting external procedures

If you want to use external procedures from your BMR 4.7 environment with
NetBackup BMR 6.5, you must do the following:
■ Modify the external procedure scripts. Commands and environment
variables were changed in BMR 6.5, so you must modify the external
procedure scripts to accommodate the changes.
■ Add the external procedures to the BMR database. BMR 6.5 and later
manages external procedures differently than BMR 4.7. You must add them
to the BMR database so they are available during a restore.
The naming convention for external procedures has not changed.
Modify the external procedure scripts

Changes in BMR 6.5 require that you modify your existing external procedures if
you use them with NetBackup 6.5 and later. The following table summarizes the
changes:
bmrlog The bmrlog command was removed. Use the bmrc command to write a
message or output from a command to the BMR restore log.
For more information, see “External procedure logging” on page 97.
bmrget The bmrget command was removed. Use the bmrc command to
retrieve files from the master server during a restore.
For more information, see “External procedure data transfer” on
page 96.

bmrshell The bmrshell command was renamed bmrShell (case sensitive).

Replace bmrshell with bmrShell in the external procedure scripts.
For more information, see “Interaction with external procedures” on
page 97.
Environment The naming scheme for BMR environment variables changed. Since
variables many environment variables have name changes, you must change
them in your external procedure scripts.
For more information, see “External procedure environment variables”
on page 100.
bmrc command Use the full path to the bmrc command:

path ■ /usr/openv/netbackup/bin on UNIX and Linux clients
■ %SystemDrive%\BMR\NBU\bin on Microsoft Windows clients.
At the firstboot external procedure point, the path to the bmrc
command is install_path\NetBackup\bin on Microsoft
Windows clients.
Adding external procedures to the BMR database

External procedures are no longer stored in the /var/bmr/epdir directory,
they are stored in the BMR database on the master server.
Use the bmrepadm command on the master server to add external procedures to
the BMR database.
For examples, see “Managing external procedures” on page 95.
Decommissioning BMR 4.7

After you migrate to NetBackup BMR 6.5, do the following to uninstall your BMR
4.7 environment:
1 Remove the bmrsavecfg command from the bpstart_notify script on
every client that BMR 4.7. protects.
2 Uninstall the BMR 4.7 client software on every client that BMR 4.7. protects.
For instructions, see “Uninstalling BMR 4.7 clients” on page 42.
3 Uninstall the BMR 4.7 boot and file servers.
For instructions, see Tips and Troubleshooting > Tips > Removing BMR
Servers in the Bare Metal Restore for Veritas NetBackup Administrator’s
Guide for BMR 4.7.
4 Remove the shared resource trees from the BMR 4.7 file servers.
Use operating system commands to remove the SRT directories. If the SRTs
reside in the directories that were deleted when you uninstalled the BMR
file servers, this step is unnecessary.

5 Uninstall the BMR 4.7 main server.

For instructions, see Tips and Troubleshooting > Tips > Removing BMR
Servers in the Bare Metal Restore for Veritas NetBackup Administrator’s
Guide for BMR 4.7.
Uninstalling BMR 4.7 clients

Use one of the following procedures to uninstall the BMR 4.7 clients:
To uninstall a BMR 4.7 client from a Windows system

Use Add/Remove Programs.
To uninstall a BMR 4.7 client from a Solaris system

Use the package remove command:
pkgrm BMRclient
To uninstall a BMR 4.7 client from a UNIX system

On AIX and HP-UX systems, remove the following directories:
/usr/lpp/baremetal
/opt/baremetal
Chapter 3
Monitoring Bare Metal
Restore activity
This chapter includes the following topics.
■ “Monitoring backup jobs” on page 43
■ “Monitoring BMR restore tasks” on page 44
■ “Viewing BMR logs” on page 46
Monitoring backup jobs

You can monitor the jobs that back up the protected clients by using the Jobs tab
in the Activity Monitor of the NetBackup Administration Console.
You can see information about a job by double-clicking the job, which opens the
Job Details dialog box. Two tabs display job information, as follows:
■ The Job Overview tab contains general information about the job.
■ The Detailed Status tab contains detailed information about the job and
about the agent that runs on the client. It collects the client configuration
information and sends it to the BMR master server. On the protected
systems that have uncomplicated configurations (one or a few disks), the
agent only takes a few seconds. The more complex systems that have disk or
volume groups may take a few minutes. Complex storage area network
environments may take up to an hour.
If the Allow Multiple Data Stream attribute is enabled in the backup policy,
NetBackup may divide backups for each client into multiple jobs. Each job backs
up only a part of the backup selection list. The jobs are in separate data streams
and can occur concurrently. For each client, only one of the jobs initiates the
agent that collects the client configuration (normally, the job with the lowest job
ID).
44 Monitoring Bare Metal Restore activity

Monitoring BMR restore tasks
Investigate nonzero status of a backup job and resolve problems so backups

occur and the agent collects and sends the configuration to the master server.

The Tasks view shows the status and resource allocation for the prepare to
restore and prepare to discover operations. Use the Refresh option to update the
details pane with new information retrieved from the master server; if an item is
highlighted, only that item is updated.
Figure 3-2 Bare Metal Restore tasks window
Table 3-1 Actions for the Tasks view
To Do the Following
Display the tasks and operations that Select Bare Metal Restore Management > Tasks.
are allocated
Monitoring Bare Metal Restore activity 45

Table 3-1 Actions for the Tasks view
To Do the Following
Display task properties Right click on a task in the details pane and then select Properties
from the shortcut menu.
Clean up a task Right click on a task in the details pane and then select Clean Up from
the shortcut menu. The resources used by the task are unallocated, the
State is set to Done, and Status is set to 150 (terminated by user). You
can clean up tasks that are in an Active or Waiting state.
Delete a task Right click on a task in the details pane and then select Delete from
the shortcut menu. You can delete tasks that are in a Done state.
The following are the columns in the Task view:
Table 3-2 Tasks view columns
Column Description
Client Name The name of the client.
Configuration The configuration used for the task.
Shared Resource Tree The SRT used for the task.
State The following are the states of restore or discovery tasks:

■ Active. The task is in progress
■ Done. The task completed.
■ Editing. Dissimilar disk restore mapping is occurring.
■ Queued. The task has not been active yet.
■ Waiting. The task was active but is waiting for some user action.
Viewing BMR logs
Table 3-2 Tasks view columns (continued)
Column Description
Operation Displays Ready when the task is Queued; otherwise, shows the following when the
restore is in progress (the State is Active or Waiting):
■ Discovery External Procedure (Active State only). An external procedure is
running during the prediscovery phase.
■ Failed (Done State only). The task failed.
■ Finalizing (Active State only). Completing the task.
■ First Boot External Procedure (Active State only). An external procedure is
running during the firstboot phase.
■ Formatting (Active State only). Formatting the drives.
■ Initializing (Active State only). Booting the client.
■ Mapping (Waiting State only). Mapping required.
■ Mapped (Active State only). Mapping completed and passed validation.
■ Post-restore External Procedure (Active State only). An external procedure is
running during the postrestore phase.
■ Pre-format External Procedure (Active State only). An external procedure is
running during the preformat phase.
■ Pre-restore External Procedure (Active State only). An external procedure is
running during the prerestore phase.
■ Restoring (Active State only). Restoring files.
■ Restore Canceled (Done State only). The user terminated the restore.
■ User Input Requested (Waiting State only). Waiting for user action.
■ Waiting for Reboot.
Status Status codes for the task.
Start Time Date and time the task started.
End Time Date and time the task ended.
Type Restore or Discover.
Viewing BMR logs

You can monitor BMR activity by viewing the messages generated by BMR. BMR
activity log files are stored in the following directories on the master server:
■ /usr/openv/logs directory (UNIX and Linux)
■ install_path\NetBackup\logs folder (Windows).
BMR uses a standardized naming format for log files. The following is an
example log file name:
51216-119-3892578826-050225-0000000000.log

Viewing BMR logs
The following are the components of this example log file name:
■ 51216 is the product ID for NetBackup.
■ 119 is the originator ID of the process that wrote the log (bmrd or bmrdb,
the Bare Metal Restore master or boot server service).
■ 3892578826 is a decimal ID for the host that created this log.
■ 050225 is the date in YYMMDD format.
■ 0000000000 is the rotation number indicating the instance of this log file.
If the file reaches maximum size and a new log file is created for this
originator, the file rotation number will increase by 1.
Three kinds of messages can appear in unified logging files:
■ Application log messages. These include informational, warning, and error
messages.
■ Diagnostic log messages. The amount of information logged depends on the
logging level.
■ Debug log messages. These are primarily for Symantec support and
engineering. The amount of debug information logged depends on the
logging level specified for the NetBackup master server.
BMR logging originator IDs

The following are the originator IDs for the BMR processes that perform
logging:
Originator ID BMR Processes that Use ID
119 bmrd and bmrbd. Bare Metal Restore master and boot server services. The bmrbd boot
server process runs on a BMR boot server.
121 bmrsavecfg. Bare Metal Restore agent that runs on client systems, collects the client
configuration, and saves the client configuration to the master server.
122 bmrc. Bare Metal Restore utility that clients use to communicate with the BMR master
server during a restore. Runs on the restoring client.
123 bmrs. The Bare Metal Restore command line interface for various activities performed
via the GUIs.
124 bmrcreatefloppy.exe (Windows systems only). Bare Metal Restore utility that
creates bootable floppy diskettes used to boot protected Windows clients for a restore.
Runs on a BMR boot server.

Viewing BMR logs
Originator ID BMR Processes that Use ID
125 bmrsrtadm. Bare Metal Restore utility that creates and manages shared resource trees
and creates bootable CD media or DVD media for restores. Runs on a BMR boot server.
126 bmrprep. Bare Metal Restore utility that prepares BMR for a client restore or discovery.
Runs on the master server.
127 bmrsetupmaster and bmrsetupboot. Bare Metal Restore master server and boot
server configuration utilities.
128 Miscellaneous programs and Bare Metal Restore libraries.
129 bmrconfig. Bare Metal Restore utility that modifies a client's configuration.
130 bmrcreatepkg.exe. Bare Metal Restore utility to add Windows drivers, service packs,
and hotfixes to the BMR master server so they can be used in a restore. Runs on
Windows boot servers.
131 bmrrst.exe and bmrmap.exe (Windows systems only). Utilities that restore Windows
Bare Metal Restore clients. Run on the restoring client.
142 bmrepadm. A utility that manages Bare Metal Restore external procedures used during
restores. Runs on the master server.
152 bmrovradm. A utility that manages custom override functions for Bare Metal Restore.
248 bmrlauncher. A utility that prompts for IP information in the new Windows Fast
Restore environment.
Configuring and using logging

The amount of information collected and how long to retain that information is
configured on the NetBackup master server in the Logging properties and
Clean-up properties. For more information, see the following:
■ NetBackup Administrator’s Guide:
■ Configuring Host Properties > Master Server, Media Server, and Client
Host Properties > Logging Properties
■ Configuring Host Properties > Master Server, Media Server, and Client
Host Properties > Clean-up Properties
■ The NetBackup Troubleshooting Guide includes more information about
using and managing logs (Using Logs and Reports > Debug Logs on Servers
> Unified Logging).

Viewing BMR logs
BMR activity log files are a special format that require commands to view and
manage. Three commands manage unified logging and log files:
Command Description
vxlogview Use this command to view the logs created by unified logging.
vxlogmgr Use this command to manage unified logging files (for example, to
move or delete log files).
vxlogcfg Use this command to configure logging settings.
These commands are located in:

■ /usr/openv/netbackup/bin directory (UNIX)
■ install_path\NetBackup\bin folder (Windows).
For more information, see NetBackup Commands manuals.
Restore logs
The BMR restore process writes messages to restore logs on the master server.
The following is the location and naming convention for the log files:
/usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX)
install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)
On UNIX and Linux systems, the messages include external procedure begin and
end messages (begin and end logging is not performed by the BMR restore
process running on Windows systems).
Unlike BMR activity logs, the restore log files are text files.

Viewing BMR logs
Chapter 4
Protecting clients
A client is protected after a NetBackup backup policy that is configured for BMR
protection backs it up. Backups must occur before a client fails and requires a
Bare Metal Restore.
This chapter includes the following topics:
■ “Back up the client” on page 51
■ “Configure NetBackup properties” on page 57
Back up the client

Each protected client must be backed up regularly by at least one policy that
performs a full backup. The policy also can perform cumulative incremental or
differential incremental backups, but a full backup must occur.
The backup saves the files of the computer on a storage device that NetBackup
manages. The backup saves the configuration of the client on the BMR master
server.
After a client is backed up by a policy that is configured for BMR protection, the
client is registered with BMR as a protected client. It then appears in the Bare
Metal Restore Clients view in the NetBackup Administration Console.
Tasks
■ “Configuring policies to back up BMR clients” on page 52
Related topics
■ “Perform complete backups” on page 53
■ “Perform a full backup after a restore” on page 53
■ “Ensure successful backups” on page 54
■ “Save custom files” on page 54
52 Protecting clients
Back up the client
■ “Monitor backups” on page 55
Best practices
■ “Use the ALL_LOCAL_DRIVES directive” on page 55
■ “Use the same client name in multiple policies” on page 55
■ “Solaris Zone support” on page 55
Configuring policies to back up BMR clients

You can use one policy or multiple policies to protect a single client.
The following are the requirements for protecting BMR clients:
■ A policy must be either type MS-Windows-NT (for Windows clients) or
Standard (for UNIX and Linux clients).
■ A policy must have the Collect disaster recovery information for Bare Metal
Restore attribute set.
On NetBackup master servers that are licensed for BMR, the following
attributes set automatically:
■ The Collect disaster recovery information for Bare Metal Restore
attribute: when you create a new MS-Windows-NT or Standard policy.
■ The Collect true image restore information and with move detection
attributes (albeit grayed out): when the Collect disaster recovery
information for Bare Metal Restore attribute is set.
These attributes enable NetBackup to restore only those files present on the
system at the time of the backup. Move detection enables NetBackup to
restore the files correctly that were moved, renamed, or newly installed.
These attributes also ensure that all of the restored files fit in the volumes
and the file systems that BMR created during the recovery.
If Collect disaster recovery information for Bare Metal Restore attribute is
not set, BMR does not protect the client.
User-initiated backups do not provide BMR protection because true image
restore information is not collected during a user-initiated backup.
■ The operating system files must be backed up by a single policy. For
Windows clients, include SYSTEM_STATE in the policy that backs up the
operating system.
Consider the following when you create policies to protect BMR clients:
■ For non-clustered clients, specify ALL_LOCAL_DRIVES is the simplest and
most thorough method to obtain a complete backup. If you back up a client
with database or application files using a NetBackup database agent or
Protecting clients 53
Back up the client
other policy, do the following: use an exclude list to exclude them from the
policy that specifies ALL_LOCAL_DRIVES.
■ For clustered clients, the most effective backup strategy uses multiple
policies. Each node should have its own policy that backs up local file
systems. Shared file systems should be backed up by the additional policies
that back up the node that currently owns the resources.
■ The logical volumes that are not part of the operating system can be backed
up with different policies. However, each logical volume must be backed up
by a single policy.
■ Schedule all policies that back up a single client to run at the same time.
■ NetBackup media servers can be protected as BMR clients. Media servers
that back up to their own storage devices (either SCSI-attached or
SAN-attached) require special procedures for restores. If you understand
these procedures, you can configure NetBackup to minimize the time and
effort that the restores require.
For more information, see “Restoring NetBackup media servers” on
page 90.
For instructions for configuring backup policies, see “Managing backup
policies” in the NetBackup online help or in the the NetBackup Administrator’s
Guide, Volume I.
Perform complete backups

To restore all files on the client, you must back up all of the files on the client. If
you exclude files during the backup, those files are not backed up and therefore
are not restored.
Perform a full backup after a restore

You must perform a full backup of a client immediately after you restore the
client and before any incremental backups occur. If the client fails again after an
incremental backup but before a full backup, BMR cannot restore the client.
You can perform a manual backup of a specific client. The policy must be set to
Active and the Go into effect at attribute must not be set to a future date and
time.
To perform a manual backup

1 In the NetBackup Administration Console, click NetBackup Management >
Policies.
2 Select the policy that backs up the client.
Back up the client
3 On the Actions menu, click Manual Backup.

4 In the Manual Backup dialog box, select the Full schedule and the client that
you want to back up.
5 Click OK to start the backup.
Ensure successful backups

Schedule backups when the risk of an incomplete backup is minimized. If a
client cannot be quiesced during a backup:
■ For UNIX clients, configure NetBackup to retry file backups if a file changes
during the backup attempt.
See “Busy File Properties” in NetBackup Administrator’s Guide, Volume I.
■ For Windows clients, configure NetBackup to use a Windows Open File
Backup option.
See “Windows Open File Backup Properties” in NetBackup Administrator’s
Guide, Volume I.
Examine the NetBackup log files regularly to ensure that any backup errors are
corrected promptly. During backup, network or server errors can occur that
affect the backup.
Save custom files

UNIX and Linux clients only.
Usually, NetBackup restores client files as the last step in the restore process.
You can specify custom files on the client so they are available in the temporary
operating system environment on the client during the restore process.
For example, a specific device driver configuration from a protected client is
required in the temporary operating system. You can specify those device driver
files so they are included in the restore environment.
Custom files are saved as part of the client’s configuration. Specify the custom
files in the following text file on the client:
/usr/openv/netbackup/baremetal/client/data/ClientCustomFiles
Specify one custom file per line, using the full pathname to the file. Use a pound
sign (#) as the first character of comment lines.
After custom files are saved (when the client is backed up), they are copied to the
SRT. They are available during the restore when you enable the SRT for
exclusive use. To do so, see:
■ “Using a shared resource tree exclusively” on page 127

When you specify a custom file, it does not remove it from backups. Custom files
are also backed up by NetBackup and then restored when NetBackup restores
Back up the client
the client files. (They are backed up and restored if the files or their directories
are included in the backup directives of the policy).
Monitor backups
You can use the NetBackup Activity Monitor to monitor the backup jobs. Details
about the backup job include information about the agent that saves the
protected client’s configuration.
Related Topics
■ “Monitoring backup jobs” on page 43
Use the ALL_LOCAL_DRIVES directive

To ensure complete system recovery, use the ALL_LOCAL_DRIVES directive to
back up all local drives. This directive backs up all files on the client and backs
up the system objects (SYSTEM_STATE) for Windows clients.
If a client has database or application files to back up using a NetBackup
database agent or other policy, you can do the following: use an exclude list to
exclude them from the policy that specifies ALL_LOCAL_DRIVES.
Use the same client name in multiple policies

If you use more than one policy to back up a client, use the exact same name for
the client in each policy.
BMR can only restore a client using the client that is named in the policy that
backed up the system files. If you use multiple policies with a different name in
each policy, a client record and its associated configuration is created for each
client name. If you restore a client by a name in a policy that does not back up
the system files, the prepare-to-restore operation fails. It fails because BMR can
only restore using the client that is named in the policy that backed up the
system files.
Therefore, if you use the same name, you do not have to choose between
multiple client names during a restore.
Solaris Zone support

When using BMR to back up and restore Solaris Zones, you need to address some
unique considerations.
Bare Metal Restore can restore a Solaris system running Zones. Although BMR
cannot restore individual non-global zones, all non-global zones in a system are
re-created as part of the global zone restoration.
Back up the client
In a dissimilar disk restoration scenario, do the following to ensure that you

restore all non-global zones:
■ Remap the file system that hosts the zone (also known as zonepath) to
restore the zone files.
■ If a non-global zone imports slices from the global zone that are not
remapped, BMR removes the slices from the zone configuration.
■ If a non-global zone imports slices from the global zone that are remapped
to different disks, the following occurs: BMR readjusts the zone
configuration and any zone vfstab (ZONEPATH/root/etc/vfstab) entries to
use the new device names.
■ If a non-global zone imports systems from the global zone file that are not
remapped, BMR removes any references to them in the zone configuration.
You may have to re-create and restore all file systems imported or used by a
non-global zone after BMR restoration. These file systems usually don't appear
in the global zone vfstab (/etc/vfstab).
In addition, to properly restore the zones, do the following:
BMR relies on entries in /etc/vfstab to document the filesystems that are subject
to restoration. Dynamically-created and mounted filesystems that do not appear
in /etc/vfstab (even if backed up by NBU) do not automatically restore. The
easiest way to force BMR to restore such filesystems is the following: add an
entry to /etc/vfstab that documents the devices and mount points used, with the
Mount at boot field set to NO. Then, the dynamic filesystems can continue to be
used as before. BMR is aware of them, recreates them unless unmapped in DDR,
and restores their contents if backed up by NBU.
Two types of zone features cause dynamically mounted filesystems to appear:
■ fs entries that involve devices in the global zone

■ device entries imported from the global zone but mounted either by the
/etc/vfstab of the non-global zone, or dynamically by the zone itself
To automate BMR zone restoration that use such features, add entries to the
global zone /etc/vfstab that cause BMR to restore them (unless unmapped by
DDR).
■ For fs entries, the global zone devices will be used as special and raw values
with a mount point that appears under the root of the non-global zone. The
entry to add to the global zone's /etc/vfstab should use the global zone's
device paths with the full path to the non-global zone mount point,
including the zone path. For example, if the zone looks like:
zonepath=/export/zone1
fs:
dir=/export
special=/dev/dsk/c0t9d0s6
Configure NetBackup properties
raw=/dev/rdsk/c0t9d0s6
type=ufs
Then the global zone entry in /etc/vfstab should look like:

/dev/dsk/c0t9d0s6 /dev/rdsk/c0t9d0s6 /export/zone1/root/export ufs - no
For device entries mounted by the non-global zone, there are two issues to
be dealt with when configuring for BMR restoration:
■ The dynamic mount used involves the imported device path under the zone
path. For a device that is mounted by an /etc/vfstab inside a non-global
zone, there will be one or more device entries in the zone such as:
zonepath=/export/zone2
device:
match=/dev/*dsk/c0t0d0s4
and in the non-global zone's /etc/vfstab:

/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /local ufs - yes
This causes the global zone to dynamically mount

/export/zone2/dev/dsk/c0t0d0s4 on mount point /export/zone2/root/local.
However, to make BMR automatically recreate the filesystem, you should
add the documenting entry to the global zone /etc/vfstab instead as:
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /export/zone2/root/local ufs - no
(If you use the device paths relative to the zone path, BMR will only recreate
the mount point instead of restoring the whole filesystem.)
■ The device match should not use wildcards to allow BMR to edit if DDR is
used. When the device specification involves a wildcard, BMR will not be
able to edit the entry if DDR mapping is done that affects the zone, such as
unmapping or moving a filesystem from one disk to another. The affected
zone's /etc/vfstab will be edited, but the device match entries will only be
edited if the match does not include a wildcard. So, instead of:
match=/dev/*dsk/c0t0d0s4
use two device entries:

match=/dev/dsk/c0t0d0s4
and
match=/dev/rdsk/c0t0d0s4
to ensure BMR DDR will correctly update the zone definitions and vfstab
file.

Configure the following NetBackup properties.
■ Enable the Allow client restore property. The BMR restore process requires
that both the BMR master server and the BMR client are able to request
restores. To allow client restores is the default NetBackup behavior; ensure
that client restores are allowed. The Allow client restore property is located
on the Client Attributes tab of the NetBackup master server properties.
■ Configure the NetBackup clients for server-directed restores, which allows
the master server to redirect restores of client files to itself. Server-directed
restores are the default NetBackup behavior; ensure that server-directed
restores are allowed. For more information, see “Server-Directed Restores”
in the NetBackup Administrator’s Guide, Volume I.
■ The Keep true image restoration (TIR) information property controls how
long TIR information is retained in the NetBackup catalog. TIR information
increases catalog size and the disk space that is uses. The following are your
options:
■ Choose a value for this attribute to match the retention policy.
■ Alternatively, if you want to minimize the size of the NetBackup
catalog, set the attribute to 0 days. The TIR information is also stored
on the backup media, so the catalog size does not increase but restores
are slower.
Set the Keep true image restoration (TIR) information property on the
Clean-up tab of the NetBackup master server properties.
For information about how to configure NetBackup, see the NetBackup
Administrator’s Guide, Volume I.
Chapter 5
Setting up restore
environments
Before you can restore a protected client, you must set up the resource
environment that is used during the restore.
You can set up the environment at any time. However, if your recovery time
objective (RTO) is short, you may want all of the resources in place. Your time is
used in recovery rather than set up.
Topics
■ “Install boot server software” on page 59
■ “Create shared resource trees” on page 60
■ “Add client resources” on page 60
■ “Create boot media” on page 61
■ “Verify the protection” on page 61
Install boot server software

Boot servers provide the environment that is required to rebuild a protected
client, including resources such as shared resource trees (SRT). You must have a
boot server for each type of client that you want to protect. In addition, you must
install the BMR boot server software before you can create SRTs and add
resources to them.
For information about how to install boot server software, see:
Related Topics
■ “Planning deployment” on page 17
60 Setting up restore environments
Create shared resource trees
■ “Managing boot servers” on page 179
Create shared resource trees

A shared resource tree (SRT) is a collection of the following:
■ Operating system files
■ NetBackup client software
■ Other programs to format drives, create partitions, rebuild file systems, and
restore the original files using the NetBackup client software
For more information about SRTs and procedures to create and update SRTs,
see:
■ “Managing shared resource trees” on page 107
Related Topics
■ “Planning deployment” on page 17
Add client resources

Windows clients only.
Dissimilar system restores may require some resources that are not included in
the protected client’s saved configuration. If so, you must add them to the client
configuration that is used for the restore (the restore configuration). Examples of
such resources are:
■ Network interface card (NIC) drivers
■ Mass storage device (MSD) drivers
■ Windows hotfixes (legacy restores only)
These resources must be in the BMR packages pool so they are available to add
to the restore configuration.
For information about how to add packages to the packages pool, see “Managing
Windows driver packages” on page 141.
Related Topics
■ “Managing clients and configurations” on page 145
Setting up restore environments 61

Create boot media
Create boot media
The BMR restore process begins by booting the client from BMR prepared boot
media (CD, DVD, or floppy) or from a BMR boot server.
If you use a network boot to begin the restore, boot media is not required.
If you have minimal network connectivity when you restore a client, Symantec
recommends that you use the boot media that contains a shared resource tree.
For more information about boot media and procedures for creating boot media,
see:
■ Managing boot media
Verify the protection

Optionally, you can verify that everything is in place to restore a client. BMR
automates the pre-recovery verification for a client when a prepare-to-restore
operation is performed.
For more information, see “Preparing to restore a client” on page 66.
62 Setting up restore environments

Verify the protection
Chapter 6
Restoring clients
The process to restore a protected system depends on the operating system of
the client and the type of restore you want to perform.
Topics
To restore to the same client and use the most recent backup, see:
To restore to a specific point in time, see:
■ “Restoring to a specific point in time” on page 81
To restore a client in which the disks are different, see:
■ “Restoring to dissimilar disks” on page 83
(Windows only.) To restore to a new target system, see:
■ “Restoring to a dissimilar system” on page 86
To restore NetBackup or BMR servers, see:
■ “Restoring NetBackup media servers” on page 90
■ “Restoring BMR boot servers” on page 93
Restore options
External procedures allow you to customize the restore process. For more
information, see:
“Using external procedures” on page 93
Related topics
“Restore process overview” on page 64
“Preparing to restore a client” on page 66
“Storage area network support” on page 103
“Multiple network interface support” on page 104
“Port usage during restores” on page 106
“Perform a full backup after a restore” on page 53
64 Restoring clients
Restore process overview

The NetBackup BMR master server manages the restore process:
■ The master server creates the necessary configuration files and restore
scripts (on UNIX and Linux) or restore processes (on Windows) and allocates
the boot server when the prepare-to-restore operation runs.
■ The client boots either by network boot or media boot.
■ The client accesses the shared resource tree, either on a boot server or on
the boot media.
■ The client runs a temporary operating system environment that is known as
the restore environment. The restore environment starts from the shared
resource tree.
■ The client restore environment retrieves the restore script and
configuration files from the master server.
■ The client restore environment starts the customized restore script, which
configures disks.
■ The client restore environment performs an automated restore using the
NetBackup client software, which restores all required files and data from
the NetBackup server.
■ The client reboots, which starts the restored operating system and
deallocates the boot server.
■ Dissimilar system restore tasks are completed (dissimilar system restore
only).
The following figures show a standard network restore and a media restore.
Restoring clients 65
Figure 6-3 Network restore
1 2 3
UNIX Client
Boot server
NetBackup media server

(backup image)
Boot server SRT
Boots from a shared
resource tree over the
network
Windows Client
Accesses files and client software Restores from the
from the SRT on the boot server NetBackup backup image
Boots from a BMR-prepared

CD, DVD, or floppy disk
Preparing to restore a client
Figure 6-4 Media restore
1 2 3
BMR Client
NetBackup media
server (backup image)
CD-based SRT or
DVD-based SRT
Boots from a BMR
prepared CD or DVD
Accesses files and client software Restores from the

from the SRT on the CD media or NetBackup backup image
DVD media

Before you restore a client, you must prepare to restore the client. During a
prepare to restore, the NetBackup master server:
■ Retrieves the client configuration from the master server database.
■ Creates the restore script and the configuration files that are used to restore
the client.
■ Allocates the boot server resources to the client.
When you prepare to restore a client, you select the configuration to use for the
restore:
■ For a standard restore (also known as a self restore, which is a restore to the
same system), select the current configuration.
■ For other types of restores, select the configuration that you created for the
restore.
To ensure that the restore includes the most recent data, Symantec recommends
that you prepare to restore immediately before you restore a system.
To prepare a client for restore

1 In the NetBackup Administration Console, expand Bare Metal Restore
Management > Hosts > Bare Metal Restore Clients.
2 Select a client or a client configuration.
3 Select Actions > Prepare to Restore.
4 In the Prepare to Restore Client dialog box, select the appropriate values for
the restore.
Some fields may be completed depending on whether you selected a client
or a client configuration.
For descriptions of fields, see “Prepare to Restore Client dialog box” on
page 67.
5 Click OK.
Bare Metal Restore runs all the processes to prepare for a restore.
6 After the processes finish, in the dialog box that appears, click OK.
The client is listed in the Tasks view with a State of Queued.
If you ran the prepare-to-restore operation to verify the protection, use the
following procedure to clean up the task. (The resources that the task uses are
unallocated, the State is set to Done, and Status is set to 150, terminated by
user). You can clean up the tasks that are in an Active state or a Waiting state.
To clean up the restore configuration

1 In the NetBackup Administration Console, click Bare Metal Restore
Management > Tasks.
2 In the details pane, right-click the client for which you want to clean up the
restore configuration.
3 Select Clean Up from the shortcut menu.
Prepare to Restore Client dialog box

Use this dialog box to select the prepare to restore options. If a client or
configuration is selected in the Administration Console window, the values and
options for them appear or are included in drop-down lists.
Related Topics
■ “Understanding BMR disk recovery behavior” on page 69
Figure 6-5 Prepare to restore client dialog box
Table 6-3 Prepare to Restore Client dialog box items
Item Description
Client The name of the client. If a client was selected in the

Administration Console, that client name appears.
Configuration The configuration to use for the restore. The drop-down list
includes all configurations for the client. If a configuration
was selected in the Administration Console, that
configuration appears.
Shared resource tree The shared resource tree that contains the resources for
restoring the client. For Windows systems, the old style
DOS based SRTs will be identified with a "(legacy)" label.
Select a shared resource tree that has the software that
matches the configuration of the client. (This information
includes the following: operating system version and level,
service or maintenance pack or level, any Veritas volume
manager that is used on the protected client, and so on.)
Use the Configuration Summary dialog box to help
determine the software in a client’s configuration.
See “Configuration summary” on page 158.
Restore system disks and Restore only those volumes that contain the operating
volumes only system.
For more information, see “Understanding BMR disk
recovery behavior” on page 69
Table 6-3 Prepare to Restore Client dialog box items
Item Description
Make available volumes on Import the volumes.

non-restored disks after the
For more information, see “Understanding BMR disk
system is restored
recovery behavior” on page 69.
Run external procedures Run external procedures during the restore.

See “Using external procedures” on page 93.
Enable logging Write messages to the log file on the master server during
the restore. Enable logging if you have adequate space in
the file system on which the NetBackup log directory
resides on the master server.
Use quick formatting (Microsoft Windows clients only.) Use quick formatting.
Understanding BMR disk recovery behavior

BMR either restores or imports disks during a restore, defined as follows:
■ To restore a disk means that BMR formats the disk and restore files to it. No
attempt is made to retain any data on the disk.
■ To import a disk means that BMR tries to reuse the volumes on it (that is,
mount the file systems after restore). BMR tries to reuse rather than format
the disk and restore files to it.
BMR always restores the system disk. For other disks, the following two options
on the Prepare to Restore Client dialog box control BMR behavior:
■ Restore system disks/volumes only. If you select this option, BMR restores
only the system disk. Otherwise, BMR tries to import (reuse) non-system
disks that are based on the disk class and the following option. System disk
is defined as the following:
■ On AIX and HP-UX, the root volume groups (rootvg and vg00) are
restored.
■ On Solaris, all disks that have any of the root file systems (/, /swap,
/var, /usr) are restored.
■ On Windows, all disks that have %SystemRoot%, %SystemBoot%, and
%TEMP% are restored. On Active Directory servers, BMR also restores
the disks that contain the Active Directory system, database, and log
files.
■ Make available volumes on non-restored disks after the system is
restored. If you select this option, BMR imports the disks. Otherwise, the
action depends on the disk class.
For more information, Table6-5‚ ”Actions for disk classes‚” on page 71.
The following are the disk classes:
■ System disks contain the operating system files required to boot the system.
■ Nonsystem disks are all other disks, as follows:
■ Restorable disks are visible in the temporary restore environment and
therefore can be restored. Visible means locally attached.
■ Nonrestorable disks are not visible in the temporary restore
environment and therefore cannot be restored. Typically these are SAN
devices. You may not know that these disks cannot be restored until
you attempt a restore. If these disks are required for a restore, you are
forced to do a dissimilar disk restore (DDR).
■ Shared disks are shared with another system using clustering software.
The client may not control them during or after the restore.
■ Missing disks may or may not have been used and are no longer
attached to the system. These disks are in the restore configuration.
For the actions to perform for missing disks, see Table6-5‚ ”Actions for
disk classes‚” on page 71.
■ New disks are attached to the system in previously unused locations
and used by any volume or any volume group. New disks are not in the
original configuration.
BMR also restricts some disks so they are not processed during a restore. For
example, BMR restricts shared disks in a cluster and unused VxVM disks on
Solaris systems. Additionally, you can restrict a disk so BMR does not process it.
The following table describes how BMR processes disks depending on the two
prepare-to-restore options:
Table 6-4 BMR disk actions
Nonsystem disks
Restore options System Disks
Restricted = false Restricted = true
System only1 = true Restore Import No action

Import2 = true
System only = true Restore No action No action

Import = false
System only = false Restore Restore if possible No action

Import = true otherwise import
Table 6-4 BMR disk actions (continued)
Nonsystem disks
Restore options System Disks
Restricted = false Restricted = true
System only = false Restore Restore No action

Import = false
1.System only is the Restore system disks/volumes only option for prepare to restore.
2.Import is the Make available volumes on non-restored disks after the system is restored option for
prepare to restore.
The following table describes the actions that BMR performs for each disk class
and any action you should perform:
Table 6-5 Actions for disk classes
Restore System Nonsystem disks

options disks Restorable Nonrestorable Shared1 Missing New
2
System only Restore Import Import No action Mark the restricted Not
= true disk , remap to a imported
Import3 = true restorable disk, or
remove the disk
from the restore
configuration
System only = Restore No action No action No action No action No action

true
Import = false
System only = Restore Restore Import No action Mark the restricted Not
false disk, remap to a imported
Import = true restorable disk, or
remove the disk
from the restore
configuration
System only = Restore Restore Remove the disk No action Mark the No action
false from the restore restricted disk,
Import = false configuration or remap to a
mark the disk restorable disk, or
restricted remove the disk
from the restore
configuration
1.To avoid conflicts with other cluster nodes that may be using surviving shared disks during a restore, shared disks should remain
restricted or be unmapped or remapped to alternate, non-shared restorable locations. Shared disks should only be unrestricted and
restored in-place if other cluster nodes are not holding the share actively during the restore.
2.System only is the Restore system disks/volumes only option for prepare to restore.
Restoring clients
3.Import is the Make available volumes on non-restored disks after the system is restored option for prepare to restore.
The following table describes the import action for each operating system or
volume manager:
Table 6-6 Import action
OS and volume manager What import means
AIX Logical Volume Manager Run importvg at restore time or during first boot
HP-UX Logical Volume Manager1 Merge lvmtab, merge fstab
Linux Merge fstab
Solaris Merge vfstab2
Veritas Storage Foundation for Assign drive letter by MountedDevices, run vxdg
Windows import
Veritas Volume Manager3 Run vxdg import, merge fstab2
Windows4 Assign drive letter by MountedDevices

1.Virtual auto import. An HP system can have VxVM managed root disks and some LVM managed disks.
In a system only restore, the LVM database (the /etc/lvmtab file) is restored. Without any action re
quired by BMR, these disks and their volumes will be available. If entries remain in /etc/fstab for the
file systems, those file systems will be available.
2./etc/fstab and /etc/vfstab merging: During a merge, BMR may remove entries in the
/etc/fstab or /etc/vfstab files by commenting them out.
3.Auto import. VxVM has the ability (a disk group option) to import disk groups automatically. If there
are entries in the /etc/fstab and /etc/vfstab files, the file systems will be available without BMR
having to take action.
4.Windows import. Without import, only drive letters that were recreated will be assigned after restore.
With import, drive letters assigned to volumes on Trusted disks will be assigned to the same location af
ter the restore. If the volume does not exist or has moved, you must edit the MountDevices registry key.
Restoring clients
Use these procedures for a standard restore (also known as a self restore, which
is a restore to the same system and disks). Before you do a standard restore, you
must run the prepare to restore operation using the current, saved
configuration.
UNIX and Linux clients can boot either over the network, from CD media, or
from DVD media.
Note: If NetBackup access management is used in your environment, you must

provide the appropriate credentials when prompted so that NetBackup can
restore the client files.
Restoring clients
Tasks
■ “Restoring BMR clients using network boot” on page 73
■ “Restoring BMR clients using media boot” on page 77
Related topics
■ “Preparing to restore a client” on page 66
■ “Using external procedures” on page 93
Restoring BMR clients using network boot

In a network boot, the BMR client boots from the shared resource tree on the
BMR boot server.
To network boot clients, BMR uses:
■ PXCE for Windows and Linux clients.

■ dhcp for Linux clients
How you boot a machine over the network depends on its manufacturer and
model. Refer to the appropriate section for your system:
■ “AIX network boot” on page 73
■ “Solaris network boot” on page 76
■ “HP-UX network boot” on page 74
■ “Linux network boot” on page 75
AIX network boot

An AIX boot (either network boot or media boot) may set the network interface
configuration, speed, and duplex mode to auto-negotiate or 10 half duplex. This
may cause the BMR restore to run much more slowly than expected. To achieve
normal restore performance, manually set the network interface configuration
through the firmware before a BMR restore.
AIX system restore requires certain information and resources. The information
varies according to architecture, but can include:
■ Network adapter type
■ BMR client IP address
■ BMR client subnet mask
■ BMR boot server IP address
■ BMR client gateway address
Restoring clients
After you perform the network boot procedure, the remainder of the restore
process is automatic and requires no manual intervention. After the restore
finishes and the client reboots itself, it is completely restored.
To network boot an AIX system that has AIX installed

This method updates the NVRAM with the proper addresses for the BMR boot
server, client, and gateway address. This method boots by bootp from the BMR
boot server. If the boot server does not answer the bootp request, the machine
boots from the hard drive. This method only works when the BMR client is
properly prepared for restore.
Caution: Do not perform this procedure unless you intend to do a restore. When
you prepare a client for restore, the process may result in a restore.
1 Prepare to restore the client.

For procedures, see “Preparing to restore a client” on page 66.
2 Boot from a network interface according to the procedures in the IBM
hardware documentation.
After you perform the network boot procedure, the remainder of the restore is
automatic and requires no manual intervention. After the restore finishes and
the client reboots itself, it is completely restored.
HP-UX network boot

HP-UX system restore requires certain information and resources. The
information varies according to architecture, but can include:
■ BMR client IP address
■ BMR client gateway address
■ BMR client subnet mask
■ Ignite Server Address (usually, the BMR boot server)
To begin this procedure, the BMR client must be OFF.
To network boot an HP-UX client

2 Ensure that the client is powered down.
Restoring clients
3 Turn on the client.

4 Press any key when the following message appears.
To discontinue, press any key within 10 seconds.
5 In the Main Menu, do one of the following to begin the network boot process:
■ If only one Ignite server is on the subnet, enter the following boot
command:
boot lan
■ If there is more than one Ignite server on the subnet, specify the Ignite
server to boot from by using the following command: (Replace x.x.x.x
with the IP address of the Ignite server and y.y with the gateway.)
boot lan.x.x.x.x.y.y
Use the same command if you use a boot helper to boot from an Ignite
server on a different subnet.
6 Enter No when the prompt asks if you want to interact with IPL.
7 If the client is a workstation, select the operating system language by
number. For example, US English is 61.
8 After you enter the language choice, press Enter twice to select and confirm
the choice. The HP-UX Ignite menu opens.
9 Use the arrow key to scroll to Run a Recovery Shell. Wait while the DHCP
search occurs and until the Network Configuration menu opens. If you
interrupt a DHCP search, the BMR restore may fail.
10 Answer the following prompts:
■ Hostname:
■ Internet Protocol Address:
■ Subnet mask:
■ Ignite Server Address (typically the BMR boot server):
11 Use the arrow key to scroll to OK and press Enter.
The system boots from the network.
Linux network boot

During the prepare-to-restore operation all the information is gathered that is
required for a Linux network boot. After the prepare to restore, boot the client to
start the restore.
To network boot a Linux client

Restoring clients

3 Turn on the client .
4 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.
Consult your hardware documentation for details.
The following message appears:
Press ENTER to start Bare Metal Restore boot:
Press the ENTER key, or wait 20 seconds for startup to begin

automatically.
5 Either press the Enter key or wait until the system boots.
The system boots and the restore begins with no further user intervention
required.
Solaris network boot

Solaris system restore requires the name of the device that directs the client to
the correct BMR boot server.
To network boot a Solaris client

4 Terminate the boot process by using the Stop+A key combination.
5 If the PROM monitor prompt displays a left angle bracket (<), use the N
command to get to the OK prompt.
6 Start the network boot by entering the following command (network
device is the device that points to the BMR boot server):
boot network device
Restoring clients
Windows network boot

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.
To network boot a Windows client

4 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. Consult your
hardware documentation for details.
DHCP....
Press F12 for network service boot
5 Press the Function 12 key and the system will boot and the restore begins
with no further user intervention required.
Restoring BMR clients using media boot

To restore using media boot requires that you first create bootable media.
For procedures, see “Creating boot media for UNIX and Linux” on page 137.
The procedure for booting the client system depends on the manufacturer and
model. See the following:
■ “AIX media boot” on page 77
■ “HP-UX media boot” on page 78
■ “Linux media boot” on page 79
■ “Solaris media boot” on page 80
AIX media boot

An AIX boot (either network boot or media boot) may set the network interface
configuration, speed, and duplex mode to auto-negotiate or 10 half duplex. This
may cause the BMR restore to run much more slowly than expected. To achieve
normal restore performance, manually set the network interface configuration
through the firmware before a BMR restore.
Restoring clients
To media boot an AIX client

1 Prepare to restore the client, using the SRT you created on the bootable
media.
See “Preparing to restore a client” on page 66.
2 Boot the client from the boot media you created. For instructions on how to
boot from a CD or from a DVD, see the IBM hardware documentation.
3 The BMR process prompts you for the following:
■ Client name (for a discovery boot, enter the client’s name as it appears
in the Tasks view from the prepare to discover operation)
■ Client IP address
■ Network mask
■ Default gateway
■ NetBackup master server name
■ NetBackup master server IP address
■ NetBackup master server gateway IP address
After you enter the required information, the restore begins.
HP-UX media boot

To media boot an HP-UX client
media.
2 Insert the bootable CD or bootable DVD into the CD-ROM drive.
3 Turn off the client, then turn on.
4 When you are prompted, press the Space bar to stop the normal boot
process.
5 Search for the location and name of the CD-ROM drive.
The search utility may be useful to determine this information.
6 Find the CD-ROM drive from the list of devices and boot the machine using
that device with the boot command.
7 In response to the Interact with IPL prompt, type No.
8 In response to the Run a Recovery Shell prompt, type Yes.
9 In response to the Start Networking prompt, type Yes.
10 In response to the Choose the Network Interface prompt, type the default
LAN device to boot from.
Restoring clients
You must enter the default LAN because the firmware uses this address for
booting from the Ignite server. Note that any network interface card can be
used for accessing the SRT or backups, but the default LAN must be used for
booting.
11 Enter the following information when prompted:
■ Hostname
■ IP address
■ Default gateway
■ Subnet mask
12 In the Is this network information temporary prompt, type No.
13 Use the arrow key to scroll to OK and press Enter.
Linux media boot

To media boot a Linux client
media.
On some systems, you may have to modify the BIOS settings so that the
system boots from the CD-ROM drive. Consult your hardware
documentation for details.
Press ENTER to start Bare Metal Restore boot:
Press the ENTER key, or wait 20 seconds for startup to begin
automatically.
4 The BMR restore process prompts you for the following:

Restoring clients
■ Client IP address
■ Network mask
■ Default gateway
■ Additional gateway address to reach the NetBackup master server
Solaris media boot

To media boot a Solaris client
media.
4 Terminate the boot process using the Stop+A key combination.
5 If the PROM monitor prompt displays <, use the N command to reach the OK
prompt.
boot cdrom
The Solaris OS Installation prompts you for network identification.

7 Enter the network identification.
Windows media boot

To media boot a Windows client
Restoring to a specific point in time

2 Create a bootable CD or bootable DVD from the SRT used during the Prepare
to Restore.
On some systems, you may have to modify the BIOS settings so that the
system boots from the CD-ROM drive. Consult your hardware
documentation for details.
4 Turn off the client, then turn it on.
press any key to boot from CD
5 The system boot and the restore begins with no further intervention
required.

When NetBackup backs up a BMR client, it also backs up the currently saved
configuration, and that configuration contains the information about the client
on that specific date and time. So you can restore to any point in time for which
you have a backup for a BMR client.
For a point in time restore, you must create a restore configuration and specify
the point in time to which you want to restore.
Tasks “Creating a point in time restore configuration” on

page 82
Related Topics “Understanding the point in time restore process” on

page 81
“When to use point in time restore” on page 82
“Preparing to restore a client” on page 66
“Perform a full backup after a restore” on page 53
Understanding the point in time restore process

Normally, BMR restores from the most recent backup. In a point in time restore,
BMR can restore the system to a state earlier than the last full backup.
To restore the system to a previous point in time, you select the point in time for
the restore when you create a restore configuration.
When to use point in time restore

A point in time restore is useful when a recent software change has rendered the
system unusable. Bare Metal Restore can restore the system to a previous known
working state. Use the point in time restore feature in the following scenarios:
■ A hardware change has destabilized the system. There may be cases in
which the software associated with the hardware cannot be removed
completely. Instead of removing all the associated drivers and software,
point in time restore can recover the system to a known working state.
■ A software addition has destabilized the system. Rather than uninstalling
the software, which may not return the system to its state before the
software was installed, point in time restore can recover the system.
■ A virus attacked the system.
■ Critical system or application files were deleted.
Creating a point in time restore configuration

This procedure creates the restore configuration for a point in time restore for
any client type. Then follow the standard restore procedures for the client.
To create a point in time restore configuration

1 In the NetBackup Administration Console, expand Bare Metal Restore
2 In the All Bare Metal Restore Clients pane, right click on the saved
configuration for the client (the configuration labelled current), then select
New from the shortcut menu.
3 In the New Configuration dialog box, enter a name for the new
configuration.
4 Click Retrieve from NetBackup then select the Policy and End Date for the
restore.
If the backup policy uses multiple data streams to back up the client, all of
the data streams for each backup job are shown in the End Date drop-down
list; select the most recent stream of the backup job on the date to which
you are restoring. Normally; backup jobs occur on separate days and data
streams within the same backup job are separated by seconds or minutes.
5 Click OK.
The new configuration appears in the list of the client's configurations. The
configuration is now ready for the prepare to restore operation.
6 Continue by following the procedures in “Restoring clients” on page 72.
Restoring to dissimilar disks
You can restore a protected client even if the disk drives were replaced. You also
can perform a dissimilar disk restore (DDR) if you need to change the volume
layout or restore only some of the disks.
Tasks
Related topics
■ “Understanding the dissimilar disk restore process” on page 83
■ “When to use dissimilar disk restore” on page 84
Understanding the dissimilar disk restore process

In a standard restore, BMR uses the current client configuration to recreate the
original system. Little or no intervention is required because the original system
is moved onto the original disk configuration.
In a dissimilar disk restore, intervention is required because you have to map
the volume configuration from the protected client to the new disks. (Disk refers
to a physical disk, and volume refers to a logical division of disk space on one or
more physical disks.) Mapping occurs as follows:
■ Before the restore. You can create a configuration you can edit (an editable
restore configuration) and initialize that configuration with the new disk
layouts. Then map the original volume configuration to the new disks. After
you finish mapping, you restore the client using the restore configuration.
This method requires a record in BMR of the following:
■ Layouts of the new disks on the client, which is necessary, for example,
when you perform a discovery operation.
■ Whether another protected client has the same disks
■ During the restore. You perform a standard restore and BMR detects that the
disks are different. BMR enters DDR mode and creates an editable restore
configuration so you can map the disks. You map disks as follows:
■ For UNIX and Linux clients, use the BMR disk mapping utility in the
NetBackup Administration console on the master server.
■ For Windows clients, you can map on the client or on the master server
using the BMR disk mapping utility in the NetBackup Administration
console.
When to use dissimilar disk restore

You should use dissimilar disk restore when:
■ A physical disk is replaced.
■ The size of one or more disks has decreased and cannot contain the same
volume arrangement.
■ The location of one or more disks changes.
■ The number of disks has decreased and the required volume arrangement
cannot be restored.
■ You need to change the layout and volumes for the restored system.
■ You want to restore only some of the disks in a system.
Caution: Changes in disk locations may prevent a clustered resource from going
online after a restore. BMR does not attempt to adjust clustered resource
attributes to account for a dissimilar disk restore.

Use the following procedures to restore to a system in which the disks are
different:
■ “Creating a restore configuration for DDR” on page 84
Notes for UNIX and Linux DDR
■ Shared disks in a cluster are marked restricted.
■ Unused VxVM disks on Solaris clients are marked restricted and should
remain restricted.
■ You cannot map Linux LVM volume groups with the physical volumes that
were created on top of multidevices with the same configuration. The
physical volumes are mapped to either disks or partitions but not to a
multidevice.
Creating a restore configuration for DDR

Use the following procedure to create an editable restore configuration and
perform disk mapping before you begin the restore.
You do not have to create a DDR configuration before you begin the restore.
To begin a restore and perform disk mapping during the restore itself, see
“Restoring to dissimilar disks” on page 85.
To create a configuration
1 Discover the configuration of the new disks.
For procedures, see “Discovering a configuration” on page 152.
2 Create an editable restore configuration by copying the current
configuration.
For procedures, see “Copying a configuration” on page 150.
3 Open the Change Configuration dialog box for the restore configuration.
For procedures, see “Modifying a configuration” on page 155.
4 Initialize the restore configuration with the disk information from the
discovered configuration and then map the the original volume
configuration to the new disks.
For procedures, see “Volumes” on page 171.
5 After you finish mapping, perform the DDR restore procedure in “Restoring
to dissimilar disks” on page 85.

Use the following procedure to restore to dissimilar disks. If you did not prepare
a restore configuration in advance, BMR creates an editable restore
configuration during this process.
To perform a UNIX or Linux dissimilar disk restore

If you prepared a current configuration or a restore configuration in
advance, use it.
2 Begin the restore by booting the client using either network boot or media
boot.
For procedures, see “Restoring clients” on page 72.
If you use a configuration where the protected system’s volume
configuration is already mapped to the new disks, the restore proceeds as a
standard restore. No intervention is required.
If BMR detects that the disks are different and are not already mapped, BMR
enters DDR mode. Continue to step 3.
3 If you use a configuration that cannot be edited, BMR creates an editable
restore configuration. It copies the current configuration and prompts you
to enter a name for it, as follows:
Current configuration name for restore is 'current'.
Please enter the name for a new editable configuration:
Enter a name for the editable restore configuration.

Restoring to a dissimilar system
4 To obtain the layouts of the new disks, BMR discovers the hardware of the
client. BMR prompts you for a name for the discovered configuration, as
follows:
Please enter the name for a new discovered configuration:
Enter a name for the discovered configuration. BMR saves the discovered
configuration. Later, you import the disk layouts from this discovered
configuration into the restore configuration.
5 After the discovered configuration is saved, in the NetBackup
Administration Console on the master server, open the Change
Configuration dialog box for the restore configuration.
6 Initialize the restore configuration with the new disk layout from the
discovered configuration and then map the original volume configuration to
the new disks.
For procedures, see “Volumes” on page 171.
7 After you finish mapping, prepare to restore and then restore the client,
using the edited restore configuration.
If the disk mapping in the restore configuration is incomplete, BMR enters
DDR mode again so you can continue to map volumes to disks.

If the target system disk(s) are different than the protected system disks, disk
and volume mapping (as performed with a dissimilar disk restore) are required
Tasks
■ “Restoring to a dissimilar system” on page 87
Related topics
■ “DSR troubleshooting” on page 186
When to use dissimilar system restore

A dissimilar system restore (DSR) restores a protected Windows client to a new
system that has a different hardware configuration.
A DSR is useful in the following situations:
■ You change the preferred vendor for a class of systems in your enterprise.
■ You migrate an application from older hardware to the newer hardware.

■ Your system experiences critical hardware failure and similar hardware is
not available for replacement.
■ Your disaster recovery provider does not have identical hardware to yours at
the disaster recovery site.
■ You stage and verify an application at a test site with different hardware
from the production site. (You can migrate the application from test to
production.)
Use DSR when any of the following conditions apply:
■ The target system has a disk controller that the protected system does not
have.
■ The target system has a network card that the protected system does not
have.
■ The target system requires a different hardware abstraction layer (HAL) or
kernel than the protected system.
■ The target system has different TCP/IP settings than the protected system
has. (Only TCP/IP properties are restored. Other networking properties,
such as Internetwork Packet Exchange (IPX), are not restored and must be
configured after the restore.)
Note: Changes in the hardware configuration may prevent clustered resources

from going online after a restore. BMR does not attempt to adjust clustered
resource attributes to account for a dissimilar system restore.

The dissimilar system restore (DSR) process has the following steps:
1 Discovering a configuration
2 Creating an editable DSR configuration
3 Adding NIC and MSD drivers
4 Changing network interfaces
5 Mapping disks
6 Creating boot media
7 Restoring the client
8 First logon
Discovering a configuration
The first step in restoring to dissimilar hardware is to discover the hardware
that is contained on the new system.
For procedures, see "“Discovering a configuration” on page 152.
Creating an editable DSR configuration

You must create a configuration to use for the restore of the protected client.
Create the DSR configuration by copying an existing configuration of the
protected client.
For example, to restore client protected to system target, create a configuration
named dsr_to_target by copying the current configuration of client protected.
To copy a configuration, see “Copying a configuration” on page 150.
After you create the DSR configuration, open the Change Configuration dialog
box to modify the configuration as described in the following sections.
See “Change Configuration dialog box” on page 157.
Adding NIC and MSD drivers

The DSR configuration must include the NIC drivers and the MSD drivers that
the target system requires.
The target system drivers were added to the packages pool when you performed
one of the procedures in “Discovering a configuration” on page 152. They are
available to add to the DSR configuration.
To add drivers, select them in the Available drivers window of the
configuration’s Drivers dialog box. Then add them to the Drivers to be used
during restore window.
For more information, see “Devices and Drivers” on page 160.
If you added the drivers to the packages pool using the following methods, the
driver description includes the name of the target system:
■ By saving the target system’s configuration

■ By extracting the drivers from the target system
The driver description helps identify which drivers are required for the target
system. Also, remove any drivers from the DSR configuration that the protected
system uses and the target system does not.
Note: Only TCP/IP properties are restored. Other networking properties, such as
Internetwork Packet Exchange (IPX), are not restored and must be configured
after the restore.
Changing network interfaces

You must change the network interfaces and network identities in the DSR
configuration.
If you installed NetBackup client software on the target system and backed it up
as described in “Discovering a configuration” on page 152, you can do the
following:
■ Import the NIC information from that configuration

■ Map the network identifiers (IP address, netmask, and domain name) from
the protected client to the NICs in the target system
If you did not save the target system’s configuration, you must determine the
MAC addresses of the NICs in the target system. Then add the network interface
information manually to the DSR configuration.
For procedures on how to import and map interfaces or change them manually,
see “Network interfaces” on page 165.
Mapping disks
A dissimilar system restore may also be a dissimilar disk restore. If the target
system has different disks than the protected client, you must map the volume
configuration from the original system to the new disks. (You map as in a
dissimilar disk restore.) You can also shrink or extend the size of the system
partition or volume. You do not have to map the vendor partition (if one exists)
from the protected client to the target system’s disks.
If you installed NetBackup client software on the target system and backed it up
as described in “Discovering a configuration” on page 152, you can do the
following: import the disk layouts from that configuration and then map disks
before the restore. Symantec recommends that you map disks before the
restore, especially when the protected client’s system partition cannot fit on the
target system’s system disk.
If you did not save the target system’s configuration, you must do the DDR
mapping during the restore.
For information about and procedures for DDR, see “Restoring to dissimilar
disks” on page 83.
Creating boot media

If boot media is not available, create media for booting the target system.
For instructions, see “Restoring clients” on page 72.
Restoring NetBackup media servers
Restoring the client

Prepare to restore the client and initiate the dissimilar system restore process
using the DSR configuration.
For instructions, see “Restoring clients” on page 72.
First logon
After the system is restored, a local administrator logon is required to complete
the DSR changes. The bmrcleanup utility runs and displays a status box that
describes the actions being performed.
While the status box is visible, Windows may display a number of New Hardware
Found wizards. Perform the following action depending on which wizard or
message screen appears.
■ In the “Digital Signature Not Found” screen, click Yes or Continue.
■ In the “Found New Hardware wizard” screen, click Cancel.
■ In the “New drivers are installed, do you want to reboot?” screen, click No.
Note: Do not reboot the system until the bmrcleanup status box completes.
Note: Windows XP and Windows Server 2003 systems may require a product
activation after a DSR.

You can restore NetBackup media servers if they are protected as BMR clients
(exception: you cannot restore a media server that is co-located with a
NetBackup master server). Two options exist for restoring NetBackup media
servers:
■ If you back up a media server to a different media server, restore the
protected media server as you would restore any protected client.
■ If a media server backs up its own data (using SCSI-attached storage devices
or SAN-attached storage devices), do the following: use BMR to restore the
media server by first configuring NetBackup to use an alternate media
server.
Tasks
■ “Configuring an alternate media server” on page 91
■ “Restoring the media server” on page 92
Related topics
■ “Perform a full backup after a restore” on page 53.
Configuring an alternate media server

Two methods exist to configure an alternate media server in NetBackup. You
must perform one of the following:
■ Configure the automatic media server failover. This method redirects the
restore only if the media server is not available. This method is most useful
if the library that contains the media is connected both to the failed media
server and the alternate media server. Normally, you configure automatic
media server failover before the failure, which results in less time and effort
during the restore.
■ Override the original media server manually. This method forces restores to
the alternate server, regardless of the state of the original media server. This
method is most useful in the following situation:
■ You did not configure automatic media server failover before the
failure.
■ You want to perform a temporary media server reassignment to restore
the original media server.
All backup and restore requests (not only BMR restores) are directed to the
alternate media servers.
For more detailed information on how to configure NetBackup to use an
alternate media server, see the NetBackup Administrator’s Guide, Volume I.
Configuring automatic media server failover

Normally, automatic media server failover is configured before the original
media server fails.
On UNIX and Linux systems, when you configure this option, it sets the
FAILOVER_RESTORE_MEDIA_SERVERS parameter in the bp.conf file.
To enable automatic failover to an alternate server

1 In the NetBackup Administration console, open the Restore Failover host
properties for the master server.
2 Add an entry in the Alternate Restore Failover Machines list; name the
media server and failover restore server(s).
3 Stop and restart the NetBackup Request Manager daemon or service on the
master server.
Overriding the original media server manually

If necessary, before you physically override the media server, move the media to
a library that is attached to the new media server. Then update the Enterprise
Media Manager database to reflect the move.
After you perform the restore, reverse the NetBackup configuration changes by
removing the alternate server entry from the Media Host Override list. The
original server performs the NetBackup backup and restore requests again.
On UNIX and Linux systems, when you configure this option, it sets the
FORCE_RESTORE_MEDIA_SERVER parameter in the bp.conf file.
To override the original server for restores manually

1 In the NetBackup Administration console, open the General Server host
properties for the master server.
2 Add an entry in the Media Host Override list; name the original backup
server and the restore server. Click OK.
3 Stop and restart the NetBackup Request Manager daemon or service on the
master server.
Restoring the media server

If you configured the alternate media server before the media server failed
(which is most likely with the automatic failover method), the following occurs:
the alternate media server is saved as a host in the original media server’s BMR
client configuration. Now you can perform a standard restore.
If you did not configure the NetBackup alternate media server before the failure,
create and modify a restore configuration to use during the restore.
To create and modify a media server restore configuration

1 Create a restore configuration.
Follow the procedures in “Copying a configuration” on page 150.
2 Open the Change Configuration dialog box.
3 Select the Hosts properties.
Restoring BMR boot servers
4 Add the alternate media server as a host.

For procedures, see “Hosts” on page 163.
5 Click OK to close the Change Configuration dialog box.
After you create and modify the restore configuration, perform a standard
restore.
Restoring BMR boot servers

You can restore BMR boot servers if you protect them as BMR clients. First, back
them up. Then use a shared resource tree on another boot server that contains
the resources to rebuild the protected boot server.
If a boot server is installed on the same system as the NetBackup master server,
you cannot protect it as a BMR client. You can recover the NetBackup catalogs
(which include the BMR databases) on the NetBackup master server. However,
you must reinstall the NetBackup and BMR software on the master server. For
more information, see the disaster recovery procedures in the NetBackup
Troubleshooting Guide.
For information about how to protect clients, see:
■ “Protecting clients” on page 51
Restore boot servers by using the procedures that are documented in the
following:
Using external procedures

External procedures are the scripts that interact with the restore process during
user exits. Using external procedures, you can minimize the interaction that is
required for the restores that are not automatic.
The following are the two external procedure types:
■ Client-specific for a specific client.
■ Operating system specific for all clients of that operating system type.
Client-specific procedures take precedence over operating system procedures.
External procedures are started only if you do one of the following:
■ Select Run External Procedures on the Prepare to Restore Client or Prepare
to Discover dialog box.
■ Specify external procedures by using the bmrprep -runep command.
External procedures operate in the restore environment (a limited operating
system environment during the restore process). Many of the commands and
capabilities that are available with a complete operating system are not
available in the restore environment.
UNIX external procedures execute as root. Windows external procedures
execute as administrator.
External procedures are stored in the BMR database on the NetBackup master
server. Use the bmrepadm command on the master server to manage external
procedures.
Note: Using external procedures requires a general knowledge of scripts.
External procedure points and names

BMR can run external procedures at five user exit points during the restore
process in the following sequence:
External Description
procedure point
prediscover Before discovery of hardware is reported to the BMR server (UNIX

clients only).
preformat Before disks are formatted and partitioned. On Windows systems,

the preformat takes place after the system drive is formatted but
before any nonsystem drives are formatted.
prerestore Before files begin to restore.
postrestore After files are restored.
first boot After the restore is complete and at the first boot of a restored client.
On Windows systems, the first boot external procedure operates as
the first user to log on after a client is restored.
An external procedure point name is used as part of the name of each external
procedure script that you create. The naming convention for client-specific
external procedures is different than for operating system specific external
procedures.
Note: Do not add a .cmd extension for the external procedures that are intended
for Microsoft Windows systems. BMR adds the appropriate filename extension
when it generates the scripts during the prepare-to-restore process.
Client-specific external procedure names

Client-specific external procedure names are in the following format:
clientname_externalprocedure
For example, the sol123_prerestore external procedure is started before
files are restored on client sol123. (The procedure starts if Run External
Procedures is specified during the prepare to restore.)
Operating system specific external procedures names

Operating system specific external procedure names are in the following format:
externalprocedure.ostype
ostype is one of the following:
ostype Operating system
aix AIX systems
hp HP-UX systems
linux Linux systems
sol Solaris systems
win Windows systems
For example, the preformat.linux external procedure is started on Linux

clients before drives are formatted. (The procedure starts if Run External
Procedures is specified during the prepare to restore.)
Managing external procedures

Use the bmrepadm command to:
■ Add an external procedure so it is available during a restore.
■ Delete an external procedure from the database.
■ Extract an existing procedure from the database.
■ List all the external procedures in the database.
For example, to add a prerestore external procedure for a client named sol123,
use this command on the NetBackup master server with a BMR license:
bmrepadm -add sol123_prerestore
The bmrepadm command does not validate client names (that is, you can add an
external procedure for a nonexistent client).
For another example, to add an external procedure auxiliary file named

ListStorageGroups.vbs, use the following command:
bmrepadm -add -data ListStorageGroups.vbs
For more information about the bmrepadm command, see the NetBackup
Commands for UNIX or the NetBackup Commands for Windows guide.
Running external procedures

You must specify during the prepare-to-restore operation that you want to run
external procedures. The BMR master server then creates the appropriate
external procedure scripts and uses them during the restore.
To specify external procedures, select Run External Procedures in a Prepare To
Discover or Prepare to Restore Client dialog box.
Alternatively, use the bmrprep command -runep option to specify external
procedures. For more information about the bmprep command, see NetBackup
Commands.
Note: External procedures should be in the BMR database before the

prepare-to-restore or prepare-to-discover operation is started.
External procedure data transfer

You can use the bmrc command to transfer files from the BMR master server to
a client during a restore.
On UNIX systems, store data in the /tmp file system or in the file systems that
are mounted under /tmp. All other file systems are read only during a restore.
On Windows systems, transferred files are stored in the current directory by
default. The directory is %SystemDrive%\ during restore. The directory is
%HOMEPATH% during the first boot procedure. You can specify other path names
or file names on the command line.
The following is an example of using the bmrc command to transfer a file from
the master server to the client:
bmrc -operation pull -resource procedure -client clientName -source
file_on_server -destination /tmp/filename
When you start the bmrc command in an external procedure, specify the full
path to the bmrc command in the restore environment:
■ On UNIX and Linux clients: /usr/openv/netbackup/bin

■ On Microsoft Windows clients: %SystemDrive%\BMR\NBU\bin
At the first boot external procedure point, the path to the bmrc command is
install_path\NetBackup\bin on Microsoft Windows clients.
For more information about the bmrc command, see NetBackup Commands.
Interaction with external procedures

UNIX and Linux clients
On UNIX systems, you can enter commands and interact with an external
procedure during restore time. To do so, start the bmrShell function from
within the external procedure script. The bmrShell function allows input from
the default console keyboard and outputs to the console monitor.
You can also use redirection to send output to the screen from an external
procedure by redirecting output to the special device. To do so, use
/dev/console (as in echo "Hello World" >> /dev/console).
On UNIX and Linux systems, the bmrShell is not available during first boot.
Microsoft Windows Clients
On Windows systems, you can enter commands and interact with an external
procedure during restore time. To do so, start the Windows command
interpreter cmd from within the external procedure script.
On Windows systems, the limited restore environment may not contain DLLs or
the same version of DLLs that were used with the original client system. Use
bmrc to transfer these DLLs during the restore to the
C:\BMR\WINNT\SYSTEM32 directory. Alternatively, add the the location of that
DLL to the PATH environment variable.
External procedure logging

The following logs are created on the BMR master server during the restore
process:
/usr/openv/netbackup/logs/bmrrst/client_name/log.mmddyy (UNIX)
install_path\NetBackup\logs\bmrrst\client_name\log.mmddyy (Windows)
On UNIX and Linux systems, the BMR restore process writes external procedure
begin and end messages to the logs. (On Windows systems, the BMR restore
process does not perform begin and end logging.) You can use the bmrc
command in your external procedure scripts to write messages to the logs also.
Procedure Logging
External procedures write messages when they start and finish. A message
includes the following: the date and time that the procedure began, the client
name, and a description that includes the external procedure name. See the
following examples:
2005/08/02 12:10:38.180 w2k200,sol157 INFO: Executing External
Procedure: sol123,sol123_prerestore.
2005/08/02 12:10:38.350 w2k200,sol157 INFO: Completed executing
External Procedure: sol123,sol123_prerestore.
User Logging
You can use the bmrc command to write messages to the restore log. The
following is an example of a bmrc command that writes a message during a
restore of client sol123:
bmrc -operation create -resource message -client sol123 -msg
“message text to log”
Alternatively, you can pipe data to the bmrc command, as in the following
example:
echo "Hello World" | bmrc -operation create -resource log -client
sol123
The following is the log entry from the previous command:

Restoration log start time: 2005/03/28 10:59:27
Hello World.
Restoration log end time: 2005/03/28 10:59:27
When you start the bmrc command in an external procedure, specify the full
path to the bmrc command in the restore environment:
■ On UNIX and Linux clients: /usr/openv/netbackup/bin
■ On Microsoft Windows clients: %SystemDrive%\BMR\NBU\bin
At the first boot external procedure point, the path to the bmrc command is
install_path\NetBackup\bin on Microsoft Windows clients.
For more information about the bmrc command, see the NetBackup Commands
for UNIX or the NetBackup Commands for Windows guide.
External procedure operational states

During the operation of an external procedure, the following operational states
appear in the NetBackup Administration Console Bare Metal Restore Tasks
view:
Operational state Description
Discovery External Procedure An external procedure runs during the prediscovery

phase.
First Boot External Procedure An external procedure runs during the first boot
phase.
Post-restore External Procedure An external procedure runs during the postrestore

phase.
Pre-format External Procedure An external procedure runs during the preformat

phase.
Operational state Description
Pre-restore External Procedure An external procedure runs during the prerestore

phase.
External procedure exit codes

Ensure that external procedures exit with a return code of 0. If an external
procedure exits with a non-zero code, the restore pauses for input.
If it is acceptable for an external procedure to fail during the restore (that is, not
vital to system functionality), ensure that you exit 0 from the external
procedure.
External procedure error handling

By default, external procedures halt the restore process and await user action if
the procedure returns a non-zero return code.
For UNIX and Linux restores, the following menu appears:
What do you want to do next? Choices are:
a) Abort the restore.
r) Retry the external procedure again.
i) Ignore the error and continue the restore.
s) Escape to shell prompt, return here when done.
If you retry, a prompt asks if you want to transfer the external procedure again
from the BMR server before running it. The prompt lets you edit the external
procedure on the master server before running it again.
Note: When a UNIX first boot external procedure is started with no terminal
defined and the procedure returns non-zero, the Bare Metal Restore process
ends.
For Windows restores, a dialog box appears with the following choices:
■ Cancel halts the restore.
■ Try Again starts the external procedure again.
■ Continue ignores the error and continues with the restore.
If you try again, a prompts asks if you want to transfer the external procedure
again from the BMR server before running it. The prompt lets you edit the
external procedure on the master server before running it again.

External procedure environment variables

BMR sets and exports certain environment variables during the restore process.
Some are general environment variables; others are specific to BMR.
UNIX and Linux environment variables

The following environment variables are exported on all UNIX and Linux
systems:
Environment variable Value
$BMRC Pathname to the bmrc executable file

(/usr/openv/netbackup/bin/bmrc)
$bootServerAddress Boot server IP address
$clAddress The IP address of the client
$clAddressHex Client IP address converted to hex
$client_firstboot Name of client-specific, first boot external procedure
$client_postrestore Name of client-specific, post-restore external procedure
$client_prediscover Name of client-specific discover external procedure
$client_preformat Name of client-specific preformat external procedure
$client_prerestore Name of client-specific prerestore external procedure
$clName The name of the client.
$clOs BMR abbreviated OS specification
$configName The name of the configuration
$default_firstboot Name of OS default first boot external procedure
$default_postrestore Name of OS default postrestore external procedure
$default_prediscover Name of OS default prediscover external procedure
$default_preformat Name of OS default preformat external procedure
$default_prerestore Name of OS default prerestore external procedure
$defaultGateway The name of the default gateway
$extProcName Current external procedure name
$importNonRootVgs Import nonsystem volume and disk groups


Environment variable Value
$logging Log restore; yes=yes, no=no
$newConfig Name of the configuration to discover
$onEpError Restore behavior on External Procedure Error:

0=cancel
1=prompt
2=ignore
$runEp Start external procedures if found 0=no, 1=yes
$runMode Mode of BMR process discover or restore
$serverAddress NetBackup server IP address
$serverGateway Gateway to the NetBackup server
$serverName NetBackup server name
AIX environment variables:
The following exported operating system environment variables are set at
restore:
$BIDATA $HOME $LIBPATH
$NIM_HOSTNAME $NIM_HOSTS $NIM_NAME
$NSORDER $ODMDIR $PATH
$PWD $SHOWLED $SPOT
$SYSCFG_PHASE
HP-UX environment variables

restore:
$DEFAULT_RELEASE_DIR $EDITOR $ENV
$ERRNO $FCEDIT $HISTFILE
$HOME $IFS $INST_CLIENT_DIR
$INST_CUR_PRIMARY_PATH $INST_IS_BOOTP_SYSTEM $INST_LOG_FILE
$INST_NOT_TEST_MODE $LINENO $MAILCHECK

$OPTARG $OPTIND $PATH
$PPID $PS1 $PS2
$PS3 $PS4 $PWD
$RANDOM $SECONDS $SHELL
$SOURCE $SOURCE_LIF_FILE $SOURCE_NET_DIR
$SOURCE_TYPE $TMOUT
Solaris environment variables

restore:
$IFS $MAILCHECK $OPTIND
$PATH $PS1 $PS2
$PWD $TZ $_DVFS_RECONFIG
Windows environment variables

CMD is used to start the Windows command-line interpreter during restore.
The following exported operating system environment variables are available
during the restore:
%ALLUSERSPROFILE% %APPDATA% %CommonProgramFiles%
%COMPUTERNAME% %ComSpec% %HOMEDRIVE%

Storage area network support
Storage area network support

Bare Metal Restore can restore a system that is attached to a Storage Area
Network (SAN). On Windows, AIX, and Solaris systems, if the host bus adapter
(HBA) drivers are available, BMR automatically restores the SAN-attached
volumes. On HP-UX systems, BMR only restores the volumes that are not on the
SAN.
Note: BMR does not support the restoration of systems with SAN attached
volumes.
SANs and dissimilar disk restores

Solaris clients only.
After a Solaris system is recovered using the dissimilar disk restore feature, you
may need to perform the following steps for SAN-attached volumes that were
left unmapped (marked not to restore).
1 Determine the differences between the current and previous vfstab files:
% diff /etc/vfstab /etc/vfstab.old.bmr.dmr
2 Review the differences.
3 Copy the entries about the SAN devices from the
/etc/vfstab.old.bmr.dmr file. Add them to the /etc/vfstab file or
uncomment the corresponding lines that are commented out when vfstab
was merged.
4 Mount the file systems that are on the SAN.
5 Manually restore the SAN file systems using the NetBackup Backup,
Archive, and Restore interface.
SANs and dissimilar system restores

Windows clients only.
If you perform a dissimilar system restore on Windows and you want to restore
to a SAN disk, you must do the following:
■ Add the HBA drivers to the restore configuration. The HBA drivers can be
added the same way as any other mass storage device driver.
■ Reconfigure your SAN so that the HBA in the target system sees the same
devices as the HBA that existed in the source system.
To add drivers, see “Adding NIC and MSD drivers” on page 88.

Multiple network interface support

BMR recovery occurs in two major stages: boot stage and restore files stage. The
Boot stage uses a single network interface to talk to the BMR Boot Server. Once
the restore environment is loaded from the Boot Server, BMR configures and
activates all network interfaces for the restore files stage.
Note: Systems with multiple network interfaces are also known as multihomed
systems. BMR fully support multihomed clients.
The following diagram illustrates a configuration that can occur with

multihomed clients. For this configuration, specify the network interface for
Network 1 when you network boot the client.
Figure 6-6 Simple multihomed example
Client configuration using gateways

BMR clients can use gateways to communicate with BMR and NetBackup servers
during a restore operation. The following table describes three gateway attributes
used during a restore. You may not have to specify all gateways. If the client can
communicate with all hosts through the default gateway, you only have to specify
the default gateway. For network boots, specify the following:
■ The gateways for the NetBackup master and media servers in the Hosts dialog
box of the restore configuration
■ The default gateway in the Network Routes dialog box

For media boots, you are prompted for these values when you create the boot
media or during the restore.
Table 6-7 Network gateways
Gateway Description
Default Gateway Defines the default network gateway for the client during the
restore.
Master Server Gateway Defines the gateway from the client to the NetBackup master
server.
Media Server Gateway Defines the gateway from the client to the NetBackup media
server used to restore the files.
The following diagram shows how gateways can be used during a BMR client
restore. The client in this diagram cannot communicate with all of the servers it
needs to by using only the default gateway. For this configuration, you should
specify the default gateway as G1, the master server gateway as G2, and the
media server gateway as G3.
Figure 6-7 Gateway example


Port usage during restores
Port usage during restores
During restores, clients communicate with BMR boot servers through the
following services and ports. If the boot server is behind a firewall,
communication between the client server and boot server must be allowed
through these ports.
Table 6-8 Port usage during restores
Service Port UNIX Linux Windows
bootp/DHCP 67, 68 X X X
ping X
lockd Unreserved X X
mountd Unreserved X X
nfsd 2049 X X
portmapper 111 X X
rpcbind X1
statd Unreserved X X
tftp 69 X X X
vnetd 13724 X X X
Windows File Sharing 445 X

1.For bootparam on Solaris only.
Chapter 7
Managing shared resource
trees
The following tasks and related topics provide information about how to create
and manage shared resource trees.
Tasks
■ “Creating a shared resource tree” on page 111
■ “Adding software in a shared resource tree” on page 121
■ “Using a shared resource tree exclusively” on page 127
■ “Copying a shared resource tree” on page 129
■ “Repairing a damaged shared resource tree” on page 130
■ “Breaking a stale shared resource tree lock” on page 132
■ “Deleting a shared resource tree” on page 133
Related topics
■ “Shared resource tree overview” on page 107
■ “Shared resource trees view” on page 109
Shared resource tree overview

A shared resource tree (SRT) is a collection of the following:
■ Operating system files
■ Programs that format drives, create partitions, rebuild file systems, and
restore the original files using the NetBackup client software
108 Managing shared resource trees

Shared resource tree overview
An SRT also provides the resources that are needed to boot the client system
and begin the restore process.
The software in an SRT is not installed permanently on the protected system. Its
purpose is to bring the protected system to a state from which the original files
can be restored.
■ Unix and Linux systems: Each client type and operating system version
requires its own SRT. For example, Solaris 9 requires a Solaris 9 SRT, AIX 5.3
requires an AIX 5.3 SRT, and so on.
■ For Windows systems: A single SRT can restore all Windows versions.
For Unix and Linux systems, you create SRTs on boot servers of the same
operating system. The boot server must run the same version or a later version
of the operating system that is installed in the SRT. For example, a Solaris 9 SRT
must reside on a Solaris 9 or later boot server. For Windows systems, any
version of Windows can host the SRT. For information about the supported
operating systems for clients, SRTs, and boot servers, see the NetBackup Release
Notes.
During a restore, a client accesses the SRT from a boot server over a network, or
on a CD or DVD. Although SRTs reside on boot servers, you can do the following:
copy an SRT to CD media or DVD media, boot the client from that media, then
access the SRT on that media.
Depending on the operating system for which an SRT is created, the SRT
requires 100 MB to 600 MB of disk space. For disk space requirements, see the
NetBackup Release Notes.
Related topics
■ “Managing boot media” on page 135
Managing shared resource trees 109

Shared resource trees view

The Shared Resource Trees view shows all the SRTs that are defined for the
protection domain. Use the Refresh option to update the details pane with new
information retrieved from the master server. If an item is selected, only that
item is updated.
Figure 7-8 Shared resource trees window


Table 7-9 Actions for shared resource trees view
To Do the following
View SRT properties Right-click an SRT in the Bare Metal Restore Shared
Resource Trees pane and then select Properties from the
shortcut menu.
Use this option to determine the software that is installed
in an SRT.
Table 7-10 Shared resource tree view columns
Item Description
Name The name of the shared resource tree.
Operating System The operating system of the shared resource tree.
State The state of a shared resource tree can be:

■ READY. Ready for use. It can be copied, deleted, modified, or
allocated to a restore task.
■ LOCKED_READ. Locked against modification because it is in
the process of being copied. This SRT may be allocated to a
restore task. It cannot be copied, deleted, or modified until the
lock is released.
■ LOCKED_WRITE. Locked against all use because it is in the
process of being created or modified. No operations can be
performed on this SRT until the lock is released.
■ BAD. Unusable and cannot be repaired. For example, a boot
server crashes in the middle of an SRT deletion. Deletion is the
only operation that is allowed on the SRT.
■ DAMAGED. Unusable, but it may be possible to repair it. An
SRT operation was interrupted before it finished, such as when
you cancel the bmrsrtadm command using Ctrl+c and leave
the SRT on the server. You can try to repair a damaged SRT
(UNIX or Linux), or you can delete it.
Type The type of shared resource tree: network, CD, or legacy DOS.
Path The absolute path where the Web-shared resource tree resides on
the boot server.
Boot Server The BMR boot server where the shared resource tree resides.
Description A description of the SRT.


Creating a shared resource tree
A shared resource tree must be created on a local file system of the boot server.
BMR sets permissions for the SRT directory to allow read access to all and read
and write access to the root or Administrator user.
When you create an SRT, you install the operating system software and
NetBackup client software into the SRT. You also can install other software
when you create the SRT or at any time thereafter.
To create an SRT, you need the installation software or images for the following
items:
■ Operating system (Unix and Linux only).
■ For Linux SRTs, the Bare Metal Restore Third-Party Products CD. This CD
contains the open source products that may not be included in the vendor
Linux distribution.
■ Optional: other applications or packages (such as Veritas Volume Manager
or Veritas File System).
■ Optional: patches, maintenance levels, maintenance packs, service packs,
filesets, or the drivers that the operating system requires or other software
that is installed in the SRT. You must install into the SRT any operating
system patches that the NetBackup client software requires. If they are not
installed, NetBackup does not function correctly in the temporary restore
environment and the restore may fail.
For package or patch dependencies, see the “NetBackup Product
Dependencies” section of the NetBackup Release Notes.
If you need more than one SRT of the same operating system, create an SRT
with only the operating system and NetBackup client software. (For example,
you want to restore the clients that have different versions of Veritas Volume
Manager or different drivers.) Then make as many copies as you need and add
the different versions of the other software to the copies. If you copy an existing
SRT, it is usually faster than if you create an SRT.
During SRT creation, you are prompted for the path to the installation program
or software if you do one of the following:
■ Place the installation program in a removable media drive of the boot server.
Then provide the path to that removable media drive.
■ Copy the contents of the installation program to a local directory. Then
provide the path to that local directory.
■ Copy the installation program contents to a remote directory, available to
the boot server through NFS or network share. Then provide the path to that
remote directory or share location.
The amount of time needed to create an SRT is between 5 minutes to 60 minutes.

It depends on the speed of the system, the operating system of the SRT being
created, and other software being installed.
Tasks
■ “Creating an SRT for UNIX or Linux” on page 112
■ “Creating an SRT for Windows” on page 121
Creating an SRT for UNIX or Linux

Use the bmrsrtadm command to create a new SRT.
To copy an SRT to a bootable CD or DVD (create boot media), see “Creating boot
media for UNIX and Linux” on page 137.
To start the bmrsrtadm command

1 On the boot server where you want to create the SRT, change to the
following directory:
/usr/openv/netbackup/bin

./bmrsrtadm
The following appears:

Select one of the following options:
1. Create a new Shared Resource Tree.
2. Create a new CD image based Shared Resource Tree.
3. Copy an existing Shared Resource Tree to a new location.
4. Import a Shared Resource Tree.
5. Modify an existing Shared Resource Tree.
6. Delete an existing Shared Resource Tree.
7. List Shared Resource Trees available on this server.
8. Quit.
Enter your selection (1-8) [1] :
3 Select the option to create a new SRT.

4 To continue to create the specific SRT type, see the following:
■ “Creating an AIX SRT” on page 113
■ “Creating an HP-UX SRT” on page 114
■ “Creating a Solaris SRT” on page 116
■ “Creating a Linux SRT” on page 118

Creating an AIX SRT

When you create an AIX SRT, you are guided through the installation process of
the following:
■ The operating system software
The following prompts appear when you create an AIX SRT.
Prompt Action or explanation
Enter the name of the SRT to create The name of the SRT also is used for the directory that contains it.
Only alphanumeric characters and underscore (_) characters are allowed.
Enter the description of the new SRT A description of the SRT.
Enter desired OS level of AIX The prompt includes the levels you can create based on the operating
system version of the boot server.
Enter the directory in which to place The path to the directory in which to create the SRT. The root of the SRT
the new SRT (called the SRT path) is the pathname to the SRT location, which includes
the SRT name.
The default is either /export/srt or the directory where an SRT was
last created successfully.
The directory must already exist.
Source of AIX install images Enter the name of the device where the operating system installation
program is inserted or enter the path to the installation image.
After you enter the device name or host:/path, the operating system is
installed into the SRT.
Enter the source of the VERITAS Enter the device name where the NetBackup client software installation
NetBackup install images. program is inserted or enter the path to the installation image.
Specify a device name or an NFS path After you enter the device name or path, the NetBackup client installation
(host:/path form), or a local directory procedure installs the client software into the SRT.
The following appears when client software installation process begins:

Symantec Installation Script
Copyright 2007 Symantec Corporation, All rights reserved.
Installing NetBackup Client Software
NOTE: To install NetBackup Server software, insert the appropriate
NetBackup Server cdrom.
Do you wish to continue? [y,n] (y) Enter y.
Do you want to install the NetBackup Enter y.

client software for this client? [y,n] (y)

Enter the name of the NetBackup Enter any non-blank value; the server name is replaced at restore time
server: with the correct values for the BMR client being restored.
Would you like to use servername as Accept the default or enter any non-blank value. The client name is
the configured name of the NetBackup replaced at restore time with the correct values for the BMR client being
client? [y,n] (y) restored.
After you install the AIX and NetBackup software, the bmrsrtadm command
provides options to install other software in the SRT. You can either add other
software now or quit (you can add software later).
For information about how to add other software, see “Adding software in a
shared resource tree” on page 121.
Creating an HP-UX SRT

When you create an HP-UX SRT, you are guided through the installation
process:
■ Ignite software
Note: If the SRT is to be used to restore PA-RISC2-based clients, use

Ignite-UX 5.3x or later to create the SRT.
■ The operating system software

The following prompts appear when you create an HP-UX SRT.
Enter the name of the SRT to The name of the SRT also is used for the directory
create that contains it.
Only alphanumeric characters and the underscore (_)
character are allowed.
Enter the description of the new A description of the SRT.

SRT
SRT OS level The prompt includes the levels you can create based
on the operating system version of the boot server.

Enter the directory in which to The path to the directory in which to create the SRT.
place the new SRT The root of the SRT (called the SRT path) is the
pathname to the SRT location, which includes the
SRT name.
The default is either /export/srt or the directory
where an SRT was last created successfully.
The directory must exist.
Location (device or directory BMR searches for the following directory (x.x is
path) of the Ignite install media. either 11.00 or 11.11):
■ Ignite-UX/FILE-SRV-x.x/opt/ignite/data/Rel_B.x.x/
(BOSdatapath)
If the BOSdatapath directory is found, BMR expects
the Ignite installation image to be in one of the
following directories. (Note that -PA indicates Ignite
version B41.)
■ Ignite-UX/BOOT-KERNEL/opt/ignite/data
■ Ignite-UX/BOOT-KERNEL/opt/ignite/boot
■ Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data
■ Ignite-UX/BOOT-KERNEL-PA/opt/ignite/boot
If the BOSdatapath directory is not found, BMR looks
for a file named INSTCMDS from the tar file supplied
in one the following directories: (Note that -PA
indicates Ignite version B41.)
■ Ignite-UX/BOOT-KERNEL/opt/ignite/data
■ Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data
If the file is not found, BMR cannot install Ignite.
Enter the location (device or The variable x.x is the SRT operating system version.
directory path) of the HP-UX x.x
install media
The following patches are If your version of Ignite requires a patch, you are
required for this SRT: patch_list prompted to provide the path to the specific patch
that the version requires.
They can be found on an HP
support plus media, or they can
be downloaded from HP Web site.
Location (device or path) of the
media that contains patch_list:

Location (device or path) of the Enter the name of the device where the NetBackup
Veritas NetBackup install media client software installation media is inserted or enter
the path to the installation image.
After you enter the device name or path, the
NetBackup client installation procedure installs the
client software into the SRT.
The following appears when the NetBackup client

software installation process begins:
Copyright 1993 - 2007 Symantec Corporation, All
Rights Reserved.
NOTE: To install NetBackup Server software, insert
the appropriate NetBackup Server cdrom.
Do you wish to continue? [y,n] (y) Enter y.

y
Do you want to install the Enter y.

NetBackup client software for this
client? [y,n] (y)
Enter the name of the NetBackup Enter any non-blank value; the server name is
server: replaced at restore time with the correct values for
the BMR client being restored.
Would you like to use Accept the default or enter any nonblank value. The
"servername" as the configured client name is replaced at restore time with the
name of the NetBackup client? correct values for the BMR client being restored.
[y,n] (y)
After you install the HP-UX and NetBackup software, the bmrsrtadm command
sofware now or quit (you can add software later).
Creating a Solaris SRT

When you create a Solaris SRT, you are guided through the following
installation process:
■ The operating system software.

BMR can create a new SRT from the following:

■ The Solaris installation program
■ The installation program that copied to a local directory or a remote
directory
■ The Solaris software that is installed in an existing SRT. Furthermore:
For CD media, use the Software 1 of 2 CD.
If you create a Solaris 9 SRT by using a network shared CD, both slice 0 and slice
1 must be shared.
Related topics
■ “Patches, packages, and Solaris SRTs” on page 126
The following prompts appear when you create a Solaris SRT:
Enter the name of the SRT to create The name of the SRT also is used for the directory that contains
it.
Only alphanumeric characters and the underscore (_) character
are allowed.
Enter the description of the new SRT A description of the SRT.
Enter desired level of Solaris/SunOS The prompt includes the levels you can create based on the
operating system version of the boot server.
Enter the directory in which to place the new The path to the directory in which to create the SRT. The root of
SRT the SRT (called the SRT path) is the pathname to the SRT
location, which includes the SRT name.
The default is either /export/srt or the directory where an
SRT was last created successfully.
Enter a [hostname:/]pathname containing a Enter one of the following: the name of the device where the
suitable Solaris x.x Boot CDROM or SRT image installation program is inserted, the path to the installation
image, or the path to an existing Solaris SRT.
After you enter the device name or path, the operating system is
installed into the SRT.

Enter a [hostname:]/ pathname containing Enter the name of the device in which the NetBackup software
NetBackup client software installation media is inserted or enter the path to the installation
program (named install).
After you enter the device name or path, the NetBackup
installation procedure installs the client software into the SRT.
The following appears when the NetBackup client software

installation process begins:
Veritas Installation Script
Copyright 2006 Software Corporation, All rights reserved.
NOTE: To install NetBackup Server software, insert the
appropriate NetBackup Server cdrom.
Do you wish to continue? [y,n] (y) y Enter y.
Do you want to install the NetBackup client Enter y.

software for this client? [y,n] (y)
Enter the name of the NetBackup server: Enter any nonblank value; the server name is replaced at restore
time with the correct values for the BMR client being restored.
Would you like to use "servername" as the Accept the default or enter any nonblank value. The client name
configured name of the NetBackup client? [y,n] is replaced at restore time with the correct values for the BMR
(y) client being restored.
After you install the Solaris and NetBackup software, the bmrsrtadm command
sofware now or quit (you can always add software later).
Creating a Linux SRT

The first time you create an SRT on a Linux boot server, you are guided through
the installation software:
■ The operating system software.
■ BMR Third-Party Products, the open source products that may not be
included in the vendor Linux distribution. You can download a CD image at
no charge from
http://seer.support.veritas.com/docs/275782.htm.
■ NetBackup client software.

During this process, the bmrsrtadm command also copies files from the
operating system installation program and BMR third-party installation
program to the following directory:
/usr/openv/netbackup/baremetal/server/data/media
Each time thereafter that you create an SRT on that boot server, bmrsrtadm
uses those installation files. You do not have to enter the path to the installation
program or images. If you want to be prompted for installation program or
image location again, remove the media directory before running bmrsrtadm.
The bmrsrtadm command on Linux also allows you to specify the path to a file
system image file. (You also can specify a device path, a local directory path, or a
network directory path). For example, the BMR Third-Party Products CD is
distributed as an ISO file system image. You can download the image and use it
as the source image or write it to CD media.
The following are the prompts that appear when you create a Linux SRT:
Enter the name of the SRT to The name of the SRT also is used for the directory that
create contains it.
Only alphanumeric characters and the underscore (_)
character are allowed.
Enter the description of the A description of the SRT.

new SRT
Enter the directory in which to The path to the directory in which to create the SRT.
place the new SRT The root of the SRT (called the SRT path) is the
pathname to the SRT location, which includes the SRT
name.
The default is either /export/srt or the directory
where an SRT was last created successfully.
The following media is The prompt includes the Linux distribution (Red Hat or
required: SuSE) and the required disk.
Linux distribution - disc x of x The bmrsrtadm command prompts you for several of
the Linux installation discs.
Please load the media now.
Some systems try to mount the media that is loaded in
Load media from :
the CD drive automatically (such as the Red Hat
magicdev process). When you are prompted for media
on those systems, do the following: load the media into
the drive, close the drive tray, and wait for the drive
light to stop flashing before pressing Enter.

The following media is Enter the name of the device in which the BMR
required: Third-Party Products CD is inserted or enter the path
to the installation image.
BMR Third-Party Products CD
(3PPCD) This CD contains open source the components that
BMR uses on Linux systems.
Load media from:
The following media is Enter the name of the device in which the NetBackup
required: client software installation media is inserted or enter
the path to the installation image.
NetBackup x.x Client
After you enter the device name or path, the
NetBackup client installation procedure installs the
Load media from: client software into the SRT.
The following appears when the NetBackup client

software installation process begins:
Copyright 1993 - 2007 Symantec Corporation, All
Rights Reserved.
NOTE: To install NetBackup Server software, insert the
appropriate NetBackup Server cdrom.
Do you wish to continue? [y,n] Enter y.

(y) y
Do you want to install the Enter y.

NetBackup client software for
this client? [y,n] (y)
OS Level Options Always choose Red Hat 2.4, even when you create an
SuSE Linux SRT.
1. IBMzSeriesLinux2.4.21
2. RedHat2.4
q. To quit from this script
Enter the name of the Enter any nonblank value; the server name is replaced
NetBackup server: at restore time with the correct values for the BMR
client being restored.
Would you like to use Accept the default or enter any nonblank value. The
"servername" as the configured client name is replaced at restore time with the correct
name of the NetBackup client? values for the BMR client being restored.
[y,n] (y)

Adding software in a shared resource tree
After you install the Linux and NetBackup software, the bmrsrtadm command
sofware now or quit (you can always add software later).
Creating an SRT for Windows

Windows SRTs no longer require the user to supply a version of Windows. The
SRTs use a special version of Windows that is shipped with the boot server.
To create a Windows SRT

1 From the Start menu on the Windows BMR boot server that is to host the
SRT, select Programs > Veritas NetBackup > Bare Metal Restore Boot
Server Assistant.
The Bare Metal Restore Boot Server Assistant appears.
2 Click Shared Resource Tree Administration Wizard.
The Shared Resource Tree Administration wizard appears.
3 Select the option to create a shared resource tree. Then follow the prompts
to create a shared resource tree. You must provide the following
information:
■ Name. The name of the SRT also is used for the directory that contains
it. Only alphanumeric characters and the underscore (_) character are
allowed.
■ Description.
■ Location for the SRT.
■ Path to the NetBackup client software image.

Install additional software into an existing SRT only if it is required during the
restore. Additional software may include an operating system patch or fileset
that NetBackup client software requires. The software in an SRT is not installed
on the restored system. It only brings the protected system to a state from which
the original files can be restored. Therefore, you do not need to install the
following: patches, maintenance levels, maintenance packs, service packs,
filesets, or drivers into an SRT that are in a protected system.
Clustering software does not need to be installed into an SRT. After the local file
systems are restored, the client rejoins the cluster.
Tasks
■ “Adding software to a UNIX or Linux SRT” on page 122
■ “Adding software to a Windows SRT” on page 126
Adding software to a UNIX or Linux SRT

The bmrsrtadm command provides options to install the following additional
software in an existing UNIX or Linux SRT: (Not all options are supported on all
systems.)
■ Veritas NetBackup Maintenance Pack.
■ Veritas Volume Manager and Veritas File System.
■ Veritas Security Service.
■ Other software. The name of the option depends on the operating system.
Note: Use only the specific options from this list to add products to an SRT.
If you did not add required NetBackup software when you created the SRT, a
prompt appears to add it when you select the modify option.
After you add the NetBackup software when you create an SRT, the bmrsrtadm
command provides options to install other software in the SRT.
If you add software during SRT creation, continue with step 5 on page 123.
To add software to a UNIX or Linux SRT

1 On the BMR boot server where the SRT resides, change to the following
directory:

./bmrsrtadm

8. Quit.

3 Select the option to modify an existing shared resource tree.

4 Enter the name of the SRT to modify.
A menu similar to the following appears (the wording for option 4 depends
on the operating system that is installed in the SRT):
---------------------------------------------------------------
SRT name: srtname
Location: /export/srt/srtname
Description: SRT description
Exclusive use: (none)
---------------------------------------------------------------
You may make modifications to this SRT. What do you want to do?
1. Install Veritas NetBackup Maintenance Pack.
2. Install Veritas Volume Manager and Veritas File System.
3. Install Veritas Security Services.
4. Install additional drivers.
5. Change SRT description.
6. Change client exclusive use of this SRT.
7. Quit.
5 Select an installation option.

The bmrsrtadm command guides you through software installation.
Usually, you have to enter the path to the installation program or image for
the software. To continue, see the following information about the software
you install:
■ “Adding NetBackup maintenance packs” on page 123
■ “Adding Veritas Volume Manager and Veritas File System” on page 124
■ “Adding Veritas Security Services” on page 125
■ “Adding other software” on page 125
Adding NetBackup maintenance packs

If a NetBackup maintenance or feature pack is installed on the clients the SRT
protects, install that maintenance pack or feature pack in the SRT.
When you install a maintenance pack or feature pack, you are prompted for the
location of the installation program or image:
Location (device or path) of the Veritas NetBackup Maintenance Pack
media

Adding Veritas Volume Manager and Veritas File System

Not supported on Linux systems.
If Veritas Volume Manager (VxVM) and Veritas File System (VxFS) are installed
on the systems that the SRT protects, install them in the SRT. Then BMR can use
them to partition disks and rebuild file systems.
The VxVM and VxFS versions in the SRT must exactly match that of the client
being restored. If the versions do not match, the restored client software is
unable to access the file systems and volumes.
If protected clients have different versions of VxVM or VxFS, create a separate
SRT for each of those versions. However, SRTs that include VxFS and VxVM can
be used to restore the clients that do not have VxFS or VxVM installed. If you
need more than one SRT of the same operating system, create an SRT with only
the operating system and NetBackup client software. (For example, you want to
restore the clients that have different versions of VxVM or different drivers.)
Then make as many copies as you need and add the different versions of the
other software to the copies. To copy an existing SRT usually is faster than to
create an SRT.
Identify any prerequisites that VxVM and VxFS require, such as operating
system patches. Install them in the appropriate order before you install VxVM
and VxFS.
Caution: On Solaris systems, verify that any patches support the patchadd -C
flag; if they do not, do not install them into the SRT. Most patches for VxFS and
VxVM do not support the patchadd -C flag. Test results show that the clients
that use patched versions of VxFS and VxVM can perform a restore successfully.
They perform restores successfully even when they use an SRT that contains
unpatched versions.
The “Install Veritas Volume Manager and Veritas File System” option in the
bmrsrtadm command prompts you to:
Install Veritas License Software (prerequisite to below)
Install Veritas Volume Manager
Install Veritas File System
You do not have to untar and uncompress the packages before you install them
in an SRT. When you are prompted for the path to each component, enter a path
to the extracted packages. Or enter a path to the root directory of the
installation program (the directory that contains the file_system and
volume_manager directories).
For operating system dependencies for VxVM and VxFS, see the NetBackup
Release Notes.

Adding Veritas Security Services

If you use NetBackup Access Management to administer access to your
NetBackup environment, install the Veritas Security Services (VxSS) software.
When you select Install Veritas Security Services from the menu, you are
prompted to install the following:
Veritas Authentication subsystem (VRTSat)
Install the client Authentication subsystem (VRTSat) software into SRTs

that restores clients in the environments that use NetBackup Access
Management. The Authentication subsystem verifies who users are.
Veritas Authorization subsystem (VRTSaz)
Install the client Authorization subsystem (VRTSaz) into Solaris SRTs that
contain NetBackup media server software. Add this subsystem if the SRT
restores a media server that is backed up to its own devices and restores
itself from its own devices. The Authorization subsystem verifies that users
have permission to perform actions.
For each option, you must provide the path to the installation image, package,
fileset, or RPM (depending on OS).
For information about Access Management components and how to use Access
Management, see “Access Management” in the NetBackup Administrator's
Guide, Volume II.
Adding other software
Note: Use only the specific Veritas options to add Veritas products to an SRT.
The following menu options for other software depend on the operating system
of the SRT:
AIX Maintenance levels (MLs) or additional filesets
HP-UX No other software is required; therefore, you cannot add software
Linux Additional drivers
Solaris Additional packages or patches
When you install other software, you are prompted for the following: the
location of the installation program, image, package, patch, fileset, RPM, and so
on (depending on operating system).

Patches, packages, and Solaris SRTs

Always use the bmrsrtadm command to install patches and packages into
Solaris SRTs. The bmrsrtadm command prevents any damage from the
packages that do not support the pkgadd -R flag.
Patches that are installed into the miniroot that do not support the patchadd
-C flag can damage BMR boot servers as well as JumpStart servers. Therefore,
do not install the patches into an SRT that do not support the patchadd -C flag.
Installing device drivers into Linux SRTs

To add or update device drivers in a Linux SRT, choose Install additional drivers.
The following options are available to install or update kernel
drivers in the boot image:
1. Install a Red Hat driver update disk (.img file) into the boot
image.
2.Install a driver module (.o file) into the boot image.
3. None of the above, leave unchanged.
Enter your selection [3] :
Some hardware vendors provide drivers in a floppy image file. Use the first
option to install these drivers. This option installs both the kernel driver module
and any related hardware identification information that is contained in the
image.
To update an existing kernel driver module, choose the second option. Do not
use this option to add new driver modules. It loads the driver module only and
not the hardware identification information that is required to associate a new
driver with the corresponding hardware.
Adding software to a Windows SRT

You can install the following into an existing Windows SRT:
■ Windows service pack (Legacy SRTs only)
■ Veritas Storage Foundation for Windows
■ NetBackup Security Services
To add software to a Windows SRT

1 On the Start menu on the Windows BMR boot server that hosts the SRT,
click Programs > Veritas NetBackup > Bare Metal Restore Boot Server
Assistant.

Using a shared resource tree exclusively
3 In the Shared Resource Tree Administration wizard click Next on the
Welcome screen.
4 Select the option to update an SRT.
5 Select one of the following resources to add to the shared resource tree:
■ Add a Windows service pack to an SRT.
■ Add or update NetBackup client software images in an SRT. An SRT
must contain a NetBackup client image that is the same version as the
system(s) to be protected.
■ Add Veritas Storage Foundation for Windows to an SRT.
■ Add Veritas Security Services to an SRT.
6 Follow the prompts to add software to the shared resource tree.
For more information, see the Shared Resource Tree Administration wizard
help.

UNIX and Linux clients only.
If you save custom files with the client configuration, you can copy those custom
files into the SRT. They then are used in the temporary operating system
environment on the client during the restore. To do so, enable the SRT for
exclusive use by the client. Other clients cannot use that SRT until you disable it
from exclusive use, which removes the custom files from the SRT.
Enable exclusive use before you do any of the following:
■ Run a prepare to restore operation
■ Run a prepare to discover operation
■ Create a bootable CD or DVD (if you create a bootable CD or DVD that
contains an SRT that has custom files)
Note: If you enable an SRT for exclusive use before custom files are saved for
that client, the prepare-to-restore or prepare-to-discover process fails.
Related Topics
■ “Save custom files” on page 54
To enable or disable SRT exclusive use

1 On the boot server where the SRT resides, change to the following directory:
/opt/openv/netbackup/bin

./bmrsrtadm

8. Quit.
3 Select the option to modify an existing shared resource tree.

4 Enter the name of the SRT to modify.
A menu similar to the following appears:
---------------------------------------------------------------
---
SRT name: srtname
Location: /export/srt/srtname
Description: SRT description
Exclusive use: (none)
---------------------------------------------------------------
---
You may make modifications to this SRT. What do you want to do?
1. Install Veritas NetBackup Maintenance Pack.
2. Install Veritas Volume Manager and Veritas File System.
3. Install Veritas Security Services.
4. Install additional drivers.
5. Change SRT description.
6. Change client exclusive use of this SRT.
7. Quit.
5 Select the option to change exclusive use of the SRT.

This action reserves the SRT for the exclusive use by a
specified client. You may specify a client name here to reserve
this SRT for that client. If you leave this blank then the
exclusive use function will be disabled.

Copying a shared resource tree
Enter client name (or blank to disable) :
6 Enter a client name to enable exclusive use or press Enter without entering
anything to disable exclusive use.
Copying a shared resource tree

You can create a new SRT by copying another SRT.
The new SRT is created on the boot server where you run the bmrsrtadm
command (UNIX and Linux) or Shared Resource Tree Administration wizard
(Windows). The existing SRT may reside on either a local or a remote boot
server.
NFS services are required to copy an SRT that resides on a remote boot server.
The remote boot server must have NFS server services enabled.
An SRT that is in the process of being modified cannot be copied. Usually, it
takes several minutes to copy an SRT. However, it can take longer depending on
the size of the source SRT and the network speed if you copy to a different boot
server.
Copying an SRT on UNIX and Linux

On UNIX and Linux boot servers, use the bmrsrtadm command to copy an SRT.
To copy an SRT on UNIX and Linux

1 Change to the following directory on the boot server where you want to
create the SRT:

./bmrsrtadm

8. Quit.
3 Select the option to copy an existing shared resource tree.

Repairing a damaged shared resource tree
4 Use the following prompts to enter the required information:

■ The name of an existing SRT to copy.
■ The name for the new SRT.
■ The path on the boot server in which to create the SRT.
■ The description of the SRT.
■ (Linux only). The path to the device in which the BMR third-party
options CD is inserted or an installation image of the BMR third-party
options CD. (Only if the SRT is copied to a Linux boot server where an
SRT has not been created.)
Copying an SRT on Windows

On Windows boot servers, use the Shared Resource Tree Administration wizard
to copy an SRT.
To copy an SRT on Windows

1 On the Start menu on the boot server where you want to create the SRT,
Assistant.
3 In the Shared Resource Tree Administration wizard, select the option to
copy an SRT and then follow the prompts. You must enter or select the
following:
■ The name of an existing SRT to copy.
■ The name for the new SRT.
■ A description for the new SRT.
■ The path on the boot server in which to create the SRT.

UNIX and Linux boot servers only.
If BMR places an SRT into a DAMAGED state, it may be possible to repair it to
return it to a READY state. If an SRT is marked DAMAGED because a previous
bmrsrtadm command is interrupted, recovery is likely. If you are unsure why
an SRT was marked DAMAGED, delete it and create a new one from scratch.
SRT states appear in the Shared Resource Trees view of the NetBackup
Administration Console. You can view SRT states on UNIX and Linux systems,
by using the list shared resource trees option of the bmrsrtadm command.

For a description of the SRT states, see “Shared resource trees view” on
page 109.
To attempt recovery of a damaged SRT

1 Change to the following directory on the boot server on which the SRT
resides:

./bmrsrtadm

8. Quit.
3 Select the option to modify an existing shared resource tree. The following
appears:
Enter the name of an existing SRT:
4 Enter the name of the damaged SRT.

The SRT you selected is in a DAMAGED state. This typically
means that an interrupt occurred while previously performing
some operation on the SRT.
If you believe this SRT is still usable, you may choose to
continue.
If you are not sure this SRT is still usable, you should not
continue and should choose to delete the SRT instead.
Are you sure you want to continue? (y/n) :
5 Enter y.
The bmrsrtadm program attempts to repair the SRT. The program guides
you through installation of any missing SRT components.
If repair is successful, the bmrsrtadm modify menu appears. When you
quit the program, the SRT is in a READY state.

Breaking a stale shared resource tree lock
Breaking a stale shared resource tree lock
UNIX and Linux boot servers only.

An SRT in the LOCKED_READ or LOCKED_WRITE state is busy and most
operations are not allowed. To manage a locked SRT, you should wait for the
process using the SRT to finish and release the lock before you proceed. (The one
exception is that you can allocate an SRT in a LOCKED_READ state to a restore
task.)
In rare cases, an SRT may be left with a stale lock. For example, if a boot server
crashes or is rebooted in the middle of an SRT operation, the SRT may be left
locked. If you are sure that an SRT lock is stale, you can break the lock.
Do not attempt to break an SRT lock unless you are positive it is stale. If you
break the lock of an SRT while it is in use, it may become corrupted.
SRT states are displayed in the Shared Resource Trees view of the NetBackup
Administration Console. Alternatively, on UNIX and Linux systems, you can
view the SRT states by using the list shared resource trees option of the
bmrsrtadm command.
For a description of the SRT states, see “Shared resource trees view” on
page 109.
To break a stale SRT lock

1 Change to the following directory on the boot server on which the SRT
resides:

./bmrsrtadm

8. Quit.
3 Select the option to modify the Shared Resource. The following appears:
Enter the name of an existing SRT :
4 Enter the name of the locked SRT and press ENTER. The following appears:

Deleting a shared resource tree
The SRT you selected is in a LOCKED state. This typically means
that the SRT is busy, and you should wait for it to come unlocked
before you continue.
Would you like to wait for the SRT to come free? (y/n) [y] :
Caution: If you break the lock of an SRT while it is in use, it may become
corrupted.
5 Enter n to break the lock.

If you are ABSOLUTELY SURE nobody is using this SRT and this is a
stale lock, you may choose to break the lock and continue.
If you break the lock while somebody is using the SRT, you may
corrupt the SRT.
Are you ABSOLUTELY SURE you want to break the lock and continue?
(y/n) [n] :
Caution: If you break the lock of an SRT while it is in use, it may become
corrupted.
6 Enter y to break the lock.

The stale lock is broken, and the bmrsrtadm command modify menu
appears. When you quit the program, the SRT is in a READY state.

You can delete an SRT by using the bmrsrtadm command (UNIX and Linux boot
servers) or Shared Resource Tree Administration wizard (Windows boot
servers).
An SRT that is allocated to a restore task or being modified cannot be deleted.
Deleting an SRT on UNIX and Linux

On UNIX and Linux boot servers, use the bmrsrtadm command to delete an
SRT.
To delete an SRT by using the bmrsrtadm command
1 Change to the following directory on the boot server where the SRT resides:


./bmrsrtadm

8. Quit.
3 Select the option to delete an existing shared resource tree.

You are prompted to enter the SRT name.
4 Type the name of the SRT and press Enter.
You have chosen to delete the "srtname" SRT from the server.
Are you sure you want to delete this SRT? (y/n) :
5 Enter y to delete the SRT.

If the SRT is locked, this operation fails.
See “Breaking a stale shared resource tree lock” on page 132.
Deleting an SRT on Windows

On Windows boot servers, use the Shared Resource Tree Administration wizard
to delete an SRT.
To delete an SRT by using the shared resource tree wizard

1 On the Start menu on the Windows BMR boot server that hosts the SRT,
Assistant.
3 In the Shared Resource Tree Administration wizard, select the option to
delete an SRT. Then follow the prompts.
Chapter 8
Managing boot media
The following provide information about how to create and manage boot media.
Tasks
■ “Creating boot media for UNIX and Linux” on page 137
■ “Creating boot media for Windows” on page 139
Related topics
■ “Boot media overview” on page 135
■ “About writing a CD or DVD” on page 136
Boot media overview

Boot media is used to boot a client and provide the shared resource tree or the
resources to mount a shared resource tree. The boot media contains a small
runtime environment that includes a kernel, a RAM file system, libraries, and
programs. The client system firmware boots the kernel from the media. CD boot
media also contains a shared resource tree.
If you use media to boot the client system, you must use BMR to prepare the
appropriate boot media. You can prepare boot media at any time before the
restore. However, a prerequisite is that the shared resource tree for the
protected system must exist.
Boot media is created from the resources that are stored in an SRT. The boot
media must be compatible with the commands and libraries in the SRT and the
client.
136 Managing boot media

About writing a CD or DVD
About writing a CD or DVD
Note: The size of the media boot image that BMR produces depends on the
following: the optional software packages on the SRT, the operating system
version, and the install media type used (where applicable) during media boot
image creation. The structure of the installation program can change from one
release to another and from one type of media (CD) to another (DVD). Therefore,
sizes of the produced final images may be different under seemingly identical
conditions.
In all cases, if the final media boot image that BMR produces fits on a CD, burn
the image to a CD or a DVD. However, if the final image cannot fit on a CD, you
must burn a DVD.
CD/DVD media must be bootable by the system for which you create it. To
determine the correct way to create a bootable CD/DVD for the specific system,
see the instructions that are provided with your CD/DVD writing software.
In addition, consider the following:
■ The CD/DVD image that is created for AIX, Linux, and Solaris uses ISO-9660
format. HP-UX uses a binary format that is different from ISO.
■ BMR does not contain CD/DVD writing software. Burn the CD/DVD image
onto a CD/DVD using CD/DVD writing software that supports the following:
ISO-format images for AIX, Linux, and Solaris or binary images for HP-UX.
The procedures for writing CDs/DVDs vary between applications; refer to
the documentation for procedures.
■ The CD/DVD writing software may require that ISO-format or binary CD/
DVD image files end in a .iso extension. If necessary, you can add a .iso
extension to the CD/DVD image before you write it.
■ If the BMR boot server does not have CD/DVD writing hardware and
software, transfer the CD/DVD image to a system that does. Ensure that the
CD/DVD image file transmits as a binary file and transfers without errors;
corrupted CD/DVD image files produce unpredictable results.
■ For the CD/DVD media that includes an SRT, the name of the SRT appears as
the content of the root directory on the CD/DVD.
■ Label the CD/DVD for easy identification. Include the following: the client
name (Windows clients), the NetBackup version that is used, the operating
system of the SRT that is installed, and any extra software installed.
■ BMR does not use the CD/DVD image file after it is created. Therefore, you
can move, rename, or delete the image file after you write the CD/DVD.
Managing boot media 137

Creating boot media for UNIX and Linux

On UNIX and Linux systems, use the bmrsrtadm command to create a bootable
CD/DVD image that contains an SRT. After you create the CD/DVD image, you
must use CD/DVD writing software to burn the image onto a CD/DVD.
This process copies an existing SRT to the CD/DVD media; therefore, an SRT
that supports the client must exist.
The following is the required information:
■ The name of the SRT you want to use.

■ The name to use for the SRT on the CD/DVD.
■ The path to a directory that has enough free space to store the CD/DVD
image.
To start the bmrsrtadm command

1 On Solaris systems only, use the following command to verify that the vold
process is not running on the boot server where the SRT resides:
# ps -ef | grep vold
If it is running, do the following:

a Eject any CD/DVD that may be loaded:
# eject
b Stop the vold process:

# /etc/init.d/volmgt stop
2 On the boot server where the SRT resides, change to the following directory:

./bmrsrtadm

2. Create a new CD/DVD image based Shared Resource Tree.
8. Quit.
4 Select the option to create a new CD/DVD image based shared resource tree.

5 To continue to create the CD/DVD image, see the following for more
information about the operating system type:
■ “Creating boot media for AIX” on page 138
■ “Creating boot media for HP-UX” on page 138
■ “Creating boot media for Linux” on page 139
■ “Creating boot media for Solaris” on page 139
Creating boot media for AIX

You must have the AIX installation program that created the SRT that you want
to use to create the boot media copy to the CD/DVD. (You must have it even if
you created the SRT from a network copy of the media.) You must enter the
device name that contains the installation program.
The directory for the CD/DVD image should not be a direct prefix of the
directory that contains the SRT you intend to use. For example, for SRT /
export/srt/aix433esm:
■ Do not specify /, /export, or /export/srt for the location.
■ You can specify /export/srt/mb because it is not a direct prefix of the
SRT path.
Creating boot media for HP-UX

HP-UX uses a binary format that is different from ISO. The CD/DVD image file is
a binary image of the CD/DVD and does not contain an extension. However, you
can add an .iso extension to the CD/DVD image if your CD/DVD writing
software requires it.
The CD/DVD recording programs that are known to work for HP-UX images are
as follows:
■ Sony CD/DVD Extreme. Add an .iso extension to the image file name and
use the Global Image or Other Image option from the File menu options.
■ Nero. Add an .iso extension to the image file name, and use the Burn Image
to Disc option.
Note: The ROXIO Easy CD/DVD Creator recording program does not work for
HP-UX images.
Managing boot media 139

Creating boot media for Windows
Creating boot media for Linux

For Linux, the bmrsrtadm command creates a bootable ISO image file by using
the name of the SRT with an .iso extension. Any standard CD/DVD writing
software can be used to write media from this file.
Creating boot media for Solaris

You must have the Solaris installation media (Software 1 of 2) that created the
SRT you copy to the CD/DVD. You must enter the device name that contains the
installation media.
After you enter the information about the SRT, the following information
appears:
■ If Veritas Volume Manager (VxVM) is installed on the BMR boot server, the
following prompt appears:
What do you want to use for temporary space?
1. Use a disk group.
2. Use a raw partition.
Enter 1 or 2. Then enter the name of the disk group or the device file for the
raw partition. If you use a raw partition for temporary storage, you are
prompted to continue.
■ If Veritas Volume Manager (VxVM) is not installed on the BMR boot server,
the following prompt appears:
Enter the name of a partition of size 103040 or more blocks
Enter the name of the device file for the raw partition. Then respond to the
next prompt if you want to continue.
After the CD/DVD image is created, restart the vold process (/etc/init.d/
volmgt start) if you stopped it before running bmrsrtadm.

Windows systems may create a bootable ISO image which can be burned to
either a CD or DVD.
To create boot media for a Windows client

1 On the Windows BMR boot server, select Programs > Veritas NetBackup >
Bare Metal Restore Boot Server Assistant from the Start menu.
The Bare Metal Restore Boot Server Assistant screen appears.

3 Select the option for Create a Bootable CD/DVD from a Shared Resouce Tree.
4 Follow the prompts to create the boot media.
For more information, see the wizard help.

Chapter 9
Managing Windows driver
packages
The following provides information about adding Windows software packages
to BMR and managing those packages.
Tasks
“Adding a Windows driver package” on page 143
“Deleting a Windows driver package” on page 144
Related topics
“Packages overview” on page 141
“Packages view” on page 142
Packages overview
Windows packages are network interface card (NIC) drivers and mass storage
device (MSD) drivers. Packages are stored in the BMR database on the
NetBackup master server. The packages pool is comprised of the packages that
are stored in the database. The packages pool is the common pool of packages
that can be added to restore configurations.
Packages may be required when you restore to a different system, in which case
you add them to the restore configuration. If the Packages view does not contain
a driver that is required for a dissimilar system restore, add it to Bare Metal
Restore. Do not add it to the restore configuration if a driver is on the Windows
installation media that created the SRT.
If a package required for a dissimilar system restore already appears in the
Packages view, add it to the restore configuration by using the procedures in
“Devices and Drivers” on page 160.
142 Managing Windows driver packages

Packages view
Packages view
The Packages view shows all the Windows drivers in the BMR packages pool. Use
the Refresh option to update the details pane with new information retrieved
from the master server. If an item is highlighted, only that item is updated.
If a package includes Discovered in the description, it was discovered during a
backup of a protected client.
Figure 9-9 Packages window

c
Table 9-11 Actions for packages
To Do the following
Delete a package Right click the driver in the details pane and then
select Delete on the shortcut menu.
Managing Windows driver packages 143

Adding a Windows driver package
Adding a Windows driver package
Add a package as follows:

■ Use the Driver Package wizard on any Windows boot server to add a network
interface card (NIC) driver or mass storage device (MSD) driver.
■ Alternatively, install NetBackup client software on the target system and
perform a full BMR backup. The drivers are saved in that client’s
configuration and available for use during a dissimilar system restore.
Before you can add a package, you must have the installation files for the
package. Obtain them from one of the following: the vendor’s Web site, the
installation program that is provided with the NIC device or MSD device, or
another BMR Windows client in your environment.
Note: You can add only NIC and MSD drivers. All other types of drivers (audio,
video, modem, and so on) must be installed on the system after the restore is
complete.
To add a driver package by using the Windows software package wizard

1 On the Start menu on any Windows boot server, click Programs > Veritas
NetBackup > Bare Metal Restore Boot Server Assistant.
2 In the Bare Metal Restore Boot Server Assistant, click Driver Package
Wizard.
3 In the Driver Package wizard, follow the prompts as follows to add the
software package:
■ Path to the installation files for the package.
■ Description of the package.
■ Version of Windows that the package can be used with.
■ The specific driver from the package installation files (installation files
may include more than one driver).
Finding the correct driver

A driver information file (.inf or txtsetup.oem) may contain information
about more than one driver. Therefore, when you add a mass storage device
(MSD) or network interface card (NIC) driver, you may have to select from more
than one option.
The devices should be documented in the materials that come with the
computer. If not, contact the manufacturer for the driver option.
144 Managing Windows driver packages

Deleting a Windows driver package
Alternatively, use the following procedure to determine the correct name for the
driver if Windows is installed.
To find the correct driver if Windows is already installed on the computer

1 On the computer that contains the mass storage device adapter, open the
Windows device manager.
2 Expand the category for the adapter (for example, Network Adapters).
3 Note the device name that appears here. The option name in the .inf file
should be the same or similar to this one.
Deleting a Windows driver package

The following procedure deletes a driver package.
Caution: Do not delete any drivers that are required for a restore.
To delete a driver package

1 In the NetBackup Administration Console on the NetBackup master server,
click Bare Metal Restore Management > Resources > Packages.
2 In the details pane, right click the driver you want to delete.
3 Select Delete on the shortcut menu.
4 In the confirmation screen, click Yes.
The selected package is deleted.
Chapter 10
Managing clients and
configurations
The following provide information about how to create and manage clients and
configurations.
Tasks
■ “Copying a configuration” on page 150
■ “Discovering a configuration” on page 152
■ “Modifying a configuration” on page 155
■ “Deleting a configuration” on page 156
■ “Deleting a client” on page 156
Related topics
■ “Client configuration overview” on page 145
■ “Bare Metal Restore Clients view” on page 146
■ “Discovered Configurations view” on page 148
■ “Change Configuration dialog box” on page 157
Client configuration overview

Logically, a BMR client is a collection of configurations. A configuration is a
collection of information about the system to be used as a template to rebuild a
protected system. It includes the following: number of disk drives, volume
information, file system information, number and type of network adapters,
network properties, drivers, and other system software components. Most BMR
operations are performed on configurations.
146 Managing clients and configurations
Bare Metal Restore Clients view
When a BMR protected client is backed up, the configuration of the client is
saved and named current. Every time a client is backed up, the new saved
configuration replaces the previously saved configuration.
The saved, current configuration is read-only. Use the current configuration to
restore the original protected system to its state at the most recent backup (a
standard or self restore). To restore to a different point in time, to different disks,
or to a different system, create a restore configuration by copying a current
configuration. Then modify the restore configuration.

The Bare Metal Restore Clients view shows the clients that BMR protects and the
configurations for each client. You can expand the configuration for a client to
see its following components:
■ Devices & Drivers shows the devices and drivers that were discovered in the
system. Microsoft Windows clients only.
■ Hosts shows the NetBackup media servers, Bare Metal Restore boot servers,
and network hosts that are used during a restore.
■ Network Interfaces shows the interfaces that are defined in the
configuration.
■ Network Routes shows network routes that are defined in the configuration.
Microsoft Windows clients only.
■ Volumes shows the volumes (and their layouts) in a configuration.
Use the Refresh option to update the details pane with new information
retrieved from the master server:
■ If the Bare Metal Restore Clients node is selected, all the clients and
configurations are updated.
■ If a single client is selected, all the configurations for that client are
updated.
■ If a single configuration is selected, only that configuration is updated.
Managing clients and configurations 147

Figure 10-10 Bare Metal Restore clients window
Table 10-12 Actions for Bare Metal Restore clients view
To Do the following
Prepare to restore Right click a client and then select Prepare to Restore on the
shortcut menu.
Prepare to discover Right click a client and then select Prepare to Discover on
the shortcut menu.
Copy a configuration Right click a configuration in the All Bare Metal Restore
Clients tree view and select New on the shortcut menu.
Then complete the fields in the New Configuration dialog
box.
Modify a configuration Right click a configuration in the All Bare Metal Restore
Clients tree view, select Change from the shortcut menu, and
then modify the configuration. The current configuration
cannot be modified.
See “Modifying a configuration” on page 155.
Discovered Configurations view
Table 10-12 Actions for Bare Metal Restore clients view
To Do the following
Delete a configuration Right click a configuration in the All Bare Metal Restore
Clients tree view. Then select Delete from the shortcut menu.
Delete a client Right click a client and then select Delete on the shortcut
menu.

The Discovered Configurations view shows all the configurations that were
created by discovering clients. A discovered configuration contains information
about physical disks, devices, and other hardware that is attached to the system.
Use the Refresh option to update the details pane with new information
retrieved from the master server.
Usually, you discover the configuration of a target system so you can do the
following: map disks during a dissimilar disk restore or map the attributes of a
protected system to the target system during a dissimilar system restore.

Figure 10-11 Discovered configurations window
Table 10-13 Actions for discovered configurations view
To Do the following
View a configuration’s properties Right click a configuration in the details pane and
then select Properties on the shortcut menu.
Delete a configuration Right click a configuration in the details pane and

then select Delete on the shortcut menu.
Discover a configuration Click Actions > Prepare to Discover.


Copying a configuration
Copy a configuration so you can do the following:

■ Restore a client to a state that was saved in a backup before the last backup.
For more information, see “Restoring to a specific point in time” on page 81.
■ Restore a client in which the disks have changed.
For more information, see “Restoring to dissimilar disks” on page 83.
■ Restore a Windows client to a different system.
For more information, see “Restoring to a dissimilar system” on page 86.
■ Restore a client to the same hardware but with different network properties.
A copied configuration that is used for a restore is a restore configuration. After
you create the restore configuration, modify it so it matches the target hardware
properties.
Note: You do not have to modify the point in time restore configuration.
To copy a configuration
2 In the All Bare Metal Restore Clients tree pane, expand the view of the client
that contains the configuration you want to copy.
3 Right click the configuration you want to copy.
4 On the shortcut menu, select New.
5 On the New Configuration dialog box, complete the fields.
6 Click OK.
To modify the configuration, see “Modifying a configuration” on page 155.
New configuration dialog box

Use the New Configuration dialog box to select one of the following operations:
■ Copy/Import configuration. This operation allows you to change
configuration values when you perform a dissimilar disk restore or
dissimilar system restore.
■ Retrieve from backup. This operation allows you to restore the client to its
state on the date of the backup (point-in-time configuration).

Figure 10-12 New configuration dialog box
Table 10-14 New Configuration dialog box items
Item Description
New configuration name Enter the name of the new configuration.
Copy/Import a Select to copy an existing configuration of the client so you

configuration can edit it.
Source configuration Select the configuration you want to copy.
Retrieve from backup Select this item to retrieve a configuration from the client’s
backup image. This read-only configuration restores the
system to the state that was saved at the time of the backup.
Policy Select the name of the policy that is used to back up the
client. Backups from the selected policy appear in the End
date field.
End date Select the date of the backup from which to retrieve the
configuration.
If the backup policy uses multiple data streams to back up the
client, data streams for each backup job appear in the End
date field. Select the most recent stream of the backup job on
the date to which you want to restore. Normally, backup jobs
occur on separate days. Seconds or minutes separate data
streams within the same backup job.

You can discover the configuration of a new system; the system does not have to
be a NetBackup client. A discovered configuration contains the hardware and
the software information of a host.
When you discover a configuration, BMR adds it to the discovered
configurations pool. The elements of the configuration (such as disk layout) can
then be used when you perform operations such as dissimilar disk restore.
To discover a configuration
1 In the Bare Metal Restore Management node, click Actions > Prepare to
Discover.
2 In the Prepare to Discover dialog box, complete the fields and enter data as
necessary.
If you select a client in the Hosts > Bare Metal Restore Clients view, the
values for that client are included in the dialog box.
If a client is the target of a dissimilar disk restore (DDR) and VxVM manages
the protected client’s disks, specify an SRT with VxVM installed.
3 Click OK.
4 Boot the client to start the hardware discovery operation.
If you use media boot, when BMR prompts for the client name, enter it as it
appears in the Tasks view from the prepare-to-discover operation.
When the discovery operation ends, the following occurs on the client, and the
configuration appears in the Discovered Configurations view:
■ AIX clients display B55 on the LED display.
■ HP-UX, Linux, and Solaris clients display the following message:
The Bare Metal Restore hardware discovery boot has concluded.
■ Windows clients display a popup box stating that the discovery is finished,
and that you can click OK to reboot the system.
Prepare to Discover dialog box

Use this dialog box to discover the configuration of a system. The system does
not have to be a NetBackup client.

Figure 10-13 Prepare to Discover dialog box
If a client is selected in the NetBackup Administration Console window, the

values and options for that client appear or are included in drop-down lists.
When you discover a configuration, it is added to the discovered configurations
pool. The elements of the configuration (such as disk layout) then can be used to
perform operations such as dissimilar disk restores.
Table 10-15 Prepare to Discover dialog box items
Item Description
Operating system The operating system of the machine to discover. If a client is

selected, the value for that client appears.
Shared resource tree The shared resource tree to use for the discovery operation. If a
client is selected, the list includes the SRTs that match that
client’s operating system and level.
Specify an SRT with Veritas Volume Manager (VxVM) installed
in the following situation: you discover a client that is the
target of a dissimilar disk restore and VxVM manages the
protected client’s disks.
Item Description
Architecture The architecture for the system. If a client is selected, the value
for that client appears.
NetBackup master server The IP address of the NetBackup master server.

IP address
Gateway to the The gateway to reach the NetBackup master server during the
NetBackup master server discovery operation.
Console device name AIX systems only. The name of the device to write messages to.
If you do not enter a device, the LEDs on the machine to
discover are used to display operational status.
Linux systems only. The name of the device to use as system
console. To use the system default, leave this field blank. For a
virtual console, specify a device name such as tty1. For a serial
console, specify a device name and speed such as ttyS0,5760.
For information about console naming conventions, see the
serial-console.txt Linux kernel documentation file.
If a client configuration was selected for the discovery
operation, the field is populated with the values from the
configuration.
Preload values from Active if Prepare to Discover is selected from the Clients view.
interface Select an interface to populate the network properties with the
values from the interface.
IP address The IP address of the machine to discover. If an interface is

selected in the Preload Values from Interface field, the value
from that interface appears.
Network mask The network mask of the machine to discover. If an interface is

Default gateway The gateway for the network routes during the discovery
operation. If an interface is selected in the Preload Values from
Interface field, the value from that interface appears.
Hardware MAC address The media access control (MAC) address of the interface that is
used to boot the client at discovery time. If an interface is
New configuration name The name for the configuration that the discovery operation
creates.

Modifying a configuration
Item Description
Run external procedure Run external procedures during the discovery operation. You
must create the external procedures and add them to the BMR
database.
See “Using external procedures” on page 93.
Enable logging Log events on the master server. Enable logging if you have
adequate space in the file system on which the NetBackup log
directory resides on the master server. Discovery can increase a
restore log file up to 15 MBs.
Modifying a configuration
Modify a configuration so you can do the following:
■ Restore a client to a state that was saved in a backup before the last backup.
■ Restore a client in which the disks have changed.
For more information, see “Restoring to dissimilar disks” on page 83.
■ Restore a Windows client to a different system.
For more information, see “Restoring to a dissimilar system” on page 86.
■ Restore a client to the same hardware but different network properties.
You cannot modify the configuration named current; you must create a
configuration you can edit.
For procedures, see “Copying a configuration” on page 150.
To modify a configuration
2 In the All Bare Metal Restore Clients pane, expand the view of the client that
contains the configuration you want to modify.
3 Right-click the configuration you want to modify.
4 On the shortcut menu, select Change.
5 In the Change Configuration dialog box, modify properties as needed.
See “Change Configuration dialog box” on page 157.

Deleting a configuration
Deleting a configuration
You cannot delete a current configuration.
To delete a configuration
contains the configuration you want to delete.
3 Right-click the configuration you want to delete.
4 On the shortcut menu, select Delete.
5 In the confirmation dialog box, click Yes.
Deleting a client
When you delete a client, it removes only the client and its configuration from
the BMR database. It does not remove the NetBackup software on the client, nor
remove it from NetBackup, nor delete the backups of the client.
If you delete a client but do not remove it from the NetBackup policy that backs
it up, the following occurs: the client is reregistered with BMR the next time it is
backed up and appears in the Bare Metal Restore Clients view. (The NetBackup
policy that backs it up is the policy that collects BMR information.)
To delete a client
2 Right-click the client you want to delete.
3 On the shortcut menu, select Delete.
4 In the confirmation dialog box, click Yes.

Change Configuration dialog box
Use the Change Configuration dialog boxes to map the attributes of the
configuration on the protected system to the restore configuration. Map the
configurations to enable point-in-time restore, dissimilar disk restore, or
dissimilar system restore.
This section contains the following sub-sections:
■ “Configuration summary” on page 158
■ “Devices and Drivers” on page 160
■ “Hosts” on page 163
■ “Network interfaces” on page 165
■ “Network routes” on page 169
■ “Volumes” on page 171
Configuration changes are saved differently depending on which of the
following NetBackup administration interfaces you use:
■ In the Windows-based Administration Console, changes occur when you
click OK or Apply.
■ In the Java-based Administration Console, changes occur when you make
them.
To open the change configuration dialog box

contains a copied configuration.
You cannot open and edit the current configuration.
3 Right-click the copied configuration.
4 On the shortcut menu, select Change.

Configuration summary
Use Configuration Summary to do the following:
■ View a summary of the configuration
■ Change a license key for software on the protected system that requires a
license key
■ Determine the components of the restore configuration so you can select an
SRT that has the appropriate software for the restore
Figure 10-14 Configuration summary


Table 10-16 License key actions
Action Description
Add License Key Opens a dialog box in which you can add the license key for the
selected software.
Change License Key Opens a dialog box in which you can change the license key for
the selected software.
Remove License Key Deletes the selects license key.
Table 10-17 Client items
Item Description
Name The name of the client.
Operating system The operating system of the client.
Service pack Windows clients only. The service pack version on the client.
Architecture UNIX and Linux clients only. The architecture of the client.
NetBackup version The NetBackup software version on the client.
Veritas Volume The version of Veritas Volume Manager or Veritas Storage

Manager version Foundation for Windows (if any).
Table 10-18 Configuration items
Item Description
Name The name of the configuration.
State The state of the configuration. Saved indicates a configuration

that cannot be edited. Copied indicates that the configuration can
be edited.
Last modification The date and time the configuration was last modified.
Version The version of the configuration.


Devices and Drivers

Microsoft Windows clients only.
Use the Devices & Drivers dialog box to perform the following actions:
■ Initialize the devices in this configuration from a new hardware discovered
configuration or from another client's configuration.
■ Automatically select the correct mass storage device (MSD) drivers and
network interface card (NIC) drivers for the listed devices.
■ Manually add MSD and NIC drivers to the configuration.
You can also specify whether to use only BMR discovered drivers.
Figure 10-15 Devices & Drivers dialog box

Table 10-19 Hosts mapping actions
Action Description
Initialize Prompts you for another configuration from which to import the devices.
Devices... You may select a discovered configuration or one from another client.
button The initialize operation updates the Drivers packages to be used during
restore window to include the necessary drivers for this hardware.
Map Drivers Automatically matches drivers to devices without drivers. If drivers are
button added to BMR after the last initialize operation, repeat this action.
Sometimes, it may be useful to override the driver selected automatically
by using the Add button to select a specific driver manually.
Devices without a driver are identified in the Devices window by "No
matching driver" in the Enabled column. These devices are not available
during the restore.
Add button Moves the selected driver from the Available driver packages window to
the Driver packages to be used during restore window.
Remove Moves the selected driver from Driver packages to be used during
button restore window to the Available driver packages window.
Change Allows you to change two attributes of the selected driver.

button ■ The Use BMR discovered drivers instead of Windows supplied
drivers checkbox controls whether the selected driver is used if
Windows already has a built-in driver.
■ For MSD drivers, the Bootable driver to be used during text mode
portion of the installation checkbox only applies to a legacy DOS
restore. It determines if the driver is used during the installation
phase of the restore. It has no effect for a Fast Windows Restore.
Discovered Windows signed driver

When BMR saves third-party drivers from a protected system, the driver signing
is lost. (Third-party drivers are those that are not part of the Windows
distribution.) During the BMR restore, the installation process installs the
standard drivers into the temporary repair environment because the drivers
from the protected system are unsigned.
You can edit the configuration so that the discovered drivers are installed rather
than the standard Windows drivers.
To use discovered drivers during the restore

1 In the Devices & Drivers dialog box, select the desired driver from the list of
drivers in the bottom window, and click Change.

2 Select the Use BMR discovered drivers instead of Windows supplied drivers
checkbox.
3 Click OK.

Hosts
Use the Hosts dialog box to add, remove, or change the attributes of any host
that has a role in the restore process.
You can change attributes so you can restore on a network with a different
configuration, such as at a disaster recovery site.
Figure 10-16 Hosts dialog box


Table 10-20 Hosts mapping actions
Action Description
Add Opens a dialog box in which you can add a new host, specify its role, and
enter its IP address and gateway.
Change Opens a dialog box in which you can change properties for the selected host.
Remove Removes the selected host. If you don’t want to remove the host, click Cancel
to exit the Change Configuration dialog box without applying the changes.
Table 10-21 NetBackup client information
Action Description
Client Name The name by which NetBackup knows the client. The specified
client name must match the client name in the NetBackup
policy that backs up the client.
IP address The IP address of the client. All IP addresses defined in the

network interfaces are in the drop-down list.
NetBackup version The NetBackup software version on the client.


Network interfaces
Use the Network Interfaces dialog box to add or remove interfaces or change the
network identity that is associated with an interface.
Figure 10-17 Network interfaces dialog box
The Original Network Information is read-only. The New Network Information

shows the values that are used for the restore. If the configuration was not
edited, the top panes and bottom panes show the same information.
Related topics
■ “Importing and mapping interfaces” on page 166
■ “Changing interfaces manually” on page 167

■ “UNIX and Linux boot interface” on page 168
Table 10-22 Network interface mapping actions
Action Description
Initialize Opens a dialog box from which you can select a configuration to
import. Only the hardware information from the configuration is
imported, not the network identity. The interfaces from the
imported configuration replace the interfaces in the New Network
Information window.
Unmap All Unmaps all mapped interfaces in the New Network Information
window and changes all interfaces in the Original Network
Information window to Unmapped.
The unmapping removes the name, IP addresses, network masks,
gateways, and DHCP and bootable attributes. MAC addresses are
not removed.
Map Right-click an interface in the Original Network Information

window and select Map from the shortcut menu. In the Map
Interface dialog box, select an interface in which to map the IP
address, netmask, and domain name from the source network
card. The MAC address of the original interface is not mapped to
the target interface.
Unmap Right-click an interface in the New Network Information window

and select Unmap from the shortcut menu.
The unmapping of an interface removes the name, IP addresses,
network masks, and DHCP and bootable attributes. MAC addresses
are not removed.
Change Right-click an interface in the New Network Information window

and select Change from the shortcut menu.
Importing and mapping interfaces

If you restore to a dissimilar system and you save the target system’s
configuration by backing up the target system, you can do the following:
■ Import the network interface card (NIC) information from the target system
into the restore configuration
■ Then map the network identify from the NICs in the original configuration
to the NICs in the restore configuration

To import and map interfaces

1 Click Initialize.
2 In the Import configuration dialog box, select the client configuration to
import.
3 Click OK.
The network hardware information is imported into the New Network
Information window and replaces the interfaces that were in the window.
The network identity (IPs, routes, and so on) is not imported.
4 Right-click an interface in the Original Network Information window and
select Map from the shortcut menu.
5 In the Map or change interface dialog box, select an interface from the Map
to Interface drop-down list.
6 Click OK.
The IP address, netmask, and fully qualified domain name are applied to
that interface on the restored system.
Changing interfaces manually

If you restore to a dissimilar system and do not save the target system’s
configuration, you can manually change interface properties for a restore.
You must first determine the MAC addresses of the NICs in the target system.
To change an interface manually

1 Right-click an interface in the New Network Information window and select
Change from the shortcut menu.
2 In the Map or change interface dialog box, select Use DHCP (if using DHCP).
Because this action is an interface change, the dialog box includes the
Hardware MAC Address field. Go to step 5.
3 Select a row of attributes in the Attributes for Network Interface window
and click Change.
4 In the Add Network Identity dialog box, enter the IP address, netmask, and
fully qualified domain name from the interface on the protected system.
Then click OK.
5 Enter the hardware MAC address of the NIC in the target system.
6 Click OK.
The MAC address and network identity are changed. The name of the
interface is not changed, but it does not affect the restore.

UNIX and Linux boot interface

UNIX and Linux clients must use a single network interface to boot from and to
restore through. The Bootable column in the Network Interfaces dialog box
shows the interface that is configured as the boot interface. If your restore
configuration includes more than one network interface, you can specify which
one to use for the restore.
Use the following table to determine the correct interface:
Table 10-23 Bootable network interfaces
Platform or hardware type Bootable network interface(s)
AIX 1, 2 Integrated Ethernet, Ethernet card, or Token Ring
HP-UX Integrated Ethernet only
Linux Any Ethernet device
Solaris Any Ethernet device

1.chrp hardware only.
2.Booting the RS/6000 from a network adapter requires support in the system firmware.
To specify a boot interface

1 In the New Network Information window of the Network Interfaces dialog
box, right-click the interface that you want to use as the boot interface.
2 Select Change from the shortcut menu.
3 In the Map or change interface dialog box, click Bootable.
4 Click OK.

Network routes
Use the Network Routes dialog box to add a network route to use during the
restore.
Figure 10-18 Network routes dialog box
You may need to add a route if an existing route in the configuration is not
sufficient to reach the NetBackup or BMR servers. This situation can occur
during disaster recovery at a different location when you move servers from one
subnet to another. It also can occur when any routers that intervene are
changed.
For example, client 10.10.5.12 and NetBackup master server 10.10.6.23 have a
router (10.10.5.254) between them because they are on different subnets. When
you prepare to restore, the restore process configures the route to the
NetBackup master server as 10.10.5.254, and the restore is successful. However,
if the IP address of the router between them changes, the client may not be able
to reach the master server. The client cannot reach the server because the
configuration does not include the correct route to it. Therefore, you must add a

network route to the master server before you perform the prepare-to-restore
operation.
BMR attempts to reach hosts in the following order:
■ Host routes (specified on the Hosts dialog box)

■ Network routes that are specified on this screen
■ The default route that is specified on this screen
Table 10-24 Network routes mapping actions
Action Description
Default gateway The gateway to use if no other route reaches a host.
Add Opens a dialog box in which you can enter the properties for a new
network route.
Change Opens a dialog box in which you can change the properties for the
selected route.
Remove Removes the selected route.


Volumes
Use the Volumes dialog box to map the volume configuration from the protected
client to the new disks of the restore configuration.
Figure 10-19 Volumes dialog box
You can perform the following operations for mapping volumes and for
changing configurations:
■ Change the disks that make up a disk group
■ Control the file systems that are restored
■ Control the logical volumes that are created
■ Change the attributes of either a file system, a logical volume, or a disk
■ Restrict a disk to prevent it from being used as a target for mapping
■ Make a discovered disk available for mapping (remove restriction)

Given enough space on the target disk, you can map all the logical volumes and
their file systems. Or you can map specific logical volumes and file systems. You
do not have to restore all your logical volumes and file systems.
Primary partitions and simple volumes require only one disk. Striped, mirror,
and RAID-5 volumes require multiple disks.
Topics
■ “Mapping and unmapping volumes” on page 172
■ “Understanding the views” on page 174
Mapping and unmapping volumes

Wizards guide you through the mapping process; the appropriate wizard
appears depending on what you select to map.
The mapping is saved between sessions, so you can stop mapping and then
resume later. (If you map during a dissimilar disk restore process and you click
OK to close the Change Configuration dialog box, the DDR restore process
continues.)
If an element is mapped or unmapped, all the elements that are contained in it
are mapped or unmapped.
The following are the main options:
Initialize Opens a dialog box where you can select a configuration to import into the
New Volume Layout window. Only the disk information from the
configuration is imported. Use this option to initialize the configuration
with the layout of the new disks so you can begin mapping
Unmap All Removes all mapped elements in the New Volume Layout and changes all
elements in the Original Volume Layout window to Unmapped
Notes for UNIX and Linux DDR

■ Shared disks in a cluster are marked restricted.
■ Unused VxVM disks on Solaris clients are marked restricted.
■ You cannot map Linux LVM volume groups with the physical volumes that
are created on top of multidevices with the same configuration. The physical
volumes are mapped to either disks or partitions but not a multidevice.
Notes for Windows DDR
■ The system drive is always mapped and cannot be moved; however, you can
resize it if you map disks before the restore.
■ Original disks and their volumes that were clustered cannot be mapped.

■ The discovered disks that have the same disk signature as an original disk
that was clustered cannot be mapped.
To initiate mapping for individual elements

1 In the Table View or Disk View, right-click the element in the Original
Volume Layout window.
Click the appropriate map option on the shortcut menu (the map options
are context sensitive). The mapping wizard starts with the following
appropriate context:
Map The mapping wizard starts for the selected element (except main
element disk groups, disks, volumes, volume groups, and so on).
Map Volume The volume mapping wizard appears.
Map Volume The volume group mapping wizard appears.
Group
Map Disk If the element is a disk in a disk group or a volume group, the disk
group or volume group wizard appears. Then the volume mapping
wizard for each volume appears (the required properties are set).
The disk mapping wizard appears if the element is as follows:
■ A disk that is not in a disk group
■ Not part of a volume group (AIX)
■ None of its volumes span other disks (mirrors, stripes).
Then all the volumes and the file systems are populated into the
target disk. The mapped state are set for both source elements and
target elements (disks, volumes, and file systems)
Map Disk Group The disk group mapping wizard appears.
The mapping wizards do not allow you to reduce the size of a volume or
partition to less than the required space to restore files.
To unmap an element
1 In the Table View or Disk View, right-click the element you want to unmap in
the New Volume Layout window.
2 Click the unmap option on the shortcut menu. (The unmap options are
context sensitive: Unmap, Unmap Disk, Unmap Volume, and so on.)
The element is unmapped, and the values of used and free space change
accordingly.
To change the system volume size on Windows

1 In the Table View or Disk View, right-click the volume in the New Volume
Layout window.
2 Click Change Size on the shortcut menu.
3 Change the size of the volume.
To restrict a disk or remove restriction

1 In the Table View or Disk View, right-click the disk in the New Volume
Layout window.
2 Click either Restrict or Remove Restriction on the shortcut menu:
■ Restrict prevents a disk to be used as a target for mapping. Also, it is
not formatted, and the volume groups or volumes on it are not created
or restored.
■ Remove Restriction removes the restriction so the disk can be used as a
target. If mapped, it is formatted and its volumes and volume groups
are created and restored.
To promote a disk to dynamic on Windows

1 In the Table View or Disk View, right-click the disk in the New Volume
Layout window.
2 Click Promote to Dynamic on the shortcut menu.
To add or remove a Windows system mirror

If the disk is a basic disk, promote it to a dynamic disk.
1 In the Table View or Disk View, right-click the element in the New Volume
Layout window.
2 Click either Add Mirror or Remove Mirror on the shortcut menu.
3 If you add a mirror, select the disk to use for the mirror.
Understanding the views

The tree view (the left pane) shows the elements that are part of the disk layout.
The elements in the tree change depending on the operating system of the client
and the volume managers that are enabled. The tree view filters the details pane
on the right. Select an element to display its attributes in the right pane and to
filter other elements so they do not appear in the details pane.

The following indicators show an element’s state throughout the mapping

process:
Unmapped The element is not mapped into the new configuration.
Mapped The element is mapped into the new configuration.
Restricted The disk is or was shared or manually restricted and cannot be used.
The details pane on the right contains the following views:

■ The Table View shows the elements in an ordered list.
■ The Disk View shows how every disk is organized. A colored bar indicates
the type of storage layout. For extended partitions, the primary partition
color appears in the top color bar and the extended color in a bottom bar. For
soft partitions, the top bar shows the underlying volume or slice on which
the soft partition was created.
■ The Original Volume Layout (the top window) shows the volume layout and
the source elements (disks, disk groups, or volumes) in the original system.
The amount of space that is used and the size of the disk appears. To view
the properties for an element, right-click the element and select Properties
on the shortcut menu.
■ The New Volume Layout (the bottom window) shows the volume layout and
elements for the target system. If you initialize the configuration with the
layout from a discovered configuration, map elements from the Original
Volume Layout to the New Volume Layout.
Hierarchy of elements
The following is the hierarchy for volume information:
■ A disk group, volume group, or disk set contains disks.
■ A disk contains volumes and partitions.
■ A volume or a partition contains file systems.
All volume managers may not use all of these logical concepts. For example, a
Solaris slice does not belong to a disk group and has only a file system.
Elements
The following tables show the various elements in the tree view and what
appears in the Table View tab and Disk View tab.
Table 10-25 AIX and HP-UX logical volume manager elements
Selected Element Appears in Table View Appears in Disk View
Logical Volume Manager Volume groups and volumes. Not applicable.
Volume groups Volume groups in the configuration. Disks that are part of any volume group
(ordered by volume group).
A specific volume group Disks that are part of that volume group. Disks that are part of that volume group.
Volumes All the volumes that the LVM manages. Disks that have LVM volumes.
A specific volume Disks that contain that volume. Disks that contain that volume.
Table 10-26 Empty disks elements
Selected element Appears in Table View Appears in Disk View
Empty disks Disks that are not used. Disks that are not used.
Table 10-27 Nonmanaged Solaris elements
Non-managed Disks and partitions. Not applicable.
Disks All disks that VxVM does not manage and All disks that VxVM does not manage and
all disks that are not in an SVM disk set. all disks that are not in an SVM disk set.
Slices All slices that are not managed and not All disks that contain nonmanaged slices.
used as SVM metadevices.
Table 10-28 Solaris Volume Manager elements
Solaris Volume Manager Disk sets and volumes. Not applicable.
Disks sets All named (nonlocal) sets. Disks that are part of a named (nonlocal)
set (ordered by disk set).

Table 10-28 Solaris Volume Manager elements (continued)
A specific disk set Disks that are part of that disk set. Disks that are part of that disk set.
Volumes All SVM volumes. Disks that have SVM volumes.
A specific volume Disks that include that volume. Disks that include that volume.
Table 10-29 Veritas Volume Manager and Storage Foundation for Windows elements
Veritas Volume Manager Disk groups, volume sets, and volumes. Not applicable.
Disk groups Disk groups in the configuration. Disks that are part of any disk group.
A specific disk group Disks that are part of that disk group. Disks that are part of that disk group.
Volumes All the volumes that Volume Manager Disks that contain Volume Manager
manages. volumes (ordered by disk group)
A specific volume Disks that contain that volume. Disks that contain that volume.
Table 10-30 Windows elements
Node Appears in Table View Appears in Disk View
Windows Disk Management Disk and volumes Not applicable.
Disks All disks in the system. All disks in the system.
Volumes All the volumes that are defined in the Disks that contain volumes, regardless of
system, both managed or unmanaged. which volume manager created them.
One specific volume Disks that the volume spans. Disks that the volume spans.

Chapter 11
Managing boot servers
Boot servers provide the environment that is required to rebuild a protected
client, including resources such as shared resource trees (SRT). For UNIX
systems, a boot server also provides the resources used to boot the client system
when it performs a network boot prior to restore.
Boot server software is installed from the NetBackup installation media.
Tasks
■ “Removing a boot server” on page 182
Related topics
■ “Boot servers view” on page 181
Boot server requirements

For general SRT requirements that are related to boot servers, see “Shared
resource tree overview” on page 107.
General boot server requirements

You must have a boot server for each type of client that you want to protect. For
example, a Solaris client requires a Solaris boot server, a Windows client
requires a Windows boot server, and so on.
For Unix, Linux, and legacy Windows restores, a boot server at a particular
operating system version can only host SRTs of the same operating system
version or lower. For example, a Solaris 9 boot server can host Solaris 8 and
Solaris 9 SRTs, but not Solaris 10 SRTs.
180 Managing boot servers

Boot server requirements
For Unix, Linux, and legacy Windows restores, a client at a particular operating
system version requires an SRT of the same operating system version.
AIX boot server requirements

AIX boot servers do not have any special requirements. An AIX boot server can
reside on the same subnet as the subnet of the client, or on a different subnet.
However, AIX boot servers at a specific operating system version can only host
SRTs of the same or earlier operating system version. For example, a 5.3.0.10
boot server can only host 5.1.x.x, 5.2.x.x, 5.3.0.0, and 5.3.0.10 SRTs, but not
5.3.0.20 SRTs. Likewise, a 5.2.x.x boot server cannot host 5.3.x.x SRTs.
(See“General boot server requirements”.)
HP-UX boot server requirements

Each network segment with HP-UX clients must have an HP-UX boot server that
can support the clients.
The following must match: the Ignite version of an SRT on an HP-UX boot server
and the Ignite version that is installed on the boot server.
Linux boot server requirements

Each network segment that has Linux clients must have a Linux boot server.
Solaris boot server requirements

Each network segment with Solaris clients must have a Solaris BMR boot server
that can support the clients. However, you can use the following to minimize the
impact of this requirement:
■ When necessary, you can install BMR boot server software on a Solaris
machine in the network segment. Then create an SRT after the client has
failed and needs to be restored.
■ The Solaris BMR boot server can be defined on a Solaris machine that has a
physical IP presence on multiple networks.
That is, you can use a single Solaris BMR boot server with multiple network
interfaces for Solaris BMR clients on each network segment.
■ Configure a relay boot server to allow Solaris machines on remote subnets to
boot from a BMR boot server using a network gateway. Contact your support
representative for a Tech Note that describes the procedure.
Managing boot servers 181

Boot servers view
Windows boot server requirements

■ The network boot services on the boot server require a DHCP server
somewhere on the network.
■ The boot server must not run a PXE service or a TFTP service.
Boot servers view

The Boot Servers view shows all the boot servers that are defined for the current
master server. You can select one server only in the details pane. Use the
Refresh option to update the details pane with new information retrieved from
the master server; if an item is highlighted, only that item is updated.
Figure 11-20 Boot servers window

182 Managing boot servers

Removing a boot server
Table 11-31 Actions for boot servers
To Do the Following
Display all boot servers defined for the current Click Boot Servers.
master server
Display the properties for a boot server Right click on a boot server and then select
Properties from the shortcut menu.
Removing a boot server

You can remove a boot server by uninstalling it. For procedures, see the
following:
■ “Uninstalling a BMR boot server from a UNIX or Linux system” on page 24
■ “Uninstalling a BMR boot server from a Windows system” on page 36
Chapter 12
Troubleshooting
See the following for troubleshooting information:
■ “Problems booting from CD or DVD” on page 183
■ “Long restore times” on page 184
■ “Legacy restore fails on Windows client with multiple identical NICs” on
page 184
■ “Networking problems at DOS phase during legacy restore” on page 185
■ “DSR troubleshooting” on page 186
■ “Solaris media boot network parameters issue” on page 187
■ “To recover from deleting a client accidentally” on page 187
Problems booting from CD or DVD

AIX, Linux, and Solaris platforms use a common bootable CD or DVD format
(ISO-9660); HP-UX uses Logical Interchange Format (LIF). If a system cannot
boot from the CD or DVD, place it in a system that has a CD-ROM drive and
examine the contents. (Either UNIX or Windows platforms can read ISO format.)
■ If the CD or DVD contents consist of a single file, the CD or DVD was written
as a data CD or DVD instead of an ISO-9660 CD or DVD image. Repeat the
burning procedure but use the options that are required to burn an ISO
image file.
■ If the CD or DVD is blank or unreadable, remove it from the drive and
examine it closely to determine if it has been written to. Some CD or DVD
burning software by default simulates the burning of a CD or DVD to test the
capabilities of the CD or DVD burning hardware. It does not burn the CD or
DVD until the test-only option is turned off. Repeat the burning procedure
with the test-only option disabled.
184 Troubleshooting
Long restore times
■ If the boot was partially successful or if it appears that some files are not
present or some are corrupted, the following occurred: the burning process
failed or the file transfer from the BMR boot server to the machine with the
CD writer failed.
■ A partially burned CD may be bootable but may not contain significant
portions of its content. Lower the CD writing speed to allow a
successful burn. Use the test after writing or use the option to verify
that some CD writing software offers may help detect unsuccessful CD
writes.
■ A common cause of corruption occurs when the file is transferred with
FTP in ASCII transfer mode rather than binary mode.
■ Determine if the CD boots successfully on another similar machine. The
drive on the restore system may be damaged or dirty. Similarly, the CD itself
may be easily damaged or made unreadable by surface contamination after
writing. Examine the physical media and the environment in which it is
read.
■ Verify that you use the correct procedures to boot the client machine from
CD.
■ Try booting the client from the installation media to ensure that the
machine does not have a hardware problem when it boots from the CD.
Long restore times

If a restore takes an unusually long time (for example 20 hours instead of 2
hours), the media speed between the adapter and the switch or hub where it
connects may not match. For example, the media speed is set to 100 MB full
duplex, but the restore slows down because the hub uses half duplex. Change the
media speed to match the hub speed or switch speed, or change the hub-switch
setting to match that of the client.
Legacy restore fails on Windows client with multiple

identical NICs
If a restore fails during the DOS portion of recovery on a Windows client with
multiple identical NICs, the wrong network interface may be activated. (The
BMR Restore Wizard displays a red X next to Retrieving Client Information.)
DOS does not always identify PCI slot numbers in the same way that Windows
does. Therefore, during the DOS restore portion, the following may happen: DOS
may not use the correct slot number for the NIC that is specified for the
connection to the BMR boot server.
Troubleshooting 185
Networking problems at DOS phase during legacy restore
To resolve this problem, do one of the following:

■ Move the network cable to the NIC that is active during DOS time. If you
choose this solution, when BMR enters the Windows install phase, you must
move the cable back to the original slot.
■ Specify the slot number to use for the boot interface. For customized boot
media, recreate the boot media and specify another slot number for the NIC.
For generic boot media, specify the correct slot number during the enter
client information phase.
To identify the correct slot number, perform the following steps:
■ When the failure occurs (the BMR Restore Wizard displays a red X next
to Retrieving Client Information), press the F1 key to view error details.
■ Scroll up to see the output from when the DOS driver was loaded. In
most cases, you can see the slot values that can be specified and the slot
where the driver loaded.
■ Use the slot values to specify the slot number when you enter the client
information. (Do this step either when you create the customized boot
media or during the restore for generic boot media.) You may have to
try each slot number until you use the correct one.
■ If you tried all of the slot numbers, the error may be due to DOS
memory problems.
See “Networking problems at DOS phase during legacy restore” on
page 185
Networking problems at DOS phase during legacy

restore
BMR uses the following config.sys during the DOS phase while restoring a
Windows client.
files=30
SHELL=A:\COMMAND.COM /P /E:4096
DEVICE=A:\BIN\IFSHLP.SYS
lastdrive=z
DEVICE=A:\BIN\HIMEM.SYS
DEVICE=A:\BIN\EMM386.EXE i=B000-B7FF NOEMS
DOS=HIGH,UMB
The following line in this file has significant implications:

DEVICE=A:\BIN\EMM386.EXE i=B000-B7FF NOEMS
Most machines function correctly when using EMM386, but some may not; see
the following for corrective action:
186 Troubleshooting
DSR troubleshooting
■ Some machines require that options be added to this line. The DOS phase of
the restore may fail, which causes a red X to appear next to the following
status lines: Loading NIC Drivers, Starting Networking, or Retrieving Client
Information. Press F1 to view the details; check the status screen for the
following error:
Error 8: There is not enough memory available.
This error indicates that not enough memory is available to enable

networking. To configure more memory, change this line to the following:
DEVICE=A:\BIN\EMM386.EXE i=B000-B7FF i=E000-EFFF NOEMS
■ Some machines require that the options be removed. Some gigabit network
drivers may require the line to be changed to as follows:
DEVICE=A:\BIN\EMM386.EXE
■ Some machines require that the line be removed. Some combinations of

BIOS and NIC drivers do not work well with EMM386, and the machine may
hang while booting DOS. The system then does not respond to any key
strokes or to Ctrl+Alt+Delete. For this problem, remove this line from the
file.
DSR troubleshooting
HAL differences warning
Problem Near the end of the restore process, a warning about a different service pack
level appears. The message asks if the user wants to copy the kernel files from
the restore system to the restored system.
The warning message appears when some kernel files are different between the
restore environment and the restored system.
Cause Required hotfixes are not present in the configuration.
Solution If the restore is not a dissimilar system restore, click Cancel.

If the restore is a dissimilar system restore, add hotfixes to the configuration
and restart the restore. You may also install the hotfixes in the repair Windows
installation and click Retry.
Duplicate IP addresses on network
Problem The client fails to start networking during DOS. The details show that the IP
address is already in use.
Troubleshooting 187
Solaris media boot network parameters issue
Cause The source system may still be on the network when the target system is being
restored.
Solution Disconnect the source system from the network.
Solaris media boot network parameters issue

In a media boot of a Solaris client, the Solaris code polls the local subnet. The
code polls to determine if any machine on the local subnet has a record of the
network parameters for the booting client. If a JumpStart server has network
parameters for the client in the /etc/ethers or /etc/bootparams file, those
parameters are used for the boot process. The parameters are used even if they
are different than the network parameters for the boot interface configured in
BMR.
If network parameters for the client exist, the restore may fail.
To work around this issue, do one of the following:
■ Remove all references to the client system from the following files in all
other machines in the subnet of the client:
/etc/ethers file
/etc/bootparams
■ Unplug the booting client from the network until the media boot configures
the network parameters for the restore.
To recover from deleting a client accidentally

If you delete a client and its current configuration, the next time the client is
backed up, its configuration is saved. The client appears again in the Bare Metal
Restore Clients view.
If the client and configuration are deleted after a client fails (before it is
restored), use the bmrs command to retrieve the client’s previous configuration.
(You cannot perform a point in time restore because a deleted client does not
appear in the Bare Metal Restore Clients view.)
The following is the format of the bmrs command to use on the master server:
bmrs -resource config -operation retrieve -client clientName
-destination newConfigname -enddate dateFormat -policy policyName
For more information about the bmrs command, see the NetBackup Commands
for UNIX or NetBackup Commands for Windows manual.
188 Troubleshooting
To recover from deleting a client accidentally
Appendix A
Legacy Windows restore
procedures
The 6.5 release of the Bare Metal Restore option of NetBackup introduces a Fast
Restore process for Windows systems. This new simplified and faster process
covers most system restores. Use the legacy process in this appendix in the
following scenarios.
■ Restoration onto systems with less than 512 MB of memory.
■ Restoration of system using Storage Foundation for Windows.
Installation, deployment, and backup operation is unchanged for systems
requiring the Legacy Restore procedure. The legacy process differs from normal
operation in the following ways:
■ A different SRT type is required to be created.
See “Creating a legacy shared resource tree” on page 190.
■ A different type of boot media.
See “Creating legacy boot media” on page 190.
■ Completely different approach to the restore process.
“Archived Boot Floppies view” on page 192.
Using the legacy procedures, the boot media boots into DOS and performs an
automated installation of Windows onto the hard drive. This new temporary
installation of Windows is automatically booted and the recovery process
begins. From initial boot of the boot media to final reboot, the legacy restore
procedure requires between five and eight system reboots.
190 Legacy Windows restore procedures

Creating a legacy shared resource tree
Creating a legacy shared resource tree
Before a system can be restored with the Legacy Restore procedures, you must
create a legacy style SRT. The SRT Creation Wizard requests the following
items:
■ Windows Install media
■ Windows License Key
■ NBU 6.5 Client install package
To create CD boot media for a Windows client
Bare Metal Restore Boot Server Assistant from the Start menu. The Bare
Metal Restore Boot Server Assistant screen appears.
3 Select the option for Create a Bootable CD/DVD from a Shared Resouce
Tree.
4 Select an SRT that is marked (Legacy).
If the SRT is boot server that is an Active Directory Server, set the following two
security parameters to allow the legacy (DOS) restore method to share SRTs
with restoring clients:
■ Microsoft network server: Digitally sign communications (always) - Set to

Disabled
■ Microsoft network server: Digitally sign communications (if client agrees)
Set to Enabled
Creating legacy boot media

Before you begin a system restoration of a Windows system using the legacy
procedures, you must first create a boot floppy or a boot CD. The boot media
automatically installs Windows from the SRT onto the hard drive of the system.
The boot CDs access a copy of the CD that is copied to the CD itself. The boot
floppies start basic network services and access the SRT over the network from
the boot server. To create either media type, a legacy Windows SRT must
already exist.
Creating a legacy boot CD

Before creating a bootable CD, verify that you have done the following:
Legacy Windows restore procedures 191

Creating legacy boot media
■ You have created a legacy SRT that matches the OS version to be restored. If
you restore a Windows 2003 Server, you need a Windows 2003 Legacy SRT.
To verify, navigate to the Bare Metal Restore Management > Resources >
Shared Resource Trees tab on the NetBackup Administration Console.
Legacy SRTs are flagged "(Legacy)" in the Name Column.
■ You have done a Prepare-To-Restore for the system to be restored. A legacy
boot CD is customized for a specific BMR Client system to allow full
automation.
For more information about the Prepare-To-Restore step, see “Preparing to
restore a client” on page 66.
To create CD boot media for a Windows client:
Bare Metal Restore - Boot Server Assistant from the Start menu. The Bare
Metal Restore - Boot Server Assistant screen appears.
3 Click Next on the Welcome screen.
4 Select the Create a Bootable CD/DVD from a Shared Resouce Tree option
and click Next.
5 Select an SRT that is marked "(Legacy)".
6 Select the Client and Configuration to be restored.
7 Follow the prompts to create the boot media.
Creating a legacy boot floppy

A legacy boot floppy uses a version of DOS to start basic networking services
and to copy files needed for a restore environment. The SRT on the boot server
sends these to the client being restored. Boot floppies can be fully customized
(automated) for a specific BMR client or they can be generic and prompt for
information at restore time. At initial creation time, customized floppies may be
archived on the master server for quicker re-creation later.
To create a boot floppy, you need an NDIS2 (DOS) driver for the network card to
be used to access the SRT on the boot server. Nearly all NIC card vendors make
DOS drivers available on driver CDs or via the web. If you cannot obtain the NIC
DOS driver, Symantec recommends that you restore from a CD; CD boot media
for Windows does not require a NIC DOS driver.
Generic boot floppies are for the clients that have the same brand and type of
network interface card. Generic boot media requires that you enter information
about the client during the restore process. Therefore, you can use generic boot
media for more than one client.

Archived Boot Floppies view
To create a customized, generic, or archived legacy boot floppy, do the following:

Bare Metal Restore - Boot Server Assistant from the Start menu. The Bare
Metal Restore - Boot Server Assistant screen appears.
2 Click Legacy Boot Floppy Wizard.
4 Follow the prompts to create the legacy boot floppy.
Rewriting an archived boot floppy

If you archived a customized boot floppy, you can write the image to a diskette
without repeating the create boot floppy process.
To rewrite an archive boot floppy for a Windows client
1 On the Windows BMR boot server, click Programs > Veritas NetBackup >
Bare Metal Restore Boot Server Assistant on the Start menu.

2 In the Bare Metal Restore Boot Server Assistant screen, click Legacy Boot
Floppy Wizard.
4 Click Re-Write an archived floppy image and then click Next.
5 Follow the prompts to rewrite the floppy.
For more information, see the wizard help.

The Archived Boot Floppies view shows the customized Microsoft Windows boot
floppy diskette images that have been archived. Use the Refresh option to
update the details pane with new information retrieved from the master server;
if an item is highlighted, only that item is updated.
When you create a customized Windows boot floppy, you can archive the floppy
disk image so you can write a new boot floppy diskette without re-entering
information and collecting the resources needed to create a boot floppy.

Figure A-1 Archived boot floppies window
Table A-1 Actions for archived boot floppies
To Do the Following
Display the archived boot floppies Select Bare Metal Restore Management > Resources
> Archived Boot Floppies.
Delete an archived boot floppy Right click on the name in the details pane and then
select Delete from the shortcut menu.

Restoring a system with legacy procedures
Before you start a restore, make sure that you have done a prepare-to-restore,
created an SRT, and created the boot media.
Booting the legacy restore media

To boot the client, insert the boot media in the appropriate drive and reboot the
system. The BMR restore process loads from the boot media and begins the
restore. The progress and status of the restore appear in a BMR status screen.
■ A yellow arrow indicates that the activity is currently in progress.
■ A green check marks each activity as it completes.
■ A red X indicates a failed activity.
At any time, press F1 to see more information about the current process or press
Esc to quit. The F1 or Esc keys are processed only after the current step
completes.
Entering client information

(Generic boot floppy only.)
Generic boot floppy media does not contain any client-specific information;
therefore, you must enter client-specific information during the restore process.
The following prompts of interest may appear during the restore process. For
each prompt, provide the appropriate value or values..
Table A-2 Client information
Prompt Action
Set slot number Enter y to enter the slot number where the network interface card
(y/n)? is located.
Usually, you do not have to enter a slot number. Occasionally, the
DOS portion of the restore may fail if a slot number is not
specified.
To identify the failure and the corrective action that is required,
see “Legacy restore fails on Windows client with multiple
identical NICs” on page 184.
Enter the slot Appears only if you chose to enter a slot number.
number
The slot number you enter must match the slot number where the
NIC used for the restore is installed.

Verifying the boot disk and saving a vendor partition

Before BMR repartitions the book disk and begins installation of the Windows
restore environment, the boot media may require that you confirm the boot
disk. You may also need to confirm that a vendor partition needs to be saved. For
each prompt listed in Table A-2 below, provide the appropriate value or values.
Then the client reboots, formats drive C, and retrieves the files that BMR
requires from the SRT. Next, the Windows installation process installs Windows
into a temporary repair location.
BMR can save a vendor partition, an area of the hard drive that contains
configuration, diagnostic, and maintenance utilities usually provided by the
computer vendor. The partition must meet the following requirements:
■ Size less than 1 GB
■ Starts at the beginning of the drive
■ Not recognized as a DOS primary partition
To identify the vendor partition to save if more than one partition appears,
choose the one with Start Cylinder zero..
Table A-3 Partition information
Prompt Action
Following disks are The restore partition contains the temporary Windows repair
found in the system: installation. Note that all data on the restore partition may be
lost.
list of disks
Review the list of disks. Based on the description and the
First disk in the list
partition list, make sure that BMR can create the restore
will be used for the
partition on the first disk in the list.
BMR restore partition.
If the first disk in the list should not be reformatted to create
Press F2 to continue.
the BMR restore partition, power down the client system.
Change the disk cables or disconnect disks until the disk where
the BMR restore partition can be created appears first in the list.
Then start the client system to restart the restore process.
Do you want to save a Appears only if using a customized boot floppy.

partition (y/n)
Computers may have a special system partition: an area of the
hard drive that contains configuration, diagnostic, and
maintenance utilities usually provided by the computer vendor.
To save a partition, enter y.
To delete any existing partitions and create the working
partition that BMR requires, enter n. After the repartition
process completes, the system reboots.
Table A-3 Partition information (continued)
Prompt Action
Could not find any Appears if you chose to save a partition (see previous prompt)
partitions to save! Do during boot media creation and no partitions were found that
you want to proceed can be saved.
(YES/NO)? To stop the restore process, type NO and press Enter.
To continue with the restoration and creation of the working
partition that BMR requires, type YES and press Enter.
Which partition do you Appears if you chose to save a partition during boot media
want to save? (1, 3, or 0 creation and one or more partitions are found that can be saved.
if none). The list of partitions depends on the partitions on the client.
The display includes the partition number, the start cylinder (in
decimal), and the partition size. Only the partitions that can be
saved appear.
Enter a partition number to save or enter 0 to save none of the

partitions. Then press Enter.
The restore process saves the selected partition, deletes the
other partitions, then creates the working partition that BMR
requires.
All partitions will be Appears if you chose to have a safety prompt during boot media
erased. Type YES to creation. Then you chose not to save any partitions during the
confirm, or type NO to restore (that is, if you entered 0 to the previous prompt).
abandon. To stop the restore process, type NO and press Enter.
Proceed with
repartitioning To repartition the disk, type YES and press Enter.
(YES/NO)?
All partitions, except Appears if you chose to have a safety prompt during boot media
the saved partition, creation and then you selected a partition to save during the
will be erased. Type restore process.
YES to confirm, or type To stop the restore process, type NO and press Enter.
NO to abandon.
To repartition the disk (while saving the selected partition), type
Proceed with
YES and press Enter.
repartitioning
(YES/NO)?

BMR Restore Utility

After the temporary Windows installation, the system reboots and the BMR
Restore Utility appears. This utility creates all the required partitions, formats
them, and restores the files in each of the partitions. The Details box of the
Restore Utility screen shows details about the current task in progress.
Note: If NetBackup access management is used in your environment, provide the

proper credentials when prompted so that NetBackup can restore the client
files.
Each task is checked as it completes. A red X indicates failure; if a failure occurs,

a Retry wizard appears that shows the tasks to be retried. Before you retry a
task, examine the restore log to determine the reasons for failure and correct
the problem accordingly:
1 To access the temporary Windows installation menus and taskbar, click the
computer icon in the top left area of the BMR Restore Wizard screen.
2 Open a command window.
3 Run the following vxlogview command (in the C:\BMR\NBU\BIN folder):
vxlogview -i 131
Normally, you need only correct the problem that is described in the logs. Then
retry the failed task to complete a successful restore. If a problem persists,
contact Symantec Support. After all tasks complete, the system reboots.
The following actions may also be required:
■ For standard restores, log into the client as the administrator. Then use the
bmrcleanup task to remove the repair partition and perform other cleanup
tasks such as updating the client state.
■ For dissimilar system restores, you may have to log into the client as
Administrator to finish configuring the network information. For more
information, see First logon.
Restoring to dissimilar disks for Windows clients

To restore a system whose disks are different, you may edit a configuration on
the server first, which may cause a fully automated restoration. Or, you may
start a restore and allow BMR to detect the different disks. If the new disks do
not support the original disk layout, BMR automatically launches the Dissimilar
Restore Mapping utility during the restore process.
For procedures to edit a configuration before starting a restore, see Modifying a
configuration.

Bootable Windows drivers

Windows systems often use more than one mass storage device (MSD) driver.
However, only one of them is associated with the boot partition of the drive
where Windows is installed.
By default, BMR loads all MSD drivers during the boot phase of the restore. You
can edit the configuration so that only the driver that is associated with the boot
partition is loaded. Do so if the loading all of the MSD drivers interferes with the
boot process of the restore.
The system drive is always mapped and cannot be moved. However, you can
resize it if you map disks before the restore.
To load only the boot partition driver during the boot phase
1 In the Device & Drivers dialog box, select the correct driver from the bottom
box, and click Change.
2 Check the box labeled Bootable driver to be used during text mode portion
of the installation.
3 Click OK.
Index
A AIX 168
client 168
Active Directory
HP-UX 168
Windows 69
Linux 168
activity
Solaris 168
using the Tasks view 44
specifying 168
viewing BMR logs 46
UNIX and Linux 168
add client resources 60
boot media
adding license key 159
creating for AIX 138
adding new driver 143
creating for HP-UX 138
adding to packages pool 143
creating for Linux 139
Advanced Mass Storage Driver dialog 161
creating for Solaris 139
AIX
creating for UNIX and Linux 137
boot interface 168
overview 135
external procedure environment variables 101
rewriting an archived boot floppy 192
media boot 77
boot server
network boot 73
defined 179
ALL_LOCAL_DRIVES directive 55
network segment 180
archived boot floppy
removing 182
rewriting 192
requirements 179
restoring 93
B Boot Servers view 181
backups
breaking a stale shared resource tree lock 132
ALL_LOCAL_DRIVES directive 55
back up the client 51

C
configuring policies to back up BMR clients 52
CD
ensure successful 54
ISO format 136
job status 43
writing 136
monitoring 43
Change Configuration dialog 157
perform complete 53
changing license key 159
save custom files 54
clean up restore task 67
Solaris zone support 55
client
use the same client name in multiple
deleting 156
policies 55
deleting accidentally 187
Bare Metal Restore
cluster environments 16
overview 12
clusters
Bare Metal Restore Clients view 146
and dissimilar disk restore 84
Bare Metal Restore Management window 13
configuration
Before installing BMR 15
changing 155
boot floppy
collecting and saving during backup 43
rewriting archived 192
copying 150
boot interface
200
creating restore 150

when to use 84
current 146
dissimilar system restore
defined 14
adding MSD drivers 88
deleting 156
adding NIC drivers 88
deleting accidentally 187

creating boot media 89
discovering 152
creating restore configuration 88
editing 155
first logon 90
modifying 155
mapping disks 89
modifying a restore 155

restoring the client 90
restore 14, 150, 155

SAN 103
retrieved from backup 150

when to use 86
saved 146
drivers
Configuration Summary dialog 158

bootable Windows 198
copying a client configuration 150

discovered Windows 161
creating a restore configuration 150

finding the correct 143
creating boot media 61

signing 161
using discovered 161
Drivers properties 160
D DSR see dissimilar system restore
DDR see dissimilar disk restore dynamic disk
decommissioning BMR 4.7 41

promoting in Windows 174
deleting a client 156
dialog
Configuration Summary 158
E
Drivers 160
external procedures
Hosts 163
adding to database 95
Network Interfaces 165

client-specific names 95
Network Routes 169

converting from 4.7 40
Prepare to Discover 152

data transfer 96
Prepare to Restore Client 67

environment variables 100
Change Configuration 157

AIX 101
discovered drivers HP-UX 101
using during restore 161

Linux 100
discovering a configuration 152

Solaris 102
discovery 155
UNIX 100
running external procedures 155

Windows 102
discovery boot 152

error handling 99
disk recovery behavior exit codes 99
overview 68, 69, 70

interaction with 97
dissimilar disk restore logging 97
and clusters 84
names 94
introduction 83
naming 95
Linux notes 84
operating system specific names 95
mapping before the restore 83

operational states 98
mapping during the restore 83

points 94
overview 83
running 96
SAN 103
running during discovery 155
UNIX and Linux clients 84

running during restore 69
UNIX notes 84
using 93
when to performing mapping 83
201
H external procedures 97
log file location 46
hosts
log filenames defined 46
adding to configuration 163
originator IDs 47
changing in configuration 163
restore log locations 49
removing from configuration 163
viewing logs 46
Hosts properties 163
vxlogcfg command 49
hotfixes 143
vxlogmgr command 49
HP-UX
vxlogview command 49
boot interface 168
logging during 155
media boot 78
network boot 74
M
mapping
I
disk groups 172
disk sets 172
identifying the systems to protect 16
disks 172
installation
network interfaces in configuration 165
BMR boot server in a UNIX cluster 22
volume groups 172
BMR boot server on UNIX or Linux 23
volumes 172
BMR master server on UNIX or Linux 17
mapping and unmapping volumes
boot server prerequisites for UNIX and
dissimilar disk restore
Linux 20
mapping and unmapping volumes 172
prerequisites for UNIX and Linux 16
mass storage device
Installed SDK directories and files 189
adding drivers to configuration 160
Internetwork Packet Exchange 88
adding drivers to packages pool 143
IPX 88
bootable Windows drivers 198
finding correct drivers 143
J media boot
job status 43
AIX 77
HP-UX 78
Linux 79
L Solaris 80
license key
Microsoft
adding 159
Active Directory 69
adding on Windows systems 27

migrating from BMR 4.7 38
changing 159
modifying a restore configuration 155
Linux
modifying client configuration 155
boot interface 168

monitoring
boot server location 180

backups 43
dissimilar disk restore notes 84

multiple network interface (multihomed) 104
external procedure environment variable 100
installing device drivers in SRT 126
media boot 79
N
network boot 75
network boot
SAN not supported 103

AIX 73
logging
HP-UX 74
configuring and using 48

Linux 75
during a discovery 155

Solaris 76
during a restore 69
Windows 77
202
network interface card

R
adding driver to configuration 165
refresh 13
restore
adding drivers to packages pool 143
BMR boot servers 93
clean up 67
Network Interfaces properties 165
dissimilar system
network routes
creating configuration for 88
adding to configuration 169
enabling logging during 69
configuring in configuration 169
formatting Windows disks 69
removing from configuration 169
importing disks 69
Network Routes properties 169
log locations 49
nonrestored disks 69
O overview 64
one-button restore
point in time
external procedures 93
originator IDs 47
overview 81
when to use 82
process overview 64
P running external procedures 69
packages
system disks and volumes only 68
adding new driver 143

task state 45
adding to packages pool 143

unallocate resources 67
packages pool 142

Windows
defined 141
install into a temporary location 198
Packages view 142

restore configuration
phase 185
defined 14
pkgadd 126
restoring
point in time restore

to a different system 86

to a dissimilar system 87
introduction 81
to a specific point in time 81
overview 81
UNIX and Linux Clients 72
when to use 82
UNIX and Linux clients using media boot 77
prepare to discover UNIX and Linux clients using network boot 73
defined 14
UNIX client
Prepare to Discover dialog 152

media boot 77
prepare to restore
restrict a disk 174
client 66
rewriting an archived boot floppy 192
enabling logging 69
importing disks 69
nonrestored disks 69
S
quick formatting for Windows disks 69
SAN
running external procedures 69

coexistence 103
system disks and volumes only 68

dissimilar disk restores 103
Prepare to Restore Client dialog 67

dissimilar system restores 103
protection domain
Linux restore not supported 103
defined 14
support 103
SANs 103
save custom files 54
Shared 109
203
shared disks
restore fails on Windows client with multiple
and dissimilar disk restore 84

identical NICs 184
shared resource tree

Solaris media boot network parameters
breaking stale lock 132

issue 187
creating
UNIX boot from CD 183
AIX 113
HP-UX 114
introduction 111
U
Linux 112, 118
uninstalling
Solaris 116
BMR boot server from a UNIX or Linux
UNIX 112
system 24
defined 14
BMR boot server from a Windows system 36
determining the software installed in 110

BMR master server from a UNIX or Linux 18
installing Linux device drivers 126

BMR master server from a Windows system 28
overview 107
updating information in the views 13
repairing a damaged 130

using external procedures 93
states 130, 132

using the NetBackup Activity Monitor 43
using exclusively 127

using the Tasks view 44
Shared Resource Trees view 109
Solaris
V
boot interface 168

verify client protection 61
boot server requirements 180, 181

Veritas Cluster Server 121

viewing BMR logs 46
media boot 80
Volumes properties 171
network boot 76
vxlogcfg command 49
pkgadd 126
vxlogmgr command 49
unused VxVM disks marked restricted 84

vxlogview command 49
SRT see shared resource tree
Steps for Migrating to NetBackup BMR 6.0 38
stopping and starting the BMR 4.7 server

W
daemon 39
Windows
Active Directory 69
T adding drivers to packages pool 143
task
bootable mass storage device drivers 198
cleaning up 45
discovered drivers 161
deleting 45
dynamic disk
display properties 45
promoting 174
state 45
Tasks view 44
terminology 13
formatting disks 69
troubleshooting
network boot 77
deleting a client accidentally 187

writing a CD 136
different service pack level warning 187
dissimilar system restore 186
long restore times on HP-UX 184
network problems at DOS phase 185
networking problems at DOS phase during
restore 185
problems booting from CD 183
204

NetBackup AdminGuide BMR

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NetBackup AdminGuide BMR

Enviado por

Direitos autorais:

Formatos disponíveis

NetBackup_AdminGuide_BMR.

book Page 1 Thursday, May 24, 2007 1:02 PM

Bare Metal Restore™

UNIX, Windows, and Linux

Veritas NetBackup Bare Metal Restore

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED

The Licensed Software and Documentation are deemed to be “commercial computer

20330 Stevens Creek Blvd.

Printed in the United States of America.

Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled

Licensing and registration

Chapter 1 Introducing Bare Metal Restore

What's new in NetBackup BMR 6.5 ...................................................................12

Bare Metal Restore Management window .......................................................13

Chapter 2 Installing Bare Metal Restore

Identifying the systems to protect ............................................................16

Cluster environments ..................................................................................16

UNIX and Linux systems ....................................................................................16

BMR master server on UNIX and Linux systems ....................................16

Installation prerequisites for UNIX and Linux systems ................16

Installing the BMR master server on a UNIX or Linux system .....17

Uninstalling the BMR master server from a UNIX or Linux system 18

BMR boot server on UNIX and Linux systems .........................................20

Boot server installation prerequisites for UNIX and Linux systems 20

BMR boot server in a UNIX cluster ...................................................22

Installing a BMR boot server on a UNIX or Linux system .............23

Uninstalling a BMR boot server from a UNIX or Linux system ....24

BMR client software on UNIX and Linux systems ..................................25

Microsoft Windows systems ..............................................................................26

BMR master server on Windows systems ................................................26

Licensing prerequisites for Windows systems ................................26

Licensing the BMR master server on a Windows system ..............27

Uninstalling the BMR master server from a Windows system .....28

BMR boot server on Windows systems .....................................................30

Boot server installation prerequisites for Windows systems .......30

BMR boot server in a Windows cluster .............................................30

Installing a BMR boot server on a Windows system ......................31

Uninstalling a BMR boot server from a Windows system .............36

BMR client software on Windows systems ..............................................37

Upgrading and migrating from older BMR versions ......................................38

Steps for migrating to NetBackup BMR 6.5 .............................................38

Stopping and starting the BMR 4.7 server daemon ........................39

NetBackup_AdminGuide_BMR.book Page 6 Thursday, May 24, 2007 1:02 PM

Converting external procedures ................................................................ 40

Modify the external procedure scripts ............................................. 40

Adding external procedures to the BMR database ......................... 41

Decommissioning BMR 4.7 ......................................................................... 41

Uninstalling BMR 4.7 clients ............................................................. 42

Chapter 3 Monitoring Bare Metal Restore activity

Monitoring BMR restore tasks ........................................................................... 44

Viewing BMR logs ................................................................................................ 46

BMR logging originator IDs ....................................................................... 47

Configuring and using logging .................................................................. 48

Restore logs .................................................................................................. 49

Chapter 4 Protecting clients

Configuring policies to back up BMR clients ........................................... 52

Perform complete backups ......................................................................... 53

Perform a full backup after a restore ....................................................... 53

Ensure successful backups ......................................................................... 54

Save custom files ......................................................................................... 54

Monitor backups .......................................................................................... 55