Bare Metal Restore for Tivoli Storage Manager User Guideorigin-symwisedownload.symantec.com/resources/sites/SYMWISE/... · Bare Metal Restore for Tivoli Storage Manager User Guide

Bare Metal Restore for Tivoli Storage Manager

User Guide

Version 3.2.1

Bare Metal Restore for Tivoli Storage Manager Version 3.2.1User Guide Doc. Rev. December 2001, Copyright © 2001 by The Kernel Group, Inc. All rights reserved.

The Kernel Group, Inc., and TKG are registered trademarks of The Kernel Group, Inc.Bare Metal Restore™, AutoTrace™, SCTrace™, and ZeroFault™ are trademarks of The Kernel Group, Inc.

IBM® is a registered trademark of IBM Corporation. Tivoli® is a registered trademark of Tivoli Systems Inc. and IBM Corporation. VERITAS Volume Manager, VERITAS File System are trademarks of the VERITAS Software Corporation. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.This product includes software developed by the Apache Software Foundation (http://www.apache.org/).All other trademarks are the property of their respective owners.

Contact Information:The Kernel Group, Inc.1250 S. Capital of Texas Hwy.Suite 3-601Austin, TX 78746-6464

Phone: (512) 433-3300Toll Free: 800-854-7381Fax: 512-433-3200email: [email protected]

Technical Support:Phone (International): 01-512-433-3311Toll Free (U.S. only): 866-HELP-TKG (866-435--7854)email: [email protected]/support

mailto:[email protected]


http://www.tkg.com


Bare Metal Restore User Guide i

The Kernel Group, Inc. BMR v3.2.1

Table of Contents

Chapter 1Overview

New Features in Bare Metal Restore (BMR) - - - - - - - - - - - - - 2Windows 2000 TSM Backup Sets (CD) - - - - - - - - - - - - - 2Windows 2000 (CD) Media Boot- - - - - - - - - - - - - - - - - 2Windows 2000 Dissimilar Disk Restore (DDR) - - - - - - - - - - 2Windows 2000 Active Directory Authoritative Restore - - - - - - 2Windows 2000 Professional - - - - - - - - - - - - - - - - - - - 2Windows NT Device Driver Auto-Detect - - - - - - - - - - - - - 2Windows Multi-Language SRT - - - - - - - - - - - - - - - - - 3Windows NT Service Packs in SRT - - - - - - - - - - - - - - - 3Windows BMR Client Support of Microsoft Cluster Service (MSCS) 3HP-UX 11i Support - - - - - - - - - - - - - - - - - - - - - - - 3HP Ignite-UX 3.X Support - - - - - - - - - - - - - - - - - - - - 3Online Documentation- - - - - - - - - - - - - - - - - - - - - - 3

Components of Bare Metal Restore - - - - - - - - - - - - - - - - - 4BMR Server- - - - - - - - - - - - - - - - - - - - - - - - - - - 4Boot Server - - - - - - - - - - - - - - - - - - - - - - - - - - - 4File Server - - - - - - - - - - - - - - - - - - - - - - - - - - - 4TSM Server- - - - - - - - - - - - - - - - - - - - - - - - - - - 4

Sizing and Space Requirements - - - - - - - - - - - - - - - - - - - 5BMR Features - - - - - - - - - - - - - - - - - - - - - - - - - - - 6

Dissimilar Disk Restore (DDR)- - - - - - - - - - - - - - - - - - 6Media (CD) Boot - - - - - - - - - - - - - - - - - - - - - - - - 6Upgrade Mechanism - - - - - - - - - - - - - - - - - - - - - - 6Patch Mechanism - - - - - - - - - - - - - - - - - - - - - - - - 6

The Importance of Making a Complete Backup - - - - - - - - - - - 7A Complete Backup with Tivoli Storage Manager (TSM) - - - - - 7

BMR Client Installation and SRT Creation - - - - - - - - - - - - - - 8The Restoration Process - - - - - - - - - - - - - - - - - - - - - - 8

Vendor Partitions - - - - - - - - - - - - - - - - - - - - - - - - 8Advanced Features - - - - - - - - - - - - - - - - - - - - - - - 9TroubleShooting - - - - - - - - - - - - - - - - - - - - - - - - 9Patches and Upgrades - - - - - - - - - - - - - - - - - - - - - 9Deployment Planning - - - - - - - - - - - - - - - - - - - - - - 9Command References - - - - - - - - - - - - - - - - - - - - - 9Technical Support- - - - - - - - - - - - - - - - - - - - - - - - 9

Using this Manual - - - - - - - - - - - - - - - - - - - - - - - - - - 9

Chapter 2Install Bare Metal Restore

General Requirements to Install BMR - - - - - - - - - - - - - - - - - - 14General Requirements for BMR Installation on Servers - - - - - - - 14General Requirements for BMR Installation on Clients - - - - - - - - 14

AIX Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15System Requirements for AIX - - - - - - - - - - - - - - - - - - - - 15Installing the BMR AIX Server for AIX - - - - - - - - - - - - - - - - 15

Installing the BMR Server Using smitty - - - - - - - - - - - - - 16Installing the BMR Server Using installp - - - - - - - - - - - - - 16

ii

BMR v3.2.1 The Kernel Group, Inc.

Installing the BMR AIX Client - - - - - - - - - - - - - - - - - - - - 16Installing the BMR Client Using smitty - - - - - - - - - - - - - - 16Installing the BMR Client Using installp - - - - - - - - - - - - - 17

Solaris Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - 18System Requirements for Solaris - - - - - - - - - - - - - - - - - - 18Installing the BMR Solaris Server - - - - - - - - - - - - - - - - - - 18

Installing the BMR Server Using pkgadd - - - - - - - - - - - - - 18Installing the BMR Solaris Client - - - - - - - - - - - - - - - - - - 19

Install the BMR Client Using pkgadd- - - - - - - - - - - - - - - 19

HP-UX Installation - - - - - - - - - - - - - - - - - - - - - - - - - - - - 20System Requirements for HP-UX - - - - - - - - - - - - - - - - - - 20Installing the BMR HP-UX Server Using swinstall - - - - - - - - - - 20Installing the BMR HP-UX Client Using swinstall - - - - - - - - - - - 21

Windows NT Client Installation - - - - - - - - - - - - - - - - - - - - - 22System Requirements for Windows NT - - - - - - - - - - - - - - - 22

BMR Server Requirements - - - - - - - - - - - - - - - - - - - 22Installing the BMR Windows NT Client - - - - - - - - - - - - - - - - 22

Windows 2000 Client Installation - - - - - - - - - - - - - - - - - - - - 26System Requirements for Windows 2000 - - - - - - - - - - - - - - 26

BMR Server Requirements - - - - - - - - - - - - - - - - - - - 26Installing the BMR Windows 2000 Client - - - - - - - - - - - - - - - 27

Chapter 3Configure BMR

Configuring the BMR Servers and Clients - - - - - - - - - - - - - - - - 32Configuring the AIX BMR Server - - - - - - - - - - - - - - - - - - 32

Bare Metal Restore Server Configuration Process - - - - - - - - 32Configuring SAMBA- - - - - - - - - - - - - - - - - - - - - - - 33Install the License Key - - - - - - - - - - - - - - - - - - - - - 34

Configuring the AIX BMR Client - - - - - - - - - - - - - - - - - - - 34Configuring the Solaris BMR Server - - - - - - - - - - - - - - - - - 35


Configuring the Solaris BMR Client - - - - - - - - - - - - - - - - - 37Configuring the HP-UX BMR Server - - - - - - - - - - - - - - - - - 38


Configuring the HP-UX BMR Client - - - - - - - - - - - - - - - - - 40Configuring the Windows NT BMR Client - - - - - - - - - - - - - - 41Configuring the Windows 2000 BMR Client - - - - - - - - - - - - - 43Accessing the BMR GUI: - - - - - - - - - - - - - - - - - - - - - - 49

Controlling Access to the Administrative GUI- - - - - - - - - - - 51Adding TSM Servers - - - - - - - - - - - - - - - - - - - - - - - - 51Configuring TSM Servers - - - - - - - - - - - - - - - - - - - - - - 53Viewing the BMR Server Configuration - - - - - - - - - - - - - - - 54

BMR Log File - - - - - - - - - - - - - - - - - - - - - - - - - - 55BMR License Information - - - - - - - - - - - - - - - - - - - - 56

Creating Shared Resource Trees - - - - - - - - - - - - - - - - - - - - 58

Bare Metal Restore User Guide iii


Creating a Shared Resource Tree for AIX - - - - - - - - - - - - - - 58Resources needed to create an AIX SRT:- - - - - - - - 58Creating an SRT when using ADSM - - - - - - - - - - - - - - - 58Creating an SRT when using TSM- - - - - - - - - - - - - - - - 59

Creating a Shared Resource Tree for Solaris - - - - - - - - - - - - 59Resources needed to create Solaris SRTs: - - - - - - - - - - - 59Installing VERITAS File System / Volume Manager into a Solaris SRT60

Creating a Shared Resource Tree for HP-UX - - - - - - - - - - - - 62Resources needed to create HP-UX SRTs: - - - - - - - - - - - 62Install the TSM Client into the SRT - - - - - - - - - - - - - - - 62

Creating a Shared Resource Tree for Windows NT - - - - - - - - - 63Install the TSM Client into the SRT - - - - - - - - - - - - - - - 64

Creating a Shared Resource Tree for Windows 2000 - - - - - - - - 65

Configuring Media Boot - - - - - - - - - - - - - - - - - - - - - - - - - 68Creating a CD- - - - - - - - - - - - - - - - - - - - - - - - - - 68

Creating a CD-based SRT for AIX - - - - - - - - - - - - - - - - - - 69Creating a CD-based SRT for Solaris - - - - - - - - - - - - - - - - 70Creating a CD-based SRT for HP-UX - - - - - - - - - - - - - - - - 72Creating a CD-based SRT for Windows NT - - - - - - - - - - - - - 72Creating a CD-based SRT for Windows 2000 - - - - - - - - - - - - 75

Configuring Shared Resource Trees - - - - - - - - - - - - - - - - - - 80Modifying a Shared Resource Tree - - - - - - - - - - - - - - - 80Deleting a Shared Resource Tree - - - - - - - - - - - - - - - - 82Adding Network Interface Card Driver Support - - - - - - - - - - 82

Creating a Boot Image - - - - - - - - - - - - - - - - - - - - - - - - - - 84Configuring a Boot Image - - - - - - - - - - - - - - - - - - - - - - 86

Modifying a Boot Image - - - - - - - - - - - - - - - - - - - - - 88Deleting a Boot Image- - - - - - - - - - - - - - - - - - - - - - 88

Configuring a BMR Client using GUI - - - - - - - - - - - - - - - - - - 89

Creating a Boot Floppy - - - - - - - - - - - - - - - - - - - - - - - - - 92Create a Boot Floppy for Windows NT - - - - - - - - - - - - - - - - 92

Generic Network Boot Floppy Disk Creation - - - - - - - - - - - 93Create a Custom Network Boot Floppy - - - - - - - - - - - - - 96Create a Custom CD-Based Boot Floppy - - - - - - - - - - - 102

Create a Boot Floppy for Windows 2000 - - - - - - - - - - - - - - 107Create a Generic Network Boot Floppy for Windows 2000 - - - 108Create a Custom Network Boot Floppy for Windows 2000 - - - 115Create a Custom Media Boot Floppy for Windows 2000 - - - - 126

Chapter 4Restore a BMR Client

Preparing for Client Restoration - - - - - - - - - - - - - - - - - - - - 138Preparing an AIX Client for Restoration - - - - - - - - - - - - - - 138Preparing a Solaris Client for Restoration - - - - - - - - - - - - - 143Preparing an HP-UX Client for Restoration - - - - - - - - - - - - 144Preparing a Windows NT Client for Restoration - - - - - - - - - - 145Preparing a Windows 2000 Client for Restoration - - - - - - - - - 148

Initiating Client Restoration - - - - - - - - - - - - - - - - - - - - - - 153Restoring UNIX Clients - - - - - - - - - - - - - - - - - - - - - - 153

AIX Network Boot - - - - - - - - - - - - - - - - - - - - - - - 153

iv


Solaris Network Boot - - - - - - - - - - - - - - - - - - - - - 156HP-UX Network Boot - - - - - - - - - - - - - - - - - - - - - 157

Restoring a Windows NT Client - - - - - - - - - - - - - - - - - - 157Completing the Windows NT BMR Client Restore Process - - - 158

Restoring a Windows 2000 Client - - - - - - - - - - - - - - - - - 159Using Generic Boot Floppy - - - - - - - - - - - - - - - - - - 159Using Custom Boot Floppy - - - - - - - - - - - - - - - - - - 164Using Custom Media Boot Floppy - - - - - - - - - - - - - - - 168Active Directory Restores - - - - - - - - - - - - - - - - - - - 172

Chapter 5Advanced Features

Dissimilar Disk Restore (DDR) - - - - - - - - - - - - - - - - - - - - - 176Introduction to DDR - - - - - - - - - - - - - - - - - - - - - - - - 176Dissimilar Disk Restore for UNIX Clients - - - - - - - - - - - - - - 176Dissimilar Disk Restore for Windows NT / 2000 Clients - - - - - - 180

Backup Sets - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 184Using Backup Sets with Windows NT - - - - - - - - - - - - - - - 184Using Backup Sets with Windows 2000 - - - - - - - - - - - - - - 184

BareMetal Restore - - - - - - - - - - - - - - - - - - - - - - 185

Initiating a Client Restore using Media Boot - - - - - - - - - - - - - 187Media Boot for AIX - RS6K - - - - - - - - - - - - - - - - - - 187Media Boot for AIX - RSPC - - - - - - - - - - - - - - - - - - 187Media Boot for AIX - CHRP - - - - - - - - - - - - - - - - - - 187Media Boot for Solaris- - - - - - - - - - - - - - - - - - - - - 188Media Boot for HP-UX- - - - - - - - - - - - - - - - - - - - - 188Media Boot for Windows NT/2000 - - - - - - - - - - - - - - - 188

Service Packs for Windows NT - - - - - - - - - - - - - - - - - - - - 189Client Setup when a Service Pack is required - - - - - - - - - - - 189Creating a Service Pack - - - - - - - - - - - - - - - - - - - - - 190

Chapter 6Troubleshooting BMR

Solaris 2.6 causing panic on net or cdrom boot - - - - - - - - - - - - 194

How to find the correct MSD driver to add - - - - - - - - - - - - - - - 198

Identify the Vendor Partition During a Restoration - - - - - - - - - - 200

VERITAS File System without VVM - - - - - - - - - - - - - - - - - - 201

No System Objects - - - - - - - - - - - - - - - - - - - - - - - - - - 202

Unlabeled Disks in Solaris BMR Restores [9959] - - - - - - - - - - - 203

AIX 4.2.1 Boot Failure - - - - - - - - - - - - - - - - - - - - - - - - - 204

Boot from CD - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 205

BMR Server Setup - - - - - - - - - - - - - - - - - - - - - - - - - - - 206

Long Restore Times on HP - - - - - - - - - - - - - - - - - - - - - - 207

Chapter 7Upgrades and the Patch Mechanism

Major Features - - - - - - - - - - - - - - - - - - - - - - - - 210

Performing Upgrades - - - - - - - - - - - - - - - - - - - - - - - - - 211New Upgrade Procedure in 3.2.1 - - - - - - - - - - - - - - - - - 211

Upgrading the BMR server on AIX: - - - - - - - - - - - - - - 211Upgrading the BMR client on AIX: - - - - - - - - - - - - - - - 211

Bare Metal Restore User Guide v


Upgrading the BMR server on Solaris: - - - - - - - - - - - - - 212Upgrading the BMR client on Solaris: - - - - - - - - - - - - - 212Upgrading the BMR server on HP-UX: - - - - - - - - - - - - - 212Upgrading the BMR client on HP-UX: - - - - - - - - - - - - - 213Upgrading the BMR client on Windows NT: - - - - - - - - - - 213Upgrading the BMR client on Windows 2000: - - - - - - - - - 213

Using the Patch Mechanism - - - - - - - - - - - - - - - - - - - - - - 214UNIX Platforms - - - - - - - - - - - - - - - - - - - - - - - - 214Windows NT Platforms - - - - - - - - - - - - - - - - - - - - 214Windows 2000 Platforms - - - - - - - - - - - - - - - - - - - 215

Download New Patches - - - - - - - - - - - - - - - - - - - - - - 215Installing Software Fixes - - - - - - - - - - - - - - - - - - - - - 215

Server/Client Availability- - - - - - - - - - - - - - - - - - - - 215

Chapter 8BMR Deployment Planning

Placement of the BMR Servers - - - - - - - - - - - - - - - - - - 218Understanding the Tivoli Storage Manager - - - - - - - - - - 218Network Topography of the Tivoli Storage Manager Environment218Selection of the BMR Server - - - - - - - - - - - - - - - - - 219BMR File Server and Boot Server Placement - - - - - - - - - 219Understanding the use of the Shared Resource Tree- - - - - - 219

Platform Specific Requirements of BMR File Servers - - - - - - - 219General Considerations – All Platforms - - - - - - - - - - - - - - 220

AIX BMR File Server Selection - - - - - - - - - - - - - - - - 220HP-UX BMR file server Selection - - - - - - - - - - - - - - - 220Solaris BMR File Server Selection - - - - - - - - - - - - - - - 221Windows NT File Server Selections - - - - - - - - - - - - - - 221Windows 2000 File Server Selections - - - - - - - - - - - - - 221Third Party Disk Device Driver and Volume Manager Information221

Before Configuring the BMR Server - - - - - - - - - - - - - - - - 222Worksheets - - - - - - - - - - - - - - - - - - - - - - - - - - - - 222

vi


Appendix A:Command Reference 233

bmrconfig .............................................................. 234bmrcreatesrt .......................................................... 238bmrestore .............................................................. 240bmrmkcdimage ...................................................... 242lm_keyins .............................................................. 243bmrmap ................................................................. 244

Appendix B:Uninstall BMR Servers 247

Glossary 249

Technical Support Contact Information 251

Index 253


1 OverviewBare Metal Restore (BMR) provides disaster recovery features your backup system now lacks. BMR allows a machine to be completely restored from data saved in Tivoli Storage Manager (TSM). If a client loses its boot disk or suffers other catastrophic failure, Bare Metal Restore can restore the machine to the state at which it was last backed up to TSM. Separate system backups or reinstalls are not required. Bare Metal Restore is completely integrated into TSM.

Your clients are backed up to their TSM server(s) as usual - with two additional attributes:

• All of the clients’ files are backed up.

• The state of the machine configuration is saved.

BMR can completely recover a machine from the TSM backup.

Restoring a machine with Bare Metal Restore is fully automated. After installation and configuration, the entire restoration process consists of running one command on the BMR server and rebooting the client.

Topics covered in this chapter:“New Features in Bare Metal Restore (BMR)” on page 2“Components of Bare Metal Restore” on page 4“Sizing and Space Requirements” on page 5

“BMR Features” on page 6“Dissimilar Disk Restore (DDR)” on page 6“Media (CD) Boot” on page 6

“Upgrade Mechanism” on page 6“Patch Mechanism” on page 6

“A Complete Backup with Tivoli Storage Manager (TSM)” on page 7

New Features in Bare Metal Restore (BMR)


2

“The Importance of Making a Complete Backup” on page 7“The Restoration Process” on page 8

“Using this Manual” on page 9


Version 3.2.1 of Bare Metal Restore (BMR) adds the following new functionality. For details on each feature, see the appropriate section of this User Guide.

Windows 2000 TSM Backup Sets (CD)

Tivoli Storage Manager (TSM) allows a client's active files to be saved into a TSM backup set. A Windows 2000 BMR client can be restored using a TSM backup set when the backup set is stored on a CD that is placed in a CD drive locally connected to the Windows 2000 client.

Windows 2000 (CD) Media Boot

Media Boot allows a Windows 2000 BMR client to boot from a floppy disk and mount a Shared Resource Tree (SRT) from a local CD. The Windows 2000 Media Boot CD eliminates the need for the BMR servers at restore time.

Windows 2000 Dissimilar Disk Restore (DDR)

Windows 2000 restores can now use DDR to recover to a system with different disk drives. Supported differences include more or fewer disks, smaller or larger disks, and resized partitions.

Windows 2000 Active Directory Authoritative Restore

BMR now supports the ability to perform an authoritative restore of the Windows 2000 Active Directory. An authoritative restore is one in which the newly restored Active Directory database will be the master, and will be replicated to other domain controllers.

Windows 2000 Professional

BMR now supports Windows 2000 Professional in addition to the previously supported Windows 2000 Server and Advanced Server.

Windows NT Device Driver Auto-Detect

BMR Device Driver Auto-Detect enables BMR clients to obtain Network Interface Card (NIC) and Mass Storage Driver (MSD) device driver files from the live BMR client and to automatically use the correct drivers for each client during system recovery. Prior to availability of the Device Driver Auto-Detect feature, the user was responsible for



3

locating the necessary NIC and MSD drivers (usually at the manufacturer's web site or on the device's product disk), manually adding them to the SRT, and then selecting the correct drivers for use during system recovery.

BMR 3.2 introduced Device Driver Auto-Detect for Windows 2000 BMR clients. BMR 3.2.1 adds Device Driver Auto-Detect to the Windows NT platform.

Windows Multi-Language SRT

This feature allows the creation of a Windows NT or Windows 2000 Shared Root Tree (SRT) from a non-English Windows installation CD. Support is limited to single-byte non-English versions of Windows. BMR Guns, wizards, messages and logs are still in English, but BMR will function properly in the non-English environment.

Windows NT Service Packs in SRT

Previous versions of BMR used a base version of Windows NT during the temporary NT installation during recovery. Certain devices (e.g., most GB Ethernet adapters) require Windows NT Service Packs to function properly. Such devices could not be supported by BMR during system recovery.

In BMR 3.2.1, a new wizard has been added to NT BMR clients. This wizard allows a Service Pack to be added to an existing NT SRT. In most cases, adding NT Service Packs to SRTs is not necessary, but the functionality is provided to support recovery of clients that require Service Packs.

Windows BMR Client Support of Microsoft Cluster Service (MSCS)

BMR 3.2.1 has been validated with MSCS on Windows NT and 2000. BMR protects clustered systems and can be used to recover a failed system that is configured as a MSCS cluster node.

HP-UX 11i Support

BMR 3.2.1 supports HP-UX 11i (sometimes known as 11.11) for use on BMR clients and servers.

HP Ignite-UX 3.X Support

BMR 3.2.1 supports the use of Ignite-UX 3.4 to build SRTs for BMR HP-UX clients. Previous versions of BMR supported up to Ignite-UX 2.5.

Online Documentation

BMR 3.2.1 will allow access of the BMR User Guide from the BMR Administrative GUI and BMR Wizards.

Components of Bare Metal Restore


4

Components of Bare Metal Restore

BMR uses your existing TSM server(s) and adds BMR server, boot server, and File server components. The BMR components can be located on the same machine, on a separate machine or on a combination of machines.

Note: Throughout 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 Server

The 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 Server

The 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 a client from the boot server.

File Server

The 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 TSM client package.

Note: SAMBA code is included to allow Windows BMR clients to access the SRT on UNIX BMR File servers.

TSM Server

The BMR client continues to use its assigned TSM server but BMR 3.2.1 adds functionality to that server. At backup time, BMR saves the client’s configuration so that an up-to-date snapshot of the machine configuration is always saved with the system’s data.

Important! In order to recover your machine from your TSM servers, all files (including system files) must be backed up to the TSM server.

Sizing and Space Requirements


5

Sizing and Space Requirements

1 Unless using Solaris relay boot servers or DHCP2 When Main, File, and boot servers are collocated, only count once3 Space Reservation File. 4 Windows 2000 requires a minimum partition of 1.2GB. BMR requires 500MB free space to install and 512 MB reservation.

BMR Component Quantity Rules of Thumb Sizes

Main Server Executables Usually 1 Main server per site AIX 15 MB 2

Solaris 50 MB 2

HP-UX 29 MB 2

Main Server Database 1 per Main server Approx. 300-600 KB per Windows client, less than 1 KB per Unix client

File Server Executables 1 per platform (AIX),

1 per subnet (Solaris1 & HP-UX) Same as for BMR Main server 2

File Server Samba Executables 1 per File server AIX 7 MBSolaris 10 MBHP-UX 7 MB

File Server SRTs

Varies per platform:

• Typically one SRT per OS level to be restored (e.g. AIX 4.1, 4.2, 4.3)

• Cross-level restores possible in some cases; e.g. Solaris 7 & 8

NT 100-150 MBW2K 350-400 MBSolaris 200-350 MBAIX 150-200 MBHP-UX 70-100 MB

Boot Server Executables 1 per platform (AIX), 1 per subnet (Solaris1 & HP-UX)

Same as for BMR Main server 2

Boot Server Boot Images Varies per platform:

• AIX - up to 12 BIs per SRT

• Solaris - up to 4 BIs per SRT

• HP-UX - 1 BI per SRT

• Windows is not applicable

AIX 3-6 MB per BI, max 72MB per SRT

Solaris 90-200 KB per BI, max .8MB per SRT

HP-UX 35-100MB per BI (and per SRT)

Client Executables


• Unix has only executables

• Windows has executables and space reservation files

NT 210 MB+200 MB 3

W2K 4 512 MB+500 MB 3

Solaris 264 KBAIX 456 KBHP-UX 251 KB

Client Data Files


• Unix has several files

• Windows has one file, contains device drivers

NT .5 - 2 MBW2K 1 - 3 MBSolaris <1 MBAIX <1 MBHP-UX <1 MB

BMR Features


6

BMR Features

Dissimilar Disk Restore (DDR)

Introduced in Version 3.1.0, DDR enhances the ability of BMR to restore to a box that has a hardware configuration different from that of the backed up client. The focus of the new DDR feature is to support restores to machines that have the following disk differences:

• Larger disks

• Smaller disks

• Disks at different locations (addresses)

• Smaller number of disks

• Larger number of disks

• Restoration granularity at the filesystem level.

Detailed information about Dissimilar Disk Restore can be found in Chapter 4, Restore a BMR Client.

Note: DDR does not support VERITAS Volume Manager or VERITAS File Manager.

Media (CD) Boot

Media Boot was added in Version 3.1.0, and provides the option to create a bootable CD that can be used in place of a network boot. The Media Boot CD limits or eliminates network access to the BMR servers at restore time.

Refer to Chapters 4, Configure BMR, and Chapter 5, Restore a BMR Client, for more information on media boot.

Upgrade Mechanism

This section describes the upgrade and patch mechanisms for Bare Metal Restore. BMR provides a mechanism to upgrade from release 1.4.3, 3.1.0, 3.1.1, or 3.2.0. The upgrade mechanism preserves client-server relationships.

Refer to Chapter 6, Upgrades and the Patch Mechanism, for additional information.

Patch Mechanism

The patch mechanism allows software fixes to be applied within a release. Contact TKG Support to find out how to download a patch or go to www.tkg.com/support to review and download patches for BMR.

Refer to Chapter 6, Upgrades and the Patch Mechanism, for more information on the patch process.

http://www.tkg.com/support

The Importance of Making a Complete Backup


7

The Importance of Making a Complete Backup

Important! To further clarify, you must successfully save the configuration (bmrsaveconfg) and then com-pletely backup a client before BMR can restore that client.

In order for BMR to restore a client from the files backed up to the TSM, all operating system files must be backed up. Because these system files typically do not change, regular incremental backups do not increase in size. 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.

• If you have denied access to any files during the backup, they do not get backed up.

It is, therefore, important that you follow these guidelines to obtain a proper backup:

• Regularly examine the storage manager log files to ensure that any backup errors are handled promptly.

• 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. You may find a tool such as this useful to enhance the integrity of your backup.

A Complete Backup with Tivoli Storage Manager (TSM)

In order to get a complete system backup with TSM, the dsm.opt and dsm.sys files must be inspected to verify that all files are specified to be backed up and that there are no system directories in the Exclude list. For example, on NT systems, the Exclude list should not include %systemroot%\system32\config, and the BACKUPRegistryNo flag should not be set in the dsm configuration files.

In order for BMR to restore an NT client, the registry must be backed up. On NT clients, the system registry is backed up separately from the other files on the client. This can be done by selecting the SYSTEM icon in addition to the LOCAL icon from the TSM Client GUI. On the command line, the NT registry can be backed up with the command:

dsmc backup reg entire

The NT registry changes often, such as when software is added or deleted. For that reason, it is important to regularly backup registry changes that will be needed at restoration.

Important!

You must do a complete backup of your client before BMR can restore that client.

BMR Client Installation and SRT Creation


8

BMR Client Installation and SRT Creation

Installing BMR on a client is a one-time task. So is creating an SRT. Once these tasks are completed, BMR uses a highly automated process to rapidly restore a BMR client. Refer to Chapter 2 “Install Bare Metal Restore” and chapter 3 “Creating Shared Resource Trees” on page 58 and “Configuring Shared Resource Trees” on page 80”.

The Restoration Process

The standard restore process:

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

2. Boot the client from the BMR boot server or the BMR boot floppy. The BMR client starts running its customized restore procedure.

3. The client mounts the necessary filesystems from the File server.

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

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

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

7. The client reboots itself.

8. 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 amount of time required for the restoration is determined by a number of variables such as network speed, TSM server performance, tape access times, etc.

Vendor Partitions

To determine if your special partition (vendor partitions) 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.

• 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 Windows NT, primary partitions 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 exact position and length can change. Because the saved partition information was backed up for the client, BMR cannot create a duplicate special partition.

Using this Manual


9

Advanced Features

The following features, described fully in Chapter 5, may apply to your environment:

• Dissimilar Disk Restore (DDR)

• Using Backup Sets with Windows NT

• Media Boot

• Service Packs for Windows NT

TroubleShooting

Tips, solutions, work-arounds, FAQs— all under the topic of Troubleshooting, in Chapter 6.

Patches and Upgrades

Patches and upgrades, and where to get them, are described in Chapter 7. Contact TKG Support to find out how to download a patch or go to www.tkg.com/support to review and download patches for BMR.

Deployment Planning

If you care to use them, this manual contains notes and considerations, procedures, and worksheets designed to assist you with the installation of Bare Metal Restore (BMR) into your network environment. Refer to Chapter 8 in this book.

Command References

A complete command reference library is included in Appendix A.

Technical Support

If you require technical assistance using Bare Metal Restore, call TKG Support:

• 1-512-433-3311 or

• toll free, within the U.S. only, at 1-866-HELP-TKG (1-866-435-7854).

You can also visit our support website at www.tkg.com/support.

Contact technical support by email at [email protected].

Using this Manual

Conventions Used in this Book

Note: A note conveys information that is useful, but not essential.




Using this Manual


10

Important! Important tips or cautions are set off by rules.

code is written in bold Courier New, a monospaced font

When a command is too long to fit on one line within the text of this document, the following guidelines apply:

The caption on a screen button or menu item selection is Arial bold. Example: Click Save.

Keyboard actions are bold. Example: Press Enter.

1. When a space appears at the beginning of the second and/or consecutive lines of the command string shown, you are required to enter a space when you type the command.

2. When no space appears at the beginning of the second and/or consecutive lines of the command string shown, the command string continues with no spaces.

For example if you see this:

copy \program files\tkg\baremetelrestore\binbmrrc.exe c:\program files\microsoft visualstudio\vc98\bin\cl.exe

DO enter a space between visual and studio

DO NOT enter a space between \bin and bmrrc.exe

Using this Manual


11

A graphical representation of how this manual is organized:

Using this Manual


12


2 Install Bare Metal RestoreThis chapter covers the installation of the BMR server and the BMR clients on five operating systems.

Note: All BMR boot, file, and BMR servers must be running the same version of BMR software. The BMR clients can be back level to the version running on the servers.

Topics covered in this chapter:“AIX Installation” on page 15“Solaris Installation” on page 18“HP-UX Installation” on page 20

“Windows NT Client Installation” on page 22“Windows 2000 Client Installation” on page 26

Bare Metal Restore User GuideInstall Bare Metal Restore


14

General Requirements to Install BMR

General Requirements for BMR Installation on Servers• You must be the root user to perform the BMR file and boot server installation tasks.

• Verify the minimum system requirements

• Install and configure the BMR server. You must perform this procedure on the BMR server, file server, and boot server.

General Requirements for BMR Installation on Clients• You must be the root user to perform the BMR client installation tasks.

• Verify the minimum system requirements

• Each BMR client must have the BMR client software installed and the client TSM configuration must be modified to support BMR. Specifically, all client files must be backed up to the TSM server, and the bmrsavecfg command must be run before each backup to save the current machine configuration.

Important! If bmrsavecfg is not run, the client cannot be restored.

• Before installing the client(s) you must first define the TSM client(s).

AIX InstallationSystem Requirements for AIX


15

AIX Installation

System Requirements for AIX

Installing the BMR AIX Server • BMR file and boot servers can reside on the same machine or on different machines.

Hardware Requirements: Software Requirements:

TSM Server Requirements

• Any type of machine that can function as an TSM server

• Ample storage space to completely back up all the BMR clients

• ADSM server version 3.1, or TSM version 3.7, 4.1, or 4.2

BMR Server Requirements

• Any model of machine that runs AIX 4.1, 4.2, or 4.3

• Network connectivity to the BMR client machines and their TSM server(s)

• The backup and administrative clients for ADSM version 3.1, or TSM version 3.7, 4.1, or 4.2Note: 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 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

• AIX level higher than or the same as the protected BMR clients

• NFS server software

Boot Server Requirements

• Network connectivity to the BMR client machines and the BMR serverNote: File server and boot server can be, but are not required to be, the same machine

• AIX level higher than or the same as the protected BMR clients

• Bootp server software

• tftp server software

BMR Client Requirements


• SCSI disks are the only type of disk drive supported

• Network connectivity to the BMR file, boot, and TSM servers that are available at boot timeNote: 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. Please note that BMR does not destroy data on SSA drives.

• AIX 4.1, 4.2, or 4.3

• The bos.sysmgmt.sysbr fileset for AIX 4.1.x.x and 4.2.x.x clients

• The backup client for ADSM version 3.1.1, or TSM version 3.7, 4.1, or 4.2



16

Installing the BMR Server Using smitty

To install the BMR server using the smitty:

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

2. Enter the following command:

smitty install_latest

The Install and Update from Latest Available Software screen 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 Latest Available Software screen redisplays.

4. While on the ‘SOFTWARE to install’ option, 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 smitty.

When the BMR server software is installed, you must configure the server using bmrsetupserver as explained in Chapter 4.

Installing the BMR Server Using installp

Use 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.


installp -acXd <pathname> BareMetal.server

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

When the BMR server software is installed, you must configure the server using bmrsetupserver, as explained in Chapter 4.

Installing the BMR AIX Client

Installing the BMR Client Using smitty

Use the following command to install the BMR client using the smitty. This procedure must be performed on each client machine.



smitty install_latest

The Install and Update from Latest Available Software screen displays.

AIX InstallationInstalling the BMR AIX Client


17

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 Latest Available Software screen redisplays.

4. While on the ‘SOFTWARE to Install’ option, 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.

7. Press F10 to exit smitty

When the BMR client software is installed, you must configure the client using bmrsetupclient, as explained in Chapter 4.

Installing the BMR Client Using installp

Use 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.


installp -acXd <pathname> BareMetal.client

3. The pathname should be set to the path of the BareMetal distribution file or the device name of the CD-ROM drive.

4. When the BMR client software is installed, configure the client using bmrsetupclient, as explained in Chapter 3.



18

Solaris Installation

System Requirements for Solaris

Installing the BMR Solaris ServerNote: BMR file and boot servers must reside on the same machine.

Installing the BMR Server Using pkgadd

Use the following steps to install the BMR server using pkgadd.









• Any Sparc architecture model of machine that runs Solaris 2.6, 7, or 8


• The backup and administrative clients for ADSM version 3.1, or TSM version 3.7, 4.1, or 4.2

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

File Server/Boot Server Requirements



• Enough disk space to hold the SRT filesystems used by clients at restore time, approximately 300 MB per level of OS supported

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

• Solaris 2.6, 7, or 8

• NFS server software (which includes nfsd, rarpd, bootparamd, tftpd)



• 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 TSM that are available at boot time

• SSA drives are not supported by Bare Metal Restore. Please note that BMR does not destroy data on SSA drives.

• Solaris 2.6, 7, or 8

• The backup client for ADSM version 3.1.1, or TSM version 3.7 or above

Solaris InstallationInstalling the BMR Solaris Client


19

pkgadd -d <pathname> BMRserver

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


Installing the BMR Solaris Client

Install the BMR Client Using pkgadd



pkgadd -d <pathname> BMRclient

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

When the BMR client software is installed, you must configure the server using bmrsetupclient, as explained in Chapter 3.



20

HP-UX Installation

System Requirements for HP-UX

Installing the BMR HP-UX Server Using swinstall

To install the BMR server, do the following:

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

• pfs_mountd&

• pfsd 6&

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

To check what daemons are currently running enter the following command:

ps -ef | grep pfs

2. Create a mount point:

mkdir /bmr_cdrom

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







• Any model of machine that runs HP-UX 10.20 or higher


• The backup and administrative clients for ADSM version 3.1, or TSM version 3.7Note: The version of ADSM or TSM software must be the same version or higher than the BMR client’s version of software.

File Server/File Server Requirements



• Enough disk space to hold the SRT filesystems used by clients at restore time, approximately 80 MB per level of OS supportedNote: Boot servers and file servers must be configured as a single machine.

• HP-UX level higher than or the same as the protected clients

• Ignite server 2.4 installed

• GNU zip utility



• 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 TSM servers that are available at boot time

• HP-UX 10.20 or higher

• The backup client for ADSM version 3.1, or TSM version 3.7

HP-UX InstallationInstalling the BMR HP-UX Client Using swinstall


21

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

6. Clean up the installation of BMR:

rm -r /bmr_cdrom


Installing the BMR HP-UX Client Using swinstall

To install the BMR client, do the following:

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

pfs_mountd&

pfsd 6&

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

To check what daemons are currently running enter the following command:

ps -ef | grep pfs


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 client software using this command:

swinstall -s /bmr_cdrom/hp BareMetal.client



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, as explained in Chapter 3.



22

Windows NT Client InstallationThis section covers the installation of the BMR client on a Windows 2000 computer.

You can complete the entire installation process (install, setup, and configuration) using the CD, or you can install BMR v3.2.1 using the CD and then stop the procedure by clicking Cancel. Once you have installed BMR v3.2.1 on your system, the setup and configuration can be completed at any time. Do any of the following by clicking on the Start menu, then Programs, then Bare Metal Restore:

• Add a driver

• Create a new floppy boot disk

• Create an SRT

• Setup a Client

• Save a Configuration

System Requirements for Windows NT

The following requirements must be met to use Bare Metal Restore.


The BMR server, boot server, and file server should be UNIX (AIX, HP-UX, Solaris) systems, though all can be on one system. Refer to the previous sections in this chapter for the system requirements for those servers and for the TSM system requirements.

Installing the BMR Windows NT Client

The following procedure installs Bare Metal Restore onto your client computer. After BMR is installed using the CD-ROM, continue (now or later) the setup procedures from the Start Menu.

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

2. Do one of the following:

• If your CD-ROM does not have autorun enabled, click Start - Run - and type D:\setup.exe, where D: is the letter of your CD-ROM drive. The install shield loads and the Welcome screen displays.



• Any type of machine that can function as a TSM server


• TSM version 4.1.2 or later


• ISA or PCI based PC.

• If two identical ISA-based NICs exist on the machine, the wrong interface for restoring files may be configured during recovery.

• Ethernet card with a NDIS 2.0 (DOS) driver available

• Windows NT 4.0

• TSM version 3.7, 4.1, or 4.2

• SAMBA server. Refer to the relevant section in this chapter about running bmrsetupserver for instructions on installing and configuring the SAMBA server.

Windows NT Client InstallationInstalling the BMR Windows NT Client


23

• If your CD-ROM does have autorun enabled, the install shield runs automatically when the disk is put into the drive. The install shield loads and the Welcome screen displays.



24

3. After reading the information on the installation screen, click Next. The Destination Folder dialog displays:

4. The program installs into the default directory: (C:\Program Files\TKG\BareMetal\). To change the destination, click Change and define the destination directory.

5. Click Next. A status dialog displays;

Windows NT Client InstallationInstalling the BMR Windows NT Client


25

When the installation is complete the following dialog displays:

The Bare Metal Restore is installed successfully.

6. Click Finish.

7. Remove the CD from the disk drive. Continue with the configuration steps by accessing BMR through the Start menu, as shown below:



26

Windows 2000 Client InstallationThis section covers the installation of the BMR client on a Windows 2000 computer.

You can complete the entire installation process (install, setup, and configuration) using the CD, or you can install BMR v3.2.1 using the CD and then stop the procedure by clicking Cancel. Once you have installed BMR v3.2.1 on your system, the setup and configuration can be completed at any time.

Do any of the following by clicking on the Start menu, then Programs, then Bare Metal Restore:

• Create a new boot disk

• Create an SRT

• Save a Configuration

• Setup a Client

System Requirements for Windows 2000


Refer to the previous sections in this chapter for the system requirements for those servers and for the TSM server system requirements.

To support Windows 2000 BMR clients, the BMR file server must have a SAMBA server installed. Refer to the relevant section in this chapter about running bmrsetupserver for instructions on installing and configuring the SAMBA server.



• Any type of machine that can function as a TSM server


• TSM version 4.1.2 or later

BMR File Server • SAMBA server


• PCI based PC

• Ethernet card with a NDIS 2.0 (DOS) driver available

• Windows 2000 with Service Pack 2, if using Active Directory

• Backup client for TSM 4.1.3 or later

Windows 2000 Client InstallationInstalling the BMR Windows 2000 Client


27

Installing the BMR Windows 2000 Client1. Insert the BMR v3.2.1 CD. The Install Wizard automatically begins the Setup process. The Install Shield

Wizard displays.



28

2. Click Next. The Readme dialog displays.

3. Click Next. The Destination Folder dialog displays.

4. Check the default destination folder:



29

• To install in a different folder, click Change, select a destination folder, then click Next

• To install to the default folder, click Next

The InstallShield Wizard begins. The Status bar displays the install progress

When installation is complete the Wizard Completed dialog displays.



30

5. Click Finish. The Install process is complete. The BMR Setup Wizard displays.

6. You can do one of the following:

• Click Next to continue with the client setup process. Go to Chapter 3, “Configuring the Windows 2000 BMR Client” on page 43

• Click Cancel, and continue later from the Start menu.


3 Configure BMR

Once Bare Metal Restore is installed on the BMR server, file server, boot server, and clients you can 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.

Topics covered in this chapter:“Configuring the BMR Servers and Clients” on page 32“Creating Shared Resource Trees” on page 58

“Configuring Media Boot” on page 68“Configuring Shared Resource Trees” on page 80“Creating a Boot Image” on page 84

“Configuring a BMR Client using GUI” on page 89“Creating a Boot Floppy” on page 92

Bare Metal Restore User GuideConfigure BMR


32

Configuring the BMR Servers and Clients

Configuring the AIX BMR Server

The bmrsetupserver program configures the BMR server. This command must be run while logged in as the root user. bmrsetupserver must be run on all three servers; BMR, File, and boot servers.

1. Create a BMR administrator user and group on your AIX server.

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

2. Change the current directory to:

/usr/lpp/BareMetal


./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 appear. The questions below indicate a system where the BMR server, boot server, and file server are all the same machine.

Bare Metal Restore Server Configuration Process

a. Before you begin the BMR setup process, it is recommended that you check the TKG web site at http://www.tkg.com/support for the latest patch information. Continue with setup right now? [N] y

Note: If an upgrade situation is detected at this point, prompts confirming the upgrade appear. Otherwise, the following configuration interaction occurs:

Note: All UNIX systems with Windows clients need SAMBA so the Windows client can see the UNIX hard disks. If you need to configure SAMBA, refer to instructions, “Configuring SAMBA,” in the next section of this chapter.

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

c. Enter BMR server's hostname [somemachine]:

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

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

f. Enter the BMR administrator's group name [bmradmin]:

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

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

i. Enter DSM_DIR [/usr/tivoli/tsm/client/ba/bin]:

j. BMR can log messages to a log file or to syslog. Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [s]:

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

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

Configuring the BMR Servers and ClientsConfiguring the AIX BMR Server


33

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

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

o. If you answered n to this question, refer to 'How to Configure SAMBA.”

p. Enter the SAMBA user name [bmradmin]:

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

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 should enter a value leaving off the undesired interfaces.

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

These are host and network values that control which IP addresses will be able to access SAMBA. By default they will be all hosts on the subnets of the local interfaces only.

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

This directory must be writeable by the SAMBA user entered above. If it does not exist, it will be cre-ated as owned by that user. Otherwise, you are warned to make it writeable by that user.

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

The program pauses for a brief period, while waiting for all the BMR daemons to start, and then exits.

Configuring SAMBA

When you run “bmrsetupserver”, you have the option to have our script modify the smb.conf file. If you choose to not have our script do the modification, the file server will not service win32 (NT and 2000) clients. This instruction explains how to enable this service.

How to Modify an existing file server to support NT and 2000 clients using SAMBA

Make sure the SAMBA configuration file (/usr/local/lib/smb.conf) has the following modifications:

1. Modify “hosts allow” to specify the networks/hosts that have access to this samba server.

2. Modify “interfaces” to specify the interfaces you want samba service to be available on.

3. Modify “guest account=” to specify the BMR admin user name.

4. Add a stanza called, “[bmrsrt]” with the following attributes:

• [bmrsrt]

• comment = BMR shared resource tree

• path = /export/srt

• writable = yes

• printable = no

Note: The path is set to the shared root tree directory



34

5. Set ‘FSwin and FSsmbpath’ for this file server. For example, if the file server is named “fileserver” and your path as specified in the above stanza is ‘/export/srt’ then you would run the following command from the file server:

bmrc -h <bmr server hostname> -p <bmr server port number> -o change -r FS fileserver“FSwin+enabled\nFSsmbpath=/export/srt”

6. Make sure the BMR admin user can write into the SRT. For example:

chmod +w /export/srtchown bmradmin /export/srt

Install the License Key

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.


/usr/lpp/BareMetal/aix

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.

Configuring the AIX BMR Client1. The bmrsetupclient program configures the client. Run this command while logged in as the root user.


/usr/lpp/BareMetal


./bmrsetupclient

The following is an example of the information that the system asks for when bmrsetupclient runs. If you are upgrading from a previous version of BMR, there is an alternate prompt which confirms the upgrade. Otherwise, the following configuration interaction occurs:

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.

Configuring the BMR Servers and ClientsConfiguring the Solaris BMR Server


35

Configuring the Solaris BMR Server

The bmrsetupserver program configures the server. This command must be run while logged in as the root user. bmrsetupserver must be run on all three servers.

1. Create a BMR administrator user and group.

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


/opt/BareMetal


./bmrsetupserver










f. Enter the BMR administrator's group name [bmradmin]:



i. Enter DSM_DIR [/opt/tivoli/TSM/client/ba/bin]:

j. BMR can log messages to a log file or to syslog.Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [s]:




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



36

o. If you answered n to this question, refer to 'How to Configure SAMBA.”

p. Enter the SAMBA user name [bmradmin]:

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


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


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

This directory must be writeable by the SAMBA user entered above. If it does not exist, it will be created as owned by that user. Otherwise, you are warned to make it writeable by that user.

Note: On Solaris, BMR file servers are automatically configured as boot servers as well.


Configuring SAMBA





2. modify “interfaces” to specify the interfaces you ant samba service to be available on.



• [bmrsrt]



• writable = yes

• printable = no





Configuring the BMR Servers and ClientsConfiguring the Solaris BMR Client


37





/opt/BareMetal/sol

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



Configuring the Solaris BMR Client

The bmrsetupclient program configures the client. This command must be run while logged in as the root user.


/opt/BareMetal


Note: Be sure you have defined all ESM servers to the BMR server before you run bmrsetupclient

./bmrsetupclient

The following is an example of the information the system asks for when bmrsetupclient runs. If you are upgrading from a previous version of BMR, there is an alternate prompt which confirms the upgrade. Otherwise, the following configuration interaction occurs:.

a. Enter BMR server's hostname []:


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

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

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


bmrsetup server automatically defines the ESM servers that it uses for backup. At that time, all ESM servers used by clients should already be defined. If they are not already defined, the process will not be successful.



38

Configuring the HP-UX BMR Server

The bmrsetupserver program configures the server. This command must be run while logged in as the root user. bmrsetupserver must be run on all three servers.

Note: A BMR file server cannot coexist with an Ignite-UX server. Because BMR makes use of some Ignite-UX components it is possible that BMR activities will conflict with those of an Ignite-UX server. Specifically, both servers, BMR and Ignite-UX, make use of the /opt/ignite/boot directory. Either service can overwrite files placed in this directory by the other service.

1. Create a BMR administrator user and group.

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


/opt/BareMetal


./bmrsetupserver










f. Enter the BMR administrator's group name [imnadm]:



i. Enter DSM_DIR [/opt/tivoli/ TSM/client/ba/bin]:

j. BMR can log messages to a log file or to syslog.Enter 'm' to use /var/bmr/log/messages or 's' to use syslog [s]:



Configuring the BMR Servers and ClientsConfiguring the HP-UX BMR Server


39


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

Note: If you answered n to this question, refer to 'How to Configure SAMBA.”

o. Enter the SAMBA user name [bmradmin]:

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


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


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

This directory must be writeable by the SAMBA user entered above. If it does not exist, it will be cre-ated as owned by that user. Otherwise, you are warned to make it writeable by that user.

Note: On HP-UX, BMR file servers are automatically configured as boot servers as well.


Configuring SAMBA





2. modify “interfaces” to specify the interfaces you ant samba service to be available on.



• [bmrsrt]



• writable = yes

• printable = no




40








/opt/BareMetal/hp

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



Configuring the HP-UX BMR Client

The bmrsetupclient program configures the client. This command must be run while logged in as the root user.


/opt/BareMetal


./bmrsetupclient

The following is an example of the information the system asks for when bmrsetupclient runs. If you are upgrading from a previous version of BMR, there is an alternate prompt which confirms the upgrade. Otherwise, the following configuration interaction occurs:

a. Enter BMR server's hostname []:


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

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

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


Configuring the BMR Servers and ClientsConfiguring the Windows NT BMR Client


41

Configuring the Windows NT BMR Client

To configure the Windows NT client for BMR:

3. Click Next. The TSM Configuration screen displays.

4. Using the Browse button, find the DSM.opt file. The TSM Server Name and TSM Client Node Name fields are automatically filled in.

Field Description

Location of the dsm.opt file The dsm.opt file contains configuration and system information for the TSM client.

TSM Server Name Name of the computer (resolvable to an IP address) that will be the BMR server for this client.

TSM Client Node Name Port on which the BMR server will be listening. By default, this is 8362.



42

5. Click Next. The Service Pack Option screen displays:

The service pack option is only required if a service pack is required during the restore. The most flexible configuration is to keep the “Service Pack Required” box checked.

6. Click Next. The setup client verification screen displays.

Configuring the BMR Servers and ClientsConfiguring the Windows 2000 BMR Client


43

7. All the above information comes from the dsm.opt file (which contains configuration and system information for the TSM client) except the TSM file. Do one of the following:

• If you want to change this file, click Back. The TSM Configuration dialog redisplays.

• Click Finish. The BMR client creates the reservation space, registers the client, verifies the license, and completes the setup process. When it is finished the machine is completely configured as a Bare Metal Restore client.

If there is no Windows NT SRT, the above procedure prints a warning stating that an SRT needs to be created. Refer to the section, ‘Creating a Shared Resource Tree for Windows NT’ for additional information.

Configuring the Windows 2000 BMR Client

The Bare Metal Restore Setup Wizard follows automatically from the Install Wizard if you choose continue with the configuration process at the time of installation. If you click Cancel, you can complete the BMR client configuration later by accessing BMR from the Start menu.

Configure the Windows 2000 BMR Client

1. From the Start menu, select Programs, then select Bare Metal Restore, then select Setup Client.



44

The Setup Wizard displays. This wizard helps you register your Windows 2000 computer with a BMR server.



45

2. Click Next. The BMR Server Information dialog displays:

3. Enter the name of the computer that will be your BMR server.

4. 8362 is the default server port. If this is not correct, enter the correct number

Field Description

BMR Server Name Name of the computer (resolvable to an IP address) that will be the BMR server for this client.

BMR Server Port Port on which the BMR server will be listening. By default, this is 8362.



46

5. Click Next. The TSM Configuration dialog displays:

6. If the path or filename of the dsm.opt file is not correct, click Browse and locate the correct dsm.opt configuration file.

Field Description

Location TSM options file.

TSM Server Name Name of the TSM server. This field is automatically filled from the dsm.opt.file and cannot be changed.

TSM Client Node Name Name by which the TSM server knows this client. This field is automatically filled from the dsm.opt.file and cannot be changed.



47

7. Click Next. The BMR Client Registration dialog displays. The list is checked off as each item is completed.The program stops at “Run Create SRT Wizard” (green arrow) and a 2nd dialog (Create a New SRT?) displays (see below):

Note: The Configure Client step can take a few minutes. The status is displayed in the box.

a. To create an SRT later, click Create it Later. If you click Create it Later, the setup wizard continues, but you can create an SRT later as explained in Chapter 3 “Creating a Shared Resource Tree for Win-dows 2000” on page 65.



48

b. To create an SRT now, click Create an SRT Now. If you click Create an SRT Now, the dialog (Create a New Shared Resource Tree (SRT) displays. Go to Chapter 3 “Creating a Shared Resource Tree for Win-dows 2000” on page 65 to continue with the Create SRT process.

8. The boot floppy creation process follows automatically after the Create an SRT process. The Boot Options Wizard displays:

a. To create an boot floppy later, click Create it Later. If you click Create it Later, the setup wizard continues, but you can create a boot floppy later as explained in Chapter 3 “Create a Boot Floppy for Windows 2000” on page 107.

b. To create an boot floppy now, click Create a Floppy Now. If you click Create a Floppy Now, the dialog (Boot Floppy Option) displays. Go to Chapter 3 “Create a Boot Floppy for Windows 2000” on page 107 to continue with the boot floppy creation process.

9. When all the steps in the setup wizard are complete, the client is registered with the BMR server:

Reminder: you must make at least one complete system backup before a system restore can take place.

Configuring the BMR Servers and ClientsAccessing the BMR GUI:


49

The final checkmark displays on the BMR Client Registration dialog.

When the process is completed, the Finish button becomes active (black).

10. Click Finish. BMR has been successfully configured.

Accessing the BMR GUI:

The BMR Graphical User Interface (GUI) is a web based administrative tool, accessed from a browser.

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 GUI 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.



50

3. Enter “bmradmin” as the username and the password. The BMR GUI screen displays with the BMR navigation bar on the left side of the screen:

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

• BMR servers

• Enterprise Storage Management (ESM) servers

Note: ESM refers to Tivoli Storage Manager (TSM)

• Shared Resource Trees

• Boot images

• BMR clients

Common buttons used throughout the Bare Metal Restore GUI:

Button Function

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.

Button Function

Save Saves any changes made to the fields on the screen.

Next Moves to the next dialog in a process for completing a series of steps

Back Moves to the previous dialog. You can make changes to this dialog, then click Next and the next dialog reflects your changes

Finish Indicates you have completed a series of steps in a process.

Cancel Resets the screen to appear as it was before you edited the fields. In some situations, clicking the Cancel button returns you to the selection screen.

Configuring the BMR Servers and ClientsAdding TSM Servers


51

Sort Data in Screens

Some screens, such as the list of available SRTs, have the ability to sort alphabetically and numerically . By clicking the field heading that is underlined, the contents are sorted alphabetically or numerically depending on the field’s contents. Note that the columns that can be sorted have underlined headings. Here is an example from the SRT selection screen of the field headings that can be sorted:

Controlling Access to the Administrative GUI

The 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 relationship 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. Using the appropriate pathname for the operating system running the BMR Administrative GUI, change to one of the following directories.

For AIX:

/usr/lpp/BareMetal/httpd/bin

For HP-UX and Solaris:

/opt/BareMetal/httpd/bin


./htpasswd /var/bmr/httpd/shadow/.htpasswd bmradmin

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

If you wish to specify the password on the command line, enter:

./htpasswd -b /var/bmr/httpd/shadow/.htpasswd bmradmin <password>

Adding TSM Servers

To add a new TSM server:

1. Click ESM Server on the navigation bar. The List Enterprise Storage Management Servers screen displays. The ESM servers that are already configured display on this screen:



52

2. To add a new ESM server, click Add ESM. The Add Enterprise Storage Management server screen displays.

Add an EMS server to BMR:

Field Description

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 specific ESM server.

Configuring the BMR Servers and ClientsConfiguring TSM Servers


53

1. Enter the name of the ESM (TSM) server.

2. Enter the IP address for the ESM server.

3. Enter the ESM server IP port number.

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

5. Click Save. The system creates the ESM server and stores it within BMR for future reference.

6. To cancel adding an ESM server, click Cancel. The current list of ESM servers reappears.

You have successfully added an ESM server to BMR. If you list the ESM servers again, you should now see you new ESM server.

Configuring TSM Servers1. From the BMR navigation bar, click ESM Server. The the List Enterprise Storage Management Servers

dialog displays.

2. From the List Enterprise Storage Management Servers dialog, click the name of the server you want to configure. The Configure Storage Management Server dialog displays.

3. From the Configure Storage Management Server dialog you can modify the information for the selected server:.



54

4. To add an IP address to a TSM server:

• Enter the IP address of the new server.

• Click Save. The new IP address is added.

5. To delete an IP address from the TSM server:

• Highlight the desired IP address.

• Click Delete Address. The selected IP address is deleted.

6. Click Save. Your changes are saved and the server is configured/reconfigured.

Viewing the BMR Server Configuration

The BMR server configuration is defined when bmrsetupserver is run and can be viewed using the GUI. To view this configuration click BMR Servers on the Navigation bar and then click the BMR server you want to view.

The following screen is an example of the information found on the View BMR Server Configuration screen.

Field Description

BMR Server Name The name you have given to this BMR server

Hostname The hostname of the BMR server

IP Address The network IP address of the BMR server

Netmask The network mask of the BMR server

IP Port The port the BMR server listens to

Configuring the BMR Servers and ClientsViewing the BMR Server Configuration


55

BMR Log File

The BMR log file is useful when troubleshooting. It contains useful information concerning BMR activity and events. Messages in this file are useful in identifying problems and potential problems. SKG support will often ask to review these logs with you when troubleshooting a problem.

When using the Log Files from the BMR GUI, only the most recent 50 messages are displayed. To review additional messages, the actual file can always be interrogated.

BMRDIR Directory path for BMR

DSMDIR Directory path for DSM

DSM Config The directory where BMR is installed. The executables are installed in this directory.

Data Directory The directory where BMR stores its data

State The current state of the BMR server

OS The operating system of the BMR server

Log Directory The directory where BMR events are logged

Log File Defined as “messages” if logged to a file or “syslog” if logged to syslog

Field Description



56

Here is an example of a BMR Server Log File screen:

BMR License Information

The BMR license information screen displays the following:

• the number of total licenses available

• the number of licenses currently being used by BMR clients

• a list of those clients registered with the BMR server

• the version of BMR you are using

This information is often useful to TKG Support when you call for assistance. Please have this information handy when placing a Support call.

Configuring the BMR Servers and ClientsViewing the BMR Server Configuration


57

Here is an example of the BMR Server License Information screen:



58

Creating Shared Resource Trees

Creating a Shared Resource Tree for AIX

It is not necessary to create a shared resource tree (SRT) 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 typically takes up to 30 minutes but much longer on slower systems.

Resources needed to create an AIX SRT:

• AIX OS CD-ROM or local (non-NFS) copy of same for AIX install images

• xlC.rte 3.6.4.0 or later (unless using AIX 4.3.2 images or later)

• ADSM or TSM install images

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 can not be restored with a lower level of the ADSM/TSM client software. The latest level of ADSM/TSM client software available must be installed into the SRT.

Creating an SRT when using ADSM

On the appropriate BMR file server:


/usr/lpp/BareMetal


./bmrcreatesrt

The following is an example of the kind of information the system asks for when bmrcreatesrt runs. Some details of the interaction depend on the OS level and the version of ADSM installed:

a. SRT name: 1423t_420_31adsm

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

c. SRT OS level 41, 42 or 43, 51: 42

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

Note: This step requires some time. Then, the following messages display:

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

f. Prerequisite fileset expected is xlC.rte 3.6.4.0.Press Enter to accept or enter alternate [xlC.rte 3.6.4.0]:

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

h. Prerequisite fileset expected is adsm.client.aix42.common.Hit RETURN to accept or enter alternate [adsm.client.aix42.common]:

Creating Shared Resource TreesCreating a Shared Resource Tree for Solaris


59

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

j. Prerequisite fileset expected is adsm.client.aix42.base.Hit RETURN to install required fileset [adsm.client.aix42.base]:

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

l. Additional fileset name:

Creating an SRT when using TSM



/usr/lpp/BareMetal


./bmrcreatesrt

The following is an example of the kind of information the system asks for when bmrcreatesrt runs. Some details of the interaction depend on the OS level and the version of TSM installed:

a. SRT name: aix4

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

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

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

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

f. Prerequisite fileset expected is tivoli. TSM.client.ba.aix43.32bit.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 this information is entered correctly, the SRT is created.

Creating a Shared Resource Tree for Solaris

It is not necessary to create a shared resource tree (SRT) 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 typically take about 30 minutes, but longer on slower systems.

Resources needed to create Solaris SRTs:

• Solaris OS boot CD-ROM or image such as online copies of slice 0, existing SRTs or Jumpstart servers (Note: Solaris 8 should use the Software 1 of 2 CD)

• For Solaris 2.7 SRTs, an install image for any version of patch 106327



60

• TSM install images for TIVsmCapi and TIVsmCba

• Install images for VERITAS Volume Manager and File System, if required

• Any required patches for VERITAS Volume Manager, if required

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 can not be restored with a lower level of the TSM client software. The latest level of TSM client software available must be installed into the SRT.



/opt/BareMetal


./bmrcreatesrt

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

a. SRT name []:

b. Enter desired level of Solaris/SunOS (2.6/5.6, 7/5.7, or 8/5.8) [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]:

After the Solaris boot image has been copied into the SRT, the TSM installation process starts.

3. Follow the prompts to install the TSM client.

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

Note: Documentation for TSM indicates patch 106300 should also be installed with 106327, but patch 106300 is specifically for 64 bit kernels, and standard Solaris boot images are 32 bit kernels. This produces a harmless error message announcing that patch 106300 fails to install. For that reason, patch 106300 does not have to be supplied for BMR SRTs based on current research, though the SRT creation code supports the attempt if desired.

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

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

For an SRT that supports VERITAS File System or Volume Manager on Solaris 2.6 and Solaris 7 see ‘Installing VERITAS File System / Volume Manager into a Solaris SRT’. If not, the SRT is created when this information is entered correctly.

Installing VERITAS File System / Volume Manager into a Solaris SRT

Installing additional software into a Solaris SRT requires that you identify all the additional software components that are required and install them in the appropriate order. For example, if you are trying to restore a BMR client that uses VERITAS File System and VERITAS Volume Manager, you would determine that VRTSvxfs and VRTSvxvm are needed in the SRT.

Creating Shared Resource TreesCreating a Shared Resource Tree for Solaris


61

Note: In order to restore a client using VERITAS Volume Manager, the same version of Volume Manager which was running on the restore client needs to be installed into the SRT.

Next, you must identify any prerequisites required by your needed packages. For example, the documentation for VRTSvxfs version 3.3.2 does not indicate that any particular OS patches or other prerequisites are required. Thus, installation of VRTSvxfs 3.3.2 can proceed immediately without any other prerequisite steps.

In the case of VRTSvxvm 3.0.3, the package release notes indicate that Solaris 2.6 requires patches 105223 and 105357. Solaris 7 requires patch 106541 to install VRTSvxvm. For versions of VRTSvxvm 3.0.3 through 3.1.1 the same patch dependencies exist when dealing with their respective operating system versions.

Most versions of the Solaris 7 CD include the required patch just as most versions of the Solaris 2.6 CD include the two patches required under Solaris 2.6, but the specific needs of the VRTSvxvm package you are using require that you confirm this for yourself. For a Solaris 7 SRT you need to check for the existence of patch 106541 in the SRT before installing VRTSvxvm version 3.0.3 into the SRT. The Solaris commands to do this for an SRT installed in /export/srt/one would be:

patchadd -p -R /export/srt/one/Solaris_2.7/Tools/Boot | grep 106541

A typical output showing that a version of the patch is present looks like the following:

Patch: 106541-08

Obsoletes: 106832-03, 106976-01, 107029-01, 107030-01, 107334-01, 107031-01, 107117-05 Requires: 107544-02

Incompatibles:

Packages: SUNWcar, SUNWcar.2, SUNWcar.3, SUNWcar.4, SUNWcar.5, SUN-Wcsl, SUNWcsr, SUNWcsu, SUNWcvc, SUNWesu, SUNWipc, SUNWkvm, SUN-Wkvm.2, SUNWkvm.3, SUNWkvm.4, SUNWkvm.5, SUNWsxr, SUNWtoo

From the output above you can see that patch version 106541-08 is already installed in this SRT. For patch 106541 and Solaris 7 any version of the patch (the number after the dash indicates its version) can be used before installing the VRTSvxvm package. If the patch is not listed in the output, you must install the appropriate patch before installing VRTSvxvm into the SRT.

For the example in the procedure below, the SRT being built uses a version of the Solaris 7 CD that did not include any version of 106541. The patch can be downloaded from sunsolve.sun.com.

At this point, examine the prerequisites of the version of the patch you downloaded as it may require patches in its own right. Any prerequisite patches are described by lines in the pkginfo file(s) that come with the patch. For example, patch version 106541-11 requires patches 107544 and 109104. Any prerequisite patches must be present in the SRT before installing the intended patch. You can use the patchadd command from above to test to see which patches are present in the SRT. In this case patch 107544 is already present but 109104 is not. So, you must download a version of patch 109104 (such as 109104 -01) and check its prerequisites. Because patch version 109104-01's prerequisites are all met by this example SRT you can now begin the installation of the patches to support VERITAS Volume Manager.

Note: Installing a patch into an SRT with missing prerequisites produces output documenting the specific patches required, so a more convenient way to “chain” through any patch-specific prerequisites is to try to install the VERITAS-required patch(es) into the SRT and see if anything is missing. For example, installing patch 106541-11 fails and produces an error message that indicates patch 109104 is required. Patch installation automatically checks prerequisites but package installation does not. For that reason you should always investigate what patches are required by packages using vendor documentation and examining the SRT to find out what patches are already present.



62

The following example details the steps required to install VRTSvxvm and VRTSvxfs into a Solaris 7 SRT. Remember that if patch 106541 is already present in the SRT, you do not need any patches in the SRT. Also, the patch versions shown are just an example: There may be other versions of the patches which work, and not all versions of 106541 require 109104.

Note: The first step in this procedure continues with the last step 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 [ ]:

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

d. Enter a [hostname:]/pathname containing the 106541-11 patch image [ ]:

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

f. Enter a [hostname:]/pathname containing the VRTSvxvm package image [ ]:

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

h. Enter a [hostname:]/pathname containing the VRTSvxfs package image [ ]:

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

Note: If adding only VRTSvxfs, note that some versions require VRTSlic as a prerequisite. The package VRTSvxvm provides the same functionality so, if installing both VRTSvxfs and VRTSvxvm, install VRTSvxvm first.

Creating a Shared Resource Tree for HP-UX

Creating 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 typically take about 10 minutes but can take much longer on slower systems.

Resources needed to create HP-UX SRTs:

• HP-UX OS installation CD-ROM

• Ignite 2.4 install image

• TSM install image for TIVsm in directory

Note: You must be logged in as the root user to run this procedure.

Install the TSM Client into the SRT

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

Creating Shared Resource TreesCreating a Shared Resource Tree for Windows NT


63

client software, it can not be restored with a lower level of the TSM client software. The latest level of TSM client software available

must be installed into the SRT.

In order to install any version of TSM in an HP SRT, the TIVsm package tar file must first be untarred into directory format. For example, if a CD-ROM containing the TSM tar format package is mounted on /cdrom and the current directory is where you want to untar the TIVsm package tar file, run:

tar xvf /cdrom/ TSMcli/hp11/TIVsm

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



/opt/BareMetal


./bmrcreatesrt


a. SRT Name: hpuxtsm

b. SRT location [/export/hp11]:

c. SRT OS level [11.00]:

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

If the OS level of the file server is not the same as the OS level of the SRT, the following additional prompt displays:

e. If your version of Ignite requires a patch, you will be prompted to provide the path to the specific patch version required, such as patch PHCO_22205.

f. If the OS level of the file server is not the same as the OS level of the SRT, the following additional prompt displays:

Location (device or path) of HP-UX X.Y install media [/dev/dsk/c0t2d0]: where X.Y is the SRT OS level. Otherwise, the files are copied from the file server.

g. Package name of TSM/ADSM client [TIVsm]:

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

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

Creating a Shared Resource Tree for Windows NT

Creating 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 100 MB is needed to create an SRT. Creating an SRT takes at least 10 to 20 minutes.



64


The TSM backup client directory files are copied into the SRT from the Windows NT BMR client on which bmrinitSRT is run. The TSM client software in the SRT 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 is not restorable with a lower level of the TSM client software. Because of this, bmrinitSRT must be run on a Windows NT BMR client with the latest supported level of TSM client software.

For Windows NT SRTs, Windows NT Server must be used in the SRT. At restore time, this SRT can be used to restore both Windows NT Server and Windows NT Workstation clients. Before you create an SRT on the file server the bmrinitSRT command needs to run one time on the Windows NT client machine.

On the appropriate Windows NT Server client machine:

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

The Create a New NT Shared Resource Tree (SRT) screen displays.

2. 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 containing the I386 directory.

5. Enter the name of the BMR file server.

Note: If not in the same subnet, it may be necessary to first add the name and IP address to the local %systemroot%\system32\drivers\etc\lmhosts file so that the share can be accessed. Also, the bmrsrt SAMBA share directory on the BMR file server must be writable by the SAMBA user or a write error can occur.

6. Click Create. After the SRT is created, do the following on the appropriate BMR file server:

Note: You must be logged in as the root user to run this procedure.

Creating Shared Resource TreesCreating a Shared Resource Tree for Windows 2000


65

a. Change the current directory to the location where bmrcreatesrt is located:

• on AIX BMR server, /usr/lpp/BareMetal

• on HP-UX or Solaris BMR servers, /opt/BareMetal

a. Enter the following command to complete the SRT creation:

./bmrcreatesrt -a nt


• SRT name:This should match the name created with bmrinitSRT

• SRT path:This should be the UNIX path to the SRT location; the bmrsrt SAMBA share directory with the name of the SRT appended to it. For example, if the SAMBA share directory is /export/srt and the name of the SRT is nt40, the UNIX SRT path is /export/srt/nt40

Creating a Shared Resource Tree for Windows 2000

Creating 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 360 MB is needed to create an SRT. Creating an SRT can take 15 to 30 minutes, depending on system hard ware and network conditions.


The TSM backup client directory files are copied into the SRT from the Windows 2000 BMR client on which bmrcreateSRT is run. The TSM client software in the SRT 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 is not restorable with a lower level of the TSM client software. Because of this, bmrcreateSRT must be run on a Windows 2000 BMR client with the latest supported level of TSM client software.

For Windows 2000 SRTs, Windows 2000 server must be used in the SRT. At restore time, this SRT can be used to restore both Windows 2000 server and Windows 2000 Workstation clients.

1. From the Start menu, select Programs, then select Bare Metal Restore, then select Create SRT



66

The Create a New Shared Resource Tree (SRT) displays:

2. Enter the name for the new SRT

3. From the drop down list, select the BMR file server

4. Enter the complete filepath of the install image location

5. Enter the Product Key (including hyphens)

Field Description

New SRT Name A name to refer to this SRT

BMR File Server Name of the computer that was configured as a file server for Windows clients

Location Location of the i386 directory

Windows 2000 Product Key The product key, in upper case letters.

Creating Shared Resource TreesCreating a Shared Resource Tree for Windows 2000


67

6. Click Create. The program starts creating the SRT. A status dialog displays. The status bar tracks progress. This will take a few minutes.

When the process is complete, this dialog displays:

7. Click OK. The SRT operation is complete.



68

Configuring Media BootIn order to use BMR’s media boot feature, you must create a CD-based SRT from a net-based SRT. Once the CD-based SRT is created and the resulting SRT image file has been burned as a bootable CD-ROM, see the section in Chapter 5 titled Initiating a Client Restore Using Media Boot.

Creating a CD

The image created by bmrmkcdimage for AIX and Solaris uses something commonly called “ISO” format, short for “ISO-9660”, a standard for bootable CDs that is used by AIX and Solaris, among others. For HP-UX, a binary format is used that is not precisely the same as ISO format, but which may be burnt using ISO-format options if the CD image is renamed to have “.iso” as a filename extension.

Burn the CD image onto a CD-ROM using any conventional CD recording software that supports ISO-format images for AIX or Solaris or binary images for HP-UX, using the procedure required for that particular software. This may require multiple steps as demanded by the circumstances involved.

For example, you may need to FTP the CD image from the BMR file server to another machine which has an appropriate CD-R or CD-R/CD-RW drive as well as CD burning software. Make sure the CD image file is transmitted as a binary and is transferred accurately: corrupted CD image files are a possible source of problems.

Some brands of CD burning software may require that ISO-format or binary CD image files end in “.iso” as a filename extension. Once written, BMR does not use the CD image file, so it may be renamed or moved as needed.

The details of burning ISO-9660 format CD-ROMs vary from one piece of software to another. Follow the specific procedure for the software of your choice.

Examples:

For Sony CD Extreme: (known to work with AIX and Solaris ISO-format and HP-UX binary format CD image files if renamed with .iso extension;)

1. Use the “File” menu to display the “New Job” menu and select “Global Image or Other Image ....”

2. Enter the path to the CD image file ending in “.iso”, or browse to it, changing the “Files of type” to the “Other image...” option so that .iso files will display.

3. Select other options such as burn speed as needed by circumstances. Note that some older client hardware may require a slower burn speed than the CD writer is capable of; consult the client hardware vendor documentation if needed.

4. Burn the CD.

For Adaptec Easy CD Creator: (known to work with AIX and Solaris ISO-format CD image files if renamed with .iso extension; does NOT work with HP-UX binary format even when renamed with .iso extension).

1. Use the “File” menu to select “Create CD from CD Image....”

2. In the browser dialog that pops up, change the “Files of type” to the “ISO Image Files” option and select the CD image file.

3. 3) Select other options such as burn speed as needed by circumstances. Note that some older client hardware may require a slower burn speed than the CD writer is capable of; consult the client hardware vendor documentation if needed.

Configuring Media BootCreating a CD-based SRT for AIX


69

4. Burn the CD.

For Nero: (known to work with AIX and Solaris ISO-format and HP-UX binary format CD image files if renamed with .iso extension):

1. Use the “File” menu to select “Write CD-Image”.

2. In the browser dialog, change the “File of type” option to allow ISO-format files to be selected, and select the CD image file.


4. Burn the CD.

For GearPro: (known to work with AIX and Solaris ISO-format and HP-UX binary format CD image files; renaming with .iso extension is not required)

1. Select “Open external physical image” as the type in the GEAR Project panel pull down.

2. Click Open next to the GEAR Project panel and In the browser dialog, select the CD image file desired.

3. In the External Image Parameters dialog that pops up, select MODE1 for Track type, and choose 2048 for Sector size. (HP-UX binary CD image is compatible with these ISO-format settings.)


5. Burn the CD.

Creating a CD-based SRT for AIX

You can use any CD-writer software that can burn ISO-format CD images to make a bootable CD from the CD-based SRT image file output by the following procedure:

To create a CD-based SRT for AIX:

1. Create your SRT as you would normally using the procedure in the section titled “Creating Shared Resource Trees for AIX”.

2. On the file server (FS) enter the following command:

./bmrmkcdimage

Example prompts that appear after entering the bmrmkcdimage command.

• Enter the name of the SRT to use as the source: aix433esm

• Enter the name to use for the new SRT: aix433esmcd

• Enter the name to use for the new BI: aix433esmcdbi

• Enter a directory with 1400MB or more free space: /export/srt/mb (see Note)

Note: The directory used should not be a direct prefix of the directory containing the net-based SRT selected in step 1. For example, if the SRT aix433esm resides in /export/srt/aix433esm, then do not specify here



70

/, /export, /export/srt, or /export/srt/aix433esm. Specifying /export/srt/mb would work because it is not a direct prefix of the SRT path.

3. Enter the CD-ROM device name [/dev/cd0]:

4. Insert the AIX 4.3.3.0 CD into the CD-ROM drive. (CD version is dependent on SRT OS level.)

5. Press Enter when ready (or ctrl-c to quit)...

A series of informative messages displays as the command progresses. When the command finishes, it displays the final CD image file name.

6. Burn the CD image onto a CD-ROM using conventional CD recording software. If there is no CD-R drive on the computer where the SRT was created, you should FTP the image to a box where there is a CD-R drive and burn the software on that box.

When the CD is created, label the CD for easy identification. For example the following information could appear on the face of the CD. This allows the CD to be distinguished from other CD-based SRTs you create.

• SRT name: aix433esmcd

• BI name: aix433esmbicd

• BMR server: aixp9

Creating a CD-based SRT for Solaris

You can use any CD-writer software that can burn ISO-format CD images to make a bootable CD from the CD-based SRT image file output by the following procedure:

This process is valid for the following three scenarios:

A. VRTSvxvm is NOT installed into the SRT.

B. VRTSvxvm is installed into the SRT, but NOT on the file server.

C. VRTSvxvm is installed into the SRT, and also on the file server.

To create a CD-based SRT for Solaris:

1. Create your SRT as you would normally using the procedure in the section titled Creating a Shared Resource Tree for Solaris.

2. Check to see if vold is running on the file server.

ps -ef | grep vold

a. If it is running, eject any CD that might be loaded.

eject

b. Stop the vold process.

/etc/init.d/volmgt stop

c. Check to see if the vold process was stopped.

ps -ef | grep vold

3. On the file server enter the following command:

./bmrmkcdimage

Configuring Media BootCreating a CD-based SRT for Solaris


71

Note: Depending upon the case (A, B, or C) the command ./bmrmkcdimage results in a different series of prompts

3.a Following is the scenario for case A.

a. Enter the name of the SRT to use as the source: sol

b. Enter the name to use for the new SRT: solcd

c. Enter the name to use for the new BI: solcdbi

d. Enter a directory with 1400MB or more free space: /export/mb

e. Enter the CDROM device name [/dev/dsk/c0t2d0s2]:

f. Insert Solaris 2.6 CD into the CDROM drive.

g. Press ENTER when ready (or CTRL-C to quit)...


3.b Following is the scenario for case B.








h. Enter the name of a partition of size 103040 or more blocks: /dev/dsk/c0t0d0s5

i. All data on /dev/dsk/c0t0d0s5 will be lost. Do you want to continue? y


3.c Following is the scenario for case C.








h. Enter the name of a Disk Group with 51MB or more free space: rootdgYou do not need to do anything. During this process, the following dialog displays on your screen:



72


4. Burn the CD image onto a CD-ROM using conventional CD recording software. If there is no CD-R drive on the computer where the SRT was created, you should FTP the image to a box where there is a CD-R drive and burn the software on that box.

5. When the CD is created, label the CD for easy identification. For example the following information could appear on the face of the CD:

• SRT name: sol7esm

• BI name: sol7esmbicd

• BMR server: sol7tkg

Creating a CD-based SRT for HP-UX

You can use any CD-writer software that can burn binary CD images (also known as external or foreign images) to make a bootable CD from the CD-based SRT image file output by the following procedure:

To create a CD based SRT for HP-UX:

1. Create your SRT as you would normally using the procedure in the section titled Creating an SRT for HP-UX.

2. On the file server (FS) enter the following command:

./bmrmkcdimage

The following are example prompts that appear after entering the bmrmkcdimage command.

a. Enter the name of the SRT to use as the source: hp11srt

b. Enter the name to use for the new SRT: hp11esmcd

c. Enter the name to use for the new BI: hp11esmcd_bi

d. Enter the name of a Volume Group with 96MB or more free space: vg00

e. Enter a directory with 144MB or more free space: /export/srt

3. Burn the CD image onto a CD-ROM using convential CD recording software. If there is no CD-R drive on the computer where the SRT was created, you can FTP the image to a box where there is a CD-R drive and burn the software on that box.

4. Label the CD for easy identification. For example, the following information could appear on the face of the CD. This allows the CD to be distinguished from other CD-based SRTs.

• SRT name: hp11esmcd

• BI name: hp11esmbicd

• BMR server: hpp9

Creating a CD-based SRT for Windows NT

After you create a Windows NT SRT as described in Creating Shared Resource Trees section of Chapter 3, carry out the following steps to prepare the SRT for media boot:

Configuring Media BootCreating a CD-based SRT for Windows NT


73

1. From the Start menu, select Programs, then select Bare Metal Restore, then select bmrfloppy.

The Boot Options dialog displays:

This screen allows you to choose one of two options:

• Create a boot floppy disk. More information on creating boot floppies can be found in Chapter 3, Creating a Boot Floppy section.

• Prepare an SRT for Media Boot. This option prepares the SRT to be ready for Media Boot use. Such an SRT can be copied to a CD for use with Media Boot.

2. Select Prepare an SRT for Media Boot.



74

3. Click Next. The Media Boot Options dialog displays:

This screen allows you to choose the following:

• The name of an SRT to be prepared for Media Boot. Select an SRT from the pull down list.

• A list of clients to be included in the SRT. Only the clients that are included in the SRT will be able to use the Media Boot CD.

4. Do one of the following

a. Choose to include all clients defined on the BMR server.

b. Specify the name of a file that contains the list of clients to be included. Use Browse to select the name(s) of the file(s) to be included.

Configuring Media BootCreating a CD-based SRT for Windows 2000


75

5. Click Finish. The Preparing SRT for Media Boot status box displays:

Progress details are reported in the Details box. When the SRT preparation phase has completed, the following confirmation displays:

The SRT is now ready to be burned onto a CD-ROM for use with Media Boot.

6. Click OK.

7. Using your favorite CD creation software, burn the contents of the SRT directory onto the CD. That is, after the CD creation process, the contents of the SRT directory should appear as the contents of the root directory on the CD. The SRT directory itself does not appear on the CD.

Note: The machine that has the CD creation software must have access to the SRT directory on the file server.

Creating a CD-based SRT for Windows 2000

After you create a Windows 2000 SRT as described in Creating Shared Resource Trees section of Chapter 3, carry out the following steps to prepare the SRT for media boot.



76

1. From the Start menu, select Programs, then select Bare Metal Restore, then select Boot Options.



77

The Boot Options dialog displays:

This screen allows you to choose one of two options:

• Create a Boot Floppy disk. More information on creating boot floppies can be found in Chapter 3, Creating a Boot Floppy section.

• Prepare an SRT for Media Boot. This option prepares the SRT to be ready for Media Boot use. Such an SRT can be copied to a CD for use with Media Boot.

2. Select Prepare an SRT for Media Boot.



78

3. Click Next. The Media Boot Options dialog displays:

This screen allows you to choose the following:

• The name of an SRT to be prepared for Media Boot. Select an SRT from the pull down list.

• A list of clients to be included in the SRT. Only the clients that are included in the SRT will be able to use the Media Boot CD.

4. Select an SRT from the pull down list.

5. Do one of the following

a. Choose to include all clients defined on the BMR server.

b. Specify the name of a file that contains the list of clients to be included. Use Browse to select the name(s) of the file(s) to be included.



79

6. Once you are satisfied with your selections, click Finish. The Preparing SRT for Media Boot status box displays:

Progress details are reported in the Details box. When the SRT preparation phase has completed, the following confirmation box displays:.

7. Click OK. The SRT is now ready to be burned onto a CD-ROM for use with Media Boot.

8. Using your favorite CD creation software, burn the contents of the SRT directory onto the CD. That is, after the CD creation process, the contents of the SRT directory should appear as the contents of the root directory on the CD. The SRT directory itself does not appear on the CD.

Note: The machine that has the CD creation software must have access to the SRT directory on the file server.



80

Configuring Shared Resource TreesThe 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 Tree

It may become necessary to modify an existing shared resource tree (SRT). Modify an SRT by completing the following instructions:

1. Click on Shared Resource Trees in the Navigation bar. A list of SRTs displays.

2. From the SRT list, click on the SRT you want to modify. The current configuration for the selected SRT displays on the screen.This figure is an example of an AIX SRT.

Configuring Shared Resource TreesCreating a CD-based SRT for Windows 2000


81

Field Description

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

Architecture The hardware architecture for this SRT.

OS The operating system of this SRT.

OS Level The operating system version of this SRT.

Path The path to this SRT. The variables for this field are as follows:

ready - ready to be used by a client to restore

downlevel - this is an SRT created by a previous version of BMR and is obsolete.

allocated - SRT is allocated to a client for a restore. i.e. a client is actively using this SRT.

defined - The SRT is defined in the database but has not been created yet.

State The current state of this SRT.

Version The version of this SRT.

Checksum The checksum of the SRT used for verification.

Type The type of SRT. The variables for this field are as follows:



82

3. Modify the desired fields.

4. Click Save Changes. The changes to the selected SRT are saved.

Deleting a Shared Resource Tree

1. Click on Shared Resource Trees in the Navigation bar. A list of SRTs displays.

2. From the SRT list, click on the SRT you want to delete. The current configuration for the selected SRT displays on the screen.

3. Click DELETE. A confirmation screen displays.

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

Adding Network Interface Card Driver Support

Introduction

If your BMR Windows NT client requires additional driver support for the restore to succeed, use the Add Driver command to add these drivers to a Windows NT SRT:

NIC 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.

nfs - net-baed

cdfs - CD-based

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.

Field Description

Configuring Shared Resource TreesCreating a CD-based SRT for Windows 2000


83

Add a network interface card driver to the BMR Server:

1. Click Start - Programs - Bare Metal Restore - bmradddriver. The BMR Add Drivers to an SRT wizard opens.

2. 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 NIC card as there can be numerous drivers installed into any one SRT.

3. In Location of Driver Files field, enter the path or use Browse to locate the directory where oemsetup.inf or oemsetnt.inf reside.

4. Click Add. The Select OEM Option screen displays:.

5. Since the oemsetup file can contain more than one driver, select the correct driver for your card.

6. Click OK. The NIC is added to the BMR server.

Creating a Boot ImageCreating a CD-based SRT for Windows 2000


84

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 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 Shared Resource Trees in the navigation bar. The List of Shared Resource Trees displays.

2. Click the name of the SRT from which you wish to create a boot image. The Configure Shared Resource Tree screen displays:

Creating a Boot ImageCreating a CD-based SRT for Windows 2000


85

3. To create a boot image of this SRT, you do not need to enter any additional information. Confirm the information for this SRT and click Create Boot Image. The Create AIX Boot Image screen displays:

4. Complete the vacant fields on this screen as follows:

Field Description

BI Name The name of the selected boot image.

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

SRT OS The operating system of this SRT.

SRT OS Level The operating system version of this SRT.

SRT Type The type of SRT (nfs for net-based, or cdfs for CD-based)

SRT Path The path to the selected SRT.

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.

Creating a Boot ImageConfiguring a Boot Image


86

a. Enter the name for the boot image.

b. Enter the name of the boot server.

c. Enter the boot server port.

d. Enter the path to the boot image.

e. Select the correct architecture.

f. Select the correct processor type.

g. Select the type of network interface card.

5. Click Create. The boot image is created and the complete list of boot images is listed.

Configuring a Boot Image

The Boot Image Configuration screen allows you to view important information related to the selected boot image. Also, this is where you configure the boot server hostname, the boot server IP address, and the boot server IP netmask.

1. From the BMR navigation screen, click Boot Images. The List Boot Images screen displays:



87

2. Click the name of the image you want to configure from the BI Name column. The Configure Boot Image dialog displays:

Field Description

BI Name The name of the selected boot image.

BI Type net=network boot imagecd=media boot CD

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

OS The operating system of this SRT.

OS Level The operating system version of this SRT.

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

Network Card ent=ethernettok=token ring

Architecture The architecture this boot image supports. chrp/rsgh/rspc



88

Modifying a Boot Image

To modify 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 displays.

3. Modify the desired fields.

4. Click Save.

The changes to the selected boot image are saved.

Deleting a Boot Image

To deleted a boot image:

1. On the BMR navigation bar click Boot Images.

2. Select the boot image you wish to delete. The Boot Image Configuration screen displays.

3. Click Delete. A confirmation screen displays.

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

State The current state of the boot image.

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

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

Boot Server IP Address IP address of the boot server.

Boot Server IP Netmask Netmask of the boot server.

Boot Server Port The port number of the boot server.

Field Description

Configuring a BMR Client using GUIConfiguring a Boot Image


89

Configuring a BMR Client using GUIBMR clients define themselves to the BMR server when they run the bmrsetupclient command for the first time. After that point, their configuration is uploaded every time bmrsavecfg runs, which is usually every day, 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 Ethernet Address fields can 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.



90

The Client Configuration screen displays.



91

3. Enter or modify data as appropriate.

4. Click Save to save the changes. The following message displays when the update is complete, “Update completed successfully.”

Field Description

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 Ether 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.

Client BMR Port The port used to communicate to the server.

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

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

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

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

ESM Server Gateway The IP address of the gateway the client uses at restore time to reach the TSM 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.



92

Creating a Boot Floppy

Create a Boot Floppy for Windows NT

A BMR floppy boot disk begins the restore process.

Requirement:

• A floppy disk - formatted or unformatted

To create a Windows NT floppy Boot Disk:

1. Click Start - Programs - Bare Metal Restore - bootoptions. The BMR Boot Floppy Wizard opens.

2. Select Create a Boot Floppy.

Creating a Boot FloppyCreate a Boot Floppy for Windows NT


93

3. Click Next. The Boot Floppy Option dialog displays:

This screen allows you to choose from three types of BMR floppy boot disks. Before starting any of these procedures you need a floppy disk; it does not need to be formatted.

• Create a generic network boot floppy disk. The floppy is configured to work on any system with the brand and type of network card found in the client machine.

• Create a customized network boot floppy that requires no intervention once the restore begins. Note: this option configures this boot disk specifically for the client machine so it cannot work on any other system.

• Create a boot floppy customized for Media Boot.

4. Select the type of boot floppy you wish to create.

Note: If the client is unable to connect to the BMR server, only the creation of a generic boot floppy is allowed.

The three types are discussed in the following order: Generic; Custom w/Network SRT; Custom w/CD SRT.

5. Click Next.

Generic Network Boot Floppy Disk Creation

From the Boot Floppy Options screen:

1. Click the Generic radio button.

2. Click Next. The NIC Driver Information screen displays.



94

3. Enter the path to the DOS NDIS2.0 driver for your network card. These drivers can be found on the network card vendor CD, floppy, or on the vendor’s website.



95

4. Click Next. The Optional SCSI Driver Information dialog displays:

This screen allows you to specify the DOS driver for any SCSI adapter that you have in your system. This driver will be loaded at restore time (with the optional initialization string) to make the SCSI adapter usable during restore phase. These drivers are commonly available from the install media or from the manufacturer’s web site.

You do not have to enter anything here if either of the following apply:

• You don’t have a SCSI adapter

• You do not need the SCSI adapter to be available to restore the system

5. If you do want to specify the DOS driver, do the following:

a. Enter an appropriate path in the Driver name field.

b. Enter an appropriate value in the Optional initialization string field.

Field Description

Driver name: Path to the DOS SCSI driver

Optional initialization string Some manufacturers require an additional string.



96

6. Click Next. The Insert a Floppy screen displays:

7. Insert a floppy disk into the disk drive. The floppy can be formatted or unformatted. The Finish button becomes active.

8. After verifying that the information is correct, click Finish. The following warning is displayed and must be heeded:

Warning: 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 out 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.

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

Create a Custom Network Boot Floppy

To create a customized BMR boot floppy:

1. Starting at the Boot Floppy Options screen select the Customized w/ Network SRT radio button.



97

2. Click Next. The NIC Driver Information screen displays

3. Enter the path to the DOS NDIS2.0 driver for your network card. These drivers can be found on the network card vendor CD, floppy, or on the vendor’s website.



98









Field Description





99

6. Click Next. The Client IP Information screen displays:

7. Select the appropriate client for this boot disk from the pull-down menu.

The appropriate IP address and Subnet Mask are entered automatically depending on the client selected. These IP properties are gathered from the last time the bmrsavcfg was run. The Slot Number refers to the PCI slot where the NIC card resides. If any of the information has changed, you can modify those fields. For example, if you moved the PCI card, you can change the slot number information on this screen.



100

8. Click Next. The Extra Safety Prompt screen displays:

Warning: The BMR boot floppy destroys all existing partitions on the machine being restored. The optional Safety Prompt can prevent unintended completion of the boot floppy process.

9. To prevent 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:

• Add a Safety Prompt

• Do NOT add a Safety Prompt

The safety prompt pauses the restore process before the irreversible portion of the restore process begins.

Example: a safety prompt can help guard against accidently booting from the disk when the disk is in the drive.



101

10. Click Next. The Save Partition screen displays:

11. If your machine has a partition on it that is unreadable to Windows NT, click Yes on this screen. Otherwise, click No.

To determine if your vendor (special) partition can be saved during the restore process, use the following guidelines:




• 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 exact position and length can change.



102


13. Choose an SRT for the client from the drop-down menu.



Warning: 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 out 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.

Create a Custom CD-Based Boot Floppy

To create a CD-Based customized boot floppy:

1. Starting at the Boot Floppy Options screen select the Customized w/ CD-SRT radio button.



103

2. Click Next. The following dialog displays:


• Enter the path name to the drivers for your CD-ROM drive.

• If you do not know or do not have the drivers for the CD-ROM, click Use Default. The default uses a generic CD-ROM driver that is compatible with your IDE CD-ROM drive. A default SCSI CD-ROM drive driver is available at www.connectcom.net.



104


If this machine requires a DOS SCSI driver, enter the path to that driver here.










105

6. Click Next. The Client IP Information dialog displays:

7. Select the appropriate client for this boot disk by selecting it from the pull down menu.

8. Click Next. the Extra Safety Prompt screen displays:



106


9. To prevent 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:



The safety prompt pauses the restore process before the irreversible portion of the restore process begins. A safety prompt can help guard against accidently booting from the disk when the disk is in the drive.

10. Click Next. The Save Partition screen displays:

11. If your machine has a partition on it that is unreadable to Windows NT, click Yes on this screen. Otherwise click No.

To determine if your special partition can be saved during the restore process, use the following guidelines:





Creating a Boot FloppyCreate a Boot Floppy for Windows 2000


107




Warning: 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.

Create a Boot Floppy for Windows 2000

A Windows 2000 BMR Client can be restored using three types of boot floppies:

• Generic boot floppy, used with network based SRTs

• Customized boot floppy, used with network based SRTs

• Customized boot floppy, used with CD-based SRTs

This section explains how to create each of these floppies.



108

Create a Generic Network Boot Floppy for Windows 2000




109

2. The Boot Options dialog displays:

This screen allows you to choose from one of two options:

• Create a boot floppy disk

• Prepare an SRT for Media Boot. This option prepares an SRT ready for Media Boot use. More information on preparing an SRT for Media Boot can be found in this chapter, in the section ‘Creating a CD-based SRT for Windows 2000’




110


From this screen, you have three options:


• Create a customized network boot floppy that requires no intervention once the restore begins. Note: this option cinfigures this boot disk specifically for the client machine so it cannot work on any other system.


5. Select Generic.



111

6. Click Next. The Specify Network Interface Card (NIC) Driver dialog displays:

Enter the full path for the NDIS2 driver for the NIC card on the machine OR use Browse to locate the file. These drivers are commonly available from the NIC install media or from the manufacturer’s web site.



112









Field Description





113

9. Click Next. The Insert a Floppy dialog displays:

This screen displays a summary of all the information that has been gathered/entered.

10. Verify the information.

If you need to change information in a field, click Back to reach the appropriate screen, correct the information, and continue forward with the process again.

11. Click Finish. the following prompt displays:



114

12. Insert a 1.44MB floppy into Drive A. The floppy can be formatted or unformatted.

Warning: All data on the floppy will be erased!

13. Click OK. The Creating Boot Floppy... progress dialog displays:

This dialog shows the progress of the floppy creation process. The activity currently in progress is displayed in the Details area, with a blue progress bar indicating the overall progress.

The following confirmation dialog displays after the boot floppy is successfully created:

14. Click OK. The generic boot floppy is now ready for use.

15. Remove the floppy from the drive and label it.

Refer to ‘Restoring a Windows 2000 Client’ in chapter 5 for details on how to use generic boot floppies to restore a Windows 2000 client.



115

Create a Custom Network Boot Floppy for Windows 2000

At the time of restore, you need a boot floppy to start the process.




116



• Create a boot floppy disk

• Prepare an SRT for Media Boot. This option prepares an SRT ready for Media Boot use. More information on preparing an SRT for Media Boot can be found in this chapter, in the section ‘Creating a CD-based SRT for Windows 2000’




117






5. Select Customized.



118

6. Select Next. The Specify Network Interface Card (NIC) Driver dialog displays:

7. Enter the full path for the NDIS2 driver for the NIC card on the machine OR use Browse to locate the file.

These drivers are commonly available from the NIC install media or from the manufacturer’s web site.



119

8. Click Next. The Optional SCSI Driver Information box displays:








Field Description





120

10. Click Next. The SRT and File Servers IP Information dialog displays:

11. Select an SRT from the drop-down menu.

File server details are automatically displayed. You can change the addresses used to access the file server at this time.

Field Description

SRT Name Name of the SRT that was created using the procedure described in Chapter 3, ‘Creating a Shared Resource Tree for Windows 2000’.

IP Address IP address of the file server

Hostname Name of the file server. This name must be resolvable to the IP address specified above.



121


13. Select the name of the client from the BMR Client Name drop-down menu.

14. Select the name of the network interface from the drop-down menu.

15. Other information may be displayed automatically. If not, enter the correct values.

Field Description

BMR Client Name Name of the client computer

NIC Description The NIC card found on the system

DHCP Enabled Check this box if you want DHCP to be used at boot time. If this box is checked, the remaining four fields are masked out.

IP Address IP address of the interface

Netmask Netmask of the interface

Default Gateway Default gateway for this client

Slot Number Slot number of the NIC card



122

16. Click Next. The extra Safety Prompt dialog displays:


To prevent accidents when using a customized boot floppy, a safety prompt can be added to the disk. Opting for a safety prompt pauses the restore process before the irreversible portion of the restore process begins. A safety prompt can half guard against accidentally booting from the floppy disk when the floppy disk is in the drive.

17. Select one of the following:



Field Description

Add a Safety Prompt Selecting the option to make the restore process ask for a confirmation before repartitioning the drive.

Do NOT add a Safety Prompt Select this option to skip the above confirmation.



123

18. Click Next. The Create special system Partition dialog displays:

19. If your machine has a partition on it that is unreadable by Windows 2000, click YES on this screen. Otherwise, click No.

Note: A system partition is a special area of the fixed disk containing configuration, diagnostic, and maintenance utilities. These utilities are more readily available and run faster when installed on the system partition.

To determine if your special partition can be saved during the restore process, use the following four guidelines:



Field Description

YES, (save a partition) The restore process asks for the partition to be saved out of the partitions found on the disk.

NO (do not save a partition) The restore process skips saving a partition



124

• 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 Windows NT, primary partitions should be backed up into the storage manager and restored without a custom setup.



This screen displays a summary of all the information that has been gathered/entered. Clicking Finish will create the floppy.





125

22. Click Finish. The following prompt displays:


Warning: All data on the floppy will be erased.





126


25. Click OK. The customized network boot floppy is now ready for use.


Refer to Restoring a Windows 2000 Client in chapter 4 for details on how to use customized network boot floppies to restore a Windows 2000 client.

Create a Custom Media Boot Floppy for Windows 2000




127



• Create a boot floppy disk.

• Prepare an SRT for Media Boot. This option prepares an SRT ready for Media Boot use.




128

4. Click Next. The Foot Floppy Option dialog displays:





5. Select Customized for Media Boot.



129

6. Click Next. The CD-ROM Driver Information dialog displays

This screen lets you choose the device driver for the CD-ROM device that you are using. You can either enter the full path name of the device driver file, or use the Browse button to browse and select the driver file. Clicking on the Use Default will result in using the default driver (oakcdrom.sys), which should work with most ATAPI CD-ROM devices. Drivers are commonly available from the install media or from the manufacturer’s web site.

7. Choose the appropriate CD-ROM driver by doing one of the following:

• Enter the full path name of the device driver file.

• Select Browse to browse and select the driver file.

• Click Use Default.



130

8. Click Next. The Optional SCSI Driver Information box displays:










131


11. Select the name of the client from the BMR Client Name drop-down menu.

12. Select the name of the network interface from the drop-down menu.

13. Other information may be displayed automatically. If not, enter the correct values.

Field Description

BMR Client Name Name of the client computer

NIC Description The NIC card found on the system

DHCP Enabled Check this box if you want DHCP to be used at boot time. If this box is checked, the remaining four fields are masked out.

IP Address IP address of the interface

Netmask Netmask of the interface

Default Gateway Default gateway for this client

Device Number Slot number of the NIC card



132

14. Click Next. The extra Safety Prompt dialog displays:


To prevent accidents when using a customized boot floppy, a safety prompt can be added to the disk. Opting for a safety prompt pauses the restore process before the irreversible portion of the restore process begins. A safety prompt can half guard against accidentally booting from the floppy disk when the floppy disk is in the drive.

15. Select the desired option.

Field Description

Add a Safety Prompt Selecting the option to make the restore process ask for a confirmation before repartitioning the drive.

Do NOT add a Safety Prompt Select this option to skip the above confirmation.



133

16. Click Next. The Create special system Partition dialog displays:

17. If your machine has a partition on it that is unreadable to Windows 2000, click YES on this screen. Otherwise, click No.

To determine if your special partition can be saved during the restore process, use the following four guidelines:



• 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 Windows NT, primary partitions should be backed up into the storage manager and restored without a custom setup.

Field Description

YES, (save a partition) The restore process asks for the partition to be saved out of the partitions found on the disk.

NO (do not save a partition) The restore process skips saving a partition



134



This screen displays a summary of all the information that has been gathered/entered.





135

20. Click Finish. The following prompt displays:


Warning: All data on the floppy will be erased!





136


23. Click OK. The customized Media Boot floppy is now ready for use.


Refer to Restoring a Windows 2000 Client in chapter 4 for details on how to use customized Media Boot floppies to restore a Windows 2000 client.


4 Restore a BMR ClientAfter completing the installation and configuration of Bare Metal Restore, you are prepared to completely restore your BMR client machines from their TSM backups in the event of a system failure. BMR requires one full normal TSM client backup after BMR is installed. Whenever the BMR client changes configuration, bmrsavecfg should be rerun and the client backed up again. We recommend that you configure bmrsavecfg to run automatically as part of the backup procedure. (Use the preschedulecmd option in dsm.sys.)

All BMR restore operations can be performed using the Bare Metal Restore graphical user interface.

These topics are covered in this chapter:“Preparing for Client Restoration” on page 138“Initiating Client Restoration” on page 153

Important!

You must successfully save the configuration (bmrsaveconfg) and then completely backup a client

before BMR can restore that client.

Bare Metal Restore User GuideRestore a BMR Client


138

Preparing for Client RestorationNormally, this step immediately proceeds the restore. The benefit in waiting until immediately prior to restore it that you then restore even the most recent data.

This step is completed on two screens, the Configure Client screen, where you verify and/or change appropriate fields and the Prepare to Restore screen, where you enter your passwords and identify the appropriate server.

Preparing an AIX Client for Restoration1. From the BMR navigation bar, click Clients. The clients list displays on the screen.

Preparing for Client RestorationPreparing an AIX Client for Restoration


139

2. Click on the client you wish to restore. The Client Configuration screen displays on the screen:



140

T

Field DefinitionClient Name BMR 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.Service Pack Required The client’s previously installed MS Service Packs can be restored, but must be identifiedClient Boot IP Address The IP address of the client used at restore time.Client Boot Netmask The netmask used by the client used at restore time.Client Boot Ether Address The Ether address of the client at restore time.Client Processors The number of processors this client supportsClient Boot Interface The Client’s console deviceClient Boot Console The Client’s LANG (NLS) variableClient Boot Language The Network Interface Card used by this client during bootClient State The Client’s setup state (installed, allocated, ready)Client BMR Port The Client’s port number used to contact the BMR master 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.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 default gateway the client uses at restore time to contact the BMR server.

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.

Preparing for Client RestorationPreparing an AIX Client for Restoration


141

4. Click Prepare to Restore. This is an example of the The Prepare to Restore screen that displays.



142

Field DefinitionClient Name The name of the client to restore.Allocated BI Name The name of the boot image used by the client at restore time. ESM Server Name The TSM server to which the client’s files are backed up.ESM Client Name The name by which the TSM server knows the client. Client Processors The number of processors this client supports (mp=multiprocessor, up=uniprocessor)Client Boot Interface The client’s console deviceClient Boot Console The client’s LANG (NLS) variableClient Boot Language The Network Interface Card used by this client during bootESM Client Password The password for the TSM Client.ESM Admin Password The password for the TSM administrator.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.Dissimilar Enables the dissimilar restore functionality. BMR Server IP Address The IP address the client uses to reach the BMR server. BMR Server Netmask The IP netmask the client uses to reach the BMR server. Boot Server IP Address The IP address the client uses to reach the boot server. Boot Server Netmask The IP netmask the client uses to reach the boot server. File Server IP Address The IP address the client uses to reach the file server. File Server Netmask The IP netmask the client uses to reach the file server.

5. Enter the TSM client password. Do one of the following:

• If the password is known, type it in the TSM Client Password text box.

• If the password is unknown, click Set Password and enter the TSM admin password.

Warning: If using the Set option, the TSM client password entered in this screen becomes the client's new password, replacing any previous TSM password on the TSM server. You may want to use TSM administrative procedures to restore the desired password after restoration: the password used here only needs to be valid during the restoration.

6. For UNIX systems, select the desired restore option from the selection menu from the following:

• All disks/volumes. This option recovers all disks.

• Only system disks/volumes. This option restores only those disks necessary to recover a bootable OS.

Warning: Before clicking OK to complete this procedure, ensure NFS is up and running between the BMR server and the File server.

7. Select whether or not to enable logging for the restore. Logging provides details about the recovery process that may be useful to you or TKG Customer Support in the event of a problem. It is recommended that logging always be enabled if you have adequate space.

Note: If using dissimilar restore, this controls logging during the hardware discovery boot phase of restoration.

8. Select whether or not to enable Dissimilar Restore.

Note: Enabling restoring to dissimilar disks also provides a more granular way to select which disks, volumes, or filesystems are restored.

9. Verify the information on this screen.

10. Click OK.

Preparing for Client RestorationPreparing a Solaris Client for Restoration


143

Note: If you wish to cancel the restoration after generating the restore files, run the following command from the system command line interpreter while logged in as root on the BMR server:

bmrcleanup <clientname>

11. After the command finishes, the following screen is displayed.

12. Click OK. You are finished with Prepare to Restore and ready to proceed to final restore.

Preparing a Solaris Client for Restoration1. From the BMR navigation bar, click Clients. The clients list displays on the screen.

2. Click on the client you wish to restore. The Client Configuration screen displays on the screen:T


4. Click Prepare to Restore.




Note: If using Set option, the TSM client password entered in this screen becomes the client's new password, replacing any previous TSM password on the TSM server. You may want to use TSM administrative procedures to restore the desired password after restoration: the password used here only needs to be valid during the restoration.

6. For UNIX systems, select the desired restore option from the selection menu: “Only system disks/volumes” try to restore only those disks necessary to recover a bootable OS, while the other option recover all disks. Select the desired restore option from the selection menu.

Warning: Before clicking OK to complete this procedure, ensure that NFS is up and running between the BMR server and the File server.

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






144

9. Click OK.

Note: If you wish to cancel the restoration after generating the restore files, run the following command while logged in as root on the BMR server:



11. Click OK. You are finished with Prepare to Restore.

Preparing an HP-UX Client for Restoration1. From the BMR navigation bar, click Clients. The clients list displays on the screen.

2. Click the client you wish to restore. The Client Configuration screen displays on the screen:T












8. Click OK.




10. Click OK. You are finished with Prepare to Restore and are ready to restore your client.

Preparing for Client RestorationPreparing a Windows NT Client for Restoration


145

Preparing a Windows NT Client for Restoration1. From the BMR navigation bar, click Clients. The clients list displays on the screen.



146

2. Click on the Windows NT client you wish to restore. The Configure Client screen displays on the screen:

T

Preparing for Client RestorationPreparing a Windows NT Client for Restoration


147

Field DefinitionClient Name The client host name, followed by the TSM server nameAllocated 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.Service Pack Required The client’s previously installed MS Service Packs can be restored, but must be identifiedClient Boot IP Address The IP address of the client used at restore time.Client Boot Netmask The netmask used by the client used at restore time.Client Boot Ether Address The Ether address of the client at restore time.Client Processors The number of processors this client supportsClient Boot Interface The Client’s console deviceClient Boot Console The Client’s LANG (NLS) variableClient Boot Language The Network Interface Card used by this client during bootClient State The Client’s setup state (installed, allocated, ready)Client BMR Port The Client’s port number used to contact the BMR master ESM Server Name The TSM server to which the client’s files are backed up.ESM Client Name The name by which the TSM server knows the client node.ESM Server IP Address The IP address of the TSM 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. 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.

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. It is necessary to define this field if the BMR server is not in the same subnet as the client.











8. Click OK.



148




10. Click OK. You are finished with Prepare to Restore.

Preparing a Windows 2000 Client for Restoration

This example demonstrates how to prepare a Windows 2000 client for restoration:

1. From the BMR navigation bar, click Clients. The clients list displays on the screen.

Preparing for Client RestorationPreparing a Windows 2000 Client for Restoration


149

2. Click the Windows 2000 client you wish to restore. The Configure 2000 Client screen displays on the screen:

FIELD DESCRIPTIONClient Name BMR name of selected clientClient Host Name Hostname of the clientAllocated SRT Name Name of the SRT used at restore timeConfig Network Interface List of IP addresses of interfaces on the client systemClient Architecture Hardware architecture of the clientClient OS Operating system of the BMR clientClient Boot Language Client’s languageClient State State of the client (installed, allocated, ready)Client BMR Port Port on which the BMR server is listeningClient Processors Number of processors on the client system



150

ESM Server Name The ESM server to which the client’s files are backed upESM Client Name The name by which the ESM server knows the clientESM Server IP Address The IP address of the ESM serverESM Server Alternate IP The IP address the client uses at restore time to reach the ESM serverESM server Gateway The IP address of the gateway the client uses at restore time tor each the ESM server BMR Server Hostname The hostname of the BMR serverBMR Server IP Address The IP address of the BMR serverBMR Server Netmask The netmask of the BMR serverBMR Server Port The TCP port number used by the BMR server processBMR Server Gateway The IP address of the default gateway the client uses at restore time to contact the BMR server


2. From the Allocated SRT Name drop-down menu, select an SRT to be used during restore.

3. From the Config Network Interface drop-down menu, select the IP address of the interface to be used at restore time.

4. If you want to modify the characteristics of the network interface, click View Interface. The Client Network Interface dialog displays:

FIELD DESCRIPTIONClient Name BMR name of the selected clientClient Host Name Hostname of the clientDescription Description of the selected adaptorIP Address IP address of the selected adapter used at restore timeNetmask Netmask used by the client at restore timeGateway IP address of the default gateway that the client uses at restore timeService A tag field, used to denote the selected adaptor

5. Verify and/or correct the network interface information.

6. Click Save. The Configure 2000 Client screen reappears.

Preparing for Client RestorationPreparing a Windows 2000 Client for Restoration


151

7. On the Configure 2000 Client screen, click Prepare to Restore. The Prepare to Restore 2000 Client screen displays:

Click Prepare to Restore. The Prepare to Restore 2000 Client screen displaysFIELD DESCRIPTIONClient Name Name of the selected clientAllocated SRT name Name of the SRT used at restore timeESM Server Name Name of the ESM server to which the client’s files are backed upESM Client name The name by which the ESM server knows the client node Restore From ESM_server or Local_CD_backupsetBackup Set File Name Your name for the backup set file. TSM adds the volume number.ESM Client Password Password used to connect to ESM serverSet Password To change the ESM client password, check this box and enter your ESM admin password.ESM Admin Password Independent of BRM. Set at time you set up ESM server.



152

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.

Formatting Check the box to use Windows’s Quick Formatting option at restore time.Authoritative AD Restore Enables an authoritative restore of the Active Directory database. This option appears only if the machine

being restored is an Active Directory Domain Controller.BMR server IP Address The IP address of the BMR serverBMR Server Netmask The netmask of the BMR serverFile server IP address The IP address that the client uses to reach the File server. This information is not saved in the databaseFile server Netmask The IP address the client uses to reach the boot server. This information is not saved in the database.

8. Click OK. After the processing completes, the following dialog displays:

9. Click OK. The client is ready to be restored and you are ready begin the restore.

Initiating Client RestorationRestoring UNIX Clients


153

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

Restoring UNIX Clients

To 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.

AIX Network Boot

Use the appropriate method to network boot your architecture of AIX client. The options include:

• AIX Method A (Micro Channel-based RS6K)

• AIX Method B (Micro Channel-Based, Symmetric Multiprocessor Systems)

• AIX Method C (RSPC Platform Machine)

• AIX Method D (updates the NVRAM)

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.

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 for ethernet, and, 16 Mb data rate, or 4 Mb data rate for Token Ring.

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.



154

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

Note: If no gateway is used by the client, this field can 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.

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 BMR client ON.

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

4. Press Reset 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 Select BOOT (Startup) Device.

8. Select the network adapter from which the machine boots. 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 corresponds 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 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.



155

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 asks 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 displays, the client boots normally instead of using the SMS disk.

3. If you are using an ASCII terminal, press 4.

4. Select Utilities from the SMS menu.

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

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

7. 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.

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

9. Press Enter. The settings save and the Network Parameters menu displays.

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

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

12. 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.

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

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

15. 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 D

This 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 and 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 OK from within the graphical user interface.



156

Warning: Don’t perform this procedure unless you are intending to do a restore. Preparing a client for restore may result in a restore whether that is what you want to do or not.

1. To restore a client using this method:

2. Log into the client as the root user.

3. 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 then Method A is not appropriate for your hardware.

4. 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 can be a hexadecimal dump of the boot list or a list of device names.

5. Invalidate the current boot list.

bootlist -m normal -i

6. 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.

Solaris Network Boot

1. To begin a network boot of a Solaris client the client must be turned OFF.

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

2. To initiate the restore, turn the client ON.

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


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.

Initiating Client RestorationRestoring a Windows NT Client


157

HP-UX Network Boot

To expedite this procedure, have all the information required on hand.

1. To begin a network boot of a Solaris client the client must be turned OFF.

2. To initiate the restore, turn the client ON.

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


boot lan

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

6. 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.

7. Using the arrow key scroll to “Run a Recovery Shell”. Wait 30 seconds. The Network Configuration Menu opens.

8. Answer the following prompts:

Hostname:

a. Internet Protocol address:

b. Default Gateway:

c. Subnet mask:

d. Ignite server address:

9. Use the arrow key to scroll to OK and press Enter. The system boots from the network and continues the restore process.

Restoring a Windows NT Client

There are several ways to restore a Windows NT BMR client. Only the initial boot step for each restoration method differs.

Client-Generic Floppy Boot

This is similar to the client specific floppy boot except that during the procedure you choose to be able to use the same disk for multiple Windows NT BMR clients. The prompts that occur during the machine specific floppy boot disk creation appear here when you initiate a restore of your NT client. During this procedure you are also asked whether or not your clients use DHCP. This type of restore requires the most amount of user intervention.

1. If your system requires a special partition to function correctly, create that partition first. After the partition is created, continue the normal BMR restore process.

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

The following prompts appear:

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

Initiating Client RestorationRestoring a Windows NT Client


158

• Enter the SRT path:

• Enter the BMR client name:

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

Note: If you answer No to this prompt, the next prompt does not appear.

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

The first reboot erases all the hard drives on the client machine and creates a temporary BMR restoration partition. The save partition (if any) is not included in this formatting.

Client-Specific Floppy Boot

If you wish to do a floppy boot of a specific Windows NT BMR client you first create an NT floppy boot disk. 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.

1. If your system requires a special partition to function correctly, create that partition first. After the partition is created, continue the normal BMR restore process.

2. 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 elected to have a safety prompt, this prompt displays now.

• To continue enter Yes.

• If during the floppy boot disk creation you elected to create a save partition the following prompt displays:

• 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 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.

Completing the Windows NT BMR Client Restore Process

To complete the Windows NT BMR client restore process:

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

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

2. On the third reboot a message displays on the screen telling you to remove the floppy disk and reboot the computer.

3. The third reboot takes place off the hard drive.

4. A fourth reboot occurs automatically and upon recovering from the reboot, the standard Windows NT desktop appears. This is where BMR begins restoration of the clients files.

5. If you are using Dissimilar Disk Restore (DDR) the DDR GUI begins at this point. See the section “Dissimilar Disk Restore for Windows NT / 2000 Clients” on page 180 for information about the DDR GUI.

Initiating Client RestorationRestoring a Windows 2000 Client


159

6. For normal restores the restoration process continues when the Windows NT desktop appears (continuing from step 4). For those using DDR the restore process from this point forward is the same as the normal restore process.

At this point the restore process is automatic. Here is a description of what happens:

• BMR partitions the 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.

Restoring a Windows 2000 Client

There are several ways to restore a Windows 2000 BMR client. Only the initial boot step for each restoration method differs.

Using Generic Boot Floppy

Generic boot floppies do not contain any client-specific information (except for the NIC driver). Hence, a series of questions ask for client-specific information during this type of boot.



160

1. To begin the restoration using a generic boot floppy, insert the generic boot floppy in the floppy drive, and reboot the system.: The following status screen displays the progress of the restore process.

• As each activity is completed, that item is marked with a green check.

• A yellow arrow indicates that the activity is currently in progress.

• A red X indicates a failed activity.

At any time, press <F1> to see details of activities carried out. Or, press <ESC> to abort. Note that <F1> or <ESC> are processed only after the current activity completes.

A series of prompts are displayed. For each prompt, enter the appropriate value(s) and press Enter:

a.

Type Y or N. Press Enter. If you entered Y, go to Step e.

b. .



161

Type the IP address of the client. Press Enter.

c.

Type the subnet mask of the client. Press Enter.

d.

Type the default gateway of the client. Press Enter.

e.

Type file server’s name. Press Enter.

f.

Type file server’s IP address. Press Enter.

g.

Type the SRT name. Press Enter.

h.

Type the client computer name. The client computer name must be unique on this network segment.

Press Enter. The restore process brings up the network and retrieves additional client information from the BMR server. After “Retrieving Client Information” is completed, the following dialog displays:

i.

Type Y or N. Press Enter.

• If you typed N, the restore process creates the required partitions. After repartitioning completes, the system reboots. Go to step 2.



162

• If you typed Y and if no partitions were found that can be saved, the following dialogs are displayed:

To stop the restore process, type NO and press Enter. The Restore process is aborted.

To proceed without saving any partitions, type YES and press Enter. The restore process creates the required partitions, and the system reboots. Go to step 2.

• If you typed Y and one or more partitions are found that can be saved, a list of partitions, displaying the partition number, the partition’s start cylinder (in decimal), and the partition’s size (in Megabytes) is displayed. For example, you may see something similar to the following:

Note that the actual list may be different on your display, depending on which partitions were found.

Type a number from the list, or 0 to not save any partition. Press Enter. Restore process creates the required partitions, and the system reboots.



163

2. After the system reboots, the following status screen is displayed. A check displays beside each activity as it completes:

After “Copying BMR Files” completes, Windows 2000 installation starts to install Windows 2000 into a temporary repair partition. (Note that this is only a temporary installation, and will be removed from the system after the restore process completes.) This process typically takes 20 - 30 minutes; the time can vary drastically depending on system speed and network behavior.

Note: Leave the boot floppy in the drive until told to remove it!

After Windows installation completes, the system reboots into this temporary installation and BMR takes over the rest of the restore process.



164

3. After the system reboots, the BMR Restore status screen displays:

This sequence creates all the required partitions, formats them, and restores the files in each of the partitions. The Details box within the “BMR Restore” dialog displays details about the current activity in progress.

Each activity is checked as it is completed. In the unlikely event of an activity failure, a red X displays next to the failed item. Check the system log and application log to note the reasons for failure. In most cases, correcting the problem described in the event logs, and restarting the restore process is sufficient to effect a successful restore. If any problem persist, contact TKG support.

After all activities are completed, a dialog displays asking you to confirm that the system reboot, and the system is rebooted. The rebooted system should be identical to the system as was last backed up.

Using Custom Boot Floppy

If you wish to do a floppy boot of a specific Windows 2000 BMR client, first create a Windows 2000 boot floppy specific to that client. While creating the boot floppy for your specific BMR client, you have the option of having safety prompts. These prompts allows the process to pause, and requires you to confirm that a restore is what you intend to do before the restore process begins. This type of restore requires a minimum amount of user intervention.



165

1. To begin a restore process using the customized boot floppy, insert the boot floppy into the floppy drive and reboot the system. The following screen is displayed:

After “Retrieving Client Information” is completed, the following series of dialogs may appear, depending on how the boot floppy was created.

• If, during the boot floppy creation, you selected to save a partition and if no partitions were found that can be saved, the following dialogs are displayed:

To stop the restore process, type NO and press Enter. Restore process is aborted.

To proceed without saving any partitions, type YES and press Enter. The restore process creates the required partitions, and the system reboots. Go to step 2.



166

• If, during the boot floppy creation, you selected to save a partition and if one or more partitions are found that can be saved, a list of partitions, displaying the partition number, the partition’s start cylinder (in decimal), and the partition’s size (in Megabytes) is displayed. For example, you may see something similar to the following:

Note that the actual list may be different on your display, depending on which partitions were found).

Type a number from the list, or 0 to not save any partition. Press Enter.

• If, during the boot floppy creation, you opted not to have a safety prompt, the restore process creates the required partitions. After repartitioning completes, the system reboots. Go to step 2.

• If during the boot floppy creation you opted for a safety prompt and you typed 0, the following dialogs appear:

• If during the boot floppy creation you opted for a safety prompt and you typed other than 0, the following dialogs appear::

To stop the restore process, type NO, and press Enter. Restore process is aborted.

To repartition the disk (while saving the selected partition), type YES, and press Enter. After repartitioning completes, the system reboots. Go to step 2.



167

2. After the system reboots, the following screen displays:

As with the previous screen, items are check marked as each item is completed.

After “Copying BMR Files” completes, Windows 2000 installation starts to install Windows 2000 into a temporary repair partition. (Note that this is only a temporary installation, and will be removed from the system after the restore process completes.) This process typically takes 20 - 30 minutes; the time can vary drastically depending on system speed and network behavior.

Note: Leave the boot floppy in the drive until told to remove it!

After Windows installation completes, the system reboots into this temporary repair installation and BMR takes over the rest of the restore process.



168

3. After the system reboots, the following screen displays:

This step creates all the required partitions, formats them, and restores the files in each of the partitions. The Details box within the “BMR Restore” dialog displays details about the current activity in progress.

Each activity is checked as it is completed. In the unlikely event of an activity failure, a red X displays next to the failed item. Check the system log and application log to note the reasons for failure. In most cases, correcting the problem described in the event logs, and restarting the restore process is sufficient to effect a successful restore. If any problem persist, contact TKG support.


Using Custom Media Boot Floppy

1. To begin a restore process using the customized Media Boot floppy, carry out the following three steps:

a. Insert the Media Boot floppy into the floppy dirve

b. Insert the Media Boot CD into the CD-ROM drive

c. Reboot the system.



169

The following status screen displays:

After “Retrieving Client Information” completes, the following series of dialogs may appear, depending on how the boot floppy was created:

2. If, during the boot floppy creation, you selected to save a partition and if no partitions were found that can be saved, the following dialog are displayed:

Do one of the following:

• To stop the restore process type NO and press Enter. The restore process is aborted.

• To proceed without saving any partitions, type YES and press Enter.



170

3. If, during the boot floppy creation, you selected to save a partition and if one or more partitions are found that can be saved, a list of partitions, with partition number, start cylinder (in decimal), and size (in Megabytes) is displayed as follows:

Note that the actual list may be different on your display, depending on how many partitions are found and how they are laid out.

a. Type a number from the list, or 0 to not save any partition

b. Press Enter

4. If, during the boot floppy creation, you opted to have a safety prompt and you typed 0, the following dialogs appear:

Do one of the following:

• To stop the restore process, type NO and press Enter. The restore process is aborted.



171

• To repartition the disk (while saving the selected partition), type YES and press Enter. After repartitioning completes, the system reboots, and the status screen reappears with items check marked as each item is completed.

After “Copying BMR files” completes, Windows 2000 installation starts to install Windows 2000 into a repair partition. (Note that this is only a temporary installation, and will be removed from the system after the restore process completes.) This process typically takes about 10 minutes; the time can vary drastically depending on system speed and CD-ROM drive speed.

Note: Leave the boot floppy in the drive until BMR asks you to remove it.



172

After Windows installation completes, the system reboots into this temporary repair installation and BMR takes over the rest of the restore process. The BMR Restore status screen displays:

This step creates all the required partitions, formats them, and restores the files in each of the partitions. The Details box in the lower portion of the “BMR Restore” dialog displays specific details about the activity currently in progress.

Each activity is checked as it is completed. In the unlikely event of an activity failure, a red X displays next to the failed item. Check the system log and application log to note the reasons for failure. In most cases, correcting the problem described in the event logs, and restarting the restore process in sufficient to effect a successful restore. If problems persist, contact TKG Support.


Active Directory Restores

If the Windows 2000 client was configured as an Active Directory server, BMR will detect this and configure the system to reboot in Active Directory repair mode. This is a Windows 2000 feature called Safe Boot Mode. When the system reboots in Active Directory repair mode, you are prompted for the password of the Active Directory administrator.

Once you login as the Active Directory administrator, BMR automatically invokes programs to restore the Active



173

Directory. The Restore Active Directory status screen displays:

If the Authoritative AD Restore option is selected during the prepare to restore phase, the following dialog displays:

5. Select Yes to authoritatively restore the AD database.

As each activity is completed, a check mark displays next to the item on the Restore Active Directory screen. After all items are completed, the system is rebooted. The Active Directory is completely restored, and should be identical to the system as was last backed up.



174


5 Advanced Features

Topics covered in this chapter:“Dissimilar Disk Restore (DDR)” on page 176“Backup Sets” on page 184“Initiating a Client Restore using Media Boot” on page 187

“Service Packs for Windows NT” on page 189

Bare Metal Restore User GuideAdvanced Features


176

Dissimilar Disk Restore (DDR)

Introduction to DDR

Bare Metal Restore provides utilities that allow the restoration of a client to hardware with different physical disk properties. For the purposes of this explanation, “disk” will refer to a physical disk, and “volume” will refer to a logical division on a physical disk.

The ability to perform a DDR is useful when one or more physical disks needs to be replaced before the restore or when restoring to a machine that is similar to the original client but has a different physical disk configuration. This ability is also useful when the user decides not to restore some volumes automatically.

The Dissimilar Disk Restore feature of BMR allows restoration when any of the following have occurred:

• The size of one or more disks has increased.

• The size of one or more disks has decreased but can still contain all original volumes.

• The location of one or more disks has changed.

• The number of disks has increased but can still contain all required volumes, in some arrangement.

• The number of disks has decreased but can still contain all required volumes, in some arrangement.

• The user has decided to restore only critical volumes and not restore other volumes.

BMR supports Dissimilar Disk Restore for AIX, Solaris, HP-UX, Windows NT, and Windows 2000. As examples, this guide uses AIX and Windows NT/2000 clients.

BMR Dissimilar Disk Restore does not support VERITAS Volume Manager or VERITAS File Server.

Dissimilar Disk Restore for UNIX Clients

(This instruction only addresses the DDR process. It does not address other fields on these screens in the Prepare to Restore phase. In addition, it should be noted that the process for restoring dissimilar disks is the same as that for restoring similar disks with one exception - click the Dissimilar field on the Prepare to Restore screen.)

To begin a dissimilar restore:

1. From the BMR navigation bar, click Clients. The List BMR Clients screen displays.

2. Click the name of the client. The Configure Client screen displays.



177

3. Click Prepare to Restore. The Prepare to Restore screen displays.

4. On the Prepare to Restore screen, click Dissimilar Disk: (Enable Dissimilar Disk Restore).

5. Click OK.



178

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.


7. Click OK. The Boot Client screen displays.

8. Reboot the client to perform the hardware discovery phase of the restoration.

Note: BMR client naming convention is “server name,storage manager name”

Note: In the GUI, clicking the Cancel button at this point allows you to perform other operations in the GUI until the discovery boot has been done. At that point, the client state becomes “WFDMR” and displays as an HTML link on the BMR Client list page that allows you to reach the Map Dissimilar Client Restore screen seen below for the restoring BMR client.



179

9. After UNIX completes its discovery boot, Click Next. The Map AIX Dissimilar Client Restore dialog displays:

10. Create your new disk configuration.

a. On the screen above, click Available Disks. This is what BMR discovered during the reboot of the BMR cli-ent as your new disk availability. Below that box is a pull down menu of available volume groups. Click on

Field Definition

Client Name The name of the dissimilar restore client.

Client OS The operating system of the dissimilar restore client.

ESM Client Password The TSM Client password for the dissimilar restore client.

Available Disks A list of discovered disks to be used in the restore process.

Original Disks Your original pre-crash disk configuration.

Restore Disks A list of assigned disks used in the restore process.

Restore File Systems A list of what filesystems and logical volumes that are associated with each volume group.

Size This keeps track of how much hard drive space is allocated in your new disk configuration.

OK Proceed with the restore

Cancel Cancel the restore



180

a selection in Available Disks and select a volume group for that disk to be assigned to. Click the + button. This moves the selected hard disk to the selected volume group.

b. Under each of the individual volume groups you can inspect the original configuration to get an idea of what how much space you want to assign each volume group. Keep in mind the guidelines for dissimilar restore while you assign disks to different volume groups.

c. To remove an assigned disk from a volume group, click on the disk you wish to remove and click the X but-ton associated with that volume group. This moves the selected hard drive back to the list of available hard drives. You can then assigned that hard drive to a different location.

d. In the Restore FileSystems field, select the logical volumes and filesystems you wish to install into your volume groups. Given enough space, you can either select all the logical volumes and their filesytems or you can choose specific logical volumes/filesystems. You do not have to restore all your logical volumes and filesystems because, given your new disk configuration, you may not have enough disk space.

11. Click OK. The restore proceeds.

Dissimilar Disk Restore for Windows NT / 2000 Clients

(This instruction only addresses the DDR process. It does not address other fields on these screens in the Prepare to Restore phase. In addition, it should be noted that the process for restoring dissimilar disks is the same as that for restoring similar disks with one exception - click the Dissimilar Disk field on the Prepare to Restore screen.)

A restoration is marked as DDR by one of the following:

• On the “Prepare to Restore” screen, click Dissimilar Disk.

• On the command line option of bmrrestore, type -d.

To begin a dissimilar restore:

1. From the BMR navigation bar, click Clients. The List BMR Clients screen displays.

2. Click the name of the client. The Configure Client screen displays.



181

3. Click Prepare to Restore. The Prepare to Restore screen displays:

4. Click Dissimilar Disk.

5. Click OK.

6. Reboot the client. The restore begins. At an appropriate point in the restore, the BMR Disk Mapping Utility displays:

The DDR disk mapping utility runs on the restoring client towards the beginning of the Windows phase of the restoration process. This utility displays all the partition information from the saved configuration in the top panel and all the disk information on the restoring machine in the bottom panel.



182

7. From the top panel, select the Partition Information to create or restore. Note the scroll bar for the top panel.

Each Partition Information panel contains the following information:

Name - identifier for this partition

a) Drive letter for Windows logical drives

b) “Unlettered#_#” for Windows logical drives without drive letters

c) “Unknown#_#” for partitions not recognized by Windows

d) “Ext Free Space #” for extended partition space not allocated to logical drive

Type - the type of this partition. One of:

a) “Primary” - for Windows logical drives that are primary partitions

b) “Extended” - for Windows logical drives that are extended partitions

c) “Container” - for extended partition free space

d) “Unknown Primary” - for primary partitions not recognized by Windows

e) “Unknown Extended” - for extended partition not recognized by Windows

Used File Space - space consumed by files on this partition from saved configuration

Original Size - size of partition from saved configuration

Restore Size - size partition will be after restoration

Original Disk - disk name that partition was on from saved configuration

Restore Disk - disk partition will be on after restoration



183

Restore Files Option - indicates whether or not to format partition and restore files; applies only to Windows logical drives

Required - label

8. From the bottom panel, via the Discovered Disk Information. Each Discovered Disk information panel contains the following items:

Name - identifier for this disk

Disk Size - total size of the disk, in gigabytes

Space Available - total size of disk less space allocated to partitions, in gigabytes

Selecting a Partition to Create: All partitions, except required partitions, are initially marked as “Do not create.” To create a partition, select the target disk from the “Restore Disk” selection. If the selected disk has enough space available, the partition will be allocated space on the selected disk. If there is not enough space, an error message will appear and the partition will revert to its previous state.

Selecting a Partition to Restore: Partitions that contain a Windows logical volume have an additional checkbox towards the bottom of the panel. This checkbox is used to select whether or not to format the logical drive and restore its backed-up files. If the box is checked, the logical drive is formatted and files restored. Otherwise, it is left as a raw partition.

Altering the Size of a Partition: The DDR utility allows the resizing of partitions. Entering a new size into the “Restore Size” edit field changes the size of that partition after restoration. After increasing its size, the partition must still fit on its assigned disk. Windows logical drives must remain large enough to contain all its files. If the partition size is set to an invalid value, an error message displays, and the partition returns to its previously set size.

9. To continue with the restoration process, click Done. The restore continues and progress is displayed on the BMR Restore wizard screen.

• Disks are partitioned.

• Clients reboot.

• All drives are formatted on the client machine.

• The temporary partition created earlier is removed.

• The client is cleaned up after the BMR restore process to change the state of the client from ‘restoring’ to ‘ready’.

After these operations finish the Windows client is completely restored.



184

Backup Sets

Using Backup Sets with Windows NT

Backup sets are a self-describing snap shot of active files. They do not require a TSM server.

Once you have created the backup set using TSM, copy the backup set image onto a CD-ROM using conventional CD burning software. If you do not have a CD-R drive on your TSM server, you can FTP the image onto a machine that does and make the CD that way.

After you have created the CD, do a Prepare to Restore:

1. From the BMR navigation bar, click Clients.

2. Click on the client you wish to restore.


4. In the field labeled backup sets, enter the file name of the backup set.

5. Click OK.

6. Insert the CD into the CD-ROM drive of the BMR client.

7. Restore the machine using the procedure labeled Restoring a Windows NT Client in Chapter 4.

8. Towards the end of the restore process instead of accessing the network for the TSM files, BMR goes to the file on your CD-ROM drive and the restoration continues normally.

Using Backup Sets with Windows 2000

TSM Backup Sets

A TSM backup set is a collection of backed up active client files stored on a TSM server or other media managed as a single object. A client may have multiple backup sets. Backup sets may be stored on removable media (CD-ROM, ZIP or JAZ) drives allowing LAN-Free restores from devices attached directly to the client machine. A backup set may contain client nodefilespace for all active client files or a specific filespace. Bare Metal Restore for Windows 2000 requires all active filespace and the SYSTEMOBJECT are contained in backup sets being used for BMR.

Generating Backup Sets (all client node filespace)

Note: Before generating backup set(s) for use with Bare Metal Restore, all client node files including SYSTEM OBJECT/Registry should be backed up.

A device class should be defined on the TSM server using device types that are supported on both client and server.

In the following example a device class (devclass) will be used to write the client's files to the TSM server. These file(s) will later be transferred to a machine with WORM CD-ROM via ftp. The transferred files will be written to CD. The client has a CD-ROM attached from which backup sets will be read.

Define DEV CLASS

tsm> define devclass CDROMFILES devtype=files maxcapacity=640m



185

dir=/much_space_here

Note: Using the above device class specifies that backup set data will be stored in files (“devtype=files”). These files will be stored in the directory/file system “much_space_here” (“dir=/much_space_here”). The maximum size file is 640 megabytes. If more than 640 megabytes is needed to generate the backup set then another file (volume) will be used. Files will have a .OST extension but can be renamed (i.e. vol1,vol2,vol3,etc...) when written to CD.

Generate BACKUP SET

tsm> generate backupset myclient_node myprefix devclass=CDROMFILES wait=yes

Note: The above command generates a backup set for nodename myclient_node. TSM adds a suffix to “myprefix” to name the backup set. The actual data will be stored in the directory specified by the DEVCLASS. Use tsm command: “query volhist” to determine which files are in a backup set.

Transfer files to a machine with CD write hardware/software and write each file to CD. There are now backup sets located on the server and CD. These may be used to perform a BMR.

Except for “Prepare to Restore 2000 Client”, follow the procedures documented in the “Preparing for Client Restoration” section.

If a restore is being made with backup sets, follow the instructions below at the “Prepare to Restore 2000 Client” module .

BareMetal Restore

GUI

• From local CD-ROM: “Prepare to Restore 2000 Client,” “Local_CD_Backup_Set,” enter the name of first volume in “Backup Set File Name:”



186

Note: The backup set is the file name of the first volume. If the first volume is mybackup_vol.1, enter it into this field. This example uses W2K214VOL.1.

CLI

The CLI is an alternative to the GUI

• From local CDROM:

#bmrrestore -r -l -c backupset_name -S file my_client_name

Note: If using a multivolume CD backup set, during a Bare Metal Restore, the client prompts to enter the location of the next volume in the backup set. At this prompt insert the CD containing the next volume in the backup set.



187

Initiating a Client Restore using Media BootThe following sections describe the process of using Media Boot to boot off the CD-ROM drive in each of the three UNIX operating systems and Windows NT and 2000.

Media Boot for AIX - RS6K

To initiate a client restore off the CD-ROM drive on an RS6K machine:

1. Start with the machine powered off.

2. Insert the CD-ROM SRT into the CD-ROM drive.

3. Turn the switch to Service mode.

4. Turn the power on to the restore client.

5. The machine boots off the CD.

6. Enter network and BMR server information at the prompts. The restore proceeds.

7. After the machine finishes booting but before the restore is complete, turn the switch to the “normal” position.

Media Boot for AIX - RSPC

To initiate a client restore off the CD-ROM drive on an RS6K 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 asks 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 Select Boot Device from the System Management Services menu.

4. Select Boot Other Device from the menu.

5. Select SCSI CDROM from the menu.

6. The machine boots from the CD.


8. After the machine finishes booting but before the restore is complete, turn the switch to the Normal position.

Media Boot for AIX - CHRP

To initiate a client restore off the CD-ROM drive on an CHRP machine:

1. Turn the power ON to the restore client.

2. Press F1 (if using an ASCII terminal, press 1) when icons (or keywords) begin appearing on the bottom of the screen, after the keyboard icon (or keyword) is displayed.

3. Select the Multiboot to display its menu.



188

4. Select the “Install From” (or from ASCII terminal, “Select Install Device”) option

5. A menu displays the OS level for the Media Boot CD; select that option. The machine boots off the CD.


Media Boot for Solaris

To initiate a client restore off the CD-ROM drive in Solaris:

1. Reboot the client

2. At the OK prompt type:

boot cdrom

3. Enter network and BMR server information at the prompts. The restore proceeds..

Media Boot for HP-UX

To initiate a client restore off the CD-ROM drive in HP-UX:

1. Power on the HP-UX client.

2. Within 10 seconds, press the Space Bar to stop the normal boot process.

3. Search for the location and name of the CD-ROM drive.

4. Find the CD-ROM drive from the list of drive choices and enter the path number.

5. Answer yes to the question inquiring about starting up networking.

6. Answer the following prompts:

a. Hostname:

b. Internet Protocol address:

c. Default Gateway:

d. Subnet mask:

e. Ignite server address:

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

8. Enter the IP Address of the BMR server.

9. Enter the port number of the BMR server. The system boots from the CD-ROM and continues the restore process.

Media Boot for Windows NT/2000

To initiate a client restore in Windows systems:

1. Insert the CD with the SRT

2. Insert the floppy prepared by the Boot Options Wizard

3. Reboot the computer. The restore begins automatically.

Client Setup when a Service Pack is required


189

Service Packs for Windows NTSome Windows NT clients may require a service pack during the restore process. For example, if the client has a network device that is only supported with a service pack and that network device is used to do the restore then a service pack is required at restore time.

Clients that require a service pack needs more reservation space, a total of 313 MB up from 150 MB for clients that do not require a service pack. For this reason you must indicate whether a client requires a service pack when “Configuring the Windows NT Client”.

Clients that require a service pack needs more reservation space, a total of 313 MB up from 150 MB for clients that do not require a service pack. For this reason you must indicate whether a client requires a service pack when “Configuring the Windows NT Client”.

Client Setup when a Service Pack is required

If your NT client requires a service pack, indicate this when running the client setup wizard by checking Service Pack Required.

The above form presents the “Service Pack Required” option. It is pre-selected and it is best to keep it checked if you have the disk space for the extra reservation space. Thus, you always have the option of using a service pack or not.

If your NT client is already configured, you must rerun the bmrsetupclient program if you want to enable using service packs.



190

Note: Even if your NT client has a service pack installed, you are not required to have a service pack at restore time. The service pack is only required if it is needed during the restore. That said, the most flexible configuration is to check the “Service Pack Required” check box.

Creating a Service Pack

This section describes all the steps necessary to create and use a service pack.

1. From the Start menu, select Programs, select Bare Metal Restore, select createPKG.

2. The following screen displays:

Creating a Service Pack


191

The OS field is set to “NT”, The Description has a default value of “Service Pack” and the file server drop-down menu is populated with all defined file servers.

3. Fill in the required fields.

Field Description

Name Field with an 8 character name of your choosing that will help you identify this service pack.OS Operating system for the client.Description Edit this field if appropriate. File Server Select the File Server from a drop-down menu of all defined File Servers in your BMR environment. This

File Server is where the service pack will be copied to.Service Pack Executable Select the location of the service pack. The service pack must be a self-extracting executable which is the typical

format downloaded from the internet. 4. Click Finish.

5. The service pack is copied from the specified location to the share directory on the specified file server. This operation can be canceled at any time.

The copy operation completes and the BMR database is updated. The Completed Successfully status dialog displays:

The service pack is successfully created. The OK button becomes active.

6. Click Ok to end the Create Package wizard.



192


6 Troubleshooting BMRThis chapter describes tips, solutions, work-arounds, FAQs— all under the topic of Troubleshooting.

Topics covered in this chapter:“Solaris 2.6 causing panic on net or cdrom boot” on page 194“How to find the correct MSD driver to add” on page 198“Identify the Vendor Partition During a Restoration” on page 200

“Error 53: The computer specified in the network path cannot be located.” on page 200“VERITAS File System without VVM” on page 201“No System Objects” on page 202

“Unlabeled Disks in Solaris BMR Restores [9959]” on page 203“AIX 4.2.1 Boot Failure” on page 204“Boot from CD” on page 205

“BMR Server Setup” on page 206“Long Restore Times on HP” on page 207

Bare Metal Restore User GuideTroubleshooting BMR


194

Solaris 2.6 causing panic on net or cdrom boot

Symptoms There is a problem with certain Solaris systems that causes a panic when booting from some Solaris 2.6 boot images. The symptoms are that the network or cdrom boot proceeds to a certain point and then the system panics, usually during processing of the /etc/system kernel configuration parameters. You may see references to BAD TRAP: cpu=# type=31 or type=34 among other possible references.

Reportedly this may affect E3000-E10000 model machines, but could affect others as well.

The Problem The essential problem has to do with hardware limitations affecting the use of CPU cache.

This problem is well understood by Sun technicians but may not be well known to all Sun administrators, and may sometimes be referred to as “the ecache problem” or “the limit-ecache-size problem”.

For affected systems, certain Solaris 2.6 CDs will not be bootable without the panic occurring, and network boots (such as using BareMetal Restore SRTs built using those Solaris 2.6 CDs) will also have the panic problem.

Solutions There are two possible solutions, with some variations: (1) use the limit-ecache-size Open Boot PROM (OBP) command approach, or (2) use a version of Solaris 2.6 with a kernel that does not have the problem.

Approach (1) has been tested in the field and is known to definitely work for E4500 and E10000 systems. Note that leaving limit-ecache-size permanently persistent may limit performance unnecessarily, so read the details below to understand how to use it appropriately.

Approach (2) is based on documentation for Solaris patch 105181-19 or later, but has not been thoroughly tested.

Approach 1: Use the limit-ecache-size OBP command

The panic is caused by a version of the kernel that cannot deal with the CPU cache size of the hardware being used. Sun recognized this problem and provided PROM updates that include an additional command, “limit-ecache-size”, that *TEMPORARILY* limits the size of the CPU cache to 4 megabytes. If this command is used before a network or CD boot, all Solaris 2.6 boot images should work as desired. However, the following issues may apply:

(Issue 1.A)The version of the PROM in question may not support limit-ecache-size.

Sun has released PROM versions that have limit-ecache-size predefined. If so, you merely execute it to implement Solution 1. Here, we show you how to deal with PROM versions that do not predefine it.



195

How to test Issue 1.A: at the ok> prompt, try limit-ecache-size.

If no error occurs, the PROM supports the command and the limit will be in effect until the next hardware reset.

Workaround 1.A:

Test to see if Issue 1.B also applies. If it applies, see its workaround (below) for the things you must do instead or as well as the following:

• If the PROM does not have the command, type the following code exactly as shown at the ok> prompt to define the limit-ecache-size command until the next hardware reset:

: (limit-ecache-size)

“ device_type” get-property if

exit

then get-encoded-string “ cpu” $= if

“ ecache-size” get-property if

exit

then drop dup l@ 4meg min swap l!

then

;

: limit-ecache-size

“ /” ['] (limit-ecache-size) scan-subtree

;

You should now be able to execute the limit-ecache-size command. It will take effect immediately but only persist until the next hardware reset.

(Issue 1.B) Some PROM versions force hardware resets too often

The definition of limit-ecache-size given in Issue 1.A may be complicated if the PROM version or configuration always forces a hardware reset when “boot net” or “boot cdrom” is used. Hardware resets undo the effects of limit-ecache-size.

How to test Issue 1.B:

When using “boot net” or “boot cdrom” at the ok> prompt, observe the results: if a hardware reset (screen clears, with or without OBP POST output) happens, or if limit-ecache-size seem to have no effect, you should try the following workaround for Issue 1.B.

Workaround 1.B:

Use the NVRAMRC to make limit-ecache-size persistent. You can do this using the following steps:

Use the nvedit command at the ok> prompt:

ok> nvedit

(The current contents of NVRAMRC will display.)



196

Use Control-N to move to the last line of NVRAMRC. Use Return (or Enter) to start a new blank line.

Enter the following text: (Note that if Issue 1.A also applies, you should also enter the entire definition for limit-ecache-size into NVRAMRC first.)

limit-ecache-size

Use Control-C to exit nvedit.

Use the nvstore command to save the NVRAMRC contents:

ok> nvstore

Test the current setting of use-nvramrc?:

ok> printenv use-nvramrc?

If not currently true, make it so:

ok> setenv use-nvramrc? true

From now on, when this machine boots, its CPU cache will be limited.

Network and CD boots should now complete, and the machine should be restorable using BareMetal Restore. IMPORTANT: SEE NOTE:

Note: Limiting CPU cache size in NVRAMRC may reduce performance, and for that reason it is recommended that the limit-ecache-size command be removed from NVRAMRC after the machine is restored. To do that. use the following procedure:

Use the nvedit command at the ok> prompt:

ok> nvedit

(current contents of NVRAMRC displays)

Use Control-N to move to the line that executes limit-ecache-size. (If it was necessary to define it here also because of Issue 1.A, leave the definition in place since it will be useful for any future CD or network boots from older Solaris 2.6 boot images. The definition causes no problems, only making its use persistent does.)

Delete only the line that executes “limit-ecache-size” using Control-U (erase whole line) or Control-D (delete next char) and Control-K (delete end-of-line).

Use Control-C to exit nvedit.

Use the nvstore command to save the NVRAMRC contents:

ok> nvstore

Approach 2: Use a Solaris 2.6 kernel that supports the full ecache:

Later versions of Solaris 2.6 cdrom boot images include a patch that supports use of the full ecache, making the limit-ecache-size approach unnecessary. Approach 2 addresses how to locate such a boot image. NOTE: this approach is based on Sun Solaris documentation for patch 105181 and has not been as thoroughly tested. Sun has documented that patch 105181-19 or later (which almost



197

certainly requires patch 106429-02 or later as a prerequisite) should fix the panic problem on affected hardware.

Issue 2.A:Determine if the patch(es) are already in place:

How to test Issue 2.A:

Locate the boot image root directory on the CD or SRT. This will be the Solaris_2.6/Tools/Boot directory, such as

/cdrom/cdrom0/s0/Solaris_2.6/Tools/Boot

or under an SRT such as

/export/srt/sol26/Solaris_2.6/Tools/Boot

Run:

patchadd -p -d /cdrom/cdrom0/s0/Solaris_2.6/Tools/Boot

and look in the output for patch 105181-19 or later.

If not present, either use Approach 1, or proceed with the following.

Workaround 2.A:

Download and install the patch(es) needed in the SRT from sunsolve.sun.com. Locate the current version of patch 105181 and its perquisites. Currently these would be 105181-28 and 106249-02. Note that the patches need to be in directory format, so unspool them if necessary after downloading using the patchadd -s option.

Add them to your SRT after TSM installed in the “add item” phase, installing the prerequisite (if any) first and then the main patch.

Your Solaris 2.6 SRT should now be network-bootable, and media boot CDs made from it should be CD-bootable without the limit-ecache-size workaround.



198

How to find the correct MSD driver to add

Symptom bmradddriver comes up with more than one option while adding an MSD driver

Note: This applies to pre BMR 3.2.1 NT clients

Solution 1. Find the driver file name:

a. Goto Control Panel -> Scsi.

b. Click on the desired controller and click Properties

c. Select Driver tab and note the driver file name (for example: cpqarry2.sys)

2. In the driver diskette (or CD) open txtsetup.oem file (using notepad, wordpad, or any text editor)

The file name you found in step 1-c should be under one of the [Files.scsi.xxxxx] sections.

For example, txtsetup sections may look like this: [SCSI]

fs2_40 = “Compaq 32-Bit SCSI-2 Controllers for Windows NT 4.0"

ida_40 = “Compaq Drive Array for Windows NT 4.0"

fbr_40 = “Compaq Fibre Channel Host Controller (Disaster Recovery Only)”

ftr_40 = “Compaq Fibre Channel Filter Driver (Disaster Recovery Only)”

ary2_40 = “Compaq Integrated Smart Array/42xx/43x Con-trollers”

[Files.SCSI.fs2_40]

driver = d1,cpq32fs2.sys,Cpq32FS2

inf = d1,fastscsi.inf

[Files.SCSI.ida_40]

driver = d2,cpqsmgrk.sys,cpqsmgrk

driver = d2,cpqarray.sys,cpqarray

inf = d2,cpqarray.inf

[Files.SCSI.fbr_40]

driver = d3,cpqsmgrk.sys,cpqsmgrk

driver = d3,cpqfcalm.sys,cpqfcalm

inf = d3,cpqfcalm.inf

[Files.SCSI.ftr_40]

How to find the correct MSD driver to add


199

driver = d4,cpqfcftr.sys,cpqfcftr

inf = d4,cpqfcftr.inf

[Files.SCSI.ary2_40]

driver = d5,cpqarry2.sys,cpqarry2

inf = d5,cpqarry2.inf

In this example, cpqarry2.sys is under [Files.SCSI.ary2_40] section. Thus the correct “option name” is ary2_40.

[SCSI] section, ary2_40 corresponds to:

ary2_40 = “Compaq Integrated Smart Array/42xx/43x Controllers”

so this option should be chosen when adding drivers.



200

Identify the Vendor Partition During a Restoration

Description Bare Metal Restore can save vendor partitions.

Vendor partitions are partitions used by a vendor for various reasons. For instance, RAID implementations may use a vendor partition.

Problem When the boot floppy was created you indicated that a special partition must be saved.

BMR Requirements Bare Metal Restore will preserve the vendor partition (special partition) if it adheres to the following basic requirements (most vendor partitions meet these):

1. The vendor partition must be less than 1 GB

2. It must start at the beginning of the drive.

3. It must not be recognized as a DOS primary partition.

4. Its partition type must be unique to other partitions on the drive.

Solution During the restoration you are prompted for which partition to save:

• If there is more than one partition, chose the partition with a non-zero size.

• If more than one partition has a non-zero size, chose the one with 'Cylinder' zero

• Error 53: The computer specified in the network path cannot be located.

VERITAS File System without VVM


201

VERITAS File System without VVM

Upon restoring a client that has vxfs filesystems (but not Volume Manager), the restore fails because vxlicense command is unavailable.

If VRTSlic is needed and not installed, the SRT will need to have it added before a successful restore of vxfs filesystems can be done.



202

No System Objects

Problem Machine doesn't restore because of no SYSTEM OBJECTS. This error can occur with TSM clients.

Prevent it because there is no solution. If you get into this state you need to reinstall your machine.

Solution Ensure that you backup “System Objects”.

Also, note that TSM 3.7.1 server will not backup “System Objects” from a 4.1.3 client.

Solution If restore fails (because vxlicense command is unavailable), install VRTSlic into SRT and do client restoration boot again.

Some versions of VRTSvxfs package require VRTSlic as a prerequisite if VRTSvxvm is not also installed in the SRT. If there is a VRTSlic package with the VRTSvxfs package, you have such a version.

Unlabeled Disks in Solaris BMR Restores [9959]


203

Unlabeled Disks in Solaris BMR Restores [9959]

Symptom There has been a problem dealing with Solaris BMR having to do with unlabeled disks. The most common way(s) this will be encountered are brand-new disks installed in machines being recovered, or someone corrupting the label of a disk in a machine, such as with the dd or format analyze commands.

When an unlabeled disk is present in a machine during BMR restore or DMR discovery boot, you will see error messages complaining about a bad disk label and/or bad magic number in the disk label. The error message tells you which disk is involved.

Problem Beginning with BMR 3.1.1 patch 002, regular BMR restoration will handle unlabeled disks in all known configurations, but Dissimilar Disk Restore (DMR) scenarios still will not in any configuration. For DMR restores, the following procedure will be needed.

Solution Prior to BMR 3.1.1 patch 002, restoring BMR clients that use VERITAS Volume Manager will need the following procedure for regular BMR restoration. (DMR is not supported for VERITAS Volume Manager.)

1. Boot from the SRT in single user mode: “boot net -s”

2. When the machine finishes booting, run the format command, choose an unlabeled disk (they will show up during the boot phase with error messages about bad magic numbers), then use the label option of the format menu.

3. Repeat for all disks that have no label.

4. Continue with normal restoration/DMR discovery by using the “unit 2” command to resume the rest of the restore/discovery boot process.

Unlike the procedure for dealing with failed restores that dumps you out to a shell prompt, this workaround does not seem to require you manually create a /dev/tty symlink to /dev/console before the format command will work. This may be due to the use of the single-user mode (the -s option to boot) or absence of interference from logging issues that occur later.



204

AIX 4.2.1 Boot Failure

Problem AIX 4.2.1 or greater booting from a 4.2.0 boot image (BI) doesn't work.

Solution AIX 4.2.1 introduced 'chrp' support (devices.chrp.* filesets). So, if the client is a 'chrp' it must boot from a BI created from a 4.2.1 or later.

Boot from CD


205

Boot from CDAll three UNIX platforms use a common bootable CD format (ISO-9660). If a system will not boot from the CD, examine the CD by placing it in any available system with a CD-ROM drive and see if the CD has been written successfully. (ISO format can be read by either UNIX or Windows platforms.)

1. If the contents of the CD are a single file, it was written as a data CD instead of an ISO-9660 CD image. Repeat the burning procedure but use the options required to burn an ISO image file to the replacement CD.

2. If the CD is blank or unreadable, examine it closely to see if in fact it has not been burned at all. (Some CD burning software by default “simulate” burning a CD to test the capabilities of the CD burning hardware, and so will leave the CD unwritten until the “test only” option is turned off. Repeat the burning procedure with the “test only” option disabled.

3. If booting was partially successful, or if it appears that some files are present but some are missing or corrupted, either the burning process or the file transfer from the BMR file server to the machine with the CD writer may have failed or partially failed.

a. A partially burned CD may be bootable but may be missing significant portions of its content. Lowering the CD writing speed may allow suc-cessful burns that fail due to system load. Using the “test after writing” option offered by some CD writing software may help detect unsuccess-ful CD writes.

b. Closely examine the CD image file used by the CD writing software: could it have been corrupted? Try comparing checksum values of the original and copied version to see if they differ. Examine FTP transfer logs. Make sure enough free disk space existed and the file was not truncated.

4. See if the CD boots successfully on another (similar) machine: sometimes CD drives may become dirty through either frequent or infrequent use and may need to be cleaned. Similarly, the CD itself may be easily damaged or made unreadable by surface contamination after writing. Examine the physical media and the environment in which it is being read.

5. Verify that you are using the correct procedures to boot the client machine from CD.

BMR Server Setup


206

BMR Server Setup

Problem While doing Setup of a BMR server, it looks like the Setup program is looking for dsm.sys and dsm.opt in the same directory as the TSM executables.

It is common for Zeppelin to install their TSM executables in another directory than the one with the .opt and .sys files as a sort of protection when they upgrade TSM, so their configuration is not overwritten by mistake.

Bmrsetupserver bails out on this.

Workaround Copy the .opt & .sys files in the DSM dir. This works, but it does not look nice.

Issue Where does bmrsetupserver look for/use dsm.opt and dsm.sys? Isn't that more of a bmrsetupclient kind of thing? Or an bmrinitsrt activity?

Solution The BMR server needs access to the TSM server, and thus should be a client of it. The bmrsetupserver procedure asks for the location of DSM_DIR. TSM. Executables are located in this directory, and the dsm.sys and .opt files also. That is, per default...

Zeppelin puts the executables in one directory, and the opt and sys files in another. Once the server is installed, we use our own copies of both files; they are copied during the setup procedure.

TSM uses DSM_CONFIG to point to a dsm.opt file. DSM_DIR must be the location of dsm.sys and the tsm executables. It is not BMR that has this restriction. BMR knows about and also uses these variables. So Alain, if the dsm.opt is in another directory, just set the DSM_CONFIG variable to point to that file. Then run bmrsetupserver. BMR will find it. If you run dsmc it will use the same variables to find the TSM server IP address. So a good way to check is to run dsmc to see what server it connects to. If it is correct, then bmrsetupserver should find the same one. If it doesn't it is a defect in BMR.

Long Restore Times on HP


207

Long Restore Times on HP

Symptom Unusually long BMR restore times have been found on HP systems (20 hours versus 2 hours).

Problem There is a mismatch of media speed between the adapter and the switch/hub to which it is connected. For example, if the media speed is set to 100Mb full-duplex, the restore slows down because it is connected to a hub which does not handle full-duplex.

Solution Change your media speed using the boot console before entering 'boot lan'.

Instructions You need to access the LAN Configuration commands to change the media speed.

1. From the boot console prompt “Press any key ...” The Main menu displays. The Main menu has the following commands:

2. Select the Configuration menu by doing the following: At the prompt “Main menu: Enter command >” enter “co” and press Enter.

The Configuration Menu displays

...<snip>...

...<snip>...

3. At the prompt, “Configuration menu: Enter command >” enter “he lc” and press Enter. [he=HElp, lc=LanConfig] The following information displays: using these commands you can configure and display the configuration of the network interface:

Command Description

BOot [PRI|ALT|[<path>] Boot from specified path

PAth [PRI|ALT|CON|KEY] [<path>] Display or modify a path

SEArch [DIsplay|IPL] [<path>] Search for boot devices

COnfiguration [<command>] Access Configuration menu/commands

INformation [<command>] Access Information menu/commands

SERvice [<command>] Access Service menu/commands

DIsplay Redisplay the current menu

HElp [<menu>|<command>] Display help for menu or command

RESET Restart the system

LanConfig [<params>] Display or set LAN configuration

Command Description

LanConfig Display current configuration settings

LanConfig 10/Half_dx Operate in 10 Mbit/s, half duplex mode

LanConfig 100/Half_dx Operate in 100 Mbit/s, half duplex mode

LanConfig 10/Full_dx Operate in 10 Mbit/s, full duplex mode



208

Note: This display may differ depending on your hardware.

Note: If you do not use this method, the system boots up with the default setting, AUTO_Detect.

4. At the prompt “Configuration menu: Enter command >” enter “lc 100/full_dx” and press Enter. Confirmation is displayed as follows:

Setting is now 100/Full_dx.

This will take effect at the next BOot or SEArch command.

5. At the prompt, “Configuration menu: Enter command >” enter boot lan and press Enter.

This returns you to the standard restore procedure as described in Chapter 4.

Example 1. To set the media speed on the client machine to 100 Mb full-duplex, use the Main menu.

2. At the prompt, “Main menu: Enter command >” enter “co” and press Enter. The Configuration Menu displays

3. At the prompt “Configuration menu: Enter command >” enter “lc 100/Full_dx” and press Enter. Confirmation is displayed.

4. At the prompt, “Configuration menu: enter command >” enter boot lan and press Enter.

5. Return to the standard Restore procedure in Chapter 4.

LanConfig 100/Full_dx Operate in 100 Mbit/s, full duplex mode

LanConfig AUTO_detect (default) Enable auto-negotiation

LanConfig AUI Use the AUI port (10 Mbit/s, half duplex)

Command Description


7 Upgrades and the PatchMechanism

This section describes the upgrade and patch mechanisms for Bare Metal Restore. Upgrading was introduced with BMR 3.1.0; patching was introduced with BMR 3.1.1. If you are installing a new major release on top of an earlier one, do an upgrade. If you are installing software fixes within a major release, do a patch. For example, if installing BMR v3.2.1 on either a BMR 3.1.0, 3.1.1, or 3.2.0 installation, use the upgrade procedures. If installing patch 001 on a BMR 3.2.1 installation, use the patch procedure.

• Upgrades are done by installing the most recent product version CD available from TKG.

• Patches are done by installing the most recent software fixes available from TKG support

If bmrsetupserver and/or bmrsetupclient have not been run, upgrading does not occur: only normal installation procedures apply. Normally, patching can be done either before or after bmrsetupserver and/or bmrsetupclient are run. See the documentation that comes with each patch for possible exceptions.

Note: All BMR servers must be running the same version of BMR software.

Topics covered in this chapter:“Major Features” on page 210“Performing Upgrades” on page 211“Using the Patch Mechanism” on page 214

Bare Metal Restore User GuideUpgrades and the Patch Mechanism


210

Major Features

• Upgrades are done by installing a new version of the product, replacing the old.

• Patching tracks and logs patch application, and archives replaced files on a per-patch basis.

• Each patch comprehensively includes all previous patches for the versions to which they apply, including both server and client code, so only the most recent patch ever needs to be downloaded and installed for either servers or clients.

• Both upgrades and patches can have a minimum applicable product level; patching also has a maximum applicable product level. This prevents regressing to older versions of the product.

New Upgrade Procedure in 3.2.1


211

Performing Upgrades


In 3.2.1 the procedures for upgrading are different than in previous releases. For all platforms except Solaris, the procedures to upgrade will be the same as those to do an initial install. On Windows NT and Windows 2000 the initial screen is no longer displayed and the installation/upgrade goes directly to the correct setup.

Upgrading the BMR server on AIX:Note: You must be the root user to perform the BMR server upgrade tasks.

1. Insert the CD into the CD-ROM drive and enter the command smitty install_latest. The smitty software installation environment displays.

2. Enter the device name of the CD-ROM drive and press RETURN.

3. Press F4.

4. Select Bare Metal Restore for AIX Server

5. Press F7.

6. Press RETURN to confirm changes and exit to the main menu.

7. Press RETURN to execute the changes.


9. Press 'Y' to continue.

Warning: Performing an upgrade from 3.1.0, 3.1.1, or 3.2.0 to 3.2.1 marks all existing SRTs as “downlevel”. These SRTs need to be removed and rebuilt.

Upgrading the BMR client on AIX:Note: You must be the root user to perform the BMR client upgrade tasks.

1. Insert the CD into the CD-ROM drive and enter the command smitty install_latest. The smitty software installation environment displays.

2. Enter the device name of the CD-ROM drive and press RETURN.

3. Press F4.

4. Select Bare Metal Restore for AIX Client

5. Press F7.

6. Press RETURN to confirm changes and exit to the main menu.

7. Press RETURN to execute the changes.


9. Change the current directory to /usr/lpp/BareMetal



212

10. Run ./bmrsavecfg. Refer to “Configuring the AIX BMR Client” in the BMR User’s Guide.

11. Backup your client as usual.

Upgrading the BMR server on Solaris:Note: You must be the root user to perform the BMR client upgrade tasks.

1. Insert the CD into the CD-ROM drive and enter the command

pkgadd -a <pathname>/upgrade_admin -d <pathname> BMRserver


Upgrading the BMR client on Solaris:Note: You must be the root user to perform the BMR client upgrade tasks.

1. Insert the CD into the CD-ROM drive and enter the command:

pkgadd -a <pathname> /upgrade_admin -d <pathname> BMRclient

2. Change the current directory to /opt/BareMetal

3. Run ./bmrsavecfg Refer to “Configuring the Solaris BMR Client” in the BMR User's Guide.


Upgrading the BMR server on HP-UX:Note: You must be the root user to perform the BMR server upgrade tasks.

1. Make sure the following daemons are running:

a. pfs_mountd &

b. pfsd 6 &

This starts six separate instances of pfsd.rpc


mkdir /bmr_cdrom

and mount the CD-ROM:

pfs_mount -o unix <cdrom_device_path> /bmr_cdrom

3. Make sure you are in the root directory and execute:

swinstall -s /bmr_cdrom/hp BareMetal.server



and clean up:

rm -r /bmr_cdrom



213


Upgrading the BMR client on HP-UX:Note: You must be the root user to perform the BMR client upgrade tasks.

1. Make sure the following daemons are running:

• pfs_mountd &

• pfsd 6 &

This starts six separate instances of pfsd.rpc


mkdir /bmr_cdrom

and mount the CD-ROM:

pfs_mount -o unix <cdrom_device_path> /bmr_cdrom

3. Make sure you are in the root directory and execute:

swinstall -s /bmr_cdrom/hp BareMetal.client



and clean up:

rm -r /bmr_cdrom

5. Change the current directory to /opt/BareMetal

6. Run ./bmrsavecfg

7. Refer to “Configuring the HP-UX BMR Client” in the BMR User's Guide.


Upgrading the BMR client on Windows NT:Note: You must be logged in as administrator to perform the BMR client upgrade tasks.

1. Insert the CD into the CD-ROM drive. If autorun is not set, run setup.exe

• The process the exactly is same as a regular install. Refer to the Chapter 2.

• Make sure it is setup.exe in the NT directory of the CD-ROM.

Upgrading the BMR client on Windows 2000:Note: You must be logged in as administrator to perform the BMR client upgrade tasks.

1. Insert the CD into the CD-ROM drive. If autorun is not set, run setup.exe

• The process is exactly the same as a regular install. Refer to the Chapter 2.

• Make sure it is setup.exe in the 2000 directory of the CD-ROM.



214

Using the Patch Mechanism

UNIX Platforms

The Bare Metal Restore includes these files for the patch mechanism:

• bmrpatchserver

• patchserver.bmr

• bmrpatchclient

• patchclient.bmr

Each patch mechanism for the Unix platforms (AIX, HP-UX and Solaris) consists of:

• patch- TSM-<patchid>.tar

• a README file which enumerates and describes the defects addressed by the patch as well as instructions on applying the patch

To apply a patch the command specification is:

bmrpatchserver –f patch-<TSM>-<patchid>.tar

For example: To apply patch 3.1.1-002 on a server machine the command is:

bmrpatchserver -f patch-TSM-3.1.1-002.tar

or

bmrpatchclient –f patch-TSM-<patchid>.tar

Windows NT Platforms

The Bare Metal Restore includes this file for the patch mechanism:

• bmrpatch.exe

Patches for Windows NT clients consist of:


• README enumerates and describes the defects addressed by the patch as well as containing instructions on applying the patch

The executable which applies software patches to BMR client installations is bmrpatch.exe

patch- TSM-<patchid>.tar contains the replacement files in archive format.

Front-End Executable:

invokes this Executable:

which applies the software patches to the:

The replacement files in archive format are:

bmrpatchserver patchserver.bmr BMR server installation

patch-TSM-<patchid>.tar

bmrpatchclient patchclient.bmr BMR client installation

patch-TSM-<patchid>.tar

Download New Patches


215

To apply a patch to a Windows NT BMR client:


• Specify the bmrpatch command from a DOS prompt

• Double-click through the File Manager

2. Select the patch for execution from the GUI. On start-up a window displays which requests the patch archive file as input.

Windows 2000 Platforms

The Bare Metal Restore utility for patching the installed software is:

• bmrpatch.exe

Patches for Windows 2000 clients consist of:


• README enumerates and describes the defects addressed by the patch as well as containing instructions on applying the patch

The executable which applies software patches to BMR client installations is bmrpatch.exe

patch- TSM-<patchid>.tar contains the replacement files in archive format.

To apply a patch to a Windows 2000 BMR client:


• Specify the bmrpatch command from a DOS prompt

• Double-click through the File Manager

2. Select the patch for execution from the GUI. On start-up a window displays which requests the patch archive file as input.

Download New Patches

Contact TKG Support to obtain a URL for the relevant patch.

To find the version number of the patch use: “bmr -v”.

Installing Software Fixes

Server/Client Availability

The server and client software for BMR may be temporarily unavailable during the application of software patches.

Patch Identifiers



216

Patch IDs consist of the release ID concatenated with the specific patch identifier for that release:

patchid = <releaseid>-<patch>

The specific patch identifier is a three-digit numeric identifier. The patch ID for patch 002 for release 3.2.0 is:

3.2.0-002

Installed Patches

The list of installed patches is archived in:

<BMRdataDir>/patches/installed

Archive of Replaced Files

Replaced files are placed under the directory:

<BMRDIR>/<patchid>/<BMRDIR>

Warning: Do Not Tinker With Archived Files!


8 BMR Deployment PlanningThis chapter provides notes and considerations, procedures, and worksheets to expedite the installation of Bare Metal Restore (BMR) into your network environment. Use the planning worksheets included at the end of this chapter to help you with the process.

Topics covered in this chapter:“Placement of the BMR Servers” on page 218“Platform Specific Requirements of BMR File Servers” on page 219“General Considerations – All Platforms” on page 220

“Before Configuring the BMR Server” on page 222Worksheets:

“ESM Server Network Interface Worksheet Instruction” on page 223

“ESM Server Network Interface Worksheet” on page 224“Network Topology Worksheet Instruction” on page 225“Network Topology Worksheet” on page 226

“BMR Server Candidate Worksheet Instruction” on page 227“BMR Server Candidate Worksheet” on page 228“BMR File Server Worksheet Instruction” on page 229

“BMR File Server Worksheet” on page 230“Shared Resource Tree Worksheet Instruction” on page 231“Shared Resource Tree Worksheet” on page 232

Bare Metal Restore User GuideBMR Deployment Planning


218

Placement of the BMR Servers

Understanding the Tivoli Storage Manager

An understanding of the Tivoli Storage Manager environment is essential for the proper placement of the BMR server. The BMR server needs to know about all the Tivoli Storage Manager that are used by the BMR clients and all the TCP/IP addresses of the TSM servers, which these clients normally use to communicate with the TSM servers.

The BMR server must be able to communicate with every TSM 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 TSM server. This has two implications:

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

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

Network Topography of the Tivoli Storage Manager Environment

The BMR clients must be configured as TSM clients, and must be backed up to the TSM 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 TSM and BMR servers using this interface. This interface can be different from the one with which the client normally communicates to the TSM server. If your network configuration allows TCP/IP connectivity to the BMR and TSM servers through the client's network boot interface, then no changes to the TSM environment are needed. 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, determine the interface used during the boot. This interface is platform and hardware dependent. Use the following table 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”.

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.

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

Windows NT Ethernet

Windows 2000 Ethernet

Platform Specific Requirements of BMR File Servers


219

Selection of the BMR Server

This section explains the forms located in the back of this chapter. Start by making copies of the following forms.

• “ESM Server Network Interface Worksheet” on page 224

• “Network Topology Worksheet” on page 226

• “BMR Server Candidate Worksheet” on page 228

• “BMR File Server Worksheet” on page 230

• “Shared Resource Tree Worksheet” on page 232

BMR File Server and Boot Server Placement

BMR allows you to define as many BMR file servers or boot servers as you require.

Understanding the use of the Shared Resource Tree

The BMR file server holds the Shared Resource Trees (SRTs) for the BMR clients. The BMR boot server holds 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 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 TSM client software. The UNIX and Windows 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 must be run from the local drive, and only Windows can create all the file system types that may be required by any Windows client. Therefore it is necessary for BMR to install a Windows system onto a temporary partition on one of the disk drives of the NT BMR client. The Windows SRT exists on a UNIX BMR file server, and provides the installation images for Windows, as well as the TSM client executables, and any disk device drivers or network drivers required by the client that are not part of the normal Windows installation. The Windows BMR clients access the SRT from the UNIX system by using the SMB protocol and the SAMBA server.

The complete restoration process, from installing Windows into the temporary partition to the reformatting of the drives, re-creating the file systems, and the final cleanup and removal of the temporary Windows 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 (except Windows 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 (except for Windows SRTs).

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.



220

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)

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.

General Considerations – All Platforms• AIX is the only platform for which the BMR file and boot server components can reside on different

machines. The BMR boot server requires space in /tftpboot for the clients’ boot images. Boot images are relatively small, and one boot image can be used for many clients. There can be circumstances where separating the boot and file servers is beneficial, but for most instances, the BMR file and boot server 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 must be uncommented and inetd needs to be refreshed for the BMR boot server to function.

• The BMR file server requires 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.

• Windows 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 “bmrsrt” from an external SAMBA share can be configured so the files shared are writable by the BMR server.

AIX BMR File Server Selection

You 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 depends on network connectivity speeds and NFS access considerations. For example, you can 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 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 server Selection

Each Network Segment IP in the BMR File Server Worksheet must have a HP-UX file server/boot server. The HP-

General Considerations – All Platforms


221

UX BMR file Severs must also be BMR boot servers. You 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 11.00 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.

Solaris BMR File Server Selection

Each 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:

• The Solaris BMR boot/file server does not need to be available until it is required. When needed, a Solaris boot/file server can be installed and an SRT created. This process can occur after the client has failed and needs to be restored.

• 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.

Windows NT File Server Selections

A Windows NT client can use any one of AIX, HP-UX, or Solaris systems as a file server. However, the following considerations apply:

• The File server must have SAMBA configured, as explained in the later sections of this document.

• This File server must be reachable by the BMR client (at restore time) using the same interface that is used to reach the BMR server. This restriction stems from the fact that only one interface can be brought up by BMR client at restore time.

Windows 2000 File Server Selections

A Windows 2000 client can use any one of AIX, HP-UX, or Solaris systems as a file server. However, the following considerations apply:

• The File server must have SAMBA configured, as explained in the later sections of this document.

• This File server must be reachable by the BMR client (at restore time) using the same interface that is used to reach the BMR server. This restriction stems from the fact that only one interface can be brought up by BMR client at restore time.

Third Party Disk Device Driver and Volume Manager Information

BMR 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 apply to the BMR clients served by this SRT.



222

Before Configuring the BMR Server

Server screen of the BMR web GUI: this writes a new stanza in the /var/bmr/bin/dsm.sys file used at Prepare to Restore time.

After the BMR server is initially configured, all of the IP addresses for each TSM server must added to the BMR database. Additional IP addresses can be added by bringing up the Web GUI, entering the TSM servers screen, and then the TSM server. Use the SAVE button to add the IP addresses to the TSM server. When a BMR client is 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 TSM server, and tells the BMR server that it is using the TSM server with this IP address. If the BMR server does not know of a TSM server with this address, the client will fail registration verification and cannot be configured.

Worksheets

The following worksheets and worksheet instructions are designed to help you plan your installation:

Worksheets


223

ESM Server Network Interface Worksheet Instruction

For each TSM server, complete a separate TSM Server Network Interface Worksheet. For each interface on the TSM server, fill out one row of the worksheet table. The worksheet follows the description below.

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 TSM server's network interface.

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

• 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.



224

ESM Server Network Interface Worksheet

TSM Server Name:

TSM Server Software Version and Release:

Network Interface Name

Network Interface Address

Network Segment IP

Worksheets


225

Network Topology Worksheet Instruction

Use this worksheet to describe the network topology of the TSM backup network. The worksheet follows the description below.

• 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 Windows NT clients, include the network interface's network segment which will be used during a BMR floppy boot.

• The Gateway to ESM Server column is the IP address of a router in this segment that can be used to reach the TSM server. If the TSM server has a presence on this network (if there is an Network Segment IP match for this segment in the TSM 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.



226

Network Topology Worksheet

Page ___ of ____

Network Segment IP

Gateway to TSM Server

Gateways to other Networks

Worksheets


227

BMR Server Candidate Worksheet Instruction

Use 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 TSM 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, or 8 and HP-UX 10.20 or 11.00.

2. TSM client software installed:

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

b. A TSM administrative client must be installed.

c. BMR server candidate must have permission to retrieve files from the TSM server for any UNIX BMR cli-ent.

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

Use the TSM 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:

• TSM Servers Connectivity column: Use schism Server Network Interface Worksheet(s). If the candidate is able to ping at least one of the Network Interface Address entries for every TSM server, place a check mark in the TSM 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 TSM client software and Version in the blanks provided.



228

BMR Server Candidate Worksheet

Candidate TSM Servers Connectivity Client Connectivity

Selected BMR Server

Operating System and Version:

TSM Client software and Version:

AIX: uname -mSolaris: hostidHP: uname -i

Worksheets


229

BMR File Server Worksheet Instruction

Make 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. If a BMR client has multiple network interfaces, count it only once. If a BMR client has multiple network interfaces, choose an interface from which it can network boot to 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.



230

BMR File Server Worksheet

Page ___ of ____

Network Segment IP

Link Speed

AIX Solaris HP-UX Windows

4.1 4.2 4.3 5.1 2.6 7 8 10.20 11.00 NT 2000

Worksheets


231

Shared Resource Tree Worksheet Instruction

Make copies of the BMR Shared Resource Tree Worksheet. 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 needed to create the SRT. This corresponds to the OS level used by the BMR clients that use this SRT.

The Required TSM Client Release and Version is the Version of the TSM client software to 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.



232

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 Level

Require ESM Client Release and Version

Third Part Disk Device Driver and Volume Manager Information

Third Party Software or Drivers Used by BMR Clients

VERITAS Volume Manager

Version:

VERITAS File System Version:

OEM Network Drivers

OEM Disk Drivers

Other

Location of Images for SRT Creation

OS

TSM Client

Third Party SoftwareNetwork Driver

Disk Drivers

Other:

Other:

NT/2000License Key


Appendix A: Command Reference

These topics are covered in this chapter:“bmrconfig” on page 234“bmrcreatesrt” on page 238

“bmrestore” on page 240“bmrmkcdimage” on page 242“lm_keyins” on page 243

“bmrmap” on page 244s

Bare Metal Restore User Guide


234

NAME

bmrconfig Execute BMR configuration actions.

SYNOPSISbmrconfig [-h bmrserver [-p port]] -o {define|query|change|create|allocate|deallo-cate|verify|delete|destroy|push|pull} -r {BI|SRT|BMR|ESM|CL|MSG|LOG|LIC|CLC|INFO} resourcename args|[key=value]...

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

DESCRIPTION

Bare 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 procedure.

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.

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 to specify. For example, all databaseoperations (define, query, and change) require the BMR server to be specified with the -h option.All operations on the SRT (Shared Resource Tree) resource require the FS and all operations on theBI (boot Image) resource require the 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 –r determines the method to execute.

There are two types of operations:1) operations that manipulate database objects and 2) operations that perform actions based on the data base values.

The operations that manipulate database objects are:

• define - creates a new file in a directory (row in a table)

• change - updates the attributes of one file (row)

• query - returns the attributes of one or more files (rows)

• delete - marks a file as deleted (can not be queried or changed)

• undelete - reverses delete

• purge - removes a file marked for delete. Can not be undeleted.

The operations that perform actions are:

Command Reference


235

• create - creates a resource

• destroy - destroys the resource

• allocate - allocates the resource

• deallocate - deallocates the resource

• verify - verifies the resource

• push - send a file to the BMR main server

• pull - retrieve a file from the BMR main server.

Not all operations are allowed with all resources. The following operations and resources are allowed:

1. Operations on the BI resource.

If the -h <host> is specified then <host> is assumed to be the boot server (BS) associated with the specified arguments. If -p <port> is specified 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>

2. Operations on the SRT resource:

If the -h <host> is specified then <host> is assumed to be the File server (FS) associated with the specified arguments. If -p <port> is specified 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 the bcreatesrt 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 BMR server (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>



236

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

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

4. Operations on the ESM resource:

If the -h <host> is specified, then <host> is assumed to be the BMR server (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 BMR server (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>

ARGUMENTS

Each operation/resource combination can require arguments as shown above. The definition of these arguments are listed as follows:

<define_args> Arguments for the define operation are one or more name=value constructs as in, “name=value” [“name=value” ...]

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

<query_args> The arguments to the query operation are one or more names as in, “name” [“name” ...]

EXAMPLES

1. Define a boot image:

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

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

bmrconfig -o query -r CL demo,adsmsvr CLipaddr CLnetmask CLmacaddr

This command returns:

CLipaddr=198.3.134.34

CLnetmask=255.255.254.0

unset CLmacaddr

3. 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

Command Reference


237

4. Allocate a BI named, aix432, to the client, node,adsm:

bmrconfig -o allocate -r BI aix432 node,adsm



238

NAME

bmrcreatesrt Create a shared resource tree.

SYNOPSIS

bmrcreatesrt [-a nt]

DESCRIPTION

The bmrcreatesrt command is run on the BMR File server. bmrcreatesrt creates a Shared Resource Tree (SRT) for BMR clients at a particular operating system (OS) level and ESM client 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 level and ESM client 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.

The following OS levels are supported for AIX:

• 4.1.x

• 4.2.x

• 4.3.x

• 5.1

The following OS levels are supported for Solaris:

• 2.6

• 7

• 8

The following OS levels are supported for HP-UX:

• 10.20

• 11.00

• 11.11

The following OS levels are supported for Windows NT:

• NT 4.0 server

• NT 4.0 enterprise server

This command is not required for Windows 2000 clients.

bmrcreatesrt 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:

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.

Command Reference


239

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.

SRTtype The media type of this SRT

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 Windows NT only.



240

NAME

bmrestore prepares a client for restoration

SYNOPSIS for bmrrestore for TSM — [-l] [-r] [-q] [-A] [-d|-D] [-P <password> [-R -W <password>]] [-c <file-name>][-S “file”|”server”] [-a <ip address>][-p <port>][-n <NIC driver>] clientname

DESCRIPTION

The bmrrestore command prepares a client for restoration. The command is run on the BMR server to restore any BMR client. The bmrrestore command allocates the assigned SRT (Shared Resource Tree) and BI (boot Image) to the specified client.

The following attributes must be in the database entry for the specified client:

BIname required

SRTname required

ESMgateway optional, depending on network

CLconsole required for AIX

CLlang required for AIX

CLhostname required

CLipaddr required

CLnetmask required

CLarchitecture required

CLos required

CLoslevel required

CLprocessors required for AIX

CLnic required

USAGE: bmrrestore Options ... Clientname

OPTIONS:

-P <TSM password> (e.g. secret)

If the ESM node password is not specified with the -P option

then bmrrestore will prompt for this password.

-R Reset TSM password. This requires -W.

-W <TSM admin password> (e.g. admin)

-l Turn logging on.

Logs the entire restoration process. The log is created in $BMRlogdir/<clientname>. BMRlogdir is defined in /var/bmr/etc/server_env.

-r Restore non-rootvg VGs

-q use quick format on NT clients

-A Perform an authoritative restore of Active Directory

-d prepare for dissimilar restore mapping

Command Reference


241

-D generate dissimilar restore files

-c <Backup Set File Name>

-S “file”|”server” location of TSM backup set

-a <Alternate TSM ip address>

-p <Alternate TSM port>

-n <Alternate NIC driver>-n <Alternate NIC driver>



242

NAME

bmrmkcdimage creates a raw cd image of an SRT

SYNOPSIS

bmrmkcdimage

DESCRIPTION

bmrmkcdimage asks the user a series questions for things like the source SRT name, name for the new SRT and BI, pathname of a directory with sufficient space, etc., and then creates a raw cd image of the given SRT. The resulting image, when burned onto a CD, makes the CD bootable. A BMR client can be restored booting off of such a CD.

SEE ALSO

bmrcreatesrt, and BMR user guide.

Command Reference


243

NAME

lm_keyins installs a new license key on the BMR server

SYNOPSIS

lm_keyins -k key [-g]

DESCRIPTION

The lm_keyins command can be used to install or upgrade a license key on the BMR server. During initial server setup, this command will be run automatically if a license key is provided to the setup script. License keys can be obtained from TKG Support for either purchased software or evaluation copies. License keys can only be used to generate a new license database within 60 days of it's date of issue.

OPTIONS

-k key The license key obtained from The Kernel Group.

-g Generate a new license database, or repair an existing database.

Repairing a database is required in cases where the database file has been moved around or copied around, and the BMR server complains about it. Repairing a license database does not result in either adding or deleting clients from the database, only the time stamps in the database are fixed.



244

NAME

bmrmap Manipulates client configuration for Dissimilar Disk Restore

SYNOPSIS

bmrmap [-R] [-n|-N] [-t|-T] [-o|-O name] [-v|-V name] clientname [change operation flags]

DESCRIPTION

The bmrmap command is used to map a UNIX client restore onto dissimilar disks. This mapping can be performed either from the main BMR GUI or with the bmrmap command.

After selecting the dissimilar disk restore option at Prepare to Restore time and network booting the UNIX client, a discovery agent is automatically run to determine the hardware on the client. This discovered information is passed back to the BMR server, and is made available to this bmrmap command. The client will suspend restoration until the BMR server passes back the remapped restore procedure.

The bmrmap command can be run as many times as needed to arrive at the desired mapping. At which time, the bmrrestore -D command should be issued to invoke the dissimilar restore procedure.

The bmrrestore command -D automatically makes this new restore procedure available to the waiting client.

OPTIONS

-R reset client configuration information to original

-n discovered device information for client

-N list discovered device information for client in terse format

-t show volume groups or disk layout for client

-T show volume groups or disk layout for client in terse format

-o display original volume group or disk data

-O display original volume group data in terse format

-V perform operation on volume_group or disk for client terse format

-v perform operation on volume_group or disk for client

Change Operation Flags:

-s save client configuration data

Important! Change operations only take effect when -s option is specified.

-g show configuration data in pipe delimited format (automatically set with -O or -V)

-d delete the named object specified with the above -v option

-r sets remove flag to be used in conjunction with the following:

Command Reference


245

-l logical volume

-f file system

-h hard drive name

-c change hard drive

AIX: “hdisk0=hdisk5|00-00-06,1|1000”

HP: “dev/dsk/c0t5d0=/dev/dsk/c0t6d0”

Sol: “c0t0d0=c0t1d0”

-a add hard drive.

AIX: “hdisk3|00-00-06,1|500”

HP “/dev/dsk/c0t3d1|c0t2d1|9000”

EXAMPLES

1. To display a list of current volume groups for myclient:

bmrmap -t myclient

2. To display discovered disk info for myclient:

bmrmap -n myclient

3. To display configuration of myvg on myclient:

bmrmap -v myvg myclient

4. To display original configuration of myvg on myclient:

bmrmap -o myvg myclient

5. To display configuration of ssavg on myclient in “|” format:

bmrmap -V ssavg myclient

6. To display original configuration of ssavg on myclient in “|” format:

bmrmap -O ssavg myclient

7. To reset myclient to original configuration:

bmrmap -R myclient

8. To delete oldvg from myclient's configuration:

bmrmap -v oldvg myclient -d

9. To remove logical volume testlv from volume group extravg for myclient's confg:

bmrmap -v extravg myclient -r -l testlv

10. To remove file system ncfs from volume group dcvg for myclient's config:

bmrmap -v dcvg myclient -r -f ncfs

11. To change harddrive hdisk0 to hdisk3 on myclient's rootvg:

AIX: bmrmap -v rootvg -c “hdisk0=hdisk3|00-03-01,0|1000”

HP: bmrmap -v rootvg -c “dev/dsk/c0t5d0=/dev/dsk/c0t6d0”

Sol: bmrmap -v rootvg -c “c0t0d0=c0t1d0”

12. To add harddrive hdisk11 to myclient's dbvg for:



246

bmrmap -v dbvg myclient -a “hdisk11|00-11-00,0|750”

13. Make a change to client configuration and get ready for restore:

bmrmap -v dbvg myclient -r -f /weblog -s

14. To remove hard drive hdisk2 from myclient's slevg:

bmrmap -v slevg myclient -r -h hdisk2

SEE ALSO

bmrrestore


Appendix B: Uninstall BMR Servers

If you need to uninstall BMR (for example, if you installed BMR for evaluation and do not have a license key) use the following procedures.

1. Edit /etc/inittab. Remove the 2 BMR related entries.

bhd:3:once:/opt/BareMetal/httpd/bin/httpd -d /var/bmr/httpd

1>> /var/bmr/httpd/logs/error_log 2>&1

bmr:3:respawn:/opt/BareMetal/rc.bmr 1> /var/bmr/log/bmrd.out

2> /var/bmr/log/bmrd.err

The first is the BMR daemon, the second is the httpd daemon.

2. Kill the bmr related daemons: Do an ps -ef | grep bmr.

bmradmin 300 299 0 03:02:08 ? 0:00/opt/BareMetal/httpd/bin/httpd -d /var/bmr/httpd

root 292 1 0 03:02:03 ? 0:00 /opt/BareMetal/sol/bmrd-p 8362

root 299 1 0 03:02:07 ? 0:00 /opt/BareMetal/httpd/bin/httpd -d/var/bmr/httpd

bmradmin 301 299 0 03:02:08 ? 0:00/opt/BareMetal/httpd/bin/httpd -d /var/bmr/httpd

Use kill -9 <PIDnumber> to kill the daemons.

3. If you have installed SAMBA, you should also kill the nmbd daemon: do an ps -ef | grep nmb. Use kill -9 <samba's PID number> to kill the daemon

4. Check with mount if any file system you are going to remove are not exported.

5. Remove files:

For AIX:

cd /var

rm -R bmr (be very careful with removal, check your command line before pressing enter)

cd /export/srt

rm -R * (be very careful with removal, check your command line before pressing enter)

use smitty to remove all BMRserver filesets.

cd /usr/local

ls (you should see a samba dir.)

rm -R samba

For Solaris:

cd /var



248


cd /export/srt


use pkgrm BMRserver to remove the BMR filesets

cd /opt

ls (list: you should see a samba dir.)

do a rm -R samba

For HP-UX:

cd /var


cd /export/srt


use SAM to remove the BMR filesets

cd /opt

ll (list: you should see a samba dir.)

rm -R samba

Future releases of BMR won't need this removal anymore. TKG is working to have an automated upgrade of the install & setup procedure.

Glossary


249

Glossary

aAIX: A version of UNIX produced by IBM.

bBMR Boot Server: The boot server provides the boot image to the client when it performs a network boot prior to restoration.

BMR client: The term BMR client refers to the machine on which the BMR client software is installed.

BMR File Server: The file server makes the necessary filesystems available to the client at restore time using NFS or SMB.

BMR server: The term BMR server refers to the server machine on which the BMR server software resides.

Boot Image (BI, network BI) see Media Boot

bootp: Short for Bootstrap Protocol. An Internet protocol that enables a BMR client to discover its own IP address, the IP address of a BOOTP server on a network, and a file to be loaded into memory to boot the machine.

bootparam: An AIX and HP-UX protocol used for network booting.

cchecksum: An error-detection scheme where a block of data is accompanied by a computed value based on the number of set bits in the message.

ddaemon: A process that runs in the background and performs a specified operation at a specified time or in response to certain events. Windows calls a daemon a system agent or service.

DHCP: A protocol for assigning dynamic IP addresses to devices on a network.

eESM server: The Enterprise Storage Management server used for normal backups and restores. This is your Tivoli Storage Manager (TSM) server.

ethernet: A local-area network (LAN) protocol

fHP-UX: A version of UNIX produced by Hewlett-Packard.

iIP Address: An unique number identifying computer or device on a TCP/IP network. The format of an IP address is written as four numbers separated by periods. Each number can be zero to 255.

mMAC Address (Media Access Control): A hardware address that uniquely identifies each node of a network.

mount: To make a file system available.

Media Boot: Media Boot refers to the process of using a CD-ROM disk that contains the SRT so that the client does not need network access to the SRT — it is on the CD.

• The UNIX Media Boot CD also contain boot Image.

• The Windows Media Boot CD require a boot floppy that has been prepared with the Media Boot option.


250 Bare Metal Restore User Guide

nNDIS: A Windows device driver interface that enables a single NIC to support one or more network protocols.

NFS: NFS provides access to shared files through an interface called the Virtual File System (VFS) that runs on top of TCP/IP.

sSAMBA server: The BMR file server running the SMB code.

SAMBA: Short for Server Message Block (SMB). The utility that allows UNIX to share servers file systems with Windows NT.

System partition A system partition is a special area of the fixed disk containing configuration,

diagnostic, and maintenance utilities. These utilities are more readily available and run faster when installed on the system partition.

Shared Resource Tree (SRT): The SRT provides the resources needed to build the boot images.

Solaris: A version of UNIX produced by Sun Microsystems.

tToken Ring: A local-area network (LAN) protocol.

wWindows NT: An operating system by Microsoft intended for business workstations and servers.


Technical Support Contact Information

For technical support with Bare Metal Restore, contact The Kernel Group:

email: [email protected]

U.S. toll free: 1-866-435-7854

Outside U.S.: 01-512-433-3311

Fax: 1-512-433-3200

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



252

253

The Kernel Group, Inc. Version 3.2.1

Index

A

Active Directory Restore 172

Add Driver

Windows 2000 82

Windows NT 82

B

Backup Sets

Windows NT 184

Backup, make a complete 7

BMR Boot Server Placement 219

BMR File Server Placement 218–219

BMR License 56

BMR Log File 55

BMR server requirements 219

bmrconfig 234

bmrcreatesrt 238

bmrmap 244

bmrmkcdimage 242

bmrrestore 240

Boot Floppy

Create 92

Windows 2000 107

Custom Media Boot 126Custom Network Boot 115Generic 108

Windows NT 92

Boot Image

configure 86

create 84

delete 88

modify 88

Boot Server Placement 219

C

Client Restoration 138

Client Restore

AIX 138

UNIX 153

Windows 2000 148, 159

Command Reference

bmrconfig 234

bmrcreatesrt 238

bmrmap 244

bmrmkcdimage 242

bmrrestore 240

lm_keyins 243

mbrmkcdimage 242

Configure the BMR Client

AIX 34

HP-UX 40

Solaris 37

using GUI 89

Windows 2000 43

Windows NT 41

Configure the BMR Server

AIX 32

HP-UX 38

Solaris 35

Configuring a Shared Resource Tree 80

Creating a Shared Resource Tree

AIX 58

HP-UX 62

Windows 2000 65

Windows NT 63

Creating an SRT

CD

AIX 69

HP-UX 72

Solaris 68

Windows 2000 75

Windows NT 72

D

DDR, see Dissimilar Disk Restore

Device driver 221

Dissimilar Disk Restore 6, 176

UNIX clients 176

Windows clients 180

F

File Server Placement 219

File server selection

AIX 220

HP-UX 220

Solaris 221

Windows 2000 221

Windows NT 221

G

GUI

Administrative 51

Graphical User Interface 49

I

Installation

AIX 15

HP-UX 20

Solaris 18

Windows 2000 26

Windows NT 22

Installing the BMR Client

AIX 16

Using installp 17

HP-UX

Using swinstall 21

Solaris 19

Windows 2000 27

Windows NT 22

Installing the BMR Server

AIX

Using installp 16

Using smitty 15–16

HP-UX

Using swinstall 20

Solaris 18

Using pkgadd 18

L

License Key

AIX 34

HP-UX 40

Solaris 37

License, BMR 56

lm_keyins 243

Log file 55

254

The Kernel Group, Inc. Version 3.2.1

M

Media Boot 6, 68

AIX 69

Creating a CD 68

Adaptec Easy CD Creator 68

GearPro 69

Nero 69

Sony CD Extreme 68

HP-UX 72

Solaris 70

Windows 2000 75

Windows NT 72

N

Network Topology 218

P

Partition, special (Win NT/2000) 106, 157

Patch 6, 209, 214

Download 215

Install 215

UNIX (AIX, Solaris, HP-UX) 214

Windows 2000 215

Windows NT 214

Placement of the BMR Servers 218

R

Restoration process 8

Restore

Initiate

AIX 153

Solaris client 156

using Media Boot 187

Windows 2000 client 159

Windows NT client 157

Initiate Client 153

Prepare to

AIX client 138

HP-UX client 144

Solaris client 143

Windows 2000 client 148

Windows NTclient 145

Restore Time on HP 207

S

SAMBA configuration file 33, 36, 39

Server

Adding 51

BMR 4

boot 4

Configuration, view via GUI 54

Configure via GUI 53

Environment 218

file 4

Install

Using installp 16

Using smitty 16

Server requirements 219

Service Packs

Windows NT 189

Shared Resource Tree (SRT)

add network interface card (NIC) 82

configuring 80

Creating

Windows 2000 65

Windows NT 63

delete 82

modify 72, 80

understanding 219

Special partition 8, 101, 106, 123, 133

SRT, see Shared Resource Tree

Support, Contact Info 251

System Requirements

AIX 15

HP-UX 20

Solaris 18

Windows 2000 Client 26

Windows NT Client 22

T

Technical Support 251

Technical Support info 251

TroubleShoot

Add correct MSD driver 198

BMR Server Setup 206

Long Restore Times on HP-UX 207

No System Objects 202

Solaris 2.6 on boot 193

Unlabeled disks 203

VFS without VVM 201

U

Upgrade 6, 209, 211

BMR client on AIX 211

BMR client on HP-UX 213

BMR client on Solaris 212

BMR client on Windows 2000 213

BMR client on Windows NT 213

BMR server on AIX 211

BMR server on HP-UX 212

BMR server on Solaris 212

V

Vendor partition (see Special partition) 101

Volume Managers 221

W

Worksheets

BMR File Server 230

BMR Server Candidate 228

ESM Server Network Interface 224

Network Topology 226

Server Network Interface 223

Shared Resource Tree 232

Documents

Bare Metal Restore for Tivoli Storage Manager User Guideorigin-symwisedownload.symantec.com/resources/sites/SYMWISE/... · Bare Metal Restore for Tivoli Storage Manager User Guide