bmr users guide tsm 143gold

Bare Metal RestoreUser Guide

For Tivoli Storage Manager

Version 1.4.3

Bare Metal Restore User Guide: Version 1.4.3March 23, 2001 Copyright © 2001 by The Kernel Group, Inc. All rights reserved.Bare Metal Restore, BMR, The Kernel Group, Inc., and TKG are registered trademarks of The Kernel Group, Inc.The following product names are trademarks of Tivoli Systems Inc. or the International Business Machines Corporation: ADSM, IBM, Tivoli, Tivoli Management Environment, TME, and TSM.Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and/or other countries.This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Contact Information:The Kernel Group, Inc.1250 South Capital of Texas Hwy.Suite 3-601Austin, TX 78746-6456Phone: (512) 433-3300Toll Free: 800-854-7381

email: [email protected]

Bare Metal Restore User Guide iii

The Kernel Group, Inc. Version 1.4.3

Table of Contents

Chapter 1Overview

Components of Bare Metal Restore ................................1Client and Server terminology .....................................2BMR Server ...............................................................2Boot Server ................................................................2File Server .................................................................2ESM Server ...............................................................2SAMBA Server ...........................................................3

The Restoration Process ...............................................4Making a Complete Backup .........................................5

Placement of the BMR Servers ......................................5Understanding the Enterprise Storage Manager Environment ...............................................................5Network topology of the Enterprise Storage Manager's environment ...............................................................6Selection of the BMR Server .......................................7ESM Server Network Interface Worksheet ....................7Network Topology Worksheet ......................................8BMR Server Candidate Worksheet...............................9BMR File Server and Boot Server Placement ............. 11Understanding the use of the Shared Resource Tree ..11Platform Specific Requirements of BMR File Servers ..12Selection of the BMR File Servers location ................ 13General Considerations – All platforms ...................... 14AIX BMR File Servers Selection ................................ 15HP-UX BMR File Servers Selection ........................... 15Solaris BMR File Servers Selection ........................... 16Shared Resource Tree Worksheets ........................... 16

iv

Version 1.4.3 The Kernel Group, Inc.

Third Party Disk Device Driver and Volume Manager Information .............................................................. 17Before Configuration of the BMR Server .................... 18

Chapter 2Installing Bare Metal Restore

AIX Installation ....................................... 21AIX Installation Requirements ..................................... 21

ESM Server Requirements ....................................... 21BMR Server Requirements ....................................... 22File Server Requirements ......................................... 22Boot Server Requirements........................................ 23BMR Client Requirements ........................................ 23

Installing the BMR Server ........................................... 24Installing the BMR Server Using SMIT ...................... 24Installing the BMR Server Using installp .................... 25

Configuring the AIX BMR Server ................................. 25Installing the License Key ........................................ 27

Controlling Access to the Administrative GUI ............... 28Installing the BMR Client ............................................. 29

Installing the BMR Client Using SMIT........................ 29Installing the BMR Client Using installp ..................... 30

Configuring the AIX BMR Client ................................... 30Sun Solaris Installation ......................... 32Solaris Installation Requirements ................................ 32

ESM Server Requirements ....................................... 32BMR Server Requirements ....................................... 32File Server/Boot Server Requirements ...................... 33BMR Client Requirements ........................................ 33

Installing the BMR Server ........................................... 34Installing the BMR Server Using pkgadd ................... 34

Configuring the Sun Solaris BMR Server ...................... 34Installing the License Key ........................................ 36

Controlling Access to the Administrative GUI ............... 37Installing the BMR Client ............................................. 38

Bare Metal Restore User Guide v


Installing the BMR Client Using pkgadd ..................... 38Configuring the Sun Solaris BMR Client .......................39HP-UX Installation ..................................40HP Installation Requirements ....................................... 40

ESM Server Requirements ........................................ 40BMR Server Requirements ........................................ 40Boot Server/File Server Requirements .......................41BMR Client Requirements .........................................41

Installing the BMR Server ............................................ 42Installing the BMR Server .........................................42

Configuring the HP-UX BMR Server .............................43Installing the License Key .........................................45

Controlling Access to the Administrative GUI ................ 45Installing the BMR Client ............................................. 46

Installing the BMR Client .......................................... 46Configuring the HP-UX BMR Client .............................. 47Windows NT Client Installation ............49Windows NT Installation Requirements ......................... 49

Server Requirements ................................................ 49BMR Client Requirements .........................................49

Backing Up the Windows Registry ................................ 50Registry Backup with TSM ........................................ 50

Installing the BMR NT Client ........................................ 50Configuring the NT BMR Client .................................... 51

Chapter 3Configuring Bare Metal Restore

Accessing the BMR Graphical User Interface ................ 55Add ESM Servers ........................................................ 57Configuring ESM Servers ............................................ 60

Adding an IP Address to an ESM server .................... 61Deleting an IP Address from an ESM Server .............. 61Modifying an Existing ESM Server’s ESM Port ........... 61Modifying an Existing ESM Administrator User Name .61

Viewing the BMR Server Configuration ......................... 62

vi


BMR Log File........................................................... 63BMR License Information ......................................... 64

Creating a Shared Resource Tree for AIX .................... 65Creating an SRT for ADSM....................................... 66Creating an SRT for TSM ......................................... 67

Creating a Shared Resource Tree for Sun Solaris ........ 67Installing Veritas Volume Manager into a Sun Solaris SRT ........................................................................ 69

Creating a Shared Resource Tree for HP-UX ............... 70Creating a Shared Resource Tree for Windows NT ....... 71Configuring a Shared Resource Tree ........................... 73

Modifying a Shared Resource Tree ........................... 73Deleting a Shared Resource Tree ............................. 76Additional Driver Support for Windows NT ................. 76

Creating a Boot Image ................................................ 80Configuring a Boot Image ............................................ 83

Modifying a Boot Image............................................ 85Deleting a Boot Image.............................................. 85

Creating a Windows NT Floppy Boot Disk .................... 86Generic Boot Floppy Creation ................................... 88Custom Boot Floppy Creation ................................... 89

Configuring a BMR Client ............................................ 95

Chapter 4Restoring a Bare Metal Restore Client

Preparing for Client Restoration .................................100Initiating Client Restoration ........................................106

Initiating Restoration of a UNIX Client ......................106Sun Solaris Network Boot ........................................106HP-UX Network Boot ...............................................107AIX Network Boot ...................................................108Initiating a Restoration of an NT Client.....................115

Bare Metal Restore User Guide vii


Appendix A:Command Reference

Appendix B:BMR Planning Worksheets

Appendix C:Technical Support

viii



1 Overview

Bare Metal Restore (BMR) allows a machine to be completely restored from the data that is saved in an Enterprise Storage Manager (ESM), without requiring separate system backups or reinstalls. In the event that a client loses its boot disk or suffers some other catastrophic failure, Bare Metal Restore can be used to restore the machine to the state at which it was last backed up to an ESM. Bare Metal Restore is completely integrated into your ESM, providing the disaster recovery feature that it lacks.

When you use BMR, your clients are backed up normally to their ESM server(s). The only differences are that all of the clients’ files are backed up and a program is automatically run before the backup is performed to save the state of the machine configuration. This information allows BMR to completely recover a machine from just the ESM backup.

Restoring a machine with Bare Metal Restore is easy and fully automated. The entire restoration process consists of running one command on the BMR server and rebooting the client over the network. The following sections describe the BMR components and the restoration process in more detail.

Components of Bare Metal RestoreBMR uses your existing ESM server(s) and adds BMR server, boot server, and file server components. The BMR components can be located on the same server machine, separately, or in any combination.

Bare Metal Restore User GuideOverview


2

Client and Server terminologyThroughout this manual, the term BMR client refers to the machine on which the BMR client software is installed. In this context, it is probable that a BMR client is also a server for other applications or data.

BMR ServerThe BMR server manages the process of client restoration. It makes the appropriate boot image and filesystems available to the client, ensures that the boot server and file server are properly configured, and generates a customized client boot script. The BMR server must be running at all times because it is the license server for BMR clients.

Boot ServerThe boot server provides the boot image to the client when it performs a network boot prior to restoration. BMR uses the standard bootp or bootparam protocol to network-boot the client from the boot server.

File ServerThe file server makes the necessary filesystems available to the client at restore time via NFS or SMB. These include the shared resource tree (SRT) filesystem that contains the necessary operating system commands and libraries, the BMR client package, and the ESM client package.

ESM ServerThe BMR client continues to use its normal ESM server. In order to be able to recover the machine from your ESM software, all files (including system files) must be backed up to the ESM server. BMR also saves the client’s configuration at backup time so that an up-to-date snapshot of the machine configuration is always saved with the system’s data.

CHAPTER 1Components of Bare Metal Restore


3

SAMBA ServerNT BMR clients access restoration scripts and files using a SAMBA server that is accessible or resident on a file server.

BMR Client/Server Configuration



4

The Restoration ProcessThe Bare Metal Restore process is highly automated and efficient. These are the steps taken to restore a client using BMR:

1. The user tells the BMR server to prepare to restore the client.

2. The BMR server retrieves the UNIX client’s configuration data from the ESM server. NT clients retrieve the client configuration file from the ESM server and to control re-configuration.

3. The BMR server creates a customized client boot script and makes the appropriate boot image and filesystems available to the client.

4. The client boots from the boot server and starts running its customized boot script.

5. The client mounts the necessary filesystems from the file server or SAMBA server.

6. The client configures its disks, logical volumes, filesystems, etc.

7. The client uses the standard ESM client to restore all its files from the ESM server, including the operating system, applications, configuration data, and user files.

8. The client configures its boot record and configuration database.

9. The client reboots itself.

10. The client performs post-boot cleanup.

After this process is complete, the client machine is fully restored to the state at which it was last backed up.

The entire restoration process can take less than 30 minutes for a relatively small machine. The majority of the time is spent restoring the client’s data from your ESM server. The amount of time required for the restoration is determined by network speed, ESM server performance, and tape access times.

CHAPTER 1Placement of the BMR Servers


5

Making a Complete BackupIt is important that every backup captures a complete snapshot of the system because BMR restores the machine to the state at which it was last backed up. There are several issues that can cause an incomplete backup, including:

• Network or server errors that occur during backup can compromise the integrity of the system's backup data.

• Files that change while the backup is occurring can lead to inconsistencies between related files or within the same file.

• Files to which access is denied during the backup will not get backed up.• It is therefore important that you follow these guidelines to maximize your chances

of obtaining a complete backup:Regularly examine the storage manager log files to ensure that any backup errors are handled promptly.Whenever possible you should ensure that a system is backed up during a "quiet time" when the risk of an incomplete backup is minimized.

For systems that cannot be acquiesced during a backup, your storage manager options should be set to retry file backups if a file changes during the backup attempt. In addition, on certain platforms there are third-party programs that attempt to resolve the open-file issue by presenting a coherent view of the filesystems to the storage manager.

Placement of the BMR Servers

Understanding the Enterprise Storage Manager EnvironmentAn understanding of the Enterprise Storage Management environment is essential for the proper placement of the BMR server. The BMR server needs to know about all the Enterprise Storage Managers that are used by the BMR clients, and all the TCP/IP addresses on the ESM server, which these clients normally use to communicate with the ESM Server.



6

In BMR version 1.4.2 , the BMR server must be able to communicate to every ESM server used by the BMR clients. For UNIX BMR clients, the BMR server must be able to retrieve the BMR client's configuration data from the ESM server. This has two implications:

• The BMR server must have the authority to retrieve these files from the ESM Server.

• The version of ESM client software installed on the BMR server must be able to retrieve these files from the client's ESM server. In the case of Tivoli Storage Manager, this means that the BMR server must have the same or later version of the ESM Backup client software as any of its BMR clients.

Network topology of the Enterprise Storage Manager's environmentThe BMR clients must be configured as ESM clients, and must be backed up to the ESM server before they can be restored using BMR. Normally, during a BMR restore, a BMR client has access to only one network interface. It must be able to contact its ESM and BMR servers using this interface. This interface may be different from the one with which the client normally communicates to the ESM server. If your network configuration allows TCP/IP connectivity to the BMR and ESM servers through the client's network boot interface, then no changes to the ESM environment need to be made. BMR allows alternate IP addresses and gateways to be specified for the servers if required during the Prepare to Restore operation. However, before a client can be configured, the interface used during the boot must be determined. This is platform and hardware dependent. Use the following table as a guide to determine which network interface to use as the boot interface on each client. A more comprehensive overview of the network boot procedures is included in “Initiating Restoration of a UNIX Client” beginning on page 106.



7

Note: Booting the RS/6000 from a network adapter requires support in the system firmware. See the section entitled "Network Boot options" to determine which interfaces can be used to boot.

Selection of the BMR ServerThis section explains the forms located in Appendix A. Start by making copies of the following forms.

• ESM Network Interface Worksheet• Network Topology Worksheet• BMR Server Candidate Worksheet

ESM Server Network Interface WorksheetFor each ESM Server, complete a separate ESM Server Network Interface Worksheet. For each interface on the ESM server, fill out one row of the worksheet table.

• The Network Interface Name column contains the name of the network interface (for example en0, tr2, eth1, or lan0).

• The Network Interface Address column contains the IP address of the ESM Server's network interface.

• The Network Segment IP column contains the IP address of the network to which the interface has connectivity.

Platform or Hardware type Bootable Network Interface(s)

AIX (all)7 Built-in Ethernet, Token Ring, or Ethernet Card

HP-UX Internal Ethernet only

Solaris Any Ethernet Card

NT Ethernet or Token Ring



8

• For example, a network interface with an IP address of 198.3.130.100, and an IP network mask of 255.255.255.0, would have a Network Interface Address column entry of 198.3.130.100, and the Network Segment IP column would contain 198.3.130.0.

Here is an example of the ESM Server Network Interface Worksheet

Network Topology Worksheet Use this worksheet to describe the network topology of the ESM backup network.

• Network Segment IP column: For each network interface from which the BMR clients can network boot, determine the network segment IP address. The network segment IP address is the dotted decimal IP of the Network Segment. For example, if the client network IP address is 198.3.130.100 and the netmask is 255.255.255.0, the network segment IP address is 198.3.130.0. For each unique network segment IP address, place an entry in the Network Segment IP column of the Network Topology Worksheet. For NT clients, include the network interface's network segment which will be used during a BMR Floppy boot.

ESM Server Name: demo

ESM Server Software Version and Release:

TSM 4.1

Network Interface Name

Network Interface Address Network Segment IP

en0 198.3.130.100 198.3.130.0/24



9

• The Gateway to ESM Server column is the IP address of a router in this segment that can be used to reach the ESM server. If the ESM server has a presence on this network (if there is an Network Segment IP match for this segment in the ESM Server Network Interface Worksheet) then no gateway is required.

• The Gateway to other Networks column should contain the IP addresses of the other router interfaces on this segment that could be used to reach other networks.

Here is an example of the Network Topology Worksheet.

BMR Server Candidate WorksheetUse this worksheet to select a suitable machine on which to install the BMR server software. First, choose a short list of potential BMR server candidates. Remember not to exclude the ESM servers if they meet all the other criteria. Use the following criteria to narrow your choices:

1. The BMR server must be running one of the following Operating Systems: AIX 4.X, Solaris 2.6, 7, and HP-UX 10.20 or 11.00.

2. ESM client software installed:

a. ESM Backup/Archive client must be at or higher than the version on any UNIX BMR client.

b. An ESM administrative client must be installed.

c. BMR server candidate must have permission to retrieve files from the ESM server for any UNIX BMR client.

Network Segment IP

Gateway to ESM Server

Gateways to other Networks

198.3.130.0 198.3.130.254 198.3.17.254



10

• Candidate Column: List all the candidates meeting the above criteria in the Candidate column of the BMR Server Candidate Worksheet.

Use the ESM Server Network Interface Worksheet and the Network Topology Worksheet to verify connectivity of every candidate. For each candidate listed in the BMR Server Candidate Worksheet, fill out the remaining columns of the worksheet:

• ESM Servers Connectivity column: Use the ESM Server Network Interface Worksheet(s). If the candidate is able to ping at least one of the Network Interface Address entries for every ESM server, place a check mark in the ESM Servers Connectivity column. If a candidate does not meet this criterion it cannot be used as the BMR server and can be crossed off the list.

• Client Connectivity column: Use the Network Topology Worksheet(s). If the candidate is able to reach at least one gateway listed in either the Gateway to ESM Server or Gateways to other Networks column for every Network Segment IP entry in all Network Topology Worksheet(s), place a check mark in the Client Connectivity column. If a candidate does not meet this criterion, it cannot be used as a BMR server.

• Select a BMR server from the available remaining candidates. The candidate must have a check mark in each column of the worksheet. Write your choice in the blank for the Selected BMR Server. Fill in the information for the Operating System and Version, and the ESM client software and Version in the blanks provided.



11

Here is an example of the BMR Server Candidate Worksheet.

BMR File Server and Boot Server PlacementThere are no restrictions on the number of BMR file servers or boot servers that you can define to the BMR server. They are not licensed entities. BMR allows you to define as many BMR file servers or boot servers as you require.

Understanding the use of the Shared Resource TreeThe BMR file server will hold the Shared Resource Trees (SRTs) for the BMR clients. The BMR boot server will hold the boot images. The function of the SRT is the same regardless of the BMR client type. The SRT provides the resources needed to build

Candidate ESM Servers Connectivity

Client Connectivity

demo X X

Selected BMR Server demo

Operating System and Version:

AIX 4.3.3

ESM Client software and Version:

TSM 4.11

AIX: uname -mSolaris: hostidHP: uname -iBMR License Key



12

the boot images. During BMR restoration it provides the executables and utilities needed to reformat the drives, re-build the file systems, and restore the files using the ESM client software. The UNIX and NT BMR clients differ in the way the SRT is used and accessed.

The UNIX BMR clients access the SRT using NFS. The SRT is NFS mounted early in the boot sequence, and provides all the utilities needed to rebuild the BMR client.

Windows NT must be run from the local drive, and only NT can create all the file system types that may be required by any NT BMR client. Therefore it is necessary for BMR to install an NT system onto a temporary partition on one of the disk drives of the NT BMR client. The NT SRT exists on a UNIX BMR file server, and provides the installation images for NT, as well as the ESM client executables, and any disk device drivers or network drivers required by the client that are not part of the normal NT installation. The NT BMR clients access the SRT from the UNIX system by using the SMB protocol and the SAMBA server. The complete restoration process, from installing NT into the temporary partition to the reformatting of the drives, re-creating the file systems, and the final cleanup and removal of the temporary NT partition, is completely automated by BMR.

Platform Specific Requirements of BMR File Servers1. The BMR file server must be of the same platform type as the BMR clients that

uses them. For example, an AIX file server cannot restore a Solaris BMR client.

2. An SRT can only be used by a BMR client of the same platform type for which the SRT was built. For example, is not possible to use a Solaris SRT to restore an HP-UX client machine.

3. The BMR file servers must be of the same platform type as the SRT’s they hold.

4. If multiple versions of the HP-UX exist, there must be at least one file server for each version. The HP-UX file server can have many SRTs but can only have one boot image for any given SRT.

5. HP-UX machines can only network boot from their internal Ethernet card from an HP-UX BMR boot server existing in the same network segment. (OS specific limitation)



13

6. Solaris clients can only network boot from a Solaris BMR boot server existing in the same network segment. (OS specific limitation)

7. For both HP-UX and Solaris, the BMR boot and file server must reside on the same machine. (OS specific limitation)

8. AIX file servers must be at the same or higher level of AIX than any of the SRT’s it holds. For example, an AIX 4.3 BMR file server can be used to hold an AIX 4.1 SRT, but an AIX 4.1 BMR file server could not be used to hold an AIX 4.3 SRT.

Selection of the BMR File Servers locationMake a copy of the form entitled BMR File Server Worksheet. For each Network Segment IP on the Network Topology Worksheet, make an entry for it in the Network Segment IP column of the BMR File Server Worksheet.

In the Link Speed column, place the end-to-end network bandwidth speed from the network containing the BMR server. For example, if the network segment were located at a remote location accessed via a Frame Relay 56K link, the Link Speed column would be 56K, even though the network segment itself and the network segment containing the BMR server are both high-speed networks.

Then, for each segment determine the number of the different types of BMR clients in that network segment. Do not count a BMR client more than once if it has multiple network interfaces. If a BMR client has multiple network interfaces, choose an interface from which it can network boot, and that will minimize the number of SRT’s required. For example, if there are several Solaris machines with multiple interfaces, each having an interface on a single common network segment, count each machine once as being in the common network segment, and do not count the machines again in the other network segment. Once the form is completed, continue with the next step.



14

Here is an example of the BMR File Server Worksheet.

General Considerations – All platformsAIX is the only platform for which the BMR file and boot server components can reside on different machines. The BMR boot server will require space in /tftpboot for the clients’ boot images. Boot images are relatively small, and one boot image may be used for many clients. There may be some circumstances where separating the boot and file servers is beneficial, but for most instances, the BMR file and boot server will reside on the same machine.

For network segments with slow links to the BMR server, consider placing the file and boot servers on a network with a faster link to the segment, or somewhere on the segment itself.

The BMR boot server requires the TCP/IP services tftp and bootps to be available (Solaris uses bootparam instead of bootp). Make sure that these services are available to be started on an AIX boot server. AIX 4.3.3 ships with these services commented out of /etc/inetd.conf. They will have to be uncommented and inetd will need to be refreshed for the BMR boot server to function.

The BMR file server will require the NFS Server services to be available to serve UNIX BMR clients. Look for the nfsd process in the process table. If it is not present, make sure that NFS Server is installed and configured.

NT clients require the use of a SAMBA server. Either the SAMBA server provided with BMR must be installed on the file server. Alternatively, a SAMBA share called

Number of BMR ClientsNetwork Segment IP

Link Speed

AIX HP-UX NT Solaris4.1 4.2 4.3 10.20 11.00 4.0 2.6 7 8

198.3.130.0 100Mb 1 4 1 20 1198.3.17.0 10Mb 2 10



15

“bmrsrt” from an external SAMBA share can be configured so the files shared are writable by the BMR server.

NT BMR clients can be served by any UNIX BMR file server or SAMBA server when the client is correctly configured.

AIX BMR File Servers SelectionYou will need a minimum of one AIX file server for all the AIX BMR clients in the network. The actual number of AIX file servers you need will depend on network connectivity speeds and NFS access considerations. For example, you may want to place an AIX BMR file server for use at remote locations, where NFS access from the remote site would be impractical. Use the Link Speed column of the BMR File Server Worksheet to determine if a “closer” BMR file server/boot server is desirable for the network segment.

The AIX file servers chosen must be the same or higher level of AIX as any of the BMR clients they serve. Each AIX file server must contain an SRT for every major level of the AIX BMR clients that it serves. For example if you have every level of AIX between 4.1.0 and 4.3.3, you will need three AIX SRT’s: One for AIX 4.1, one for AIX 4.2 and one for AIX 4.3. These can be located on the same AIX file server. The AIX BMR file servers can also be BMR boot servers for AIX, or the BMR boot servers for AIX BMR clients can be located on other AIX or HP-UX machines.

HP-UX BMR File Servers SelectionEach Network Segment IP in the BMR File Server Worksheet must have a Solaris BMR file server/boot server. The HP-UX BMR file Severs must also be BMR boot servers. You will need a minimum of one HP-UX BMR file server for each level of HP-UX of your BMR clients. A single HP-UX BMR file server can only serve a single SRT. For example, an HP-UX 10.20 BMR file server can hold either an HP-UX 11.00 SRT or an HP-UX 10.20 SRT, but not both. As with the AIX BMR file servers, the actual number and placement of the HP-UX BMR file servers is dependent on network connectivity and NFS access considerations.



16

Solaris BMR File Servers SelectionEach Network Segment IP in the BMR File Server Worksheet must have a Solaris BMR file server/boot server. Each Solaris file server can hold many Solaris SRTs. Although a Solaris BMR file server/boot server must be available in each network segment before a BMR client can be restored, there are ways to minimize this impact of this requirement:

1. The Solaris BMR boot/file server does not actually need to be available until it is required. In a matter of minutes, a Solaris BMR file server/boot server can be installed, an SRT can be copied from another Solaris file/boot server and defined to BMR, then allocated to the client. This process can occur after the client has failed and needs to be restored.

2. The Solaris BMR boot/file server can be defined on a Solaris machine that has a physical IP presence on multiple networks. That is, a single Solaris BMR boot/file server with multiple network interfaces can be used for Solaris BMR clients on each of the network segments to which it is attached.

Shared Resource Tree WorksheetsMake copies of the BMR Shared Resource Tree Worksheet from Appendix B. For each selected machine designated to be a BMR file server or boot server, fill out a BMR Shared Resource Tree Worksheet. If more than one SRT is to be defined on the BMR file server, use a separate form for each SRT. Place the BMR file server’s hostname and OS level in the first two rows of the form.

If the BMR file server will also be a boot server, check the Yes box in the BMR boot server row.

Fill in all of the Network Segment IP’s that the SRT will serve into the Network Segment IP’s Served section.

In the next section, in the SRT OS and Level row, place the level of the OS that will be needed to create the SRT. This corresponds to the OS level used by the BMR clients that will use this SRT.



17

The Required ESM Client Release and Version is the Version of the ESM client software that will be installed into the SRT. For TSM, it must be the same or higher level of the TSM client software as any of the BMR clients that will be using this SRT.

Third Party Disk Device Driver and Volume Manager InformationBMR can handle a variety of different client restorations using a variety of non-standard device drivers or volume managers. This requires the installation of the device drivers or volume managers into the BMR SRT so that the disks can properly be configured prior to restoration. A non-standard device driver or volume manager is defined as the required software needed to access the disk drives or file systems of the client that is not supplied by the base operating system of the client. On the BMR Shared Resource Tree Worksheet, in the Third Party Disk Device Driver and Volume Manager Information section, check the boxes that will apply to the BMR clients that will be served by this SRT.

Use the Location of Images for SRT Creation section to record the location of the images that will be needed for the SRT. If this location is on an NFS file server, use the location as it would appear in an NFS mount command. For example:

cws:/spdata/sys1/install/aix433/lppsource.

If the source is on a CD-ROM, use the name and location of the CD-ROM.



18

Here is an example of the Location of Images for SRT Creation form.

Before Configuration of the BMR ServerIf you are using Tivoli Storage Manager (or ADSM), you may have multiple TSM Servers installed in your environment. If there are multiple TSM Server's being used by the BMR clients, it is suggested that the dsm.sys file on the BMR server be updated to contain an appropriate server stanza for each TSM Server. This is because the BMR server will need to know how to connect to each TSM client's ESM Server.

During the configuration step, the dsm.sys file is digested and a private copy is placed into the /var/bmr/bin directory. If a new TSM Server is added into the environment after the BMR server has been configured, a new stanza must be created in the /var/bmr/bin/dsm.sys file, and the server must be added to the BMR database using the "Add ESM" button in the ESM Server screen of the BMR Web GUI.

After the BMR server is initially configured, all of the IP addresses for each ESM server must added to the BMR database. Additional IP addresses can be added by bringing up the Web GUI, entering the ESM Servers screen, and then the ESM server. Use the Add button to add the IP addresses to the ESM Server. When a BMR client is

Location of Images for SRT CreationOS /dev/cd0ESM Client /dev/cd0Third Party SoftwareNetwork Driver

Disk Drivers /dev/cd0Other:

Other:



19

configured, it registers itself with the BMR server. As part of the registration process, the BMR client determines the IP address it uses to connect to the ESM Server, and tells the BMR server that it is using the ESM server with this IP address. If the BMR server does not know of an ESM Server with this address, the client will fail registration verification and cannot be configured.



20


F

2 Installing Bare Metal Restore

AIX InstallationInstallation of Bare Metal Restore involves verifying the minimum system requirements and installing the BMR server and clients.

AIX Installation RequirementsThe following requirements must be met to use Bare Metal Restore.

ESM Server RequirementsHardware Requirements:• Any type of machine that can act as an ESM server• Storage space to completely back up all the BMR clients

Software Requirements:• ADSM server version 3.1, or TSM version 3.7 or 4.1

Bare Metal Restore User GuideInstalling Bare Metal Restore


22

BMR Server RequirementsHardware requirements:• Any model of machine that runs AIX 4.1, 4.2, or 4.3• Network connectivity to the BMR client machines and their ESM server(s)

Software Requirements:• The backup and administrative clients for ADSM version 3.1, or TSM version 3.7

or 4.1.

Note: The version of ADSM or TSM software must be the same version or higher than the BMR client’s version of TSM software.

• NFS client software

File Server RequirementsHardware Requirements:• Network connectivity to the BMR client machines and the BMR server• Enough disk space to hold the SRT filesystems used by clients at restore time,

approximately 300 MB per level of OS supported

Software Requirements:• AIX level higher than or the same as the protected BMR clients• NFS server software• Install images of the OS level and ESM client version

CHAPTER 2AIX Installation Requirements


23

Boot Server RequirementsHardware Requirements:• Network connectivity to the BMR client machines and the BMR server

Software Requirements:• AIX level higher than or the same as the protected BMR clients• Bootp server software

BMR Client RequirementsHardware Requirements:• Any model of machine that runs AIX 4.1, 4.2, or 4.3• Enough disk space to hold the system being restored• SCSI disks are the only type of disk drive supported• Network connectivity to the BMR file, boot, and ESM servers that is available at

boot time

Note: Restoring a client over an SP switch interface is not supported because the switch interface is not available at boot time. The client can still be backed up over the switch if desired.

Note: SSA drives are not supported by Bare Metal Restore.

Software Requirements:• AIX 4.1, 4.2, or 4.3 • The bos.sysmgmt.sysbr fileset for AIX 4.2.x.x clients.• The backup client for ADSM version 3.1, or TSM version 3.7 or 4.1



24

Installing the BMR ServerInstallation of a BMR server includes installing the BMR package and configuring the BMR server. You must perform this procedure on each BMR server, file server, and boot server.

Note: You must be the root user to perform the BMR server installation tasks.

Installing the BMR Server Using SMITUse the following command to install the BMR server using the SMIT GUI.

1. Insert the CD into the CD-ROM drive.

2. Enter the following command:

smitty install_latest

The SMIT software installation environment displays.

3. In the field labeled “INPUT device / directory for software” enter the path to the BareMetal distribution file or the device name of the CD-ROM drive (i.e., /dev/cd0) and press Return.

The Install and Update from ALL Available Software menu appears.

4. Press F4.

5. Using the arrow keys move the selection bar to “Bare Metal Restore for AIX - Server” and press F7.

6. Press Return three times to confirm the changes and exit to the main menu.

7. Press F10 to exit SMIT.

When the BMR server software is installed, you must configure the server using bmrsetupserver.

CHAPTER 2Configuring the AIX BMR Server


25

Installing the BMR Server Using installpUse the following steps to install the BMR server using installp.

1. If you are installing BMR from the distribution CD, make sure that the server machine’s CD-ROM drive is properly mounted. Otherwise, copy the BMR distribution file BareMetal to a temporary location.

2. Enter the following command:installp -acXd <pathname> BareMetal.server

where pathname is the path to the BareMetal distribution file or the device name of the CD-ROM drive.


Configuring the AIX BMR ServerThe bmrsetupserver program configures the server. This command must be run while logged in as the root user. bmrsetupserver is run on all three servers.

1. Create a BMR administrator user and group.

The BMR files are owned by the user. The BMR GUI daemon runs as the BMR administrator user and group. The default user and group is bmradmin.

2. Change the current directory to:

/usr/lpp/BareMetal



26


./bmrsetupserver

The following is an example of the information the system asks for when bmrsetupserver runs. Depending on the type of server being configured, different prompts may or may not appear. The questions below indicate a system where the BMR, boot, and file servers are all the same machine.

a. Will this machine be a BMR server? [y]

b. Enter BMR server's hostname [somemachine.tkg.com]:

c. Enter the BMR server port number [8362]:

d. Enter the BMR administrator's user name [bmradmin]:

e. Enter the BMR administrator's group name [db2iadm1]:

f. Will this server run the BMR GUI daemon? [y]

g. Enter the GUI server's port number [80]:

h. Enter DSM_DIR (location of dsm.sys) [/usr/lpp/adsm/bin]:

i. Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [m]:

j. Do you want to install the BMR license key? [y]

k. Enter the license key or a file name containing the key:

CHAPTER 2Configuring the AIX BMR Server


27

l. Will this machine be a file server? [y]

i. SAMBA is required for NT clients. Do you want SAMBA installed now? [y]:

ii. Enter the SAMBA user name [bmradmin]:

iii. What network interfaces should SAMBA communicate on? [ ]:

The values entered for this prompt includes all interfaces on the current file server. Accepting the default value allows SAMBA to share access across any of these interfaces. If you want to limit the interfaces SAMBA uses you need to enter a value leaving off the undesirable interfaces.

iv. What hosts are allowed access to SAMBA? [ ]:

These are interfaces SAMBA uses for browsing.

v. What directory will you share via SAMBA? [/export/srt/]:

This directory must be writable by the default SAMBA user (nobody). This is the SRT path that you will create later with bmrcreatesrt.

m. Will this machine be a boot server? [y]

Installing the License KeyNote: If you answered ‘no’ to step ‘k’, did not know the license key at the

time, or want to install it later, the license key can be entered using this procedure.

To install the license key for BMR:

1. Change the current directory to:/usr/lpp/BareMetal/aix



28

2. Enter the provided license key using the following command:

./lm_keyins -k <license key> -g

The variable <license key> is the key string provided with the product.

Controlling Access to the Administrative GUIThe web-based BMR Administrative GUI allows access only to a specified user. Administrators must enter the GUI user's username and password in order to gain access to the BMR GUI.

Note: The username and password used by the BMR GUI have no relation-ship to the system's usernames and passwords.

By default, only the "bmradmin" user is allowed access to the GUI. The default password for the default user is "bmradmin". It is highly recommended that you change this password to something more secure using the following procedure.

As either root or the BMR administrative user:

1. Change the current directory to:/usr/lpp/BareMetal/httpd/bin

2. Enter the following command:./htpasswd /var/bmr/httpd/shadow/.htpasswd bmradmin

3. Enter the user's password and confirm it when prompted.

If you wish to specify the password on the command line, you may enter:./htpasswd -b /var/bmr/httpd/shadow/.htpasswd bmradmin<password>

CHAPTER 2Installing the BMR Client


29

Installing the BMR ClientEach BMR client must have the BMR client software installed and its ESM configuration must be modified to support BMR. Specifically, all client files must be backed up to the ESM server, and the bmrsavecfg command must be run before each backup to save the current machine configuration. If bmrsavecfg is not run, the client cannot be restored.

Before installing the clients you must first define their ESM server(s) using the procedure described on page 60.

Note: You must be the root user to perform the BMR client installation tasks.

Installing the BMR Client Using SMITUse the following command to install the BMR client using the SMIT GUI.



smitty install_latest

The SMIT software installation environment displays.

3. In the field labeled “INPUT device / directory for software” enter the path to the BareMetal distribution file or the device name of the CD-ROM drive (i.e., /dev/cd0) and press Return.

The Install and Update from ALL Available Software menu appears.

4. Press F4.

5. Using the arrow keys move the selection bar to “Bare Metal Restore for AIX - Client” and press F7.

6. Press Return three times to confirm the changes and exit to the main menu.



30

7. Press F10 to exit SMIT

When the BMR client software is installed, you must configure the client using bmrsetupclient.

Installing the BMR Client Using installpUse the following steps to install the BMR client using the command line. This procedure must be performed on each client machine.

1. If you are installing BMR from the CD, make sure that the server machine’s CD-ROM drive to properly mounted. Otherwise, copy the BMR distribution file BareMetal to a temporary location.

2. Enter the following command:installp -acXd <pathname> BareMetal.client

where the pathname is the path to the BareMetal distribution file or the device name of the CD-ROM drive.

When the BMR client software is installed, you must configure the client using bmrsetupclient.

Configuring the AIX BMR ClientThe bmrsetupclient program configures the client. This command must be run while logged in as the root user.


/usr/lpp/BareMetal

CHAPTER 2Configuring the AIX BMR Client


31


./bmrsetupclient

The following is an example of the information the system asks for when bmrsetupclient runs:

a. Enter BMR server's hostname [aixp152]:

b. Enter the BMR server port number [8362]:

c. Enter this client's network interface used for booting [en0]:

d. Modify the pre-schedule command to automatically run bmrsavecfg? [y]

e. Change pre-schedule command to "/usr/lpp/BareMetal/bmrsavecfg"? [y]

Once this information is entered the system indicates it is running bmrsavecfg for the first time. When it is finished the machine is completely configured as a Bare Metal Restore client.



32

Sun Solaris InstallationInstallation of Bare Metal Restore involves verifying the minimum system requirements and installing the BMR server and clients.

Solaris Installation RequirementsThe following requirements must be met to use Bare Metal Restore.



BMR Server RequirementsHardware requirements:• Any Sparc architecture model of machine that runs Solaris 2.6 or 7.• Network connectivity to the BMR client machines and their ESM server(s)


or 4.1.

Note: The version of ADSM or TSM software must be the same version or higher than the BMR client’s version of software.

• NFS client software

CHAPTER 2Solaris Installation Requirements


33

File Server/Boot Server RequirementsHardware Requirements:• Network connectivity to the BMR client machines and the BMR server• Enough disk space to hold the SRT filesystems used by clients at restore time,


Note: Boot servers and file servers must be configured as a single machine. There must also be one boot server/file server per subnet.

Software Requirements:• Solaris 2.6 or 7• NFS server software• bootparamd server software• Install images of the OS level and ESM client version

BMR Client RequirementsHardware Requirements:• Any Sparc architecture model of machine that runs Solaris 2.6 or 7• Enough disk space to hold the system being restored• SCSI and IDE disks are the only type of disk drives supported• Network connectivity to the BMR and ESM servers that is available at boot time

Note: SSA drives are not supported by Bare Metal Restore.

Software Requirements:• Solaris 2.6 or 7• The backup client for ADSM version 3.1, or TSM version 3.7.x

Note: Optionally, clients can use Veritas Volume Manager. BMR supports version 3.03 of Veritas Volume Manager.



34

Installing the BMR ServerInstallation of a BMR server includes installing the BMR package and configuring the BMR server. You must perform this procedure on each BMR server and boot server/file server.


Installing the BMR Server Using pkgaddUse the following steps to install the BMR server using pkgadd.


2. Enter the following command:pkgadd -d <pathname> BMRserver

where the pathname is the path to the Solaris distribution directory.

Note: To find the pathname of the CD-ROM drive, run “mount” and look for the mount point of the CD-ROM.


Configuring the Sun Solaris BMR ServerThe bmrsetupserver program configures the server. This command must be run while logged in as the root user. bmrsetupserver is run on all three servers.




/opt/BareMetal

CHAPTER 2Configuring the Sun Solaris BMR Server


35


./bmrsetupserver









h. Enter DSM_DIR (location of dsm.sys) [/usr/lpp/adsm/bin]:

i. Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [s]:





36





The values entered for this prompt includes all interfaces on the current file server. Accepting the default value allows SAMBA to share access across any of these interfaces. If you want to limit the interfaces SAMBA uses you need to enter a value leaving off the undesirable interfaces.

iv. Do you want to continue with the installation of SAMBA <SAMBAroot> [y, n?]:

v. What hosts are allowed access to SAMBA? [ ]:


vi. What directory will you share via SAMBA? [/export/srt/]:

/export/srt should be writable by bmradmin, automatically configuring this machine as a boot server.

Installing the License KeyNote: If you answered ‘no’ to step ‘k’, did not know the license key at the


1. Change the current directory to:/opt/BareMetal/sol

CHAPTER 2Controlling Access to the Administrative GUI


37






By default, only the "bmradmin" user is allowed access to the GUI. The default password for the default user is "bmradmin". It is highly recommended that you change this password to something more secure using the following procedure.


1. Change the current directory to:/opt/BareMetal/httpd/bin






38


Before installing the clients you must first define their ESM server(s) on the BMR server using the procedure described on page 60.


Installing the BMR Client Using pkgaddUse the following steps to install the BMR client using pkgadd.


2. Mount the CD-ROM drive:insert command here

3. Enter the following command:pkgadd -d <pathname> BMRclient

where the pathname is the path to the Solaris distribution directory.

Note: To find the pathname of the CD-ROM drive, run “mount” and look for the mount point of the CD-ROM.

When the BMR client software is installed, you must configure the server using bmrsetupclient.

CHAPTER 2Configuring the Sun Solaris BMR Client


39

Configuring the Sun Solaris BMR ClientThe bmrsetupclient program configures the client. This command must be run while logged in as the root user.


/opt/BareMetal


./bmrsetupclient


a. Enter BMR server's hostname []:


c. Enter this client's network interface used for booting [hme0]:


e. Change pre-schedule command to "/opt/BareMetal/bmrsavecfg"? [y]




40

HP-UX InstallationInstallation of Bare Metal Restore involves verifying the minimum system requirements and installing the BMR server and clients.

HP Installation RequirementsThe following requirements must be met to use Bare Metal Restore.



BMR Server RequirementsHardware requirements:• Any model of machine that runs HP-UX 10.20 or higher• Network connectivity to the BMR client machines and their ESM server(s)


or 4.1.

Note: The version of ADSM or TSM software must be the same version or higher than the BMR client’s version of software.

CHAPTER 2HP Installation Requirements


41

Boot Server/File Server RequirementsHardware Requirements:• Network connectivity to the BMR client machines and the BMR server• Enough disk space to hold the SRT filesystems used by clients at restore time,


Note: Boot servers and file servers must be configured as a single machine.

Software Requirements:• HP-UX level higher than or the same as the protected clients• Install images of the OS level and ESM client version• GNU zip utility

BMR Client RequirementsHardware Requirements:• Any model of machine that runs HP-UX 10.20 or higher• Enough disk space to hold the system being restored• SCSI disks are the only type of disk drive supported• Network connectivity to the BMR and ESM servers that is available at boot time

Software Requirements:• HP-UX 10.20 or higher• The backup client for ADSM version 3.1, or TSM version 3.7 or 4.1



42

Installing the BMR ServerInstallation of a BMR server includes installing the BMR package and configuring the BMR server. You must perform this procedure on each BMR server and boot server/file server.


Installing the BMR ServerUse the following steps to install the BMR server.

1. If they are not already running start three daemons:pfs_mountd&

pfsd 6&

pfsd.rpc (Six separate instances of this daemon should be ruunning)

To check what daemons are currently running enter the following command:ps -ef | grep pfs

2. Make a mount point:mkdir /bmr_cdrom

3. Mount the CD-ROM using the following command:pfs_mount -o unix <cdrom device path> /bmr_cdrom

Note: To find the device path name run ioscan -nFC disk

4. From the root directory, install the BMR server software using this command:swinstall -s /bmr_cdrom/hp BareMetal.server

5. Unmount the CD-ROM drive:pfs_umount /bmr_cdrom

CHAPTER 2Configuring the HP-UX BMR Server


43

6. Clean up the installation of BMR:

rm -r /bmr_cdrom


Configuring the HP-UX BMR ServerThe bmrsetupserver program configures the server. This command must be run while logged in as the root user. bmrsetupserver is run on all three servers.




/opt/BareMetal


./bmrsetupserver










44


h. Enter DSM_DIR (location of dsm.sys) [/opt/tivoli/tsm/client/ba/bin]:

i. Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [m]:







The values entered for this prompt include all interfaces on the current file server. Accepting the default value allows SAMBA to share access across any of these interfaces. If you want to limit the interfaces SAMBA uses you need to enter a value leaving off the undesirable interfaces.

iv. What hosts are allowed access to SAMBA? [ ]:


v. What directory will you share via SAMBA? [/export/srt/]:

This directory must be writable by the default SAMBA user (nobody). This is the SRT path that you will create later with bmrcreatesrt.

m. Will this machine be a boot server? [y]

CHAPTER 2Controlling Access to the Administrative GUI


45

Installing the License KeyNote: If you answered ‘no’ to step ‘j’, did not know the license key at the


1. Change the current directory to:/opt/BareMetal/hp






By default, only the "bmradmin" user is allowed access to the GUI. The default password for the default user is "bmradmin". It is highly recommended that you change this password to something more secure, using the following procedure.


1. Change the current directory to:/opt/BareMetal/httpd/bin




46




Before installing the clients you must first define their ESM server(s) using the procedure described on page 57.


Installing the BMR Client Use the following steps to install the BMR client.

1. If they are not already running start three daemons:pfs_mountd&

pfsd 6&

pfsd.rpc (Six separate instances of this daemon should be ruunning)

To check what daemons are currently running enter the following command:ps -ef | grep pfs

2. Make a mount point:mkdir /bmr_cdrom

CHAPTER 2Configuring the HP-UX BMR Client


47

3. Mount the CD-ROM using the following command:

pfs_mount -o unix <cdrom device path> /bmr_cdrom

Note: To find the device path name run ioscan -nFC disk

4. From the root directory, install the BMR client software using this command:swinstall -s /bmr_cdrom/hp BareMetal.client

5. Unmount the CD-ROM drive:pfs_umount /bmr_cdrom

6. Clean up the installation of BMR:rm -r /bmr_cdrom

When the BMR client software is installed, you must configure the server using bmrsetupclient.

Configuring the HP-UX BMR ClientThe bmrsetupclient program configures the client. This command must be run while logged in as the root user.


/opt/BareMetal


./bmrsetupclient


a. Enter BMR server's hostname []:


c. Enter this client's network interface used for booting [lan0]:



48


e. Change pre-schedule command to "/opt/BareMetal/bmrsavecfg"? [y]


CHAPTER 2Windows NT Installation Requirements


49

Windows NT Client Installation

Windows NT Installation RequirementsThe following requirements must be met to use Bare Metal Restore.

Server RequirementsThe BMR servers must be a UNIX (AIX, Solaris, HP-UX) system. Refer to the previous sections in this chapter for the basic system requirements for the BMR server, boot server, file server and the ESM server.

To support NT clients, the file server must have an SMB server installed. Refer to the previous sections in this chapter about running bmrsetupserver for instructions on installing the SMB server.

BMR Client RequirementsHardware Requirements:• ISA or PCI based PC• 200 MB of Hard Disk space• Ethernet card with a NDIS 2.0 (DOS) driver available

Software Requirements:• Windows NT 4.0 with Service Pack 3 - 6a• The backup client for TSM version 3.7 or 4.1 or ADSM 3.1



50

Backing Up the Windows RegistryUnlike your previous ESM solutions, backing up the Windows NT registry was unnecessary because the operating system was not backed up when your ESM clients were backup. With Bare Metal Restore, backing up the Windows NT registry is essential for a smooth client restoration.

Registry Backup with TSMPlease make sure that the dsm.opt and adsm.sys are set to follow these rules.

• The TSM dsm.opt file does not contain the value: “BACKUPRegistryNo”• %SYSTEMROOT%\adsm.sys is not excluded from the backup list.Both dsm.opt and adsm.sys are located on the individual TSM client machine. The values listed here are the TSM default values. For more information consult the Tivoli Storage Manager documentation.

Installing the BMR NT Client Use the following steps to install the BMR client.

1. Insert the BMR CD into the CD-ROM drive.

2. Click Start - Run - and type D:\setup.exe, where D: is the letter of your CD-ROM drive.

If your CD-ROM has Autorun enabled, the install shield runs automatically when the disk is put into the drive. The install shield loads and the installation screen appears.

3. Click Next after reading the information on the installation screen.

4. Select the Program Folder for Bare Metal Restore to be installed in.

5. Click Next.

The program installs into the default directory. (C:\Program Files\TKG\BareMetal\)

CHAPTER 2Configuring the NT BMR Client


51

Configuring the NT BMR ClientThe bmrsetupclient program configures the client.

To configure the NT client for BMR:

1. Click Start - Programs - Bare Metal Restore - bmrsetupclient

The bmrsetupclient wizard begins.

Configuring the NT BMR Client2. Enter the BMR Server Name

3. If the default BMR server port is incorrect, enter the correct BMR server port number.



52

4. Click Next.

The DSM.opt file screen displays.

DSM.opt Configuration File5. Using the browse button, find the DSM.opt file.

6. Click Next.

The setupclient verification screen displays.

CHAPTER 2Configuring the NT BMR Client


53

Setupclient Information Verification7. Click Finish.

The BMR client creates the reservation space, registers the client, verifies the license, and completes the setup process.



54


The first NT client that is registered with the BMR server using bmrsetupclientprints a warning stating an SRT needs to be created. Refer to the section, Creating a Shared Resource Tree for Windows NT, for information about the bmrinitSRT command.


3 Configuring Bare Metal Restore

Once Bare Metal Restore is installed on the BMR server, file server, boot server and clients you may view and change their configuration using the BMR graphical user interface or the bmrconfig command. This chapter describes how to use the BMR administrative GUI to view and configure the BMR components.

Accessing the BMR Graphical User InterfaceTo access the BMR GUI:

1. Run a web browser on the BMR server.

2. Enter the URL consisting of the “localhost” and the GUI port defined during installation.

For example, if the BMR server is on port number 8080 you would specify "http://localhost:8080" as the URL.

Note: If you run the GUI server on port 80 you do not need to specify the port number in the URL.

3. Enter "bmradmin" as the username and the password that you defined during installation.

The BMR navigation bar displays on the left hand side of the screen:

Bare Metal Restore User GuideConfiguring Bare Metal Restore


56

Bare Metal Restore Navigation Bar

Field Definition

BMR Server Link to the BMR server configuration screen.

Log File Link to the last 50 lines of the BMR log file. This is helpful with troubleshooting.

License Info Link to BMR license information.

ESM Servers Link to the ESM server selection screen.

Shared Resource Tree Link to a list of available SRTs selection screen.

Boot Images Link to a list of available boot images.

Clients Link to a list of BMR clients associated with this BMR server.

Bare Metal Restore Navigation Bar

CHAPTER 3Add ESM Servers


57

All the functions of Bare Metal Restore can be accessed through the use of the BMR navigation bar. This chapter covers configuring all the components necessary to use BMR. These components are:

• BMR Server• Enterprise Storage Management (ESM) Server• Shared Resource Tree• Boot Image• BMR ClientThere are two common buttons used throughout the Bare Metal Restore GUI. The two buttons are the Save button and the Cancel button. The Save button saves any changes made to the fields on the screen. The Cancel button resets the screen to appear as it was before you editted the fields. In some situations pressing the Cancel button returns you to the selection screen.

Some screens, such as the list of available SRTs, have the ability to sort alphabetically and numerically. By clicking on the field heading, it sorts that fields contents either alphabetically or numerically depending on the field’s contents. Here is an example of the field headings on the SRT selection screen.

Sort Fields Example

Add ESM ServersTo add a new ESM server:

1. Click on the ESM Server link on the navigation bar.

The ESM servers already configured display on the screen:



58

2. Click on the Add ESM button.

The Add Enterprise Storage Management server screen displays.

CHAPTER 3Add ESM Servers


59

Adding an ESM Server

3. Enter the name of the ESM server.

4. Enter the IP address for the ESM server.

Field Definition

ESM Server Name The name of the ESM server. This is the name the BMR server calls the ESM server, and is not necessarily the same as the ESM server’s hostname, or the name that its ESM clients call it.

ESM Server IP Address The IP address for this ESM server.

ESM Server IP Port The TCP port used to contact this ESM server.

ESM Administrator User Name The administrator name for this ESM server.

Adding an ESM Server



60

5. Enter the ESM server IP port number.

6. Enter the ESM administrator user name for this ESM server.

7. Click Save.

The system creates the ESM server.

If at any time you wish to cancel adding an ESM server, click the Cancel button. The Cancel button returns the GUI to the current list of ESM servers.

Configuring ESM ServersFrom the ESM Server Configuration screen you can modify the information for the selected server.

ESM Server Configuration

CHAPTER 3Configuring ESM Servers


61

Adding an IP Address to an ESM serverTo add an IP address to an ESM server:

1. If necessary, enter the IP address to add.

2. Click Save.

The new IP address is added.

Deleting an IP Address from an ESM ServerTo delete an IP address from the ESM server:

1. Highlight the desired IP address.

2. Click the Delete Address button.

The selected IP address is deleted.

Modifying an Existing ESM Server’s ESM PortTo modify an existing ESM server’s ESM port number:

1. Enter the new ESM port number.

2. Click Save.

The ESM port number is changed.

Modifying an Existing ESM Administrator User NameTo modify an existing ESM administrator user name:

1. Enter the new ESM administrator user name.

2. Click Save.

The ESM administrator user name is changed.



62

Viewing the BMR Server ConfigurationThe BMR server configuration is defined using bmrsetupserver (on page 25) and can be viewed using the GUI. To view this configuration click on the BMR Configuration button on the BMR main menu.

The following screen is an example of the information found on the BMR server configuration screen.

BMR Server Configuration

CHAPTER 3Viewing the BMR Server Configuration


63

BMR Log FileThe BMR log file is useful when troubleshooting problems that may occur. Here is an example BMR server log file screen.

Field Definition

BMR Server Name The name of the BMR server.

BMR Server Hostname The hostname of the BMR server.

BMR Server IP Address The network IP address of the BMR server.

BMR Server Netmask The network mask of the BMR server.

BMR Server Port The port the BMR server listens to.

BMRDIR The directory where BMR is installed. The executables are installed in this directory.

BMR DSM_DIR The location of the BMR server’s private ESM directory.

BMR DSMconfig The ESM options file used by BMR.

BMR datadir The directory where BMR stores its data.

BMR state The current state of the BMR server.

BMR OS The operating system of the BMR server.

BMR log directory The directory where BMR events are logged.

BMR log file Defined as “messages” if logged to a file or “syslog” if logged to syslog.




64

BMR Server Log File

BMR License InformationThe BMR license information screen displays the number of total licenses available and the number of licenses current being used by BMR clients. This screen also displays a list of those clients that are registered with the BMR server. This screen also lists the version of BMR you are using. Here is an example of the BMR License Information screen.

CHAPTER 3Creating a Shared Resource Tree for AIX


65

BMR Server License Information

Creating a Shared Resource Tree for AIXCreating a shared resource tree (SRT) is not necessary before configuring the rest of Bare Metal Restore. However, an SRT is required to perform a restore. Approximately 300 MB is needed to create an SRT. Creating an SRT can take up to 30 minutes.

An ADSM/TSM client must be installed into the SRT. It is the ADSM/TSM client software installed into the SRT that is used by the BMR client to restore its files from the ADSM/TSM server. Once a machine is backed up using a certain level of the ADSM/TSM client software, it may not be restorable with a lower level of the ADSM/TSM client software. The latest level of ADSM/TSM client software available should be installed into the SRT.

Note: This command must be run while logged in as the root user.



66

Creating an SRT for ADSMOn the appropriate BMR file server:

1. Change the current directory to:/usr/lpp/BareMetal

2. Enter the following command:./bmrcreatesrt

The following is an example of the information the system asks for when bmrcreatesrt runs:

a. SRT name: 1423t_420_31adsm

b. SRT location [/export/srt/1423t_420_31adsm]:

c. SRT OS level 41, 42 or 43 []: 42

d. Source of AIX install images [/dev/cd0]:

e. Hit return to accept or enter alternate [xlC.rte 3.6.4.0]:

f. Source of the install image [/dev/cd0]: demo:/export/software/AIX/adsm31

g. Hit return to accept or enter alternate [adsm.client.aix42.common]:

h. Source of the install image [demo:/export/software/AIX/adsm31]:

i. Hit return to install required fileset [adsm.client.aix42.base]:

j. Source of the install image [demo:/export/software/AIX/adsm31]:

k. Additional fileset name:

CHAPTER 3Creating a Shared Resource Tree for Sun Solaris


67

Creating an SRT for TSMOn the appropriate BMR file server:

1. Change the current directory to:/usr/lpp/BareMetal



a. SRT name:

b. SRT location [/export/srt/aix4xx]:

c. SRT OS level 41, 42 or 43 []:

d. Source of AIX install images [/dev/cd0]:

e. Do you want to install TSM or ADSM? [TSM]:

f. Hit return to accept or enter alternate [tivoli.tsm.client.ba.aix43.32bit]:

g. Source of the install image [/dev/cd0]:

h. Additional fileset name:

When all of this information is entered correctly, the SRT is created.

Creating a Shared Resource Tree for Sun SolarisCreating a shared resource tree (SRT) is not necessary before configuring the rest of Bare Metal Restore. However, an SRT is required to perform a restore. Approximately 300 MB is needed to create an SRT. Creating an SRT can take up to 30 minutes.



68

A Solaris SRT requires an appropriate boot image such as the bootable operating system CD-ROM. For Solaris version 7 SRTs, patch 106327 is required in all situations. For Solaris 7, 64-bit boot images patch 106300 is also required. This is indicated in step ‘f’ of this procedure.

A TSM client must be installed into the SRT. It is the TSM client software installed into the SRT that is used by the BMR client to restore its files from the TSM server. Once a machine is backed up using a certain level of the TSM client software, it may not be restorable with a lower level of the TSM client software. The latest level of TSM client software available should be installed into the SRT.

Note: This command must be run while logged in as the root user.On the appropriate BMR file server:

1. Change the current directory to:/opt/BareMetal



a. SRT name []:

b. Enter desired level of Solaris/SunOS (2.6/5.6 or 7/5.7) [5.X]:

c. Enter SRT path to use []:

d. Enter a [hostname:/]pathname containing a suitable Solaris 2.X boot CDROM or SRT image [/cdrom/cdrom0/s0]:

If this is a Solaris/SunOS 7/5.7 SRT

e. Enter a [hostname:]/pathname containing the Solaris 7 106327-* and 106300-* patch images required by TSM [/export/share]:

CHAPTER 3Creating a Shared Resource Tree for Sun Solaris


69

f. Enter a [hostname:]/pathname containing the TSM package images [/export/share]:

g. Enter a patch or package name to install additional software in SRT, or nothing if done: []:

For an SRT that supports Veritas Volume Manager on Solaris 2.6 and Solaris 7 see Installing Veritas Volume Manager into a Sun Solaris SRT, if not the SRT is created when this information is entered correctly.

Installing Veritas Volume Manager into a Sun Solaris SRTTo add Veritas Volume Manager support to a Sun Solaris SRT the procedure from above (“Creating a Shared Resource Tree for Sun Solaris” ) continues.

Patches 109104 and 106541 are only required if installing VRTSvxvm into a Sun Solaris 7 SRT. All other supported versions of Solaris do not require a patch. If only installing VRTSvxfs into a Sun Solaris 7 SRT, a no patch is required. If installing VRTSvxvm and VRTSvxfs into a Sun Solaris 2.6 SRT no patch is required.

Note: The first step in this procedure continues with the last step (Step ‘i’) in “Creating a Shared Resource Tree for Sun Solaris” .

a. Enter a patch or package name to install additional software in SRT, or nothing if done: []: 109104-01

b. Enter a [hostname:]/pathname containing the 109104-01 patch image [/export/share/patches]:

Note: If the second patch is not located in the same place as the first, there is a second prompt requesting the location of the patch.

c. Enter a patch or package name to install additional software in SRT, or nothing if done: []: 106541-11

d. Enter a patch or package name to install additional software in SRT, or nothing if done: []: VRTSvxvm



70

e. Enter a [hostname:]/pathname containing the VRTSvxvm package image [/export/share/packages]:

Note: If VRTSvxfs is not located in the same place as VRTSvxvm, there is a second prompt requesting the location of the file.

f. Enter a patch or package name to install additional software in SRT, or nothing if done: []: VRTSvxfs

g. Enter a patch or package name to install additional software in SRT, or nothing if done: []:

Creating a Shared Resource Tree for HP-UXCreating a shared resource tree (SRT) is not necessary before configuring the rest of Bare Metal Restore. However, an SRT is required to perform a restore. Approximately 300 MB is needed to create an SRT. Creating an SRT can take up to 30 minutes.

A TSM client must be installed into the SRT. It is the TSM client software installed into the SRT that is used by the BMR client to restore its files from the TSM server. Once a machine is backed up using a certain level of the TSM client software, it may not be restorable with a lower level of the TSM client software. The latest level of TSM client software available should be installed into the SRT.

In order to install TSM 4.1.0 in an HP SRT, the TIVsm package tar file stored on the TSM 4.1.0 CD-ROM must first be expanded into a directory. For example, if the CD-ROM has been mounted over a mount point called /cdrom and the current directory where you want to expand the TIVsm package tar file, run: tar xvf /cdrom/tsmcli/hp11/TIVsm

Then when prompted for the location of the TIVsm package, enter the path to the directory where the expanded files were placed.

Note: This command must be run while logged in as the root user.

CHAPTER 3Creating a Shared Resource Tree for Windows NT


71

On the appropriate BMR file server:

1. Change the current directory to:/opt/BareMetal



a. SRT Name:

b. SRT location[/export/hp11]:

c. SRT OS level [11.00]:

d. Location (device or path) of the Ignite installation media [/dev/dsk/c0t1d0]:

e. Location (device or path) of the TSM/ADSM install media [dev/dsk/c0t1d0]:

When all of this information is entered correctly, the SRT is created.

Creating a Shared Resource Tree for Windows NTCreating a shared resource tree (SRT) is not necessary before configuring the rest of Bare Metal Restore. However, an SRT is required to perform a restore. Approximately 300 MB is needed to create an SRT. Creating an SRT takes at least 20 to 30 minutes.

The ESM client backup files directory is copied into the SRT from the BMR NT client on which bmrinitSRT is run. The ESM client software in the SRT is used by the BMR client to restore its files from the ESM server. Once a machine is backed up using a certain level of the ESM client software, is not restorable with a lower level of the ESM client software. Because of this, bmrinitSRT should be run on a BMR NT client with the latest supported level of ESM client software. For Windows NT SRTs,



72

Windows NT Server must be used in the SRT. At restore time, this SRT can be used to restore both NT Server and NT Workstation clients.

Before an SRT can be created on the file server the bmrinitSRT command needs to run one time on the NT client machine.

On the appropriate Windows NT Server client machine:

1. Click Start - Programs - Bare Metal Restore - bmrinitsrt.

The bmrinitsrt screen displays.

Initializing an NT SRT2. Enter a name for this SRT.

3. Enter the product key for the Windows NT Server CD-ROM.

4. Enter the location of the NT Server CD-ROM or install image.

CHAPTER 3Configuring a Shared Resource Tree


73

5. Enter the name of the BMR file server.

6. Click Create.

On the appropriate BMR file server:

Note: This command must be run while logged in as the root user.7. Change the current directory to the location where bmrcreatesrt is located.

This example uses the directory location for an AIX SRT.usr/lpp/BareMetal

8. Enter the following command:./bmrcreatesrt -a nt


a. SRT name:

b. SRT path:

Configuring a Shared Resource TreeThe SRT Configuration screen allows for configuration of the file server hostname, the file server IP address, and the file server netmask. The SRT Configuration screen allows for viewing of other important information related to the selected SRT.

Modifying a Shared Resource TreeTo modify an SRT:

1. Select an SRT from the SRT selection menu.

2. Click SRT Configuration.

The current configuration for the selected SRT displays on the screen.



74

Shared Resource Tree Configuration



75

3. Modify the desired fields.

4. Click Save Changes.

The changes to the selected SRT are saved.

Field Definition

SRT Name The name of the selected SRT. The SRT name is set when bmrcreatesrt is run.

SRT Architecture The hardware architecture for this SRT.

SRT OS The operating system of this SRT.

SRT OS Level The operating system version of this SRT.

SRT Path The path to the selected SRT.

SRT State The current state of this SRT.

SRT Version The version of this SRT.

SRT Checksum The checksum of the SRT used for verification.

File Server Hostname The hostname of the file server.

File Server IP Address The IP address of the file server.

File Server Netmask The IP netmask of the file server.

File Server Port The port number for the file server.

Shared Resource Tree Configuration



76

Deleting a Shared Resource TreeTo delete an SRT:

1. Select the desired SRT from the selection menu.

2. Click SRT Configuration.

The SRT Configuration screen displays.

3. Click DELETE This SRT.

A confirmation screen displays.

4. Click DELETE.

The selected SRT is deleted and BMR returns to the list of available SRTs.

Additional Driver Support for Windows NTIf your BMR NT client requires additional driver support for the NT restore to be successful, you can use the add driver command to add these drivers to an NT SRT. There are two types of drivers which can be added. These types of drivers are network interface card (NIC) drivers and mass storage device drivers not found in the base installation of NT.

Adding Network Interface Card Driver SupportNIC tags come from three locations: the running system, the install floppy, and the Windows NT catalog file. The tag on the running system can be found with the command 'ipconfig -all' and dropping the last digit from "Ethernet adapter." To have an uninterrupted restore, this tag must match either a tag in the Windows NT catalog file or the [Options] stanza of the oemsetup.inf file. After running the bmradddriver wizard, match the CLnictag property for the client with the DRVtag property for the NIC driver. Change CLnictag to match if needed.

To add a network interface card driver to an SRT:

1. Click Start - Programs - Bare Metal Restore - bmradddriver.

The BMR Add Driver wizard opens.



77

Adding a NIC driver to an SRT2. Enter the SRT name to which this NIC driver is being added.

3. Enter a name for this driver. This is can be a name independent of the file name of the driver. A unique name allows easy identification of which driver goes with which NIC card as there can be numerous drivers installed into any one SRT.

4. Select the type of NIC card using the pull down menu.

5. Enter the pathname to the oemsetup.inf file describing the driver for this NIC card.

6. Click Add.

To cancel adding this driver to the selected SRT click Cancel.



78

Adding Mass Storage Driver SupportTo add a mass storage device driver to an SRT:

1. Click Start - Programs - Bare Metal Restore - bmradddriver.

The BMR Add Driver wizard opens.

Adding a Mass Storage Device Driver to an SRT2. Click on the Mass Storage Driver radio button.

3. Enter the SRT name to which this mass storage device driver is being added.

4. Enter a name for this driver. This can be a name independent of the file name of the driver. A unique name allows easy identification of which driver goes with which mass storage device as there can be numerous drivers installed into any one SRT.



79

5. Enter the pathname to the txtsetup.oem file describing the files for this mass storage device driver.

6. Click Add.

To cancel adding this driver to the selected SRT click Cancel.

Mass Storage Driver Alternative Manual ProcedureIf the txtsetup.oem file does not have a [Disks] stanza that points to the driver files, you can use this procedure to manually install a mass storage driver into the SRT.

Some mass storage device (MSD) drivers have installation utilities other than the standard NT installation mechanism using txtsetup.oem. If your MSD does not come with a floppy, or equivalent directory on CD, containing a txtsetup.oem file and the required driver files, the following procedure can be used to create the file. It is always better to have the device driver floppy from the manufacturer than follow this manual procedure.

1. Determine location of driver files and oemsetup.inf file.

2. In the directory with the driver files, create a txtsetup.oem file following this template:[Disks]

d1 = "My MSD driver string that isn't used", \<any file indirectory>, \

[Defaults]

scsi = MSDTAG [scsi] MSDTAG = "Any descriptive string,unique for each MSD"

[Files.scsi.MSDTAG]

driver = d1, <file1.sys>, ARBITRARYTAG1

driver = d1, <file2.sys>, ARBITRARYTAG2

...

inf = d1, oemsetup.inf



80

3. Run the bmradddriver wizard.

Creating a Boot Image Once an SRT is created a boot image associated with that SRT can be created at any time in advance of client restoration. In this example the SRT is from an AIX client. Therefore, the boot image is an AIX boot image. For Sun Solaris and HP-UX there are no additional fields. However, some fields do not appear because they do not apply to those operating systems.

To create a boot image:

1. Click on the Shared Resource Trees link in the navigation bar.

2. Click on the SRT you wish to create a boot image from.

The SRT Configuration screen appears.

3. Click Create Boot Image.

The Create AIX Boot Image screen displays:

CHAPTER 3Creating a Boot Image


81

Create New AIX Boot Image



82

4. Enter the name for the boot image.

5. Enter the name of the boot server.

6. Enter the boot server port.

7. Enter the path to the boot image.

8. Select the correct architecture.

9. Select the correct processor type.

10. Select the type of network interface card.

11. Click Create.

Field Definition

BI Name The name of the selected boot image. The BI name is defined in the previous screen.

SRT Name The name of the associated SRT. This is selected from the main menu before starting the create boot image process.

Boot Server The name of the boot server where the boot image will be located.

Boot Server Port The port number of the boot server.

BI Path The path to the boot image on the boot server. This field is only applicable for the AIX operating system.

Architecture The architecture this boot image supports. This field is only applicable for the AIX operating system.

Processors The number of processors this boot image supports. This field is only applicable for the AIX operating system.

NIC Type The type of network card this boot image supports. This field is only applicable for the AIX operating system.

Create a New AIX Boot Image

CHAPTER 3Configuring a Boot Image


83

Configuring a Boot ImageThe Boot Image configuration can be modified using the graphical user interface. Here is an example of the Boot Image configuration screen.

Boot Image Configuration



84

The Boot Image Configuration screen allows for configuration of the boot server hostname, the boot server IP address, and the boot server IP netmask. The Boot Image Configuration screen allows for viewing of other important information related to the selected boot image.

Field Definition

BI Name The name of the selected boot image.

BI Path The path to the boot image on the boot server.

BI OS The operating system of the boot image.

BI OS Level The operating system version of the boot image.

BI Processors The number of processors this boot image supports.

BI Network Card The type of network card this boot image supports.

BI Architecture The architecture this boot image supports.

BI State The current state of boot image.

SRT Name The name of the SRT associated with this boot image.

Boot Server Hostname The hostname of the boot server.

Boot Server IP Address The IP address of the boot server.

Boot Server IP Netmask The IP netmask of the boot server.

Boot Server Port The port number for the boot server.

Boot Image Configuration

CHAPTER 3Configuring a Boot Image


85

Modifying a Boot ImageTo modify a Boot Image Configuration:

1. On the BMR navigation bar click Boot Images.

2. Select the boot image you wish to modify.

3. Modify the desired fields.

4. Click Save.

The changes to the selected boot image are saved.

Deleting a Boot ImageTo deleted a boot image:

1. On the BMR navigation bar click Boot Images.

2. Select the boot image you wish to modify.

The Boot Image Configuration screen appears.

3. Click Delete.

A confirmation screen displays.

4. Click DELETE.

The selected boot image is deleted and BMR returns the list of available boot images.



86

Creating a Windows NT Floppy Boot DiskA BMR floppy boot disk allows an NT BMR client machine to be completely restored if your client’s network card is not able to boot from the network.

To create a media boot disk:

1. Click Start - Programs - Bare Metal Restore - bmrfloppy.

The BMR Boot Floppy Wizard opens.

NIC Driver Information2. Enter the path to the DOS NDIS2.0 driver for your ethernet card. These drivers

can be found on the network card vendor CD, floppy, or on the vendor’s website.

CHAPTER 3Creating a Windows NT Floppy Boot Disk


87

3. Click Next.

Boot Floopy Creation OptionsThis screen allows you to choose from two types of BMR floppy boot disks. The first option is to create a generic floppy boot disk. It configures the disk to work on any system with the brand and type of network card found in the client machine. The second option is for a completely automated restore which requires no intervention once the restore begins. This option configures this boot disk specifically for the client machine so it cannot work on any other system.



88

Generic Boot Floppy CreationFrom the Boot Floopy Options screen:

1. Click the Generic radio button.

2. Click Next..

Insert a Floppy3. Insert a floppy disk into the drive

4. Click Finish.

The BMR Boot Floppy wizard creates the generic floppy boot disk. Remember to remove the new BMR boot floppy from the drive and store it in a safe place.



89

Accidentally booting from this disk can cause your system to be wiped whether or not a BMR restore is scheduled or ready to be performed.

With this type of BMR boot disk, the system asks for additional information at restore time. See “Initiating a Restoration of an NT Client” on page 115 for more information about initiating a floppy boot at restore time.

Custom Boot Floppy CreationTo create a customized BMR Boot Floppy:

1. Starting at the Boot Floppy options screen select the Customized radio button.

Floppy Creation Options2. Click Next.



90

Client IP Information3. Select the appropriate client for this boot disk by selecting it from the pull down

menu.



91

BMR Client SelectionThe IP address and Subnet Mask change automatically depending on the client selected. If this client uses DHCP click on the Obtain an IP address from a DHCP server radio button.

4. Click Next.



92

Extra Safety Prompt Selection5. When used, the BMR boot floppy destroys all existing partitions on the machine

being restored. To prevent against accidents when using a customized boot floppy, a safety prompt can be added to the disk. To select whether or not to have a safety prompt, click on the appropriate selection. A safety prompt can help guard against accidently booting from the disk when the disk is in the drive.

6. Click Next.



93

Save Partition7. If your machine has a partition on it that is unreadable to Windows NT, click

Yes on this screen. To determine if your special partition can be saved during the restore process, use the following guidelines:

• Is the partition less than 1GB? This limit ensures room for DOS to create the restore partition.

• Is the partition at the start of the drive? This restriction prevents a partition being placed such that the remaining partitions cannot fit on the drive.



94

• Is the partition recognizable to DOS as a primary partition? DOS can only create a single primary partition. Because all DOS primary partitions are readable by NT, primary paritions should be backed up into the ESM and restored without a custom setup.

• Is the type of the partition unique on the system drive? The partition type is the only indicator that remains constant from live client to restore time. The position and exact length may change. Because the saved partition information was backed up for the client, BMR cannot create a duplicate special partition.

8. Click Next.

Insert a Floppy

CHAPTER 3Configuring a BMR Client


95

9. Insert a floppy disk into the disk drive.

10. After verifying the information is correct, click Finish.

The BMR Boot Floppy wizard creates the floppy boot disk. Remember to remove the new BMR boot floppy from the drive and store it in a safe place. Accidentally booting from this disk can cause your system to be wiped whether or not a BMR restore is scheduled or ready to be performed. If the disk is accidently in the drive and you chose to have a safety prompt you can abort the BMR boot floppy process.

Configuring a BMR ClientBMR clients define themselves to the BMR server when they run the bmrsavecfg command for the first time. After that point, their configuration is uploaded every time bmrsavecfg runs, which is generally daily, depending on the ESM backup schedule.

You can modify a client’s configuration using the GUI, but keep in mind that any changes made to the Client Hostname, Client Boot IP Address, Client Boot Netmask, and Client Boot MAC Address fields may be overwritten the next time the client runs bmrsavecfg.

To configure a BMR client:

1. On the BMR navigation bar click Clients.

2. Select the client you wish to modify.

The Client Configuration screen appears.



96

Client Configuration

CHAPTER 3Configuring a BMR Client


97

Field Definition

Client Name The name of the selected client.

Allocated BI Name The name of the boot image used by the client at restore time.

Allocated BI SRT Name The name of the SRT used at restore time.

Client Hostname The hostname of the client.

Client Architecture The hardware architecture of the client.

Client OS The operating system of the client.

Client OS Level The client’s operating system version.

Client Boot IP Address The IP address of the client at restore time.

Client Boot netmask The netmask used by the client at restore time.

Client boot MAC address The MAC address of the client at restore time.

Client processors This indicates if the client is a single or multi-processor machine.

Client boot interface The network interface used at boot time.

Client boot console Device to be used as the console during the restore process.

Client boot language Language to be used during the restore process.

Client state The current state of the client.

ESM Server Name The ESM server to which the client’s files are backed up.

ESM Client Name The name by which the ESM server knows the client node.

ESM Server IP Address The IP address of the ESM server.

ESM Server alternate IP The IP address the client uses at restore time to reach the ESM server.




98

3. Enter or modify data as appropriate.

4. Click the Save Button to save the changes.

ESM Server Gateway The IP address of the gateway the client uses at restore time to reach the ESM server.

BMR Server hostname The hostname of the BMR server.

BMR Server IP address The IP address of the BMR server.

BMR Server netmask The netmask of the BMR server.

BMR Server Port The TCP Port number used by the BMR server process.

BMR Server Gateway The IP address of the gateway the client uses at restore time to contact the BMR server.



4 Restoring a Bare Metal Restore Client

After completing the installation and configuration of Bare Metal Restore, you are now prepared to completely restore your BMR client machines from their ESM backups in the event of a system failure. At least one normal ESM backup of the client machines must occur after installing BMR, otherwise BMR cannot restore them in the event of a system failure.

All BMR configuration operations may be performed using the Bare Metal Restore graphical user interface or the bmrrestore command.

Bare Metal Restore User GuideRestoring a Bare Metal Restore Client


100

Preparing for Client RestorationTo prepare for the client restoration using the graphical user interface:

1. Click on the Clients link on the navigation bar.

The Clients list displays on the screen.

2. Click on the client you wish to restore.

The Client Configuration screen displays on the screen:

CHAPTER 4Preparing for Client Restoration


101




102

The following three tables describe sections of the Client Restoration Preparation screen. The first table contains items that control the properties of the client at boot time. The second table determines the ESM client back-up image being restored. The third table describes information necessary for the client to reach the server during the restoration process.

Field Definition

Client Name The name of the selected client.


Allocated BI SRT Name The name of the SRT used at restore time.

Client Hostname The hostname of the client.

Client Architecture The hardware architecture of the client.

Client OS The operating system of the client.

Client OS Level The client’s operating system version.

Client Boot IP Address The IP address of the client at restore time.

Client Boot Netmask The netmask used by the client at restore time.

Client Boot MAC Address The MAC address of the client at restore time.

Boot Control Configuration



103

3. Enter or modify the client-specific information. If necessary, be sure the BMR Server Gateway field contains the default gateway the client uses to contact the BMR server.

4. Click Save.

5. Click Prepare to Restore.

Field Definition


ESM Client Name The name by which the ESM server knows the client node.

ESM Server IP Address The IP address of the ESM server.

ESM Server Alternate IP The IP address the client uses at restore time to reach the ESM server.

ESM Server Gateway The IP address of the gateway the client uses at restore time to reach the ESM server.

ESM Client Restore Configuration

Field Definition

BMR Server Hostname The hostname of the BMR server.

BMR Server IP Address The IP address of the BMR server.

BMR Server Netmask The netmask of the BMR server.

BMR Server Port The TCP Port number used by the BMR server process.

BMR Server Gateway The IP address of the default gateway the client uses at restore time to contact the BMR server.




104

The Prepare to Restore screen displays.

Prepare to Restore



105

Field Definition

Client Name The name of the client to restore.



ESM Client Name The name by which the ESM server knows the client.

TSM Client Password The password for the TSM Client.

TSM Admin Password The password for the TSM administrator.7

Restore Selects whether all disks and volumes or only system disks and volumes are restored.

Logging Enables logging of the restore status to the BMR server. Each client restore log can take several megs of disk space on the BMR server.

BMR Server IP Address The IP address the client uses to reach the BMR server. This information is not saved in the database.

BMR Server Netmask The IP netmask the client uses to reach the BMR server. This information is not saved in the database.

Boot Server IP Address The IP address the client uses to reach the boot server. This information is not saved in the database.

Boot Server Netmask The IP netmask the client uses to reach the boot server. This information is not saved in the database.

File Server IP Address The IP address the client uses to reach the file server. This information is not saved in the database.

File Server Netmask The IP netmask the client uses to reach the file server. This information is not saved in the database.

Restoration Confirmation



106

6. Enter the TSM Client Password.

If the password is known select Use from the selection menu.

If the password is unknown select Set from the selection menu and enter the TSM Admin password.

Note: The TSM client password entered in this screen becomes the client’s new password, permanently overriding its previous TSM password.

7. Select the desired restore option from the selection menu.

8. Select whether or not to enable logging for the restore.

9. Click the Generate Restore Files button.

Note: If you wish to cancel the restoration after generating the restore files, run the following command.bmrcleanup <clientname>

Initiating Client RestorationOnce you have prepared the client for restoration, you can initiate the restoration at any time by rebooting the client according to the following instructions.

Initiating Restoration of a UNIX ClientTo begin the restoration of a UNIX BMR client, boot the machine over the network from the appropriate boot server. The method of booting a machine over the network varies depending on its manufacturer and model. Refer to the following sections to network boot your machine depending on architecture and platform.

Sun Solaris Network BootTo begin a network boot of a Sun Solaris client:

1. Begin with the machine turned off and turn the client on.

2. Terminate the boot process by pressing the Stop-A key combination.

CHAPTER 4Initiating Client Restoration


107

3. If the PROM monitor prompts displays a “<“ sign, use the “N” command to get to the OK prompt.

4. Enter the following command:boot <network device>

The network device is the device that points to the BMR boot server. After entering this command the system boots from the network and continues the restore process.

HP-UX Network BootTo begin a network boot of an HP-UX client:

1. Begin with the machine turned off and turn the client on.

2. Press any key when the message “To discontinue, press any key within 10 seconds” displays. The client continues to boot normally if a key a key is not pressed within 10 seconds.

The Main Menu opens.

3. Enter the following command:boot lan

4. Answer No to the prompt asking about interacting with IPL.

5. Select the number of the language you wish the operating system to display. For example, US English is 61. After entering a number for the language, press Enter two times to select and confirm this choice.

The HP-UX Ignite Menu opens.

6. Using the arrow key scroll to “Run a Recovery Shell”.

Wait 30 Seconds and the Network Configuration Menu opens.



108

7. Answer the following prompts:

a. Hostname:

b. Internet Protocal address:

c. Default Gateway:

d. Subnet mask:

e. Ignite Server address:

8. Use the arrow key to scroll to OK and press Enter.

The system boots from the network and continues the restore process.

AIX Network BootUse the appropriate method to network boot your architecture of AIX client.

AIX Method A (Micro Channel-based RS6K)To network boot a client :

1. Start with the BMR client powered down.

2. If necessary, insert the IPL ROM emulation disk into the drive and continue with step 6 after turning the BMR client on.

3. If your system requires IPL ROM emulation put the hardware key in the Service Position. If your system does not require IPL ROM emulation put the key the Secure position and continue with step 4

4. Turn the BMR client on.

5. When the LED displays 200, change the key position to Service and press the yellow reset button.

6. The system should be at the bootp main menu. From the bootp Main Menu, choose the “Select BOOT (Startup) Device”. A list of available boot (startup) devices displays.



109

7. Select the appropriate boot device.

8. Select the correct network adapter. This should be the adapter with the correct network type. Network types include ethernet and token-ring. This selection should also include adapter characteristics. For example adapter characteristics which may display are thick cable, twisted pair, 16 Mb data rate, or 4 Mb data rate.

9. Set or change the network address including any leading zeros but excluding ‘.’ characters. The following IP addresses are those you need to enter on this screen.

a. The client machine you are booting in the “client address” field.

b. Your BMR boot server IP address in the “bootp server address” field.

c. Your client’s gateway in the “gateway address” field.

Note: If no gateway is used by the client, this field may be left blank. 10. Verify the addresses entered are correct and type 99 to save these settings and

return to the Main Menu.

11. On the main menu, select “Send Test Transmission (PING)”.

12. Select the “Start the Ping Test” option. If the ping test fails, verify the addresses are correct and try again. If the ping test succeeds, type 99 to return to the Main Menu.

13. Select “Exit the Main Menu and Start System”.

14. Turn the hardware key to the normal position and press Enter.

After you have started a network boot, the remainder of the restoration process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored.



110

AIX Method B (Micro Channel-Based, Symmetric Multiprocessor Systems)To network boot this type of AIX BMR client

1. With the power off to the BMR client, turn the hardware key to the Secure position.

2. Turn the on the BMR client.

3. When the LED displays 200, turn the hardware key to the Service position.

4. Press the Reset button one time.

The Maintenance Menu displays.

5. Select “System Boot” from the Maintenance Menu.

6. Select “Boot from Network” from the system boot sub-menu.

The Main Menu displays.

7. Select the “Select BOOT (Startup) Device” option.

8. Select the network adapter from which the machine will boot. If there are multiple adapters type 88 to select from a complete list of available installed adapters. Type the number that corresponds to the network adapter you are using and press Enter.

The Set or Change Network Addresses Screen displays.

Note: If you are using a Token-Ring network, select the number that corre-sponds to the ring speed of your environment.

9. The address in the hardware address field should be the same address recorded in the BMR client information. If the network adapter was changed, this field must be changed and saved in the client information screen.

10. If this client and the boot server are on the same LAN, leave the IP address fields as zeros for the bootp request. If there are multiple boot servers on the LAN or the client is on a different network to the server, enter the client and



111

server IP addresses using the following steps to enter the appropriate information.

a. Type in the client and server IP addresses using leading zeros.

b. If this machine uses a gateway to reach the server, enter the IP address for the gateway.

c. Type 99 and press Enter to save the address information and return to the Main Menu.

11. On the main menu, select “Send Test Transmission (PING)”.

12. Type 3 and press Enter.

The ping test is sent. If the ping test fails verify the ip addresses from the previous screen and try again. Also check to make sure a physical network connection exists. If the ping test is successful, type 99 and press Enter to return to the Main Menu.

13. Select the “Exit Main Menu and Start System (Boot) menu item.

14. Follow the onscreen instructions to turn the hardware key to the normal position.

AIX Method C (RSPC Platform Machine)Starting with the BMR client turned off use the following procedure to network boot an RSPC platform machine:

1. If necessary, insert the System Management Services (SMS) disk into the disk drive. If you are required to use an SMS disk and you do not insert it now, a prompt later in the network boot process will ask you to insert it at that time.

2. Press F4 when icons begin appearing on the bottom of the screen. If F4 is not pressed before the last icon appears, the client boots normally instead of using the SMS disk. If you are using an ASCII terminal press 4.

3. Select “Utilities” from the SMS menu.



112

4. From the System Management Services Utilities menu, select “Remote Initial Progam Load Setup”.

5. Select “IP Parameters” from the Network Parameters screen.

6. In the fields, enter the IP addresses of the following machines:

a. The client machine you are booting.

b. The BMR boot server

c. The client’s gateway.

Use the BMR boot server IP address for the gateway address if the BMR boot server and client are on the same subnet. If the BMR boot server and the BMR client are not on the same subnet use the normal IP address for the gateway server.

Note: If your network uses broadcasting to obtain a boot image, leave the IP address fields empty.

7. If prompted, enter the subnet mask for the BMR client. All machines in the same subnet have the same subnet mask.

8. Press Enter.

The settings save and the Network Parameters menu displays.

9. On the “Network Parameters” menu, select “Ping”.

10. Select the network adapter the client uses as its boot device.

11. Verify the displayed IP addresses are the same as the addresses you entered in the Network Parameters screen. If the addresses are correct, perform a ping test by pressing Enter. If the addresses are incorrect, press ESC until you return to the main menu and go back to step 3.

12. Press Enter to acknowledge successfully completing the ping test.

13. If not already on the System Management Services menu, go there and select the “Select Boot Device” menu.



113

Select the correct network adapter your network uses. This includes the type of network adapter and the adapter characteristics associated with that adapter. Making this selection cause the machine to boot over the network automatically.

AIX Method DThis method for network booting an AIX BMR client updates the NVRAM with the proper addresses for the BMR boot server, client, and gateway address. This type of network boot can be performed at anytime prior to a BMR restore. Doing this causes the machine to attempt a network boot 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 restoration using the Generate Restore Files from within the graphical user interface. \

Warning: When performing this procedure make sure that a restore is what you intend to do. Unintentionally preparing a client for restoration can result in a restore when a restore was not what you wanted to do.

To restore a client using this method:

1. Log into the client as the root user.

2. Verify the firmware in the BMR client is capable of using the network adapter as a boot device using this command.bootinfo -q <network adapter device name>

The output of this command is either 1 or 0. A ‘1’ indicates the network adapter is capable of network booting. A ‘0’ indicates the network adapter is not capable of network booting,. If this command indicates the device is not capable of network booting Method A is not appropriate for you hardware.



114

3. Type the following command and record the current boot list.

For AIX 4.2:bootlist -m normal -o

For AIX 4.1 or earlier:bootlist -m normal -r

The output using the -r flag is hardware-platform dependant. The output may be a hexadecimal dump of the boot list or a list of device names.

4. Invalidate the current boot list.bootlist -m normal -i

5. Change the bootlist using the following commands. Use the IP addresses of the gateway, boot server, and client machine.bootlist -m normal <network adapter device name>gateway=<IP address>bserver=<IP address>client=<IP address>hdisk0

After you have started a network boot, the remainder of the restoration process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored.



115

Initiating a Restoration of an NT ClientThere are several ways to restore an NT BMR client. Only the initial boot step for each restoration method differs.

Client Specific Floppy BootIf you wish to do a floppy boot of an NT client you first create an NT floppy boot disk by using the procedure on page 86. While creating the floppy boot disk for your specific BMR client, it also gives you the option of having safety prompts. These prompts allow you to make sure a restore is what you intend to do before the restore process begins. This type of restore requires a minimum amount of user intervention.

If during the configuration process you selected to setup a special partition because Window NT cannot read it, create that partition now. When the partition is created, the BMR restore process continues normally.

Only with a client specific floppy boot disk will you see the following prompt:

1. What partition do you want to keep? (1-4, 0 to exit)

This prompt can appear in one of two places depending on whether or not you selected to have a safety prompt during the floppy boot disk creation. If you chose to have a safety prompt, this question is presented right after it. If you chose not to have a safety prompt, the question appears as the first question during the restore process. To answer this question correctly the system displays the the starting cylinder and size of the partition to help select the correct partition to keep. After answering this question, the rest of the restore process proceeds automatically, with the saved partition remaining untouched.

To begin a client specific floppy boot, power on or reboot the client machine from the floppy drive. If during creation of the floppy boot disk you selected to have a safety prompt, this prompt appears now. To continue enter yes.

Client Generic Floppy BootThis is similar to the client specific floppy boot except that during the procedure on page 86, you chose to be able to use the same disk for multiple NT BMR clients. The prompts that occur during the machine specific floppy boot disk creation appear here



116

when you initiate a restore of your NT client. During this procedure you are also asked whether your clients use DHCP. This type of restore requires the most amount of user intervention.

If your system requires a special partition to function correct, create that partition now. When the partition is created, the BMR restore process continues normally.

To begin a client generic floppy boot, power on or reboot the client machine from the floppy drive.

The following prompts appear:

1. Enter the share name (e.g., \\machine\dir):

2. Enter the SRT path:

3. Enter the BMR client name:

4. Do you want to save one partition? (y/n)

5. What partition do you want to keep? (1-4, 0 to exit)

Note: Steps 4 and 5 only appear if a special partition was created.The first reboot erases all the hard drives on the client machine and creates a temporary BMR restoration partition.

Completing the NT Restore ProcessIf during the configuration process, you decided to add network card driver support to your floppy boot disk, the rest the process is completely automatic. If, however, you did not choose to add network card driver to your floppy boot disk or did something incorrect during that process the NT restore process continues with the following procedure.

1. On the second reboot, the client boots off the network or floppy drive.

BMR copies restoration files and files specific to machine being restored. The third reboot takes place automatically.



117

Note: If the client hardware supports it, BMR resets the bootlist to point to the hard drive. If not, the client reboots off the floppy drive and prints a message to remove the disk from the floppy drive.

2. When the system reboots off the hard drive a temporary installation of NT is created. This installation is only used to recover the permanent client installation of NT. After installation the system reboots again.

3. When the system comes up the Windows NT setup program begins automatically. If your network card is properly detected by Windows NT, no error should occur. If your network card is not detected by Windows NT, an error indicating the “Detect Adapters” value is missing or invalid.

a. Click OK

This error is accompanied by a second error in all cases indicating the network failed to start. However if the card was detected but used the wrong device driver, only the second error occurs. Use the following procedure to recover from the second error:

b. Click Retry.

c. Click back until the network adaptors selection dialog appears.

d. Deselect any incorrect drivers and click the Select from list button. If no drivers are listed click the Select from list button.

e. Install the correct driver for your network card.

f. Click Next until the automated setup process continues. At this point the installation/setup process continues automatically.

g. When Windows finishes accessing the disk in the drive, eject the disk and store it in a safe place.



118

4. When the system is finished with the setup process, it reboots once again from the hard drive. When the system returns to Windows, it automatically performs the following operations.

• Partitions disks• Reboots again• Formats and restores all the drives in the client machine• Removes the temporary partition created earlier• Cleans up after the BMR restore process to change the state of the client

from ‘restoring’ to ‘ready’.After these operations finish the Windows NT client is completely restored.


Appendix A: Command Reference


120

bmrconfig


NAMEbmrconfig - Execute BMR configuration actions.

SYNOPSISbmrconfig [-h bmrserver [-p port]] -o {define|query|change|cre-ate|allocate|deallocate|verify} -r {BI|SRT|BMR|ESM|CL}resourcename args|[key=value]...

Note: There can be multiple [key=value] pairs.

DESCRIPTIONBare Metal Restore uses the bmrconfig command to configure the various servers and clients. BMR configuration performs operations (-o) on resources (-r). The bmrconfig command exists as part of the BMR command line interface. The bmrconfig command installs on all BMR, File and Boot servers. See the -h flag below for more details. You must be the 'bmradmin' user or root to run this command.The bmrconfig command sources /var/bmr/etc/server_env to establish its environment. The port number, BMRport, is defined after sourcing this file. bmrconfig will try to determine the proper hostname depending on the resource and operation specified.There are two modes of configuration, 1) defining values in the BMR database and 2) performing operations using those database values.The operations which configure and show database values are:

define Puts values in the databasequery Shows database valueschange Changes values in the database

Database operations can be performed on any resource although not all attributes of a resource are accessible.

Bare Metal Restore User Guide 121

bmrconfig


OPTIONS-h Specifies the server name. The BMR product has 3 types of servers:

• The BMR server of which there is always only one.

• A file server (FS) of which there can be more than one.

• A boot server (BS) which can also be one of many.

The operation and resource determine which server you need tospecify. For example, all database operations (define, query, andchange) require the BMR server to be specified with the -h option.All operations on the SRT (Shared Resource Tree) resource requirethe FS and all operations on the BI (Boot Image) resource requirethe BS.

-p Specifies the port number, overriding the value of BMRport set in /var/bmr/etc/server_env.

-o Specifies the operation to perform. This in conjunction with –rdetermines the method to execute. Operations can be one of:

• define - Adds values to the database.• change - Changes values in the database.• query - Shows values from the database.• create - Creates specified resource. • allocate - Allocates one resource to another.• deallocate - Reverse of allocate.• verify - Verifies the correctness of a resource.• destroy - Reverse of create.• delete - Removes database entries.The define, change and query operations modify the BMR databaseonly.


122

bmrconfig


-r Specifies the resource to operate on. Resources are:

• BI - Boot Image• SRT - Shared Resource Tree• BMR - Bare Metal Restore Server• ESM - Enterprise Storage manager server• CL - BMR clients.Not all operations are allowed with all resources. The followingoperations and resources are allowed:

1. Operations on the BI resource.

If the -h <host> is specified then <host> is assumed to be the Bootserver (BS) associated with the specified arguments. If -p <port> isspecified then <port> is assumed to be BSport. Otherwise,BShostname and BSport are taken from the environment.

bmrconfig -o create -r BI <BIname>

bmrconfig -o destroy -r BI <BIname>

bmrconfig -o allocate -r BI [<BIname>] <CLname>

bmrconfig -o deallocate-r BI [<BIname>] <CLname>

bmrconfig -o verify -r BI <BIname>

bmrconfig -o define -r BI <BIname> <define_args>

bmrconfig -o change -r BI <BIname> <change_args>

bmrconfig -o query -r BI <BIname> <query_args>


bmrconfig


2. Operations on the SRT resource:

If the -h <host> is specified then <host> is assumed to be the Fileserver (FS) associated with the specified arguments. If -p <port> isspecified then <port> is assumed to be FSport. Otherwise,FShostname and FSport are taken from the environment.

(Note that the -o create is not valid. To create an SRT the utility,bmrcreatesrt is executed directly. This utility is interactive. See thebcreatesrt man page for more details.

bmrconfig -o destroy -r SRT <SRTname>

bmrconfig -o allocate -r SRT [<SRTname>] <CLname>

bmrconfig -o deallocate -r SRT [<SRTname>]<CLname>

bmrconfig -o verify -r SRT <SRTname>

bmrconfig -o define -r SRT <SRTname> <define_args>

bmrconfig -o change -r SRT <SRTname> <change_args>

bmrconfig -o query -r SRT <SRTname> <query_args>

3. Operations on the BMR resource:

If the -h <host> is specified then <host> is assumed to be the BMRserver (BMR) associated with the specified arguments. If -p <port>is specified then <port> is assumed to be BMRport. Otherwise,BMRhostname and BMRport are taken from the environment.

bmrconfig -o define -r BMR <BMRname> <define_args>

bmrconfig -o change -r BMR <BMRname> <change_args>

bmrconfig -o query -r BMR <BMRname> <query_args>


124

bmrconfig


4. Operations on the ESM resource:

If the -h <host> is specified, then <host> is assumed to be the BMRserver (BMR) associated with the specified arguments. If -p <port>is specified, then <port> is assumed to be BMRport. Otherwise,BMRhostname and BMRport are taken from the environment.

bmrconfig -o define -r ESM <ESMname> <define_args>

bmrconfig -o change -r ESM <ESMname> <change_args>

bmrconfig -o query -r ESM <ESMname> <query_args>

5. Operations on the CL resource:

If the -h <host> is specified then <host> is assumed to be the BMRserver (BMR) associated with the specified arguments. If -p <port>is specified then <port> is assumed to be BMRport. Otherwise,BMRhostname and BMRport are taken from the environment.

bmrconfig -o define -r CL <CLname> <define_args>

bmrconfig -o change -r CL <CLname> <change_args>

bmrconfig -o query -r CL <CLname> <query_args>

ARGUMENTSEach operation/resource combination may require arguments asshown above. The definition of these arguments are listed asfollows:

<define_args> Arguments for the define operation are one ormore name=value constructs as in, "name=value" ["name=value"... ]

<change_args> The arguments to the change operation are alsoone or more name=value constructs.

<query_args> The arguments to the query operation are one ormore names as in, "name" ["name" ... ]


bmrconfig


RESOURCE ATTRIBUTESThis section describes each attribute for each resource.

SRT:

SRTname Name of the SRT, set by user.

SRTarchitecture The hardware architecture for this SRT.

SRTos Operating system type.

SRToslevel Operating system level.

SRTpath The Path to the SRT.

SRTntshare The SMB Share name of the SRT.

SRTntsharepath The path in the NT Share of the SRT.

SRTntprodid The product id for the SRT.

SRTstate The state of this SRT.

SRTversion The version of this SRT (platform specific values)

SRTchecksum The checksum of the SRT used for verification.

FShostname The hostname of the SRT or File Server

FSipaddr The IP address of the File Server.

FSnetmask The Netmask of the File Server.

FSport The port number used to contact the BMRmaster.

BMR:

BMRname The BMR server name.

OS The operating system of the BMR server.

BMRDIR The directory where executables are installed.

BMRhostname The BMR server hostname.

BMRipaddr The BMR server IP address.

BMRport The BMR server port number.

BMRnetmask The BMR server netmask.

BMRlogtype Logging with syslog or a file.


126

bmrconfig


BMRlogdir Log directory.

BMRlogfile Log file if not logging with syslog.

BMRdatadir The directory for data.

BMRstate The state of the BMR server

BI:

BIname The Boot Image name. This is user defined.

BIpath The path to the boot image. User defined.

BIos The operating system of BI, aix, sol, hp, nt.

BIoslevel The OS level of the boot image.

BIprocessors The number of processors this BI supports.

BInic The Network Interface Card used by BI.

BIarchitecture The architecture (i.e. sparc, rs6k, ...)

BIstate The state of BI (defined, ready, allocated).

SRTname The Shared Resource Tree (SRT) associated withthis bootimage.

BShostname The hostname of the Boot Server (BS).

BSipaddr The IP address of the BS.

BSnetmask The netmask of the BS.

BSport The port number of the Boot Server.

CL:

CLname The BMR client name of the form: <ESM nodename>,<ESM server>.

BIname The Boot Image this client will use at restore time.

SRTname The Shared Resource Tree this client will use atrestore time.

ESMgateway The gateway (if needed) to reach the ESMserver.

BMRhostname The BMR server's hostname.

BMRgateway The default gateway.


bmrconfig


CLarchitecture The hardware architecture of this client machine.

CLos The operating system of CL, aix, sol, hp, nt.

CLoslevel The OS level of the BMR client.

CLprocessors The number of processors this CL supports.

CLconsole The Client's console device.

CLlang The Client's LANG (NLS) variable.

CLhostname The Client's hostname.

CLnic The Network Interface Card used by CL duringboot.

CLipaddr The Client's IP address of the Boot NIC.

CLesmipaddr The alternate IP address used to contact ESM server.

CLnetmask The Client's Netmask of the Boot NIC.

CLmacaddr The Client's MAC address for the Boot NIC.

CLstate The Client's setup state (installed, allocated, ready).

CLport The Client's port number used to contact the BMRserver.

CLbmrdatadir The Client's BMR install directory

CLlonginstdir The Client's BMR install directory long name

CLenadptr The Client's adapter used to talk to the ESM andBMR

CLnictag Unique DB identifier of NIC DRV

CLslotnumber The location of the Clients NIC (PCI specific)

CLmsdtag Unique DB identifier of Mass Storage Device DRVESM:

ESMname Name of the Enterprise Storage Manager (ESM)server.

ESMaddrs List of server addresses for ESM server.


128

bmrconfig


AdminName The administrator name for this ESM server (onlyvalid for TSM).

ESMport The TCPPort used to connect to this ESM server(only valid for TSM).

EXAMPLESDefine a boot image:

bmrconfig -o define -r BI sol7_bi SRTname=sol7 BShostname=sol1BSport=8362

Query the IP address, netmask and MAC address of the above client:

bmrconfig -o query -r CL demo,adsmsvr CLipaddr CLnetmask CLmac-addr

This command returns:

CLipaddr=198.3.134.34

CLnetmask=255.255.254.0

unset CLmacaddr

Change the IP address of the above client to 10.10.10.34:

bmrconfig -o change -r CL demo,adsmsvr CLipaddr=10.10.10.34

Aallocate a BI named, aix432, to the client, node,adsm:

bmrconfig -o allocate -r BI aix432 node,adsm


bmrcreatesrt


NAMEbmrcreatesrt - Create a shared resource tree.

SYNOPSISbmrcreatesrt [-a nt]

DESCRIPTIONThe bmrcreatesrt command is run on the BMR server or a BMR File server. bmrcreatesrt creates a Shared Resource Tree (SRT) for BMR clients at a particular operating system (OS) level. It uses the appropriate installation media. bmrcreatesrt prompts the user for the SRT name. This name can be any alpha numeric string the user defines. It is recommended that the SRTname describe the type of client that can use this SRT. SRTs are specific to client OS and OS level. The specified SRT can be previously defined to the BMR database using the GUI or the command line interface program, bmrconfig. The defined attributes for the SRT are the default values used throughout the program. bmrcreatesrt can be run on a previously created SRT allowing the user to modify any SRT attributes. The following OS levels are supported for AIX:• 4.1.x• 4.2.x• 4.3.xThe following OS levels are supported for Sun Solaris:• 2.6• 7The following OS levels are supported for HP-UX:• 10.20• 11.00The following OS levels are supported for Windows NT clients:• NT 4.0 Server• NT 4.0 Enterprise Serverbmrcreatesrt requires the ESM client installation software and any or its prerequisite file packages. After the SRT is successfully created the following database attributes are updated in the BMR database:


130

bmrcreatesrt


• SRTname Name of the SRT, set by user.

• SRTarchitecture The hardware architecture for this SRT.

• SRTos Operating system type.

• SRToslevel Operating system level.

• SRTpath The Path to the SRT.

• SRTntshare The SMB Share name of the SRT.

• SRTntsharepath The path in the NT Share of the SRT.

• SRTntprodid The product id for the SRT.

• SRTstate The state of this SRT.

• SRTversion The version of this SRT (platform specific values)

• SRTchecksum The checksum of the SRT used for verification.

• FShostname The hostname of the SRT or File Server

• FSipaddr The IP address of the File Server.

• FSnetmask The Netmask of the File Server.

• FSport The port number used to contact the BMRmaster.

OPTIONS-a nt architecture for NT only.


bmrrestore


COMMANDbmrrestore - The bmrrestore command prepares a client for restoration. The command is run on the BMR server to restore any BMR client.

SYNOPSISbmrrestore [-l] [-P nodepassword] [-r [-W adminpasswd]]

DESCRIPTIONThe bmrrestore command allocates the assigned SRT (Shared Resource Tree) and BI (Boot Image) to the specified client. The following client attributes are required for bmrrestore to run correctly:

CLname Specified on the command line

BMRhostname Specified in /var/bmr/etc/server_env

The following attributes must be in the database entry for the specified client:• BIname• SRTname• ESMgateway• CLconsole• CLlang• CLhostname• CLipaddr• CLnetmask• CLarchitecture• CLos• CLoslevel• CLprocessors• CLnic


132

bmrrestore


OPTIONS-l logs the entire restoration process. The log is created in

$BMRlogdir/<clientname>. BMRlogdir is defined in /var/bmr/etc/server_env.

-P The client’s ESM node password.

-W The ESM server’s administration password

-R Resets the node password. This requires -W.

-r Restore non-rootvg disk(s) as well.

If the ESM node password is not specified with the -P option then bmrrestore will prompt for this password.



133

Appendix B: BMR Planning Worksheets

Bare Metal Restore User Guide


134

ESM Server Network Interface Worksheet

ESM Server Name:

ESM Server Software Version and Release:

Network Interface Name

Network Interface Address Network Segment IP



135

Network Topology WorksheetPage ___ of ____

Network Segment IP

Gateway to ESM Server

Gateways to other Networks



136

BMR Server Candidate Worksheet

Candidate ESM Servers Connectivity

Client Connec-tivity

Selected BMR Server

Operating System and Version:

ESM Client software and Version:

AIX: uname -mSolaris: hostidHP: uname -iBMR License Key



137

BMR File Server Worksheet

Page ___ of ____

Number of BMR ClientsNetwork Segment IP

Link Speed

AIX HP-UX NT Solaris4.1 4.2 4.3 10.20 11.00 4.0 2.6 7 8



138

BMR Shared Resource Tree Worksheet

BMR File Server HostnameBMR File Server OS and LevelBMR Boot Server Yes No

Network Segment IP’s Served

SRT OS and LevelRequire ESM Client Release and Version

Third Part Disk Device Driver and Volume Manager InformationThird Party Software or Drivers Used by BMR Clients

Veritas Volume Manager Version:

Veritas File System Version:OEM Network DriversOEM Disk DriversOther



139

Location of Images for SRT CreationOSESM ClientThird Party SoftwareNetwork Driver

Disk DriversOther:

Other:

NT License Key



140


Appendix C: Technical SupportFor technical support with Bare Metal Restore, please contact The Kernel Group:

• Email: [email protected]• Phone: 1-866-435-7854• Fax: 512.433.3200

Please refer to your maintenance agreement for further information about support terms and conditions.



142

bmr users guide tsm 143gold

Documents