VERITAS Bare Metal Restore 4.6 for VERITAS NetBackup

Transcription

1 VERITAS Bare Metal Restore 4.6 for VERITAS NetBackup System Administrator s Guide for UNIX and Windows N09870C

2 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. VERITAS Copyright Copyright VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, VERITAS Bare Metal Restore, and all other VERITAS product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation. VERITAS, the VERITAS Logo, and Bare Metal Restore Reg. U.S. Pat. & Tm. Off. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies. VERITAS Software Corporation 350 Ellis Street Mountain View, CA USA Phone Fax

3 Contents Preface xv Audience xvi Organization xvi Related Documents xvii Bare Metal Restore Documents xvii NetBackup Documents xvii System Administrator s Guides - Basic Product xvii User s Guides xviii Troubleshooting Guides xviii VERITAS Documentation on the Support Web Site xviii Conventions xix Type Style xix Notes and Cautions xix Key Combinations xx Command Usage xx Getting Help xx Chapter 1. Introduction Terminology Technical Overview How Does a Bare Metal Restore Work? How Do I Set Up BMR Restore Capabilities? What Capabilities Does the BMR Software Provide? BMR Graphical User Interface iii

4 Launching the BMR GUI BMR GUI Functions Clients BMR Servers NetBackup Servers Shared Resource Trees Boot Images Log File Licensing Help Bare Metal Restore Components BMR Main Server BMR Boot Server BMR File Server BMR Client NetBackup Server Deployment Planning VERITAS NetBackup Server Considerations Planning the BMR Installation BMR Main Server Considerations Identifying BMR Clients and SRT Requirements BMR File Server Requirements and Considerations BMR File Server Selection BMR and NetBackup Requirements and Limitations Requirements Limitations The Importance of Making a Complete Backup Chapter 2. BMR Server Installation and Configuration General Installation Requirements iv VERITAS Bare Metal Restore System Administrator s Guide

5 The altnames Directory Port Usage for BMR Client/Server Communication Upgrading from Bare Metal Restore Deletions Resulting from Upgrade Installation Upgrade Installation Procedure Installing BMR Servers HP-UX Solaris AIX Configuring BMR Servers Running the bmrsetupserver program Bare Metal Restore Server Configuration Example Configuring SAMBA on the BMR File Server Enabling Remote Access to the BMR GUI Adding a License Key Adding and Configuring NetBackup Servers Chapter 3. BMR Client Installation and Configuration General Client Installation Requirements General Requirements for BMR Installation on Clients Port Usage for BMR Client/Server Communication Upgrading from Bare Metal Restore Deletions Resulting from Upgrade Installation Upgrade Installation Procedure Installing BMR Clients HP-UX Solaris AIX Windows Configuring BMR Clients Contents v

6 Configuring UNIX Clients Configuring Windows Clients Backing Up BMR Clients Chapter 4. Creating a Shared Resource Tree (SRT) Understanding the Shared Resource Tree SRT Components Third Party Disk Device Driver and Volume Manager Network SRTs vs. CD-Based SRTs BMR File Server SRT Considerations The /var/bmr/etc/exports File bmrcreatesrt Default Path Edit the /var/bmr/etc/exports File Creating a Shared Resource Tree Creating an SRT for AIX Creating an SRT for Solaris Version Considerations Installing Additional VERITAS Software into a Solaris SRT Creating an SRT for HP-UX Creating an SRT for Windows Creating a CD-Based SRT CD Creation Considerations Creating a CD-based SRT for AIX Creating a CD-based SRT for Solaris Creating a CD-based SRT for HP-UX Creating a CD-based SRT for Windows Configuring SRTs from the BMR GUI Modifying a Shared Resource Tree Deleting a Shared Resource Tree Chapter 5. Creating Boot Images and Boot Media vi VERITAS Bare Metal Restore System Administrator s Guide

7 Understanding Boot Images Creating a Boot Image for a UNIX Client Configuring Boot Images from the BMR GUI Creating Boot Images (Floppies) for Windows Clients Generic Boot Floppy with Network-Based SRTs Custom Boot Floppy with Network-Based SRTs Custom Boot Floppy with CD-Based SRTs Running bmracceptfi on the BMR Main Server Chapter 6. Restoring a BMR Client Modifying Client Configuration BMR UNIX Clients BMR Windows Clients Preparing to Restore a Client BMR UNIX Clients BMR Windows Clients Restoring a Client Restoring UNIX BMR Clients Using Network Boot AIX Network Boot Solaris Network Boot HP-UX Network Boot Restoring UNIX BMR Clients Using Media Boot AIX Media Boot Solaris Media Boot HP-UX Media Boot Restoring Windows Clients Network Restore With Generic Boot Floppy Network Restore with Custom Boot Floppy Media Restore with Custom Boot Floppy Chapter 7. Dissimilar System Restore for Windows Clients Contents vii

8 When to Use Dissimilar System Restore Understanding the Dissimilar System Restore Process Saving the Source Client Configuration Determining Hardware Differences Adding New Drivers Adding Individual Drivers Copying Another Client s Configuration Adding a Service Pack Restoring the Client First Logon Performing a Dissimilar System Restore DSR Restore Procedure: Adding New Drivers DSR Restore Procedure: Copying Another Client s Configuration Procedures Troubleshooting Common Problems Different Service Pack Level Warning Duplicate IP Addresses on Network MAC Address Does Not Match Chapter 8. Advanced Features Dissimilar Disk Restore (DDR) When to Use Dissimilar Disk Restore Understanding the Dissimilar Disk Restore Process Dissimilar Disk Restore for UNIX Clients Dissimilar Disk Restore for Windows Clients Storage Area Network (SAN) Co-Existence Dissimilar System Restore Considerations Dissimilar Disk Restore on UNIX Considerations SAN Support Matrix Manual Recovery of Other Volumes viii VERITAS Bare Metal Restore System Administrator s Guide

9 Other Requirements Known Issues with SAN Co-Existence: Point in Time Restore When to Use Point in Time Restore Understanding the Point in Time Restore Process Service Packs for Windows Clients Including a Service Pack During Client Setup Creating a Service Pack Multiple Network Interface (Multihomed) Considerations General Constraints Clients with Multiple Network Interface Cards (NICs) UNIX Clients Windows Client Configuration Client Configuration Using Gateways Restoring NetBackup Media Servers (Solaris Only) Understanding NetBackup Catalogs and Catalog Backups Catalog Backups: NetBackup Cached Catalogs: BMR Creating a Media Server Shared Resource Tree Performing a Media Server Restore Selecting the Catalog Backup during the Prepare to Restore Process Restore Time Actions Restrictions and Limitations Restoring the BMR Server Chapter 9. Tips and Troubleshooting Tips Finding the Correct MSD Driver Identifying the Vendor Partition During a Client Restore BMR Requirements Contents ix

10 Recovering from Erroneous Input While Working with Generic Boot Floppies (Windows) Removing BMR Servers AIX LED Progress Codes Troubleshooting Solaris 2.6 Causing Panic on Net or CD-ROM Boot Symptoms Problem Solutions AIX Boot Failure Problem Solution Problems Booting from CD Long Restore Times on HP-UX Symptom Problem Solution Windows Media Boot Failure on Client with Multiple CD-ROM Drives Symptom Problem Solution Restore Failure of Windows BMR Clients with Multiple Identical NIC Cards Symptom Problem Solution The bmrd Daemon Does Not Start During bmrsetupserver Symptom Problem Solution Networking Problems at DOS Phase during Windows Client Restores x VERITAS Bare Metal Restore System Administrator s Guide

11 Failed Restores after Changing the NetBackup Server Information Symptom Problem Solution Appendix A. Upgrades and the Patch Mechanism Features Upgrading from Bare Metal Restore Space Requirements for Upgrading BMR Main Servers Deletions Resulting from Upgrade Installation Upgrade Installation Procedure Support for BMR 4.5 Clients Migrated Client Configurations Restoring a Client Using a Migrated Configuration Upgrading Migrated Clients to Using the Patch Mechanism UNIX Platforms Determining the Current Patch Level Applying a Patch Windows NT and Windows 2000 Platforms Determine the Current Patch Level Apply a Patch Appendix B. Deployment Planning Resources Specifications Sizing and Space Requirements Supported Operating Systems for BMR Servers and Clients Supported File Systems and Volume Managers Supported NetBackup Versions NetBackup Client 3.4 GA Cannot Be Used When Building SRTs Supported Hardware Components and Architectures Contents xi

12 Worksheets NetBackup Server Network Interface Worksheet Instruction NetBackup Server Network Interface Worksheet Network Topology Worksheet Instruction Network Topology Worksheet BMR Server Candidate Worksheet Instruction BMR Server Candidate Worksheet BMR File Server Worksheet Instruction BMR File Server Worksheet Shared Resource Tree Worksheet Instruction Shared Resource Tree Worksheet Dissimilar System Restore Worksheet Instruction Dissimilar System Restore Worksheet Appendix C. BMR Command Reference bmracceptfi bmrconfig bmrcreatesrt bmreditcfg bmrmkcdimage bmrnewcfg bmrrestore bmrsavecfg For UNIX platforms For Windows platforms bmrsetupclient For UNIX platforms For Windows Platforms: lm_keyins Glossary xii VERITAS Bare Metal Restore System Administrator s Guide

13 Index Contents xiii

14 xiv VERITAS Bare Metal Restore System Administrator s Guide

15 Preface This guide describes how to install, configure and use VERITAS Bare Metal Restore for VERITAS NetBackup. In this guide, VERITAS Bare Metal Restore is referred to as Bare Metal Restore or BMR. This document is the same as bmr-admin-guide.pdf distributed with the Bare Metal Restore software. xv

16 Audience Audience This guide is intended for the BMR/NetBackup system administrator responsible for configuring BMR/NetBackup. A system administrator is defined as a person with system administrator privileges and responsibilities. This guide assumes: A basic understanding of system administration. A working understanding of BMR client and server platforms. A working understanding of the NetBackup client and server software. Organization This guide is organized as follows: The Introduction provides an overview of the product s capabilities, and includes a description of the user interface and deployment planning information. The Installation chapters explain how to install and configure BMR on servers and clients. Creating a Shared Resource Tree (SRT) explains shared resource trees and gives procedures for creating network and CD- based SRTs. Creating Boot Images and Boot Media explains the process for creating boot images. Restoring a BMR Client gives instructions for performing the actual client restore, in the event of a system failure. Dissimilar System Restore for Windows Clients explains the procedure for restoring a Windows client to a system with a different hardware configuration than the original source client. Advanced Features provides explanations and instructions for using advanced BMR features. Tips and Troubleshooting gives tips for ease of use as well as symptoms, problems, and solutions for BMR troubleshooting. Appendix A, Upgrades and the Patch Mechanism, describes considerations for upgrading and applying patches to Bare Metal Restore. Appendix B, Deployment Planning Resources, provides system requirements tables and deployment planning worksheets to help plan your BMR installation. xvi VERITAS Bare Metal Restore System Administrator s Guide

17 Related Documents Appendix C, BMR Command Reference, provides explanations of the commands included with BMR. The Glossary provides definitions for terms that may be unfamiliar. Related Documents Bare Metal Restore Documents The CD-ROM for each Bare Metal Restore product has a copy of the related manuals in Adobe Portable Document Format (PDF). The PDF files are either in the root directory or the Doc directory on the CD-ROM. Note To view the PDF copies of the manuals, you need an Adobe Acrobat reader, which you can download from the Adobe web site at VERITAS assumes no responsibility for the correct installation or use of the reader. Bare Metal Restore 4.6 for VERITAS NetBackup Release Notes Provides important information about supported operating systems for Bare Metal Restore on UNIX and Windows, as well as notes that may not be in the Bare Metal Restore manuals. Bare Metal Restore 4.6 for VERITAS NetBackup QuickStart Explains how to get Bare Metal Restore software installed and running on supported UNIX and Windows platforms. Following the directions in the QuickStart guide will ensure that your BMR clients are properly backed up for a Bare Metal Restore operation. Bare Metal Restore 4.6 for VERITAS NetBackup System Administrator s Guide (current document) The System Administrator s Guide is the inclusive guide for administrators and other users. The guide explains how to install, configure, and restore BMR clients on both UNIX and Windows platforms. It also includes a troubleshooting section and a command reference appendix. NetBackup Documents System Administrator s Guides - Basic Product NetBackup DataCenter System Administrator s Guide for UNIX Preface xvii

18 Related Documents Explains how to configure and manage NetBackup DataCenter on a UNIX server. NetBackup DataCenter System Administrator s Guide for Windows Explains how to configure and manage NetBackup DataCenter on a Windows server. NetBackup BusinesServer System Administrator s Guide for UNIX Explains how to configure and manage NetBackup BusinesServer on a UNIX server. NetBackup BusinesServer System Administrator s Guide for Windows Explains how to configure and manage NetBackup BusinesServer on a Windows server. User s Guides NetBackup User s Guide for Windows Explains how to use install, configure, and use a NetBackup MS Windows client to perform backups, archives, and restores. NetBackup User s Guide for UNIX Explains how to use install, configure, and use a NetBackup UNIX client to perform backups, archives, and restores. Troubleshooting Guides NetBackup Troubleshooting Guide for UNIX and Windows Provides troubleshooting information for NetBackup DataCenter and BusinesServer products, including Media Manager. VERITAS Documentation on the Support Web Site Copies of the documentation for Bare Metal Restore (and other VERITAS products) are available on the VERITAS Support web site: 1. Open in your web browser. 2. From the main menu, click Support. The VERITAS Support page appears. Several support options are listed. 3. Click Online Documentation. The Online Documentation page appears. 4. Choose Bare Metal Restore. xviii VERITAS Bare Metal Restore System Administrator s Guide

19 Conventions 5. Choose Bare Metal Restore for NBU. 6. The page will refresh with a list of technical documents that are specific to the product you selected. Conventions The following explains typographical and other conventions used in this guide. Type Style Typographic Conventions Typeface Bold fixed width Fixed width Italics Sans serif (italics) Serif (no italics) Usage Input. For example, type cd to change directories. Paths, commands, file names, or output. For example: The default installation directory is /opt/vrtsxx. Book titles, new terms, or used for emphasis. For example: Do not ignore cautions. Placeholder text or variables. For example: Replace file name with the name of your file. Graphical user interface (GUI) objects, such as fields, menu choices, etc. For example: Enter your password in the Password field. Notes and Cautions Note This is a Note. Notes are used to call attention to information that makes using the product easier or helps in avoiding problems. Caution This is a Caution. Cautions are used to warn about situations that could cause data loss. Preface xix

20 Getting Help Key Combinations Some keyboard command sequences use two or more keys at the same time. For example, holding down the Ctrl key while pressing another key. Keyboard command sequences are indicated by connecting the keys with a plus sign. For example: Press Ctrl+t Command Usage The following conventions are frequently used in the synopsis of command usage. brackets [ ] The enclosed command line component is optional. Vertical bar or pipe ( ) Separates optional arguments from which the user can choose. For example, when a command has the following format: command arg1 arg2 the user can use either the arg1 or arg2 variable. When a command is too long to fit on one line within the text of this document, the following guidelines apply: 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. 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\veritas\baremetalrestore\bin\ bmrrc.exe c:\program files\microsoft visual xstudio\vc98\bin\cl.exe Do include a space between visual and studio. Do not include a space between \bin\ and bmrrc.exe. Getting Help For updated information about this product, including system requirements, supported platforms, supported peripherals, and a list of current patches available from Technical Support, visit our web site: xx VERITAS Bare Metal Restore System Administrator s Guide

21 Getting Help VERITAS Customer Support has an extensive technical support structure that enables you to contact technical support teams that are trained to answer questions to specific products. You can contact Customer Support by sending an to (for low-priority issues), or by finding a product-specific phone number from the VERITAS support web site. The following steps describe how to locate the proper phone number. 1. Open in your web browser. 2. Click Contact Support. The Contacting Support Product List page appears. 3. Select a product line and then a product from the lists that appear. The page will refresh with a list of technical support phone numbers that are specific to the product you selected. Preface xxi

22 Getting Help xxii VERITAS Bare Metal Restore System Administrator s Guide

23 Introduction 1 VERITAS Bare Metal Restore (BMR) provides disaster recovery features that enhance your current backup solution. If your system suffers data loss or corruption, NetBackup enables you to restore the data back on to the system. However, if your machine loses its boot capability or suffers other catastrophic failure, you must first manually restore the OS, system configuration, and NetBackup client before your NetBackup solution can completely recover the system. Bare Metal Restore automates the complete recovery of your client after catastrophic system failure. BMR is integrated with VERITAS NetBackup to ensure that your client files are backed up and restored. After installation and configuration of BMR, the recovery process can consist of running one command from the BMR GUI on the BMR main server and rebooting your client. This BMR recovery includes the operating system, the system configuration, and all system and data files. Separate system backups or reinstalls are not required. This chapter contains the following information: Terminology Technical Overview BMR Graphical User Interface Bare Metal Restore Components Deployment Planning BMR and NetBackup Requirements and Limitations The Importance of Making a Complete Backup 1

24 Terminology Terminology This section explains important terms as they apply to the operation of Bare Metal Restore. For a complete list of terms found in this book, see Glossary on page 313. For a complete list of commands and descriptions, see BMR Command Reference on page 291. Term BMR GUI BMR media boot boot image client configurations client/server SAMBA Shared Resource Tree (SRT) Definition The BMR user interface. Users access the BMR server GUI on the BMR main server. The process of using a CD-ROM that contains the appropriate SRT needed for restore so that the client does not need network access to the SRT on the BMR file server. A set of data that associates a BMR client with the appropriate SRT necessary for the restore process. BMR captures system specific configuration information such as number of disk drives, volume and file system information, number and type of network adapters, network properties, drivers, and other system software components. Each snapshot is called a Client Configuration. These configurations may change over time as system hardware and software is updated. There may also be situations in which a user must deliberately update a Client Configuration, such as for a Dissimilar Disk Restore or a Dissimilar System Restore. An architecture in which one computer can access information from another. The client is the computer that asks for access to data, software, or services. The server, which can be anything from a personal computer to a mainframe, supplies the requested data or services for the client. The utility that allows UNIX to share server file systems with Windows NT/2000. During the client restore process, the SRT provides the executables and utilities needed to reformat the drives, re-build the file systems, and restore the files using the NetBackup client software. Also, the shared resource tree (SRT) provides the resources needed to build the boot images. 2 VERITAS Bare Metal Restore System Administrator s Guide

25 Technical Overview Technical Overview The following illustration shows a simple version of a BMR system configuration. BMR main server NetBackup Master Server Backs up client A BMR client A BMR file server for client A BMR boot server for client A BMR main server - Typically, you will have one BMR main server, either an AIX, HP-UX, or Solaris machine. BMR boot servers/bmr file servers - The number of BMR boot servers and BMR file servers you have depends on the number of client platforms your BMR system will support. Each BMR UNIX client platform requires the corresponding platform type for the BMR file server and BMR boot server. Different versions of AIX BMR clients require BMR boot servers and BMR file servers of the same or greater AIX version. AIX is the only platform that allows the BMR boot server and BMR file server to reside on different machines. BMR Windows clients can use either an AIX, HP-UX, or Solaris machine as the BMR file server. BMR Windows clients do not use a BMR boot server. NetBackup Servers - All BMR clients should be regularly and fully backed up by a NetBackup server. How Does a Bare Metal Restore Work? The BMR client restore has three basic phases: Chapter 1, Introduction 3

26 Technical Overview 1. The client boots from a boot image, either via network boot or media boot. 2. The client accesses the Shared Resource Tree (again, either via the network or via media), and accesses or installs an OS image, a BMR client, and a NetBackup client. UNIX Client 3. The client performs an automated restore from the NetBackup client, restoring all requested files and data from the NetBackup server. The BMR main server manages the restore process, making the appropriate boot image and file system available to the client. The following example depicts a standard network restore BMR boot server (boot image) The UNIX client performs a network boot with the boot image on the BMR boot server. BMR file server (SRT) The client accesses system files and NetBackup client from the SRT on the BMR file server. NetBackup server (backup image) The client restores all requested files from the NetBackup backup image. Windows Client Boot image on boot floppy The Windows client boots from a boot floppy. BMR file server (SRT) The client installs system files and NetBackup client from the SRT on the BMR file server. NetBackup server (backup image) The client restores all requested files from the NetBackup backup image. 4 VERITAS Bare Metal Restore System Administrator s Guide

27 Technical Overview In the event of catastrophic failure, it may not be possible to perform a network boot. In that case, the BMR client restore relies on boot media and a CD-based SRT. The following example depicts a media restore. UNIX Client BMR CD-based SRT (boot image) The UNIX client boots from prepared boot media. BMR CD-based SRT The client accesses system files and NetBackup client from the prepared SRT on the CD. NetBackup master server (backup image) The client restores all requested files from the NetBackup backup image. Windows Client Boot image on boot floppy The Windows client boots from a boot floppy. BMR CD-based SRT The client installs system files and accesses NetBackup client from the prepared SRT on the CD. NetBackup master server The client restores all requested files from the NetBackup backup image. How Do I Set Up BMR Restore Capabilities? 1. Install and configure BMR main server, BMR boot servers, and BMR file servers. 2. Install and configure BMR clients. 3. Perform a full backup of each BMR client, including running the BMR command bmrsavecfg, which saves a copy of the client s system configuration. After your initial configuration and backup, bmrsavecfg is run automatically from the bpstart_notify script each time a backup is performed. 4. Create a Shared Resource Tree (SRT) for each client type. The SRT includes OS images, NetBackup client installation images, and other necessary system information. The SRT resides on the BMR file server, or you can create a CD-based SRT for the media boot option. Chapter 1, Introduction 5

28 BMR Graphical User Interface 5. Create a boot image for each BMR client type. This is stored on the BMR boot server, or on a floppy disk for Windows clients. 6. Verify pre-recovery setup. BMR automates the pre-recovery verification for a client when the Prepare to Restore operation is performed. See Preparing to Restore a Client on page 136 for details on verifying your pre-recovery preparation. What Capabilities Does the BMR Software Provide? BMR software provides the BMR GUI functions and command line utilities that help you perform BMR setup and restore processes: Installing BMR Configuring BMR servers Configuring BMR clients Creating SRTs Creating boot images Sharing boot images Managing SRTs and boot images Managing server configuration Managing client configuration Editing client configuration Saving client configuration Preparing to restore Performing complete client restore This guide explains the use of these tools and processes as they apply to each stage of setting up and using BMR. For a description of the BMR GUI, see BMR Graphical User Interface, below. For an explanation of command line utilities, see BMR Command Reference on page 291. BMR Graphical User Interface From the BMR graphical user interface (GUI), you can view lists of servers, clients, SRTs, and boot images. You can also view logs and configuration details. At restore time, you will use the BMR GUI to select and configure the clients you want to restore. 6 VERITAS Bare Metal Restore System Administrator s Guide

29 BMR Graphical User Interface Launching the BMR GUI The BMR GUI is available, by default, only to a browser on the BMR main server. It is possible to configure the BMR main server to allow the administrator to access the BMR GUI from other systems. For details on changing the server configuration to enable remote access, see Enabling Remote Access to the BMR GUI on page 40. To launch the BMR GUI 1. On the BMR main server, launch a web browser. 2. In the Address field, enter: where localhost is the server hostname, and 8080 is the port number. Note If you run the BMR GUI server on port 80, you do not need to specify the port number in the URL. The Logon Window displays: 3. Enter bmradmin as both the User Name and the Password. (The user name and password used by the BMR GUI have no relationship to the system user names and passwords.) Chapter 1, Introduction 7

30 BMR Graphical User Interface Following a successful logon, the BMR GUI displays: After the BMR GUI launches, the Bare Metal Restore Client List displays. From the main navigation bar along the top of the GUI, you can select a variety of BMR management options. 8 VERITAS Bare Metal Restore System Administrator s Guide

31 BMR Graphical User Interface BMR GUI Functions The functions of the BMR GUI are described in the following sections. The examples below assume you have already installed and configured the components of your BMR system. For instructions, see BMR Server Installation and Configuration on page 27. Clients A BMR client is a system that is protected by the BMR server. A BMR client will register itself to the BMR main server when the BMR Administrator runs the bmrsetupclient command for the first time. After that, a BMR client s configuration is uploaded to the BMR server every time bmrsavecfg runs. Since bmrsavecfg runs based on the NetBackup schedule, the BMR client s configuration upload usually occurs every day. Click Clients on the main navigation bar to display a list of BMR clients associated with this BMR main server. The Bare Metal Restore Client List displays: The Client List screen shows the operating system (in the OS column), as well as the client State. The following list describes the possible States: Client State Ready Ready to Restore Preparation Error Description This client has successfully registered with the BMR main server. A Prepare to Restore operation has been successfully completed on this client. The Prepare to Restore operation failed on this client. Chapter 1, Introduction 9

32 BMR Graphical User Interface Client State Restoring Restored Restoration Error Ready to Discover Discovering Discovered Description This client is currently being restored. This client has completed a restore. A failure occurred during a restore on this client. A successful Prepare to Discover operation has taken place on this client. A UNIX client is currently performing a discovery boot. A UNIX client has completed the discovery boot. Click the client in the Client Name list to view the Configuration List for Client screen. The Configuration List for a particular client displays the configurations available for the client in the Configuration Name column, as well as the configuration State. The following list describes the possible States: Configuration State Saved Edited Retrieved Description This configuration was generated when bmrsavecfg ran on the client. This configuration is an editable copy generated by a user. This configuration was retrieved from NetBackup for a Point in Time restore. 10 VERITAS Bare Metal Restore System Administrator s Guide

33 BMR Graphical User Interface Configuration State Discovered Description This is a minimal configuration generated by a UNIX client from a discovery boot. To view details of a configuration, click the name of the configuration. The Configuration Summary screen displays: This configuration information is updated every time bmrsavecfg runs on the client (usually every day depending on the backup schedule). For details on manually changing client configuration information, prior to doing a Prepare to Restore, see Modifying Client Configuration on page 122. Chapter 1, Introduction 11

34 BMR Graphical User Interface BMR Servers The BMR Servers option displays the list of BMR file and boot servers. The following screen shows an example list: BMR server configuration is defined when bmrsetupserver is run as part of the installation and initial configuration (see BMR Server Installation and Configuration on page 27). Although you cannot change the configuration from the BMR GUI, you can view a screen of configuration details. From the list above, you can select a server configuration to view by doing one of the following: Click the name of the server in the Server Name list or Click the radio button to the left of the server name, then click View. 12 VERITAS Bare Metal Restore System Administrator s Guide

35 BMR Graphical User Interface The View the BMR Server Configuration screen displays: NetBackup Servers Click NetBackup Servers on the BMR navigation bar to display the NetBackup Server List screen. On this screen, you can add or modify the NetBackup servers in your BMR configuration. For more details on this function, see Adding and Configuring NetBackup Servers on page 41. Chapter 1, Introduction 13

36 BMR Graphical User Interface Shared Resource Trees Click Shared Resource Trees on the BMR navigation bar to display the List of Shared Resource Trees screen. This screen displays available Shared Resource Trees (SRTs) for your BMR clients. For more information on SRTs, including instructions on creating and configuring SRTs, see Creating a Shared Resource Tree (SRT) on page 61. Boot Images Click Boot Images on the BMR navigation bar to display the List of Boot Images screen. This screen displays available boot images for your BMR clients. For more information on creating and configuring boot images, see Creating Boot Images and Boot Media on page VERITAS Bare Metal Restore System Administrator s Guide

37 BMR Graphical User Interface Log File The BMR log file contains useful information about BMR activity and events. Messages in this file are helpful in identifying existing and potential problems. VERITAS Customer Support often asks to review these logs with you when troubleshooting a problem. When viewing the log file from the BMR GUI, only the most recent 50 messages are displayed. To review messages before the most recent 50, you should review the actual log file on the BMR main server. The location of the log file is displayed at the top of the BMR Server Log File screen. To display the BMR Server Log File, click Log File on the BMR navigation bar. The following displays: Chapter 1, Introduction 15

38 BMR Graphical User Interface Licensing Click Licensing on the navigation bar to see the following BMR license information: Used Licenses: the total number of licenses currently used by BMR Licensed Client (s): a list of all licensed clients registered with this BMR main server BMR Version Information: a list of BMR version information, including the following: The release name of the current version of BMR that this server is running The actual product build version of BMR that this server is running The Enterprise Storage Manager used by this BMR server (NetBackup). If you need to call VERITAS Customer Support for any reason, please have your license information ready. Help Click the Help button to view an electronic (PDF) version of these two BMR manuals: Bare Metal Restore System Administrator s Guide Bare Metal Restore QuickStart 16 VERITAS Bare Metal Restore System Administrator s Guide

39 Bare Metal Restore Components Bare Metal Restore Components BMR uses your existing NetBackup server and client configuration, and adds BMR main server, BMR boot server, and BMR file server components. Depending on the platforms in your environment, the BMR server components can be located on the same machine, on a separate machine, or on a combination of machines. BMR Main Server The BMR main server manages the client restore process. It makes the appropriate boot image and filesystems available to the client, ensures that the BMR boot server and BMR file server are properly configured, and generates a customized client boot procedure. The BMR main server must be running at all times because it is the license server for BMR clients. BMR Boot Server The BMR boot server provides the boot image to the client when a BMR UNIX client performs a network boot prior to restore. BMR uses the standard bootp or bootparam protocol to network-boot a client from the boot server. BMR File Server The BMR file server makes the necessary filesystem resources available to the client at restore time via NFS or SAMBA. These resources are included in the shared resource tree (SRT) filesystem that contains the necessary operating system commands and libraries, the BMR client package, and the NetBackup client package. Note SAMBA code is included to allow Windows BMR clients to access the SRT on UNIX BMR file servers. BMR Client The BMR client is any machine on which the BMR client software is installed. BMR clients are also NetBackup clients. In this context, it is probable that a BMR client may also be a server for other applications or data. Chapter 1, Introduction 17

40 Deployment Planning NetBackup Server The BMR client continues to use its assigned NetBackup server, which backs up all the files on the client. At backup time, BMR also saves the client s configuration so that an up-to-date snapshot of the machine configuration is always saved with the system s data. Caution In order to recover your machine from your NetBackup servers, all files (including system files) must be backed up to the NetBackup server. Deployment Planning The following illustration shows an example of BMR system configuration. BMR client A Solaris Solaris Box BMR file server for client A for client B BMR boot server for client A BMR main server NetBackup Master Server Backs up client D client E BMR client D AIX BMR client B Windows NT NetBackup Master Server Backs up client A client B client C BMR client C HP-UX HP-UX Box BMR file server for client C BMR boot server for client C BMR client E Windows 2000 AIX Box BMR file server for client D for client E BMR boot server for client D VERITAS NetBackup Server Considerations NetBackup servers are important to the function of BMR in two ways: They back up the BMR client configuration, files, and data, and make this backup available to the BMR client at restore time. They supply the client configuration information to the BMR main server, or directly to a UNIX client, at restore time. Both the BMR main server and BMR clients must have a NetBackup client installation, at the same level as the lowest level of NetBackup server being used. 18 VERITAS Bare Metal Restore System Administrator s Guide

41 Deployment Planning The BMR main server must be able to communicate with every NetBackup server used by the BMR clients. When you install and configure your BMR main server, you will add all the NetBackup servers used by all your BMR clients before installing and configuring the BMR clients. Your BMR client will not be able to register with your BMR main server if the NetBackup server it specifies is not recognized. Normally, a UNIX BMR client at restore time has access to only one network interface. Before you Prepare to Restore the client, specify the network interface to use as the boot interface, if necessary. Use the following table to determine the correct interface. Platform or Hardware Type AIX (all) * HP-UX Solaris Windows NT/2000 Bootable Network Interface(s) Built-in Ethernet, Token Ring, or Ethernet card Internal Ethernet only Any Ethernet card Any Ethernet card *Booting the RS/6000 from a network adapter requires support in the system firmware. Chapter 1, Introduction 19

42 Deployment Planning Planning the BMR Installation In addition to the NetBackup considerations from the previous section, your BMR deployment planning includes three main considerations: Choosing the machine that will be the BMR main server. Identifying all BMR clients, and determining the requirements for client SRTs. Choosing the machine(s) that will be the BMR file server(s) and BMR boot server(s). Appendix B, Deployment Planning Resources on page 269, provides important platform-specific requirements that will help you in making these deployment decisions. In addition, it provides five worksheets that will help you organize and control your deployment and installation: NetBackup Server Network Interface Worksheet on page 277 Network Topology Worksheet on page 279 BMR Server Candidate Worksheet on page 281 BMR File Server Worksheet on page 283 Shared Resource Tree Worksheet on page 285 Instructions for each of these worksheets are on the opposite manual page. Create copies of the worksheets to use when planning your BMR deployment. The following sections provide some general considerations to keep in mind when planning your BMR installation. BMR Main Server Considerations The BMR main server must be running Solaris, AIX, or HP-UX. The main server must have network connectivity to and be able to resolve hostnames and IP addresses of all BMR file servers and BMR boot servers, as well as to all BMR clients and the NetBackup servers that back them up. BMR main servers running on Solaris platforms require libucb libraries. The libucb libraries are installed as part of the SUNWscpu package. For detailed system requirements, see Specifications on page 270. For detailed connectivity requirements, see BMR Server Candidate Worksheet on page 281. Identifying BMR Clients and SRT Requirements You can include HP-UX, Solaris, AIX, or Windows NT/2000 machines as clients in your BMR installation. See Specifications on page 270 for specific system requirements for BMR clients. A BMR client can be a server for other applications or processes. 20 VERITAS Bare Metal Restore System Administrator s Guide

43 Deployment Planning As part of installation and configuration, you will be creating Shared Resource Trees (SRTs) and boot images for your BMR clients. The Shared Resource Tree Worksheet on page 285 provides guidance on gathering information for creating SRTs on your BMR file servers. For a thorough explanation of SRTs, including the procedure for creating them, see Creating a Shared Resource Tree (SRT) on page 61. BMR File Server Requirements and Considerations Each platform type of UNIX BMR client requires a BMR file server of a corresponding platform type. Any supported UNIX server can be the BMR file server for Windows clients. For both HP-UX and Solaris, the BMR boot server and BMR file server must reside on the same machine. AIX is the only platform for which the BMR file and boot server components can reside on different machines. There can be circumstances where separating the BMR boot and file servers is beneficial, but for most instances, the BMR file and boot server reside on the same machine. 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. BMR file servers must be running the NFS daemon (nfsd). HP-UX and Solaris machines can only network boot from their BMR boot server (of the respective platform type) existing in the same network segment (OS- specific limitation). BMR file servers should have network connectivity to and be able to resolve the hostnames and IP addresses of all BMR boot servers and the BMR main server. For network segments with slow links to any of the BMR servers, consider placing the BMR file server and BMR boot server 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 bootp (or, for Solaris, bootparam) to be available. Some operating systems ship 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. For network boots only, the BMR file server requires the NFS server services to be available to serve UNIX BMR clients. Chapter 1, Introduction 21

44 Deployment Planning 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. See Configuring BMR Servers on page 34 for more information on configuring the SAMBA share. BMR File Server Selection AIX BMR File Server Selection Criteria An AIX BMR file server must be at the same or higher level of AIX than any of the SRTs 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 cannot be used to hold an AIX 4.3 SRT. You need a minimum of one AIX BMR file server for all the AIX BMR clients in the network. The AIX BMR file servers chosen must be the same or higher level of AIX as any of the BMR clients they serve. Each AIX BMR 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 and 4.3.3, you need three AIX SRTs: one for AIX 4.1, one for AIX 4.2, and one for AIX 4.3. These can be located on the same AIX BMR 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. Solaris BMR File Server Selection Criteria BMR file servers and boot servers running on Solaris platforms require libucb libraries. These libucb libraries are installed as part of the SUNWscpu package. Each network segment with Solaris clients in the BMR File Server Worksheet must have a Solaris BMR boot server and a BMR file server. Each Solaris BMR file server can hold many Solaris SRTs. Although a Solaris BMR file server and a BMR boot server must be available in each network segment before a BMR client can be restored, there are ways to minimize the impact of this requirement: When needed, a Solaris BMR boot server and a BMR file server can be installed and an SRT created, after the client has failed and needs to be restored. 22 VERITAS Bare Metal Restore System Administrator s Guide

45 Deployment Planning The Solaris BMR boot server and BMR 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 server/file server with multiple network interfaces can be used for Solaris BMR clients on each of the network segments to which it is attached. This may require, however, that alternate addresses for the BMR file/boot server be specified for the Boot Image, prior to the Prepare to Restore operation. HP-UX BMR File Server Selection Criteria An HP-UX BMR file server must be at the same or higher level of HP-UX than any of the SRTs it holds. For example, an HP11.00 BMR file server can be used to hold an HP10.20 SRT, but an HP10.20 BMR file server cannot be used to hold an HP11.00 SRT. If multiple versions of HP-UX exist, there must be at least one BMR file server for each version. One exception to this rule is that an HP-UX BMR file server can support both HP-UX or HP-UX BMR clients. The HP-UX BMR file server can have many SRTs but can only have one boot image for any given SRT. Each Network Segment with HP-UX clients in the BMR File Server Worksheet must have an HP-UX BMR boot server and a BMR file server. The HP-UX BMR file servers must also be BMR boot servers. The Ignite version of the SRTs on an HP-UX file server must match the Ignite version on that BMR file server. 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 at a time. For example, an HP-UX BMR file server can hold either an HP-UX SRT or an HP-UX 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. If multiple versions of HP-UX exist, there must be at least one BMR file server for each version. Windows BMR File Server Selection Criteria A Windows 2000 client can use any one of the AIX, HP-UX, or Solaris systems as a BMR file server. However, the following considerations apply: Chapter 1, Introduction 23

46 BMR and NetBackup Requirements and Limitations The BMR file server must have SAMBA configured, as explained in Configuring BMR Servers on page 34. This BMR file server must be reachable by the BMR client (at restore time) using the same network interface card that is used by the boot floppy created with the Boot Options Wizard. See Creating Boot Images (Floppies) for Windows Clients on page 98. BMR and NetBackup Requirements and Limitations Requirements Because the existence of certain files in certain directories can affect the behavior of a machine, BMR requires that NetBackup collect the true-image restore information. The Collect true image restore information / with move detection (TIR) options must be turned on for the policies that back up the BMR client. TIR information enables NetBackup to restore only those files present on the system at the time of the appropriate backup. Move detection enables NetBackup to correctly restore files that were moved, renamed, or newly installed. These options also ensure that all of the restored files will fit in the volumes and file systems created by BMR during the recovery. See the NetBackup System Administrator s Guide for a detailed explanation of True Image Restore information. Another NetBackup attribute on the Global Attributes tab, Keep TIR Information, controls how long TIR information is retained in the NetBackup catalog. This TIR information increases catalog size and disk space used. Since BMR recovers a system using the most recent full or incremental backup, the value of this attribute has to be chosen to match the retention policy. Since the TIR information is also stored on the backup media, you can choose to set the attribute to 0 days. This will eliminate the impact on the catalog size, but will make the restore slower. All communication to the NetBackup master and media servers must go over a single interface. Except for Windows NT/2000, only one network interface on the client is configured during a BMR restore. The DISALLOW_CLIENT_RESTORE server option must be turned off. The BMR restore process requires that both the BMR main server and the BMR client be able to request restores. See Setting Client List and Restore Permissions in the NetBackup System Administrator s Guide. The BMR main server must be allowed to redirect restores of client files to itself. See Allowing Redirected Restores in the NetBackup System Administrator s Guide. The files of the client operating system must be backed up by a single policy. 24 VERITAS Bare Metal Restore System Administrator s Guide

47 BMR and NetBackup Requirements and Limitations For Windows clients, this includes the SYSTEM_STATE. For unix clients, ALL_LOCAL_DRIVES must be used to ensure that recovery in all case will work. This will require that an exclude_list is created to not back up any databases or applications that require special handling for backups. These files will need to be backed up separate from the BMR backups and will then need to be restored after the server has been recovered. Using / with Cross Mount Points or specifying /, /usr, /var, /opt and so on, may, in some restores cases be successful. In other restores they will not work. Logical volumes that are not part of the operating system can be backed up with other policies but each logical volume must be backed up by only a single policy. It is recommended that all policies be scheduled to back up at the same time. BMR saves the configuration of the client before each backup; this is done with the bmrsavecfg utility. bmrsavecfg is run from the bpstart_notify script to ensure that this system configuration backup happens. If more than one policy is used and each policy has it own bpstart_notify script, then the bpstart_notify script run by the policy that backs up the operating system should run bmrsavecfg. Limitations BMR cannot be used to restore a NetBackup master server. User initiated backups are not supported. BMR requires True Image restore information. True Image restore information is not collected during a user initiated backup. BMR will only restore files using one NetBackup master server. Clients that are backed up with more than one master server cannot be fully restored without additional manual intervention. Encryption is not supported. Enhanced client/server authentication (vopie) is not supported. NetBackup Storage Migrator is not supported. FlashBackup is not supported. Database agents are not supported. BMR does not restore databases that require use of database agents. After BMR restores the operating system, the user can restore these databases manually. Block level incremental, available with VERITAS Oracle Edition, is not supported. Chapter 1, Introduction 25

48 The Importance of Making a Complete Backup The Importance of Making a Complete Backup You must perform a complete backup of your client before Bare Metal Restore can successfully restore the client. Because the system and application files typically do not change, regular incremental backups do not increase in size. A complete backup must include the following: ensuring that bmrsavecfg has been run before the backup is made. backing up all files on the client. backing up the system objects for Windows clients. There are several issues that can cause an incomplete backup, including the following: 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 excluded any files during the backup, those files do not get backed up and, consequently, they do not get restored. Therefore, it is important that you follow these guidelines to obtain a proper backup: Regularly examine the NetBackup 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 NetBackup options should be set to retry file backups if a file changes during the backup attempt. Refer to BUSY_FILE_PROCESSING in the VERITAS NetBackup DataCenter 4.5 System Administrator s Guide for UNIX or Open Transaction Manager (OTM) in VERITAS NetBackup DataCenter 4.5 System Administrator s Guide for Windows. 26 VERITAS Bare Metal Restore System Administrator s Guide

49 BMR Server Installation and Configuration 2 This chapter describes the installation and configuration procedures for BMR main servers, BMR file servers, and BMR boot servers. You can install BMR servers on Solaris, HP-UX, and AIX platforms. Most installation and configuration steps are identical on all platforms. Any differences will be noted with a reference to platform type. To determine system requirements, refer to Specifications on page 270. This chapter contains the following sections: General Installation Requirements Upgrading from Bare Metal Restore 4.5 Installing BMR Servers On HP-UX On Solaris On AIX Configuring BMR Servers Enabling Remote Access to the BMR GUI Adding a License Key Adding and Configuring NetBackup Servers 27

50 General Installation Requirements General Installation Requirements You must obtain a license key. Contact your VERITAS sales representative if you do not have a license key. You must be the root user to perform the BMR main server, BMR file server, and BMR boot server installation tasks. Verify the minimum system requirements in Specifications on page 270. The altnames Directory Configuring the altnames directory on the NetBackup master server enables the BMR main server to perform redirected restores. Before installing the BMR server software on the BMR main server, create a file on the NetBackup master server containing a list of all BMR clients. The location of this file should be as follows: For a UNIX NetBackup master server: /usr/openv/netbackup/db/altnames For a Windows NetBackup master server: <install path>:\veritas\netbackup\db\altnames directory. Name this file the peername name of the BMR main server. Note This step is not necessary if the BMR main server is added as a SERVER or MEDIA_SERVER to the bp.conf file on the NetBackup master server for the BMR clients. Refer to the NetBackup System Administrator s Guide for proper use of the altnames directory. Port Usage for BMR Client/Server Communication The BMR servers use the port you define during setup to listen for requests made by BMR clients or other BMR servers. The default port used for communication to BMR servers is The default port used for connecting to the BMR GUI is 80. BMR file servers with SAMBA installed listen on the netbios-ssn (139) and netbios-ns (137) ports. These services are used by BMR Windows clients during a BMR restore. 28 VERITAS Bare Metal Restore System Administrator s Guide

51 Upgrading from Bare Metal Restore 4.5 BMR file servers supporting UNIX clients run NFS, which uses portmapper (111), nfsd (2049), mountd, lockd, and statd. The latter three daemons use unreserved ports. These services are used by BMR UNIX clients during a BMR restore. BMR boot servers provide bootp (67 and 68), tftp (69), and bootparam (Solaris only) support to booting BMR clients. Upgrading from Bare Metal Restore 4.5 You can install Bare Metal Restore 4.6 as a brand new installation, or you can upgrade your existing Bare Metal Restore 4.5 installation. Note Upgrades from Bare Metal Restore versions prior to BMR 4.5 are not supported. Upgrade the BMR main server first, and then upgrade all of the file servers and boot servers in any order. All BMR servers must be upgraded for BMR to function correctly. Deletions Resulting from Upgrade Installation Performing an upgrade from BMR 4.5 to BMR 4.6 deletes the following Bare Metal Restore configuration components: All created Shared Resource Trees Only the database entries are removed, but not the directories where the Shared Resource Trees are created. You must manually remove those directories. All created packages All created boot images All created media boot images You must recreate all Shared Resource Trees, packages, boot images, and media boot images for use with your BMR 4.6 installation. If the Prepare to Restore step has been performed on any BMR clients, this step must be repeated after the above components have been created with the BMR 4.6 system. Upgrade Installation Procedure The procedure for upgrading your BMR servers from version 4.5 to version 4.6 is the same as for an initial installation, with one exception. During a Solaris server upgrade installation, you will use a different command string for pkgadd. This difference will be noted in the Solaris installation procedure, below. Use the instructions in the following section, Installing BMR Servers, to perform your initial or upgrade installation. Chapter 2, BMR Server Installation and Configuration 29

52 Installing BMR Servers Installing BMR Servers Install BMR Server software on your main BMR server, your BMR file server(s), and your BMR boot server(s). For HP-UX and Solaris, BMR file servers and boot servers must be on the same machine. For AIX, BMR file servers and BMR boot servers can be on different machines, but will most often be on the same machine. Refer to Bare Metal Restore Components on page 17, and Appendix B, Deployment Planning Resources on page 269 to determine which machines to choose for your BMR servers. The following sections provide server installation procedures according to platform: HP-UX on page 30. Solaris on page 31. AIX on page 32. HP-UX To install BMR server on HP-UX using swinstall 1. Insert the BMR distribution CD into the CD-ROM drive. 2. Check for the running PFS daemons: ps -ef grep pfs 3. If the PFS daemons are not running, start them: pfs_mountd& pfsd 6& 4. Create a mount point: mkdir /bmr_cdrom Note To find the CD-ROM device path name, run ioscan -nfkc disk. 5. Mount the CD-ROM: pfs_mount -o xlat=unix <cdrom device path> /bmr_cdrom 6. From the root directory, install the BMR server software: 30 VERITAS Bare Metal Restore System Administrator s Guide

53 Installing BMR Servers swinstall -s /bmr_cdrom/hp BareMetal.server 7. Unmount the CD-ROM drive: pfs_umount /bmr_cdrom 8. Clean up the installation of BMR: rm -r /bmr_cdrom 9. After the BMR server software is installed, you must do one of the following: a. If this is an initial installation, configure the server using bmrsetupserver as explained in Configuring BMR Servers on page 34. b. If this is an upgrade installation, run the following command /opt/baremetal/bmrsetupserver -u Successful completion of this command marks the completion of the upgrade process. Solaris To install BMR server on Solaris using pkgadd Note Make sure vold is running. If vold is not running, the CD-ROM will not be mounted automatically. To start manually: /etc/rc2.d/s92volmgt start Alternatively, mount the CD as usual on server system. 1. Insert the BMR distribution CD into the CD-ROM drive. 2. Enter the following command, noting the difference for an initial installation and an upgrade installation. For an initial installation: pkgadd -d <pathname> BMRserver where <pathname> is the path to the Solaris distribution directory on the CD. For an upgrade installation: pkgadd -a <pathname>/sol/upgrade_admin -d <pathname>/sol BMRserver where <pathname> is the directory where the CD-ROM is mounted. Chapter 2, BMR Server Installation and Configuration 31

54 Installing BMR Servers Note If upgrading a patched server, files introduced by patches will prompt for installation. Enter y at the prompt. 3. After the BMR server software is installed, you must do one of the following: a. If this is an initial installation, configure the server using bmrsetupserver as explained in Configuring BMR Servers on page 34. b. If this is an upgrade installation, run the following command /opt/baremetal/bmrsetupserver -u Successful completion of this command marks the completion of the upgrade process. AIX The menu driven utility, smitty, uses the installp command to install software in the AIX environment. While you can use the installp command to install the BMR server, we recommend using smitty to install the BMR server. Both the smitty and installp procedures are provided below. To install BMR server on AIX using smitty 1. If you are installing BMR from the distribution CD, make sure that the server machine s CD-ROM drive is properly mounted. Otherwise, copy the BMR distribution file, BareMetal, to a temporary location. 2. Enter the following command: 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 one of the following: the BareMetal distribution file the device name of the CD-ROM drive (/dev/cd0) 4. Press Return. The Install and Update from Latest Available Software screen redisplays. 5. While on the SOFTWARE to install option, press F4. 32 VERITAS Bare Metal Restore System Administrator s Guide

55 Installing BMR Servers 6. Using the arrow keys, move the selection bar to Bare Metal Restore for AIX - Server and press F7. 7. Press Return three times to confirm the changes and exit to the main menu. 8. To exit smitty press F After the BMR server software is installed, you must do one of the following: a. If this is an initial installation, configure the server using bmrsetupserver as explained in Configuring BMR Servers on page 34. b. If this is an upgrade installation, run the following command /usr/lpp/baremetal/bmrsetupserver -u Successful completion of this command marks the completion of the upgrade process. To install the BMR Server Using installp 1. If you are installing BMR from the distribution CD, make sure that the server machine s CD-ROM drive is properly mounted. Otherwise, copy the BMR distribution file BareMetal to a temporary location. 2. Enter the following command: installp -acxd <pathname> BareMetal.server where <pathname> is the path to the BareMetal distribution file or the device name of the CD-ROM drive (for example, /dev/cd0) 3. After the BMR server software is installed, you must do one of the following: a. If this is an initial installation, configure the server using bmrsetupserver as explained in Configuring BMR Servers on page 34. b. If this is an upgrade installation, run the following command /usr/lpp/baremetal/bmrsetupserver -u Successful completion of this command marks the completion of the upgrade process. Chapter 2, BMR Server Installation and Configuration 33

56 Configuring BMR Servers Configuring BMR Servers After you install Bare Metal Restore on the BMR main server, file server(s), and boot server(s), you must configure them before you can use Bare Metal Restore to restore a client. Note You must configure the BMR main server first, before any other component is configured. Depending on the outcome of your deployment plan, you may have multiple BMR file and boot servers. These should be configured after the BMR main server. After all BMR servers are configured, and the NetBackup servers are added to the BMR main server (see Adding and Configuring NetBackup Servers on page 41), you can then install and configure the BMR clients. Running the bmrsetupserver program The bmrsetupserver program configures the BMR server. This command must be run while logged in as the root user. bmrsetupserver must be run on the BMR main server, the BMR file server, and the BMR boot server. This procedure applies to all three BMR server types. To configure a BMR server on HP-UX, Solaris, or AIX 1. Create a BMR administrator user and group on your server machine. 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. If an existing group name is used rather than creating a new group name, the other users within that group will have access privileges to BMR. If the administrator chooses that only root will have access privileges to BMR, there should be only one user in the BMR administrator group. 2. Change the current directory to the BMR directory: For HP-UX: /opt/baremetal For Solaris: /opt/baremetal For AIX: /usr/lpp/baremetal 34 VERITAS Bare Metal Restore System Administrator s Guide

57 Configuring BMR Servers 3. Enter the following command:./bmrsetupserver Bare Metal Restore Server Configuration Example 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 appear. The questions below are from a system where the BMR main server, BMR boot server, and BMR file server are all on the same machine. Depending on the results of your deployment plan, your BMR main server may or may not have a boot or a file server component. This example procedure continues from step 3 in the procedure above, To configure a BMR server on HP-UX, Solaris, or AIX. a. Before you begin the BMR setup process, it is recommended that you check the VERITAS web site at 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. b. Will this machine be a BMR server? [y] Answer y if this machine will be the BMR main server. Otherwise, answer n. c. Enter BMR Main Server's IP hostname that resolves to an external IP address usable for routine BMR communications [somemachine]: d. Enter the BMR server port number [8362]: Supply the TCP/IP port number used by the BMR main server. e. Enter the BMR administrator's user name [bmradmin]: f. Enter the BMR administrator's group name [bmradmin]: g. Enter the BMR GUI server's port number [80]: Supply the TCP/IP port number to be used by the BMR administrative GUI. h. Enter the location of bp.conf file [/usr/openv/netbackup/]: i. BMR can log messages to a log file or to syslog. Enter m to use /var/bmr/log/messages or s to use syslog [m]: Chapter 2, BMR Server Installation and Configuration 35

58 Configuring BMR Servers If you wish BMR to log to its own log file, answer m to this prompt. j. Do you want to install the BMR license key(s)? [y] You can answer n to this step and install the license key later if it is not available now. See Adding a License Key on page 40. k. Enter a license key or a file name containing the keys: l. Do you want to install additional keys? [y]: m. Will this machine be a file server? [y] If this machine will not be a BMR file server, answer n. For AIX, if you answer n, skip to step x. For HP-UX and Solaris, if you answer n, the configuration dialog is complete. Note To restore Windows clients using Bare Metal Restore, you must have SAMBA installed on the BMR file server. By default the BMR server configuration process installs SAMBA for you. If you already have SAMBA installed, refer to Configuring SAMBA on the BMR File Server on page 37. n. If a SAMBA configuration file is found, the following question displays: SAMBA configuration found at /usr/local/lib/smb.conf. Would you like to reconfigure SAMBA? [n]: If you answered n to this question, refer to Configuring SAMBA on the BMR File Server on page 37. o. If no SAMBA configuration is found, the following prompt displays: SAMBA is required for Windows clients. Do you want SAMBA installed now? [y]: Answer y to install SAMBA. p. Enter the SAMBA user name [bmradmin]: q. Set SAMBA share as Read Only (Only bmradmin will be able to write)? [y]: r. Please enter a valid user name for SAMBA read-only access: This prompt appears if the user nobody is not a valid user on this system. You must choose to access the SAMBA share as read-only. s. What network interfaces should SAMBA communicate on? [ / /8]: 36 VERITAS Bare Metal Restore System Administrator s Guide

59 Configuring BMR Servers t. What hosts are allowed access to SAMBA? [ ]: The defaults allow only networks directly attached to access the SRT(s). In this example only Windows machines with the network addresses starting: will be able to use any SRTs created on this file server. u. Please enter a SAMBA password that will be used by bmradmin for write access to the SAMBA share: Note This password is used for the SAMBA share only. This password does not have to be the same as the system or UNIX password. v. Retype new SMB password: w. What directory will you share via SAMBA? [/export/srt]: x. Will this machine be a BMR boot server? [y] If this machine will not be BMR boot server, answer n. The setup program pauses for a brief period while waiting for all the BMR daemons to start, and then exits. Configuring SAMBA on the BMR File Server SAMBA is required to enable UNIX BMR servers to service Windows BMR clients. When you run bmrsetupserver, you have the option to modify the SAMBA configuration (smb.conf) file. If you choose to not have the BMR setup program do the modification, the BMR file server will not service Windows clients. If needed, you can enable Windows client support using SAMBA by changing the SAMBA configuration file, /opt/samba/lib/smb.conf, on the BMR file server. To enable Windows client support on the BMR file server 1. In /usr/local/lib/smb.conf, modify the hosts allow attribute to specify the networks/hosts that have access to this SAMBA server. 2. Modify the interfaces attribute to specify the interfaces you want SAMBA service to be available on. 3. Modify the guest account attribute to specify the BMR administrator user name. 4. Add a stanza called [bmrsrt] with the following attributes: comment = BMR shared resource tree Chapter 2, BMR Server Installation and Configuration 37

60 Configuring BMR Servers path = /export/srt writable = yes printable = no Note The path is set to the shared resource tree directory. 5. Set FSwin and FSsmbpath for this BMR 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 commands from the BMR file server: bmrconfig -h <bmr server hostname> -p <bmr server port number> -o change -r FS <fileserver> FSwin=enabled bmrconfig -h <bmr server hostname> -p <bmr server port number> -o change -r FS <fileserver> FSsmbpath=/export/srt 6. Make sure the BMR administrator user can write to the SRT directory. For example: chmod +w /export/srt chown bmradmin /export/srt Specifying User Access You can also modify an existing BMR file server to support NT and 2000 clients by using SAMBA with Write Only access for a specified user. These changes are also made to the SAMBA configuration file, /usr/local/lib/smb.conf, on the BMR file server. To enable Windows client support with Write access for a specified user 1. In /usr/local/lib/smb.conf, modify the hosts allow attribute to specify the networks/hosts that are to have access to this SAMBA server. 2. Modify the interfaces attribute to specify the interfaces where you want SAMBA services to be available. 3. Modify the guest account attribute to be any user other than the owner of the bmrsrt share. 4. Modify the security attribute to be security = user. This specifies all users of the SAMBA share will have passwords. 5. Modify/add the map to guest attribute to be map to guest = Bad User. This allows an invalid user attempting to access the SAMBA share to access the share as nobody or specified guest account =. This account should not be equal to the [bmrsrt] writelist attribute. 38 VERITAS Bare Metal Restore System Administrator s Guide

61 Configuring BMR Servers 6. Modify the encrypt passwords attribute to yes. 7. Set the password for bmrsrt owner: /opt/samba/bin/smbpasswd -a bmradmin Note This user name and password are used when creating a new shared resource tree (SRT). a. If the guest account is no longer the default, guest account = pcguest, unset the SAMBA password for this account: /opt/samba/bin/smbpasswd -a -n pcguest b. If a valid system username guest exists, unset the SAMBA password for this account: /opt/samba/bin/smbpasswd -a -n guest 8. Add a stanza called [bmrsrt] with the following attributes: comment = BMR shared resource tree user = bmradmin writelist = bmradmin guest ok = yes path = /export/srt create mask = 0755 strict sync = yes sync always = yes 9. Set FSwin and FSsmbpath for this BMR 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 commands from the BMR file server: bmrconfig -h <bmr server hostname> -p <bmr server port number> -o change -r FS <fileserver> FSwin=enabled bmrconfig -h <bmr server hostname> -p <bmr server port number> -o change -r FS <fileserver> FSsmbpath=/export/srt 10. Make sure the bmradmin user or the specified owner of the share can write into the SRT. For example: chmod +w /export/srt chown bmradmin /export/srt Chapter 2, BMR Server Installation and Configuration 39

62 Enabling Remote Access to the BMR GUI Enabling Remote Access to the BMR GUI By default, the BMR configuration only allows access to the BMR GUI from a browser on the BMR main server, attaching to localhost ( ). However, you can configure your BMR main server to enable the administrator to access the BMR GUI from another host. The following procedure explains how to configure httpd.conf on the BMR main server to enable remote access to the BMR GUI. To enable remote access to the BMR GUI 1. Edit /var/bmr/httpd/conf/httpd.conf. 2. Change three instances of to all or to specific IP addresses for access. 3. Signal the Apache daemon to re-read the configuration file. The command to use for signalling the Apache daemon is: kill -HUP <pid> where <pid> is the process ID of the Apache daemon whose parent process ID is 1. It is only necessary to use the kill command to signal the BMR httpd process whose parent process ID is 1. The other processes are child processes. For details on configuring more controlled access with the allow directive in the httpd.conf file, consult the Apache website at Adding a License Key If you answered No to step k of bmrsetupserver, did not know the license key at the time, or chose to add it later, use this procedure to enter the license key. 1. Change the current directory to the Bare Metal Restore directory for your platform: For HP-UX: /opt/baremetal/hp For Solaris: /opt/baremetal/sol For AIX: /usr/lpp/baremetal/aix 2. Enter the provided license key using the following command: 40 VERITAS Bare Metal Restore System Administrator s Guide

63 Adding and Configuring NetBackup Servers./lm_keyins -k <license key> -g where <license key> is the key string provided with the product. Adding and Configuring NetBackup Servers After the BMR main server is initially configured, you must add all of the IP addresses for each NetBackup server that backs up your BMR clients to the BMR database. When you configure a BMR client, the client registers itself with the BMR main server. As part of the registration process, the BMR client determines the IP address it uses to connect to the NetBackup server. The client tells the BMR main server which NetBackup server and corresponding IP address the client will use. If the BMR main server cannot determine a NetBackup server with this address, the BMR client will fail registration verification and will not be configured. The following procedures assume that you are using the BMR administrative GUI on the BMR main server. Refer to BMR Graphical User Interface on page 6 for instructions on launching the GUI. To add NetBackup servers 1. On the navigation bar, click NetBackup Servers. The NetBackup Server List screen displays, listing servers that are already configured (if any): 2. Click Add NetBackup Server. The Add a NetBackup Server screen displays. Chapter 2, BMR Server Installation and Configuration 41

64 Adding and Configuring NetBackup Servers 3. Enter the name of the NetBackup Server Hostname. 4. Enter the IP Address for the new NetBackup server. 5. Click OK. The system creates an entry for the NetBackup server and stores it within BMR for future reference. 6. To cancel adding an NetBackup server, click Cancel. The current list of NetBackup servers displays. To change NetBackup server configuration 1. From the navigation bar, click NetBackup Servers. The List NetBackup Servers screen displays. 2. From the List NetBackup Servers screen, click the name of the server you want to configure. The Configure NetBackup Server screen displays: 3. To add an IP address to a NetBackup server: a. In the IP Address to add field, enter the new IP address. b. Click OK. The new IP address is added. 4. To delete an IP address from the NetBackup server: a. Highlight the desired IP address. b. Click Delete. The selected IP address is deleted. 5. Click OK. Your changes are saved and the server is configured or reconfigured. 42 VERITAS Bare Metal Restore System Administrator s Guide

65 BMR Client Installation and Configuration 3 This chapter describes the installation and configuration procedures for BMR clients. You can install BMR client software on Solaris, HP-UX, AIX, and Windows platforms. To determine system requirements, refer to Specifications on page 270. This chapter contains the following sections: General Client Installation Requirements Upgrading from Bare Metal Restore 4.5 Installing BMR Clients On HP-UX On Solaris On AIX On Windows Configuring BMR Clients Configuring UNIX Clients Configuring Windows Clients Backing Up BMR Clients 43

66 General Client Installation Requirements General Client Installation Requirements General Requirements for BMR Installation on Clients For UNIX clients, you must be the root user to perform the BMR client installation tasks. For Windows clients, you must be the administrator to perform the BMR client installation tasks. Verify the minimum system requirements, as described in Specifications on page 270. Before installing the BMR software, you must install the NetBackup client software and configure the NetBackup clients. Each BMR client must have the BMR client software installed and the client NetBackup configuration must be modified to support BMR. Before a BMR restore can be performed successfully, all the client files must be backed up and the client configuration must be saved. In order to capture the client s current machine configuration, the client configuration must be saved before every client backup. Caution If the client configuration is not saved, the client cannot be restored by BMR. Caution On the NetBackup server that backs up your BMR client, the NetBackup policy that includes the BMR client must have Collect true image restore information/with move detection (TIR) enabled. Caution By default, bmrsavecfg will be run from the bpstart_notify script. If the time required to run bmrsavecfg exceeds the backup start notify timeout (default is 300 seconds), the backup will fail. This timeout should be set to at least 30 seconds longer than the TCP timeout of the client (normally around 300 seconds) in case the BMR client cannot connect to the BMR server. See the NetBackup System Administrator s Guide for details on how to set the backup start notify timeout. Port Usage for BMR Client/Server Communication The BMR servers use the port you define during setup to listen for requests made by BMR clients or other BMR servers. The default port used for communication to BMR servers is VERITAS Bare Metal Restore System Administrator s Guide

67 Upgrading from Bare Metal Restore 4.5 The default port used for connecting to the BMR GUI is 80. BMR file servers with SAMBA installed listen on the netbios-ssn (139) and netbios-ns (137) ports. These services are used by BMR Windows clients during a BMR restore. BMR file servers supporting UNIX clients run NFS, which uses portmapper (111), nfsd (2049), mountd, lockd, and statd. The latter three daemons use unreserved ports. These services are used by BMR UNIX clients during a BMR restore. BMR boot servers provide bootp (67 and 68), tftp (69), and bootparam (Solaris only) support to booting BMR clients. Upgrading from Bare Metal Restore 4.5 You can install Bare Metal Restore 4.6 as a brand new installation, or you can upgrade your existing Bare Metal Restore 4.5 installation. Upgrades from Bare Metal Restore versions prior to BMR 4.5 are not supported. It is not required to upgrade 4.5 clients. However, we advise that you upgrade the clients to BMR 4.6 when it is convenient. Deletions Resulting from Upgrade Installation Performing an upgrade from BMR 4.5 to BMR 4.6 deletes the following Bare Metal Restore configuration components: All created Shared Resource Trees Only the database entries are removed, but not the directories where the Shared Resource Trees are created. You must manually remove those directories. All created packages All created boot images All created media boot images You must recreate all Shared Resource Trees, packages, boot images, and media boot images for use with your BMR 4.6 installation. Note To recreate SRTs, packages, boot images, and media boot images that work with your BMR 4.6 server, you will need at least one Bare Metal Restore 4.6 client for each platform in your environment. If the Prepare to Restore step has been performed on any BMR clients, this step must be repeated after the above components have been created with the BMR 4.6 system. Chapter 3, BMR Client Installation and Configuration 45

68 Installing BMR Clients Upgrade Installation Procedure The procedure for upgrading your BMR clients from version 4.5 to version 4.6 is the same as for an initial installation, with one exception. During a Solaris client upgrade installation, you will use a different command string for pkgadd. This difference will be noted in the Solaris installation procedure, below. Use the instructions in the following section, Installing BMR Clients, to perform your initial or upgrade installation. Installing BMR Clients Refer to Bare Metal Restore Components on page 17, and Deployment Planning Resources on page 269 to determine platform requirements. The following sections provide client installation procedures according to platform: HP-UX on page 46. Solaris on page 47. AIX on page 48. Windows on page 49. HP-UX To install the BMR client on HP-UX using swinstall 1. Insert the BMR distribution CD into the CD-ROM drive. 2. Check for the running PFS daemons: ps -ef grep pfs 3. If the PFS daemons are not running, start them: pfs_mountd& pfsd 6& 4. Create a mount point: mkdir /bmr_cdrom Note To find the device path name run: ioscan -nfkc disk 46 VERITAS Bare Metal Restore System Administrator s Guide

69 Installing BMR Clients 5. Mount the CD-ROM using the following command: pfs_mount -o xlat=unix <cdrom device path> /bmr_cdrom 6. From the root directory, install the BMR client software using this command: swinstall -s /bmr_cdrom/hp BareMetal.client 7. Unmount the CD-ROM drive: pfs_umount /bmr_cdrom 8. Clean up the installation of BMR: rm -r /bmr_cdrom 9. When the BMR client software is installed, you must configure the client using bmrsetupclient, as explained in Configuring BMR Clients on page 53. Solaris To install the BMR client on Solaris using pkgadd Note Make sure vold is running. If vold is not running, the CD-ROM will not be mounted automatically. To start manually: /etc/rc2.d/s92volmgt start 1. Insert the BMR distribution CD into the CD-ROM drive. 2. Enter the following command, noting the difference for an initial installation and an upgrade installation. For an initial installation: pkgadd -d <pathname> BMRclient where <pathname> is the path to the Solaris distribution directory on the CD. For an upgrade installation: pkgadd -a <pathname>/sol/upgrade_admin -d <pathname>/sol BMRclient where <pathname> is the directory where the CDROM is mounted. 3. After the BMR client software is installed, you must configure the client using bmrsetupclient as explained in Configuring BMR Clients on page 53. Chapter 3, BMR Client Installation and Configuration 47

70 Installing BMR Clients AIX The menu driven utility, smitty, uses the installp command to install software in the AIX environment. While you can use the installp command to install the BMR client, we recommend using smitty to install the BMR client. To install the BMR Client on AIX Using smitty 1. If you are installing BMR from the distribution CD, make sure that the client machine s CD-ROM drive is properly mounted. Otherwise, copy the BMR distribution file, BareMetal, to a temporary location. 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 one of the following: the BareMetal distribution file the device name of the CD-ROM drive (/dev/cd0) 4. Press Return. The Install and Update from Latest Available Software screen redisplays. 5. While on the SOFTWARE to install option, press F4. 6. Using the arrow keys, move the selection bar to Bare Metal Restore for AIX - Client and press F7. 7. Press Return three times to confirm the changes and exit to the main menu. 8. To exit smitty press F After the BMR client software is installed, you must configure the client using bmrsetupclient, as explained in Configuring BMR Clients on page 53 of this manual. 48 VERITAS Bare Metal Restore System Administrator s Guide

71 Installing BMR Clients To install the BMR client on AIX using installp 1. If you are installing BMR from the distribution CD, make sure that the client machine s CD-ROM drive is properly mounted. Otherwise, copy the BMR distribution file BareMetal to a temporary location. 2. Enter the following command: installp -acxd <pathname> BareMetal.client where <pathname> is the path to the BareMetal distribution file or the device name of the CD-ROM drive (for example, /dev/cd0). 3. When the BMR client software installation is complete, configure the client using bmrsetupclient, as explained in Configuring BMR Clients on page 53 of this manual. Windows BMR for Windows supplies wizards to make installation and configuration easier. You can use the BMR Windows InstallShield wizard to install your BMR Windows clients. To install the BMR client on Windows 1. Insert the 4.6 CD-ROM. If autorun is set, the launcher screen is automatically started. If autorun is disabled, open the CD with Windows Explorer and double click launch.exe. Chapter 3, BMR Client Installation and Configuration 49

72 Installing BMR Clients For an initial installation, the following screen displays: Click Bare Metal Restore Client Installation to begin the installation process. If BMR 4.5 is detected, the following screen displays for an upgrade installation: Click Bare Metal Restore Client Upgrade to begin the installation process. 2. The InstallShield Wizard automatically begins the installation process. 50 VERITAS Bare Metal Restore System Administrator s Guide

73 Installing BMR Clients The InstallShield Wizard displays: 3. Click Next. The Destination Folder screen displays: 4. Check the default destination folder: To install to the default folder, click Next. To install in a different folder, click Change, select a destination folder, then click Next. Chapter 3, BMR Client Installation and Configuration 51

74 Installing BMR Clients The InstallShield Wizard begins. The status bar displays the install progress: When installation is complete the InstallShield Wizard Completed screen displays: Note You can choose to run the BMR Setup Wizard immediately by checking the Run Setup Wizard box, or choose to run it later by un-checking the box before you click Finish. For an explanation of the Setup Wizard, see Configuring Windows Clients on page Click Finish. The BMR client is installed. 52 VERITAS Bare Metal Restore System Administrator s Guide

75 Configuring BMR Clients When the BMR client software installation is complete, configure the client using the Setup Wizard as explained in Configuring Windows Clients on page 55. Configuring BMR Clients After you have installed and configured the BMR servers, and installed the BMR client software, you must configure the BMR clients. Note Before configuring any BMR client, you must specify to the BMR main server the fully qualified hostname and all IP addresses for the client s NetBackup server. During client configuration, if a client tries to register a NetBackup server that is not defined in the BMR main server, client configuration will fail. See Adding and Configuring NetBackup Servers on page 41 for details. BMR provides tools that perform client configuration. The following sections explain the procedures for using these tools: Configuring UNIX Clients Configuring Windows Clients Configuring UNIX Clients The bmrsetupclient program configures a UNIX BMR client. This command must be run while logged in as the root user. 1. Change the current directory to the BMR directory: For HP-UX: /opt/baremetal For Solaris: /opt/baremetal For AIX: /usr/lpp/baremetal 2. Enter the following command:./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: Chapter 3, BMR Client Installation and Configuration 53

76 Configuring BMR Clients a. Enter BMR server s IP hostname that resolves to an IP address usable for routine BMR communications: b. Enter the BMR server port number [8362]: c. If bpstart_notify does not already exist, the following prompt appears: The BMR command bmrsavecfg must be run before each backup of this system. The NetBackup client will run a bpstart_notify script from /usr/openv/netbackup/bin. Automatically generate bpstart_notify script? [y] If you answer with a n you see the following prompt:!!! You must now create /usr/openv/netbackup/bin/bpstart_notify If bpstart_notify does already exist, the following prompt appears: The BMR command bmrsavecfg must be run before each backup of this system. 1. The NetBackup client runs bpstart_notify (found in /usr/openv/netbackup/bin). 2. You must manually modify the bpstart_notify script to contain: /currentdirectory/bmrsavecfg > /var/bmr/log/bmrsavecfg.log 2>&1 I understand that I must make this modification manually.[n] In the example above, currentdirectory is as follows: For HP-UX: /opt/baremetal For Solaris: /opt/baremetal For AIX: /usr/lpp/baremetal bmrsetupclient verifies with the BMR main server that the NetBackup server the BMR client uses for its backup is defined (known) to the BMR main server. If the NetBackup server that the client uses is not defined to the BMR main server, bmrsetupclient will fail. If that happens, add the client s NetBackup server to the BMR main server using the procedure, Adding and Configuring NetBackup Servers on page VERITAS Bare Metal Restore System Administrator s Guide

77 Configuring BMR Clients Once this information is entered, bmrsetupclient indicates that it is running bmrsavecfg for the first time. When completed, the machine is completely configured as a Bare Metal Restore client. Once Bare Metal Restore is installed on the BMR clients, you can view, configure, or modify the configuration using the BMR graphical user interface or the bmrconfig command. Configuring Windows Clients The Bare Metal Restore Setup Wizard follows automatically from the InstallShield Wizard if you choose to continue with the configuration process at the time of installation (step 2 below). If you choose to complete the configuration process later, you can use the Start menu (step 1 below). To configure the Windows BMR client 1. From the Start menu, click Programs > Bare Metal Restore > Setup Client. Note The VERITAS Bare Metal Restore menu is only available from the Start menu of the Administrator user. Chapter 3, BMR Client Installation and Configuration 55

78 Configuring BMR Clients The Setup Wizard begins. This wizard helps you register your Windows client with a BMR main server. The Setup Wizard Welcome screen displays: 2. Click Next. The BMR Server Information screen displays. In Bare Metal Restore Main Server Name, enter the name of the computer (resolvable to an IP address) that will be the BMR main server for this client. In Bare Metal Restore Main Server Port, enter the port on which the BMR main server will be listening. By default, this is VERITAS Bare Metal Restore System Administrator s Guide

79 Configuring BMR Clients 3. Click Next. The Service Pack Option screen displays (for Windows NT clients only). Service Pack Required is checked by default. If you have adequate space, we recommend accepting the default so that you have the option to use a service pack if it becomes necessary. 4. Click Next. The BMR Client Registration screen displays. BMR client registration occurs automatically. The wizard indicates completion of the automatic steps by displaying check marks next to completed items. The program stops at Run Create SRT Wizard, and the Create a Shared Resource Tree Now? screen displays. a. To create an SRT later, click Create Later. The client setup wizard continues, but you can create an SRT later as explained in Creating a Shared Resource Tree (SRT) on page 61. Chapter 3, BMR Client Installation and Configuration 57

80 Configuring BMR Clients b. To create an SRT now, click Create Now. The screen, Create a New Shared Resource Tree (SRT) displays. Go to Creating a Shared Resource Tree (SRT) on page 61 for details on the Create SRT wizard. 5. The boot floppy creation process follows automatically after the Create an SRT process. The Create a Boot Floppy? screen displays: a. To create a boot floppy later, click Create Later. The setup wizard continues, but you can create a boot floppy later as explained in Creating Boot Images (Floppies) for Windows Clients on page 98. b. To create a boot floppy now, click Create Now. The screen, Boot Floppy Option displays. Go to Creating Boot Images (Floppies) for Windows Clients on page 98 to continue with the boot floppy creation process. When all the steps in the setup wizard are complete, the client is registered with the BMR main server. 6. An information window displays that the client was successfully registered, and reminds you to perform one complete system backup from the NetBackup server. As part of the registration, BMR attempted to create and modify the bpstart_notify.bat file. The bpstart_notify.bat change is a very important step that allows the configuration of the BMR client to be updated every time a backup is performed. Without this synchronization between the NetBackup server and the BMR main server, the BMR restores will fail. If BMR was successful in creating and modifying bpstart_notify.bat, the following information window will display: 58 VERITAS Bare Metal Restore System Administrator s Guide

81 Configuring BMR Clients Click OK. Proceed to step 7. Note Remember that you must make at least one complete system backup before a system restore can take place. If BMR was not successful in creating and modifying bpstart_notify.bat, the following information window will display: Click OK. Make the following manual changes: a. Look in the NetBackup\bin directory (usually C:\Program Files\Veritas\NetBackup\bin) for the file bpstart_notify.bat. b. If the file exists, right click the file and choose Edit from the menu. The file opens in Edit mode. Add the next two lines exactly as shown (including double quotes), where [BMRDIR] is the BMR installation Off [BMRDIR]\bmrsavecfg.exe -background c. If the file does not exist, open a common text editor and create a text file with the two lines displayed in step b, above. Save the file as bpstart_notify.bat in the NetBackup bin\directory. It is very important to save the file as plain text. It should not have a.txt extension. Chapter 3, BMR Client Installation and Configuration 59

82 Backing Up BMR Clients 7. The final check mark displays on the BMR Client Registration screen. When the process is completed, the Finish button becomes active (black). Click Finish. The BMR client is successfully configured. Once Bare Metal Restore is installed on the BMR clients, you can view, configure, or modify the configuration using the BMR graphical user interface or the bmrconfig command. Backing Up BMR Clients After you have installed and configured the BMR clients, you should run a full backup of each client. Until the client configuration is saved and a full backup is performed, BMR will not be able to restore the client. To save a UNIX client configuration, run the bmrsavecfg command. To save a Windows client configuration, from the Start menu, click Programs > Bare Metal Restore > Save Configuration. Client backups must be performed with Collect true image restore information/with move detection (TIR) enabled. For this reason, you must perform the backup from the NetBackup server, using a policy that has True Image enabled. For details on performing manual client backups from the NetBackup server, see your NetBackup System Administrator s Guide. 60 VERITAS Bare Metal Restore System Administrator s Guide

83 Creating a Shared Resource Tree (SRT) 4 The BMR Shared Resource Tree (SRT) serves two important purposes in BMR system configuration and BMR client restore: It provides the resources needed to build the boot images for the BMR clients. During the client restore process, it provides the executables and utilities needed to reformat the drives, re-build the file systems, and restore the files using the NetBackup client software. This chapter explains the function of an SRT, and describes the process for creating SRTs for your BMR clients. You can find this information in the following sections: Understanding the Shared Resource Tree BMR File Server SRT Considerations Creating a Shared Resource Tree Creating a CD-Based SRT Configuring SRTs from the BMR GUI 61

84 Understanding the Shared Resource Tree Understanding the Shared Resource Tree After you have installed and configured the BMR servers and BMR clients, the next step in preparing your BMR system to perform restores is creating shared resource trees (SRTs) for your BMR clients. The SRT is a compilation source of baseline system resources, including the means to restore all system files. When you create an SRT, you add to it all the resources a client machine needs to reformat drives, rebuild file systems, and restore the files using the NetBackup client software. In addition, you will use the SRT to create the boot image that the client uses to start the restore process. See Creating Boot Images and Boot Media on page 93. The BMR file server(s) holds the shared resource trees (SRTs) for the BMR clients. Although the basic function of the SRT is the same regardless of client type, the UNIX and Windows BMR clients differ in the way they use and access the SRT. UNIX - 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 - The Windows operating system must 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 Windows BMR client. The Windows SRT exists on a UNIX BMR file server, and provides the installation images for Windows, the BMR client executables, the NetBackup 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 via the SMB protocol. The complete restore 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. An SRT is required to perform a restore. Approximately 300 MB is needed to create an SRT for UNIX BMR client. Approximately 350 MB is needed to create an SRT for a Windows BMR client. Creating an SRT typically takes up to 30 minutes, but can take longer on slower systems. SRT Components When you create a client SRT, you will need to have the following: Platform-appropriate operating system install image on CD-ROM, or a local (for AIX, non-nfs) copy. VERITAS NetBackup 3.4.X (or later) install CD-ROM or image copy. 62 VERITAS Bare Metal Restore System Administrator s Guide

85 BMR File Server SRT Considerations Other VERITAS applications (such as VERITAS Volume Manager or VERITAS File System) as applicable. You must include the operating system install image so that the client can NFS-mount or install the appropriate OS after booting. The BMR client then uses the NetBackup client software to automatically restore all system files from the NetBackup server. Third Party Disk Device Driver and Volume Manager BMR can handle a variety of different client restores 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 restore. 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 Shared Resource Tree Worksheet on page 285, 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. Network SRTs vs. CD-Based SRTs You create the SRT for a BMR client on the BMR fileserver. Under normal circumstances, the client would access the SRT, at restore time, through NFS or SAMBA for Windows clients. However, in the case of catastrophic failure, it may be necessary to provide the SRT to the BMR client without a network interface. In that case, you must have access to a CD-based SRT. For details on creating a CD-based SRT from the SRT you create on the BMR file server, see Creating a CD-Based SRT on page 80. BMR File Server SRT Considerations As explained above, a BMR client must have access to the SRT at restore time. In addition, the BMR main server must have access to the SRTs if the file server resides on a different machine from the BMR main server. The BMR main server uses NFS to access all SRTs. To enable BMR client access to an SRT at restore time, the SRT directory must be exported on the BMR file server. The exporting step takes place when the BMR administrator prepares the client for restore. To prevent unscrupulous users from exporting arbitrary directories from BMR, SRTs are only allowed to be created in certain safe-to-be-exported directories. The Prepare to Restore function ensures that only the appropriate directories are exported. The SAMBA configuration exerts a similar control over Windows SRTs. Chapter 4, Creating a Shared Resource Tree (SRT) 63

86 BMR File Server SRT Considerations The /var/bmr/etc/exports File The names of directories where SRTs may be created and exported are stored in the /var/bmr/etc/exports file. The server configuration command bmrsetupserver creates this directory when it runs on the BMR file server. By default, the only entry in the file is /export/srt. This means that SRTs are allowed to be created only in the /export/srt directory, and only subdirectories of /export/srt are exportable to the BMR clients via NFS or SAMBA share. Note that only /export/srt/* is allowed for export, not /export/srt/*/*. bmrcreatesrt Default Path bmrcreatesrt is the BMR utility that will help you create an SRT. During SRT creation, bmrcreatesrt looks at /var/bmr/etc/exports and uses the first valid path in the file as the default base for the SRT path. If the first valid entry in your /var/bmr/etc/exports file were /var/bmr/srts, and your SRT were named MySRT, the bmrcreatesrt prompt would show that your created SRT would be /var/bmr/srts/mysrt. You can specify another path for your new SRT, but the base name of the path must exist in your /var/bmr/etc/exports file. If the path name does not appear in the exports file, bmrcreatesrt displays an error message. Note Shared resource trees contain symbolic links. Do not perform recursive file permission or ownership changes on SRT directories. (chown -R bmradmin <SRTdir>) Edit the /var/bmr/etc/exports File You can add additional directories to the list, or change the default entry, by editing the file /var/bmr/etc/exports. Below are some format considerations to keep in mind when editing the /var/bmr/etc/exports file: Use # to introduce comments. Everything following # on the same line is ignored. Each directory entry (path) must be on a separate line. Blank lines are allowed. Do not include spaces in pathnames. 64 VERITAS Bare Metal Restore System Administrator s Guide

87 BMR File Server SRT Considerations Note Use caution when adding entries to this file. All subdirectories of the specified paths are allowed to be exported. /home would be an insecure path to add, because it allows a BMR client to export any user s home directory. Instead, create a new directory in /home, such as /home/extra, and add /home/extra to the /var/bmr/etc/exports file. Ensure that the /var/bmr/etc/exports file has appropriate permissions set. Typically, you will want to restrict read/write access to the BMR administrator group, and prevent anyone else from reading this file. Chapter 4, Creating a Shared Resource Tree (SRT) 65

88 Creating a Shared Resource Tree Creating a Shared Resource Tree The procedure for creating an SRT varies with the platform and configuration of the BMR client. The sections below provide these procedures, as well as examples and special considerations: Creating an SRT for AIX on page 66 Creating an SRT for Solaris on page 67 Creating an SRT for HP-UX on page 75 Creating an SRT for Windows on page 77 You will need approximately 300 MB (350 for Windows) and roughly 30 minutes to create an SRT. Creating an SRT for AIX You will need the following resources on hand to create an AIX SRT: AIX operating system CD-ROM or local (non-nfs) copy of same for AIX install images. VERITAS NetBackup 3.4.X (or later) install CD or images. Caution The AIX SRT must be created in a JFS filesystem. Using other filesystems might result in fatal errors. To create an AIX SRT on the BMR file server 1. Change the current directory to: /usr/lpp/baremetal 2. Enter the following command:./bmrcreatesrt The following is an example of the kind of information the system asks for when bmrcreatesrt runs. Some details of the interaction depend on the operating system level and the version installed: a. SRT name: 1423t_420_31nbu Naming rules require that you include no spaces in the SRT name. b. SRT location [/export/srt/1423t_420_31nbu]: 66 VERITAS Bare Metal Restore System Administrator s Guide

89 Creating a Shared Resource Tree c. SRT operating system level 41, 42, 43 or 51: 42 d. Source of AIX install images [/dev/cd0]: Note This step requires some time. The prompts will then continue. e. Source of the VERITAS NetBackup install images [/dev/cd0]: Enter the name of the CD-ROM device where the NetBackup install CD is inserted and press Enter. The VERITAS client installation procedure follows normally. When asked for a NetBackup server and client name, any dummy non-blank values can be used; they are replaced at restore time with the correct values for the BMR client being restored. You may see the following message during this step. This error message is unimportant and can be ignored. Send a SIGHUP so inetd will reread its inetd.conf file. Could not load program /bin/ps: Symbol resolution failed for ps because: Symbol wlm_getclassname (number 71) is not exported from dependent module /unix. Examine.loader section symbols with the dump -Tv command../cp_to_client[398]: kill: bad argument count The following prompt displays after you complete the VERITAS client installation. f. Additional fileset name: Enter the names of any additional filesets you may want to install into the SRT. If none, press Enter. Creating an SRT for Solaris You will need the following resources on hand to create a Solaris SRT: Solaris operating system boot CD-ROM or image such as online copies of slice 0 or existing SRTs. Note Solaris 8 should use the Software 1 of 2 CD. VERITAS NetBackup 3.4.X (or later) install CD or images. Install images for VERITAS Volume Manager and VERITAS File System, if required. Any patches for VERITAS Volume Manager, if required. Chapter 4, Creating a Shared Resource Tree (SRT) 67

90 Creating a Shared Resource Tree Note If Volume Management (vold) is running and you are installing from CDs, you will need an additional window for ejecting the installation CDs. Version Considerations If some clients have different versions of VERITAS Volume Manager (VxVM) and/or VERITAS File System (VxFS), you need to create different SRTs to support those version levels: the version of VxVM and VxFS in the SRT must exactly match that of the client being restored. However, SRTs with VxVM and VxFS can also be used to restore clients that do not have VxVM or VxFS installed. Solaris 2.6 SRTs restore only Solaris 2.6, but Solaris 7 or Solaris 8 SRTs restore either Solaris 7 or 8 clients as long as the OS CD supports the client platform. So, if you have: Solaris 7 client with VERITAS Volume Manager 3.1, Solaris 8 client with VERITAS File System 3.3.3, and Solaris 7 client without any VERITAS software at all, all three could be restored with a single SRT: either Solaris 7 or 8, containing both VERITAS Volume Manager 3.1 and VERITAS File System On the other hand, if you have: a. Solaris 2.6 client with VERITAS Volume Manager 3.1, b. Solaris 7 client with VERITAS Volume Manager 3.1 and VERITAS File System 3.4, and c. Solaris 8 client with VERITAS Volume Manager 3.1 and VERITAS File System 3.3.3, you would need three SRTs: Solaris 2.6 SRT with VERITAS Volume Manager 3.1 (to restore a), Solaris 7 or 8 SRT with VERITAS Volume Manager 3.1 and VERITAS File System 3.4 (to restore b), and Solaris 7 or 8 SRT with VERITAS Volume Manager 3.1 and VERITAS File System (to restore c). 68 VERITAS Bare Metal Restore System Administrator s Guide

91 Creating a Shared Resource Tree To create a Solaris SRT on the BMR file server 1. Change the current directory to: /opt/baremetal 2. Enter the following command:./bmrcreatesrt The following is an example of the information the system asks for when bmrcreatesrt runs: a. SRT name [sol58srt]: Naming rules require that you include no spaces in the 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 [/export/srt/sol58srt]: d. Enter a [hostname:/]pathname containing a suitable Solaris 2.X boot CD-ROM or SRT image [/cdrom/cdrom0/s0]: Note This step requires some time. The prompts will then continue. e. You have the option to install the VERITAS NetBackup client software or the NetBackup server software into the SRT. SRTs that contain the server software can be used to restore media servers as well as non media servers. SRTs that contain the client software can only be used to restore non media servers. If this SRT is to be used to restore media servers, you must install the VERITAS NetBackup server software into the SRT, and you need the VERITAS NetBackup server software for Solaris to do so. You will see the following prompt: Do you want to install the VERITAS NetBackup server software [y/n]: Answer Y if you intend to use this SRT to restore media servers. If you answer Y, refer to Creating a Media Server Shared Resource Tree on page 223 for additional details on installing NetBackup server software into an SRT. Note Whether you answer Y or N, refer to the NetBackup documentation for any Solaris package or patch requirements, and remember to install those packages or patches into the SRT when prompted below. The SRT may not be functional if the Solaris packages or patches required by NetBackup are not installed into the SRT. This could result in failed restores. Chapter 4, Creating a Shared Resource Tree (SRT) 69

92 Creating a Shared Resource Tree f. Enter a [hostname:]/pathname containing VERITAS NetBackup [server/client] software: Enter the name of the CD-ROM device where the NetBackup install CD is inserted and press Enter. g. Enter a patch or package name to install additional software in SRT, or nothing if done: For a client that has VERITAS File System or Volume Manager installed on Solaris 2.6 and Solaris 7 or 8, refer to Installing Additional VERITAS Software into a Solaris SRT on page 70 (below). If neither product is installed on the BMR client, skip this section. Installing Additional VERITAS Software into a Solaris SRT If your Solaris BMR client has additional VERITAS software applications, such as VERITAS File System and VERITAS Volume Manager, you will also need to install these applications into the SRT for that client. To include this additional software, you must: 1. Identify all the additional software components that are required and install them in the appropriate order. Verify before installing any patches that the patchadd -C flag is honored for that patch. If the flag is not supported, damage to files on the BMR File Server may result. This is due to an issue with patchadd -C and patches that do not honor the -C flag, whether used with BMR SRTs on BMR File Servers, or JumpStart miniroots on JumpStart servers. There is code in bmrcreatesrt that prevents any potential damage for the pkgadd -R flag, but not for the patchadd -C flag. However, manual use of patchadd -C or patchadd -R with patches that do not honor the -C or -R flags, and pkgadd -R with packages that do not honor the -R flag should all be avoided whether using BMR, JumpStart, or NFS root file systems for the same reasons. Note In order to restore a client using VERITAS Volume Manager and/or File System, the same version(s) of Volume Manager and/or File System that ran on the restore client should be installed into the SRT. If the versions do not match, the restored client software will be unable to access the incorrectly configured file systems and volumes. For example, while an SRT with the base version of VERITAS Volume Manager 3.1 could not restore a client that used VERITAS Volume Manager (a different version), it can be used to restore a client that used VERITAS Volume Manager 3.1 patch 01 (a different patch level). The one exception to this has to do with patch levels. Most releases of patches for 70 VERITAS Bare Metal Restore System Administrator s Guide

93 Creating a Shared Resource Tree VERITAS Volume Manager or VERITAS File System typically do not support the patchadd -C flag, and should therefore be avoided. Testing has shown that clients using patched versions can successfully perform a restore, even when using an SRT that contains unpatched versions that have been installed into the SRT directly from base installation media. Never install a Sun patch that does not support the patchadd -C flag into a BMR SRT since this can cause damage to the file system of BMR file servers, JumpStart file servers, or other network based boot images. 2. Identify any prerequisites required by your needed packages. The following table outlines Solaris operating system patch requirements that are required if NetBackup server software is installed into a Bare Metal Restore SRT. Solaris OS Version Solaris 6 Solaris 7 Solaris 8 Patch Requirements for Installing NetBackup Server Software into BMR SRTs Requires Solaris patch or later. Note Patch has a dependency on patch Requires Solaris patch or later. Note Patch has a dependency on patch No patches are required. Chapter 4, Creating a Shared Resource Tree (SRT) 71

94 Creating a Shared Resource Tree The following table outlines special rules and considerations when using Bare Metal Restore along with VERITAS Volume Manager and/or VERITAS File System on Solaris operating systems. Note that the Solaris patches may already be installed on the Solaris OS CDs. If the Solaris CD date is earlier than that listed in the following table, the patches will have to be manually applied. Solaris OS Level VxVM/VxFS Levels Special Rules and Considerations Any Solaris version Any VRTS VxVM version prior to 3.2 with any version of VRTS VxFS prior to 3.5 This combination imposes special installation requirements, either: VRTS VxVM must be installed before VRTS VxFS or VRTSlic 1.0 (that comes with VRTS VxFS) must be installed first, then VRTS VxFS and VRTS VxVM can be installed in any order. Any Solaris version VRTS VxVM 3.2 with any version of VRTSvxfs prior to 3.5 This combination imposes special installation requirements. VRTSlic (that comes with VRTSvxvm 3.2) must be installed before VRTSvxvm and before VRTSvxfs. Then, VRTSvxvm and VRTSvxfs can be installed in any order. Do not use VRTSlic 1.0 that comes with VRTSvxfs with VRTSvxvm 3.2 or later. Any Solaris version VRTSvxvm 3.5 or VRTSvxfs 3.5 This combination imposes special installation requirements. SUNWadmfw (that comes with the Solaris OS installation CD) must be installed first. Then, VRTSvlic 3.0 (that comes with VRTSvxvm and VRTSvxfm) must be installed. Finally, VRTSvxvm and/or VRTSvxfs can be installed in any order. 72 VERITAS Bare Metal Restore System Administrator s Guide

95 Creating a Shared Resource Tree Solaris OS Level VxVM/VxFS Levels Special Rules and Considerations Solaris 2.6 versions earlier than 05/1998 Solaris 7 versions earlier than 11/1999 Solaris 8 versions earlier than 02/2002 Any version of VRTSvxvm Any version of VRTSvxvm VRTSvxvm 3.2 or VRTSvxvm 3.5 This combination requires the following Solaris patches to be applied: or its replacement, This combination requires the following Solaris patch to be applied: This combination requires the following Solaris patches to be applied: or its replacement The following gives an example for determining if the SRT that was created with the VRTSvxvm package for Solaris 7 includes the required patch 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 A typical output showing that a version of the patch is present looks like the following: Patch: Obsoletes: , , , , , , Requires: Incompatibles: Packages: SUNWcar, SUNWcar.2, SUNWcar.3, SUNWcar.4, SUNWcar.5, SUNWcsl, SUNWcsr, SUNWcsu, SUNWcvc, SUNWesu, SUNWipc, SUNWkvm, SUNWkvm.2, SUNWkvm.3, SUNWkvm.4, SUNWkvm.5, SUNWsxr, SUNWtoo From the output above you can see that patch version is already installed in this SRT. For patch 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. 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 requires Chapter 4, Creating a Shared Resource Tree (SRT) 73

96 Creating a Shared Resource Tree patches and 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 is already present but is not. So, you must download a version of patch (such as ) and check its prerequisites. Because patch version 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 fails and produces an error message that indicates patch 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. The following example details the steps required to install VRTSvxvm and VRTSvxfs into a Solaris 7 SRT. In the example, the SRT being built uses a version of the Solaris 7 CD that did not include any version of The patch can be downloaded from sunsolve.sun.com. Remember that if patch 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 require Note The first step in this procedure continues with the last step in Creating an SRT for Solaris on page 67. h. Enter a patch or package name to install additional software in SRT, or nothing if done: i. Enter a [hostname:]/pathname containing the patch image [ ]: /cdrom/cdrom0 j. Enter a patch or package name to install additional software in SRT, or nothing if done: k. Enter a [hostname:]/pathname containing the patch image: [ ]: /cdrom/cdrom0 74 VERITAS Bare Metal Restore System Administrator s Guide

97 Creating a Shared Resource Tree l. Enter a patch or package name to install additional software in SRT, or nothing if done: VRTSvxvm m. Enter a [hostname:]/pathname containing the VRTSvxvm package image [ ]: /cdrom/cdrom0 n. Enter a patch or package name to install additional software in SRT, or nothing if done: VRTSvxfs o. Enter a [hostname:]/pathname containing the VRTSvxfs package image [ ]: /cdrom/cdrom0 p. Enter a patch or package name to install additional software in SRT, or nothing if done: Creating an SRT for HP-UX You will need the following resources on hand to create an HP-UX SRT: HP-UX operating system installation CD-ROM Ignite 2.4 or 3.X install image VERITAS NetBackup 3.4 (or later) install image Note You must be logged in as the root user to run this procedure. To create an HP-UX SRT on the BMR file server 1. Change the current directory to: /opt/baremetal 2. Enter the following command:./bmrcreatesrt The following is an example of the information the system asks for when bmrcreatesrt runs: a. SRT Name: hpuxnbu Naming rules require that you include no spaces in the SRT name. b. SRT location [/export/hp11]: Chapter 4, Creating a Shared Resource Tree (SRT) 75

98 Creating a Shared Resource Tree c. SRT operating system level [11.00]: d. Location (device or path) of the Ignite installation media [/dev/dsk/c0t2d0]: BMR will search for the following directory: Ignite-UX/FILE-SRV-X-X/opt/ignite/data/Rel_B.X.X/BOSdatapath where X-X is either 10-20, 11-00, or 11-i and where X.X is either 10.20, 11.00, or 11i If the BOSdatapath is found, BMR expects the Ignite install image to be in one of the following directories (note that "-PA" indicates Ignite version B41). If not found, BMR will be unable to install Ignite. Ignite-UX/BOOT-KERNEL/opt/ignite/data Ignite-UX/BOOT-KERNEL/opt/ignite/boot Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data Ignite-UX/BOOT-KERNEL-PA/opt/ignite/boot If the BOSdatapath directory was not found, BMR will look for a file named INSTCMDS from the tar file supplied in one the following directories (note that "-PA" indicates Ignite version B41). If not found, BMR will be unable to install Ignite. Ignite-UX/BOOT-KERNEL/opt/ignite/data Ignite-UX/BOOT-KERNEL-PA/opt/ignite/data e. Location (device or path) of HP-UX X.Y install media [/dev/dsk/c0t2d0]: Where X.Y is the SRT operating system level. Otherwise, the files are copied from the BMR file server. f. If your version of Ignite requires a patch, you are prompted to provide the path to the specific patch version required, such as patch PHCO_ g. Source of the VERITAS NetBackup install images [/dev/c0t2d0]: Enter the name of the CD-ROM device where the NetBackup install CD is inserted and press Enter. The VERITAS client installation procedure follows normally. When asked for a NetBackup server and client name, any dummy non-blank values can be used; they are replaced at restore time with the correct values for the BMR client being restored. When all of this information is entered correctly, the SRT is created. 76 VERITAS Bare Metal Restore System Administrator s Guide

99 Creating a Shared Resource Tree Creating an SRT for Windows You will need the following Windows Server CD resources available to create a Windows SRT: To create Windows 2000 SRTs, use the Windows 2000 Professional CD, Windows 2000 Server CD, or the Windows 2000 Advanced Server CD. This SRT can be used to restore all Windows 2000 clients. Or, you can create separate SRTs for each Windows 2000 version. Windows 2000 OEM installation CDs are not recommended for creating an SRT, but will work in many cases. (It is not possible for us to verify all OEM CDs.) To create Windows NT SRTs, use the Windows NT Server CD. This SRT can be used to restore all Windows NT clients. Or, you can create separate SRTs for each Windows NT version. Windows NT OEM installation CDs are not recommended for creating an SRT, but will work in many cases. (It is not possible for VERITAS to verify all OEM CDs.) The NetBackup client executables are copied into the SRT from the Windows BMR client on which bmrcreatesrt is run. You do not need to have an install image for VERITAS NetBackup available when creating an SRT for a Windows BMR client. To create a Windows SRT on the Windows BMR client 1. From the Start menu, select Programs > VERITAS Bare Metal Restore > Create SRT. Chapter 4, Creating a Shared Resource Tree (SRT) 77

100 Creating a Shared Resource Tree The Shared Resource Tree Creation Wizard Welcome screen displays: 2. Click Next. The Shared Resource Tree Parameters screen displays: 3. In the New Shared Resource Tree Name field, enter a name to refer to this SRT. 4. From the Bare Metal Restore File Server list, select the machine configured as a BMR file server for Windows clients. 5. In the location field, enter the complete filepath of the install image location (i386). Alternatively, click Browse to search for the correct path. 78 VERITAS Bare Metal Restore System Administrator s Guide

101 Creating a Shared Resource Tree 6. In the Windows 2000 Product Key field, enter the Windows product key (including hyphens) in upper case letters. 7. Click Next. The program starts creating the SRT. A status screen displays. The status bar tracks the progress. This takes a few minutes. 8. If BMR is unable to write to the SAMBA share, the following screen displays: Do one of the following: To enable the user to specify a login ID and password to create the SRT on the specified host, click Yes. To return to the Create a New Shared Resource Tree (SRT) screen, click No. a. If you clicked Yes, the following screen displays: b. In the Connect As field, specify a username with permissions to create the SRT in the SAMBA share specified in the screen. c. In the Password field, enter a password. Chapter 4, Creating a Shared Resource Tree (SRT) 79

102 Creating a CD-Based SRT d. Click OK. If the login is successful, the creation of the Shared Resource Tree will resume, and the Creating an SRT, Please Stand By... status screen displays again. When the process is complete, this screen displays: 9. Click OK. The SRT creation is complete. Creating a CD-Based SRT The BMR media boot feature allows the client to use the resources included in the SRT from media (CD-ROM) instead of across the network. With a CD-based SRT, any client is able to read the files from a working CD-ROM drive rather than retrieving it from the file server. This feature will speed up the restore process and decrease network traffic at restore time. To use the media boot feature, you must create a CD-based SRT from a net-based SRT. The procedure to create the CD image differs between UNIX and Windows SRTs. In both cases, BMR provides software to create these CD images. For UNIX SRTs, BMR provides a tool called bmrmkcdimage. The bmrmkcdimage command creates a final CD image file, which can be burned onto a CD to make the CD bootable. Refer to: Creating a CD-based SRT for AIX on page 81 Creating a CD-based SRT for Solaris on page 82 Creating a CD-based SRT for HP-UX on page 84 For Windows SRTs, BMR provides a wizard called the Boot Options wizard. The Boot Options wizard prepares the SRT to be burned onto a CD. Refer to Creating a CD-based SRT for Windows on page 85 CD Creation Considerations Note The main consideration for burning an SRT CD-ROM is that the CD-ROM must be bootable for UNIX clients. Refer to the instructions provided with your CD burning software to discover the correct way to burn a bootable CD. 80 VERITAS Bare Metal Restore System Administrator s Guide

103 Creating a CD-Based SRT The image created by bmrmkcdimage for AIX and Solaris uses ISO format, short for ISO 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. If your BMR file server does not have the appropriate software, you may need to FTP the CD image from the BMR file server to another machine that has a 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 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. The details of burning ISO-9660 format CD-ROMs vary from one piece of CD burning software to another. Follow the vendor-supplied procedure for the software of your choice. Creating a CD-based SRT for AIX Use the following procedure to create a CD-based SRT for media boot. The prompts and answers in the procedure below are for example purposes, and may not appear on your machine exactly as they are presented here. To create a CD-based SRT for AIX 1. Create your SRT using the procedure Creating an SRT for AIX on page On the BMR file server (FS), cd to /opt/baremetal, and enter the following command:./bmrmkcdimage 3. Provide appropriate information to the following prompts: a. Enter the name of the SRT to use as the source: aix433esm b. Enter the name to use for the new SRT: aix433esmcd c. Enter the name to use for the new BI: aix433esmcdbi d. Enter a directory with 1400MB or more free space: /export/srt/mb. Chapter 4, Creating a Shared Resource Tree (SRT) 81

104 Creating a CD-Based SRT 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 /, /export, /export/srt, or /export/srt/aix433esm. Specifying /export/srt/mb would work because it is not a direct prefix of the SRT path. e. Enter the CD-ROM device name [/dev/cd0]: 4. Insert the AIX install CD into the CD-ROM drive. (Install CD version is dependent on SRT operating system level.) Note You must use a CD that has the same build date as the CD that was used to create the source SRT aix433esm. 5. Press Enter when ready (or Ctrl+C to quit). A series of 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 capable of creating a bootable CD-ROM. If there is no CD-RW drive on the computer where the SRT was created, you should FTP the image to a box where there is a CD-RW drive and burn the bootable CD-ROM on that box. 7. Label the CD for easy identification. For example, the following information could appear on the face of the CD: SRT name: aix433esmcd BI name: aix433esmbicd BMR file server: aixp9 Creating a CD-based SRT for Solaris Use the following procedure to create a CD-based SRT for media boot. The prompts in the procedure below are for example purposes, and may not appear on your machine exactly as they are presented here. This process is valid for the following two scenarios: VERITAS Volume Manager is not on the BMR file server. VERITAS Volume Manager is on the BMR file server. 82 VERITAS Bare Metal Restore System Administrator s Guide

105 Creating a CD-Based SRT To create a CD-based SRT for Solaris 1. Create your SRT as you would normally, using the procedure Creating an SRT for Solaris on page Check to see if vold is running on the BMR 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 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 CD-ROM device name [/dev/dsk/c0t2d0s2]: f. Insert Solaris CD into the CD-ROM drive. g. Press Enter when ready (or CTRL-C to quit)... For a Solaris SRT where VERITAS Volume Manager is not on the BMR file server, the following prompts appear: h. Enter the name of a partition of size or more blocks: /dev/dsk/c0t0d0s5 i. All data on /dev/dsk/c0t0d0s5 will be lost. Do you want to continue? y This is the last prompt for this scenario. Chapter 4, Creating a Shared Resource Tree (SRT) 83

106 Creating a CD-Based SRT For a Solaris SRT where VERITAS Volume Manager is on the BMR file server, the following prompt appears: j. Enter the name of a Disk Group with 51MB or more free space: rootdg This is the last prompt for this scenario. For all scenarios, after the last prompt a series of messages displays as the command progresses. When the command finishes, it displays the final CD image file name. 4. Burn the CD image onto a CD-ROM using conventional CD recording software. If there is no CD-RW drive on the computer where the SRT was created, you should FTP the image to a box where there is a CD-RW drive and burn the bootable CD-ROM on that box. 5. 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 file server: sol7tkg Creating a CD-based SRT for HP-UX Use the following procedure to create a CD-based SRT for media boot. The prompts in the procedure below are for example purposes, and may not appear on your machine exactly as they are presented here. To create a CD-based SRT for HP-UX 1. Create your SRT as you would normally using the procedure Creating an SRT for HP-UX on page On the BMR file server (FS) enter the following command:./bmrmkcdimage 3. Provide appropriate information to the following prompts: 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 84 VERITAS Bare Metal Restore System Administrator s Guide

107 Creating a CD-Based SRT 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 A series of messages display as the command progresses. When the command finishes, it displays the final CD image filename. 4. Burn the CD image onto a CD-ROM using conventional CD recording software capable of creating a bootable CD-ROM. If there is no CD-RW drive on the computer where the SRT was created, you can FTP the image to a box where there is a CD-RW drive and burn the bootable CD-ROM on that box. 5. Label the CD for easy identification. For example, the following information could appear on the face of the CD: SRT name: hp11esmcd BI name: hp11esmbicd BMR file server: hpp9 Creating a CD-based SRT for Windows After you create a Windows SRT as described in Creating a CD-based SRT for Windows on page 85, complete the following procedure to prepare the SRT for media boot. You must be on a BMR Windows client to perform this procedure. The BMR menu is available from the BMR Administrator login. To create a CD-based SRT for Windows 1. From the Start menu, select Programs > VERITAS Bare Metal Restore > Boot Options. Chapter 4, Creating a Shared Resource Tree (SRT) 85

108 Creating a CD-Based SRT The Boot Options Wizard Welcome screen displays: Read this screen to determine the media you will need to create your SRT. 2. Click Next. The Boot Options screen displays: 3. Select Prepare an SRT for Media Boot. This option prepares the SRT to be ready for BMR media boot. Such an SRT can be copied to a CD for use with BMR media boot. 86 VERITAS Bare Metal Restore System Administrator s Guide

109 Creating a CD-Based SRT 4. Click Next. The Media Boot Options screen displays: 5. Select an SRT from the Shared Resource Tree Name list. This is the SRT that will be prepared for BMR media boot. 6. Choose which clients to include. Click Include all clients to include all clients defined on the BMR main server. Click Select clients from file to specify the name of a file that contains the list of clients to be included. Use Browse to select the name of the file to be included. This file should be a plain text (.txt) list with the desired fully qualified configuration name for each client configuration, one configuration per line. A fully qualified configuration name consists of the client name, the NetBackup server name, the configuration state, and the configuration name. The following is an example list: w2k207,sol7esm,readonly,current w2k208,sol7esm,users,dsrconfig w2k209,sol7esm,readonly,current Chapter 4, Creating a Shared Resource Tree (SRT) 87

110 Creating a CD-Based SRT 7. 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: 8. Click OK. The SRT is now ready to be burned onto a CD-ROM for use with BMR media boot. 9. Burn 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. Note The machine that has the CD creation software must have access to the SRT directory on the BMR file server. 88 VERITAS Bare Metal Restore System Administrator s Guide

111 Configuring SRTs from the BMR GUI Configuring SRTs from the BMR GUI The SRT Configuration screen provides an interface for configuring the BMR file server hostname, the BMR file server IP address, and the BMR file server netmask. The SRT Configuration screen displays other important information related to the selected SRT, including the following: SRT Configuration Screen Fields Field Name Architecture OS OS Level Path State Version Type File Server Hostname File Server IP Address Netmask Description The name of the selected SRT. The SRT name is set when bmrcreatesrt is run. The hardware architecture for this SRT. The operating system of this SRT. The operating system version of this SRT. The path to this SRT. The current state of 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. The version of this SRT. The type of SRT. The variables for this field are as follows: nfs - net-based cdfs - CD-based The hostname of the BMR file server. The IP address of the BMR file server. The netmask of the BMR file server. Chapter 4, Creating a Shared Resource Tree (SRT) 89

112 Configuring SRTs from the BMR GUI SRT Configuration Screen Fields Field File Server Port Description The port number for the BMR file server. Modifying a Shared Resource Tree It may be necessary to modify an existing shared resource tree (SRT). Modify an SRT by completing the following instructions: 1. Click Shared Resource Trees in the navigation bar. The List of Shared Resource Trees screen displays: 2. Select the SRT you want to modify by clicking on the radio button to the left of the name in the Shared Resource Tree Name column. Click Edit. 90 VERITAS Bare Metal Restore System Administrator s Guide

113 Configuring SRTs from the BMR GUI The Shared Resource Tree Configuration screen for your selected SRT displays. This figure is an example of a Windows 2000 SRT: 3. Modify the desired fields from the following: File Server Hostname: the hostname of the BMR file server. File Server IP Address: the IP address of the BMR file server. Netmask: the netmask of the BMR file server. 4. When you have made the appropriate changes, click OK. The changes to the selected SRT are saved. Deleting a Shared Resource Tree Use this procedure to remove an SRT from the list. 1. Click Shared Resource Trees in the Navigation bar. A list of SRTs displays. 2. Select the SRT you want to delete by clicking the radio button to the left of the SRT name. 3. Click Delete. A confirmation screen displays. 4. Click OK. The selected SRT is deleted and BMR returns to the list of available SRTs. Chapter 4, Creating a Shared Resource Tree (SRT) 91

114 Configuring SRTs from the BMR GUI 92 VERITAS Bare Metal Restore System Administrator s Guide

115 Creating Boot Images and Boot Media 5 When you restore a BMR client after total system failure, the boot image provides the resources that allow the client to begin communicating with the BMR file server. The boot image associates a client with the appropriate SRT. Boot images are created from the SRTs that you created on the BMR file server. UNIX and Windows BMR clients differ in the way they access and use the boot images: UNIX BMR clients can access these boot images via the network, with the bootp or bootparam protocol. UNIX BMR clients can also boot from a CD-ROM. Windows BMR clients require that the boot image be available on floppy disk. This chapter explains boot images, and provides instructions for creating boot images. See the following sections for details: Understanding Boot Images Creating a Boot Image for a UNIX Client Configuring Boot Images from the BMR GUI Creating Boot Images (Floppies) for Windows Clients 93

116 Understanding Boot Images Understanding Boot Images The boot image is used to bring a system to a specific state where the SRT can be mounted and commands from the SRT can be run. It contains a small runtime environment that includes a kernel, a RAM file system, libraries, and programs. The system firmware will load the boot image from media or the network, then transfer control to the boot image kernel. It is important that the boot image is compatible with the commands and libraries in the SRT as well as commands and libraries restored from the client. Creating a Boot Image for a UNIX Client Once an SRT is created, a boot image associated with that SRT can be created at any time prior to client restore. Note In the following example, the SRT is from an AIX client. Therefore, the boot image is an AIX boot image. Solaris and HP-UX procedures are almost identical. There are no additional fields; however, some fields do not appear because they do not apply to those operating systems. Complete the following procedure on the BMR boot server. For most systems, this will be the same machine as the BMR file server. To create a boot image for a UNIX client 1. From the BMR GUI, click Shared Resource Trees. The List of Shared Resource Trees displays: 2. Click the radio button to the left of the SRT from which you wish to create a boot image. Confirm that the information for the SRT is correct as displayed in the list. Click Create Boot Image. 94 VERITAS Bare Metal Restore System Administrator s Guide

117 Creating a Boot Image for a UNIX Client The Create an AIX Boot Image screen displays: 3. Complete the fields on this screen as follows: a. Boot Image Name - the name of the created boot image b. Boot Server - the name of the BMR boot server c. Boot Server Port - the number of the boot server port specified when set up as a BMR server d. Boot Image Path - the directory path where the boot image will be created and reside e. Architecture - the system architecture for this boot image f. Processors - the type of processor for the system, either MP or UP g. NIC Type - the type of boot NIC, ether or token ring 4. When you have finished selecting your boot image definitions, click OK. Chapter 5, Creating Boot Images and Boot Media 95

118 Configuring Boot Images from the BMR GUI The boot image is created and the complete list of boot images is displayed: Configuring Boot Images from the BMR GUI The Configure Boot Image screen in the BMR GUI allows you to view important information related to the selected boot image. In addition to viewing the configuration of the boot images, you can also perform the following functions: Change boot image information, including BMR boot server hostname and BMR boot server IP address. Delete boot images you no longer need. To configure boot images from the BMR GUI 1. On the BMR navigation bar, click Boot Images. The List of Boot Images screen displays: 2. Select the name of the boot image you want to configure by clicking the radio button to the left of the name in the Boot Image Name column. Click Edit. 96 VERITAS Bare Metal Restore System Administrator s Guide

119 Configuring Boot Images from the BMR GUI The Boot Image Configuration screen displays: Modify the desired fields on the Boot Image Configuration screen. Boot Server Hostname Boot Server IP Address NetMask 3. Click OK. The changes to the selected boot image are saved. To delete a boot image 1. On the List of Boot Images screen, select the boot image you want to delete by clicking the radio button to the left of the name in the Boot Image Name column. 2. Verify that you have selected the correct boot image to delete. Click Delete. A confirmation screen displays: OK to delete this boot image? 3. Click OK. The selected boot image is deleted and BMR returns the list of available boot images. Chapter 5, Creating Boot Images and Boot Media 97

120 Creating Boot Images (Floppies) for Windows Clients Creating Boot Images (Floppies) for Windows Clients BMR Windows clients do not use a BMR boot server the way BMR UNIX clients do. With Windows clients, you create a boot image on the client, which you then save to a floppy disk to create a boot image floppy. Because only one floppy boot image is needed for all your BMR Windows clients, the boot image creation process pushes the boot image to the BMR main server so that other BMR clients can use it to create their boot floppies. After the initial boot image is pushed to the BMR main server, you must run the bmracceptfi command on the BMR main server. This will allow the other clients to use that boot floppy image when other boot floppies are created. BMR allows you to create three types of boot floppies to account for three possible restore scenarios: Restore via generic boot floppy, used with network based SRTs. The floppy is configured to work on any system with the brand and type of network card for which a DOS device driver is provided by the user. Use the following procedure: To create a generic network boot floppy for Windows on page 99 Restore via customized boot floppy, used with network-based SRTs. The customized network boot floppy requires no intervention once the restore begins. Note The customized boot floppy options configure the boot disk specifically for the client machine, so it cannot work on any other system. Use the following procedure: To create a customized network boot floppy for Windows on page 104 Restore via customized boot floppy, used with CD-based SRTs. The boot floppy is customized to use the BMR media boot feature. Use the following procedure: To create a custom media boot floppy for Windows on page 112 The following procedures demonstrate the process for creating boot floppies for the three scenarios. All three procedures take place on the BMR Windows client. 98 VERITAS Bare Metal Restore System Administrator s Guide

121 Creating Boot Images (Floppies) for Windows Clients For each procedure, use the Windows Start menu to evoke the Bare Metal Restore Boot Options wizard. Click Start > Programs > VERITAS Bare Metal Restore > Boot Options. Note The VERITAS Bare Metal Restore menu is available only from the BMR administrator s login. Generic Boot Floppy with Network-Based SRTs To create a generic network boot floppy for Windows 1. From the Start menu, click Programs > VERITAS Bare Metal Restore > Boot Options. The Boot Options Wizard Welcome screen displays: 2. Read the Welcome screen to determine the media requirements for creating the boot floppy, then click Next. Chapter 5, Creating Boot Images and Boot Media 99

122 Creating Boot Images (Floppies) for Windows Clients The Boot Options screen displays: 3. Click Create a Boot Floppy. Click Next. The Boot Floppy Option screen displays: 4. Click Generic. Click Next. 100 VERITAS Bare Metal Restore System Administrator s Guide

123 Creating Boot Images (Floppies) for Windows Clients The Specify Network Interface Card (NIC) Driver screen displays: 5. Enter the full path for the NDIS2 driver for the NIC card on the machine or click Browse to locate the file. These drivers are commonly available from the NIC install media or from the manufacturer s web site. 6. Click Next. The Optional SCSI Driver Information screen displays: This screen allows you to specify the full path to the DOS driver for any SCSI adapter that you have in your system. This driver is 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. If you do not have a SCSI adapter, or do not need the SCSI adapter to be available to restore the system, skip to step 7. If you do want to specify the DOS driver, enter an appropriate path in the Driver name field, and enter an appropriate value in the Optional initialization string field. Chapter 5, Creating Boot Images and Boot Media 101

124 Creating Boot Images (Floppies) for Windows Clients 7. Click Next. The Insert a Floppy screen displays: This screen displays a summary of all the information that has been entered. 8. 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. 9. Click Finish. The following prompt displays: 10. Insert a 1.44MB floppy into Drive A. The floppy can be formatted or unformatted. Caution All data on the floppy will be erased. 11. Click OK. 102 VERITAS Bare Metal Restore System Administrator s Guide

125 Creating Boot Images (Floppies) for Windows Clients The Create Boot Floppy Image screen displays: This screen appears if the BMR main server does not have a DOS boot floppy image, because either this is the first time one is created, or the bmracceptfi command has not been run. If you see this screen on a second client (after successfully creating a network boot floppy) then you must cancel, run bmracceptfi, and restart the wizard. 12. Specify the location of the MS Client 3.0 files and click Create. Status screens for four automated procedures related to creating the boot floppy image on the BMR main server display. 13. After the floppy image is created on the BMR main server you are reminded to run the bmracceptfi command on the BMR main server. bmracceptfi enables the newly created floppy image to be accessed by other BMR clients and others running the BMR Boot Options Wizard. 14. Click OK. The Creating Boot Floppy progress screen displays: Chapter 5, Creating Boot Images and Boot Media 103

126 Creating Boot Images (Floppies) for Windows Clients This screen shows the progress of the floppy creation process. The activity currently in progress is displayed in the Details area, with a progress bar indicating the overall progress. The following confirmation screen displays after the boot floppy is successfully created: 15. Click OK. The generic boot floppy is now ready for use. 16. Remove the floppy from the drive and label it. Refer to Network Restore With Generic Boot Floppy on page 155 for details on how to use generic boot floppies to restore a Windows client. Custom Boot Floppy with Network-Based SRTs To create a customized network boot floppy for Windows 1. From the Start menu, click Programs > VERITAS Bare Metal Restore > Boot Options. The Boot Options Wizard Welcome screen displays: 2. Read the Welcome screen to determine the media requirements for creating the boot floppy, then click Next. 104 VERITAS Bare Metal Restore System Administrator s Guide

127 Creating Boot Images (Floppies) for Windows Clients The Boot Options screen displays: 3. Click Create a Boot Floppy. Click Next. The Boot Floppy Option screen displays: 4. Select Customized. Click Next. Chapter 5, Creating Boot Images and Boot Media 105

128 Creating Boot Images (Floppies) for Windows Clients The Specify Network Interface Card (NIC) Driver screen displays: 5. Enter the full path for the NDIS2 driver for the NIC card on the machine or click Browse to locate the file. These drivers are commonly available from the NIC install media or from the manufacturer s web site. 6. Click Next. The Optional SCSI Driver Information screen displays: This screen allows you to specify the full path to the DOS driver for any SCSI adapter that you have in your system. This driver is 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. If you do not have a SCSI adapter, or do not need the SCSI adapter to be available to restore the system, skip to step VERITAS Bare Metal Restore System Administrator s Guide

129 Creating Boot Images (Floppies) for Windows Clients If you do want to specify the DOS driver, enter an appropriate path in the Driver name field, and enter an appropriate value in the Optional initialization string field. 7. Click Next. The Shared Resource Tree and File Server IP Information screen displays: 8. Select an SRT from the Shared Resource Tree Name list. BMR file server details are automatically displayed. You can change the addresses used to access the BMR file server at this time. 9. Click Next. The Client IP Information screen displays: 10. Complete the following fields with the correct information. Some information may be automatically displayed. Change it or supply it as necessary. Bare Metal Restore Client Name Bare Metal Restore Client Configurations NIC Description - NIC card found on the client. DHCP Enabled - Check if you want DHCP to be used at boot time. IP Address - IP address of the interface. Netmask - Netmask of the interface. Chapter 5, Creating Boot Images and Boot Media 107

130 Creating Boot Images (Floppies) for Windows Clients Default Gateway - Default gateway for this client. Slot Number - Slot number of the NIC card. For customized boot floppies used for Dissimilar System Restores, use care to ensure the slot number entered matches the target machine's definition of the NIC slot number. 11. Click Next. The extra Safety Prompt screen displays: Caution The BMR boot floppy destroys all existing partitions on the machine being restored. The optional Safety Prompt can prevent unintended erasure of the partitions. Opting for a safety prompt pauses the restore process before the irreversible portion of the restore process begins. A safety prompt can guard against accidentally booting from the floppy disk when the floppy disk is in the drive. 12. Click Add a Safety Prompt or Do NOT add a Safety Prompt, and click Next. The Create Special System Partition screen displays: 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: 108 VERITAS Bare Metal Restore System Administrator s Guide

131 Creating Boot Images (Floppies) for Windows Clients 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 storage manager 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. 13. If your BMR Windows client has a partition that is unreadable by Windows, click YES. Otherwise, click NO. 14. Click Next. The Insert a Floppy screen displays: This screen shows a summary of all the information that has been gathered and entered. 15. 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. 16. Click Finish. The following prompt displays: Chapter 5, Creating Boot Images and Boot Media 109

132 Creating Boot Images (Floppies) for Windows Clients 17. Insert a 1.44MB floppy into Drive A. The floppy can be formatted or unformatted. Caution All data on the floppy will be erased. 18. Click OK. The Create Boot Floppy Image screen displays: This screen appears if the BMR main server does not have a DOS boot floppy image, because either this is the first time one is created, or the bmracceptfi command has not been run. If you see this screen on a second client (after successfully creating a network boot floppy) then you must cancel, run bmracceptfi, and restart the wizard. 19. Specify the location of the MS Client 3.0 files and click Create. Status screens for four automated procedures related to creating the boot floppy image on the BMR main server display. 20. After the floppy image is created on the BMR main server you are reminded to run the bmracceptfi command on the BMR main server. bmracceptfi enables the newly created floppy image to be accessed by other BMR clients and others running the BMR Boot Options Wizard. 110 VERITAS Bare Metal Restore System Administrator s Guide

133 Creating Boot Images (Floppies) for Windows Clients 21. Click OK. The Creating Boot Floppy progress screen displays: This screen shows the progress of the floppy creation process. The activity currently in progress is displayed in the Details area, with a progress bar indicating the overall progress. The following confirmation screen displays after the boot floppy is successfully created: 22. Click OK. The custom boot floppy is now ready for use. 23. Remove the floppy from the drive and label it. Refer to Network Restore with Custom Boot Floppy on page 159 for details on how to use customized boot floppies to network restore a Windows client. Chapter 5, Creating Boot Images and Boot Media 111

134 Creating Boot Images (Floppies) for Windows Clients Custom Boot Floppy with CD-Based SRTs To create a custom media boot floppy for Windows 1. From the Start menu, click Programs > VERITAS Bare Metal Restore > Boot Options. The Boot Options Wizard Welcome screen displays: Read the Welcome screen to determine the media requirements for creating the boot floppy, then click Next. The Boot Options screen displays: 112 VERITAS Bare Metal Restore System Administrator s Guide

135 Creating Boot Images (Floppies) for Windows Clients 2. Click Create a Boot Floppy. Click Next. The Boot Floppy Option screen displays: 3. Click Customized for Media Boot. Click Next. The CD-ROM Driver Information screen 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 Use Default results in using the default driver (oakcdrom.sys), which should work with most ATAPI CD-ROM devices. CD-ROM device drivers are commonly available from the install media or from the manufacturer s web site. 4. Choose the appropriate CD-ROM driver by doing one of the following: Enter the full path name of the device driver file. Click Browse to browse and select the driver file. Chapter 5, Creating Boot Images and Boot Media 113

136 Creating Boot Images (Floppies) for Windows Clients Click Use Default. 5. Click Next. The Optional SCSI Driver Information screen displays: This screen allows you to specify the full path to the DOS driver for any SCSI adapter that you have in your system. This driver is loaded at restore time (with the optional initialization string) to make the SCSI adapter usable during the restore phase. These drivers are commonly available from the install media or from the manufacturer s web site. If you do not have a SCSI adapter, or do not need the SCSI adapter to be available to restore the system, skip to step 8. If you do want to specify the DOS driver, enter an appropriate path in the Driver name field, and enter an appropriate value in the Optional initialization string field. 6. Click Next. The SRT and File Server IP Information screen displays: 7. Select an SRT from the Shared Resource Tree Name list. BMR file server details are automatically displayed. 114 VERITAS Bare Metal Restore System Administrator s Guide

137 Creating Boot Images (Floppies) for Windows Clients 8. Click Next. The Select Client screen displays: 9. Complete the following fields with the correct information. Some information may be automatically displayed. Change it or supply it as necessary. Bare Metal Restore Client Name Bare Metal Restore Client Configurations NIC Description - NIC card found on the client DHCP Enabled - Check if you want DHCP to be used at boot time. 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. For customized boot floppies used for Dissimilar Disk Restores, use care to ensure the slot number entered matches the target machine's definition of the NIC slot number. 10. Click Next. The extra Safety Prompt screen displays: Caution The BMR boot floppy destroys all existing partitions on the machine being restored. The optional safety prompt can prevent unintended erasure of the partitions. Chapter 5, Creating Boot Images and Boot Media 115

138 Creating Boot Images (Floppies) for Windows Clients Opting for a safety prompt pauses the restore process before the irreversible portion of the restore process begins. A safety prompt can guard against accidentally booting from the floppy disk when the floppy disk is in the drive. 11. Click Add a Safety Prompt or Do NOT add a Safety Prompt. 12. Click Next. The Create special system Partition screen displays: 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: 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 storage manager 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. 13. If your BMR Windows client has a partition that is unreadable by Windows, click YES. Otherwise, click NO. 116 VERITAS Bare Metal Restore System Administrator s Guide

139 Creating Boot Images (Floppies) for Windows Clients 14. Click Next. The Insert a Floppy screen displays: This screen displays a summary of all the information that has been gathered and entered. 15. 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. 16. Click Finish. The following prompt displays: 17. Insert a 1.44MB floppy into Drive A. The floppy can be formatted or unformatted. Caution All data on the floppy will be erased. 18. Click OK. Chapter 5, Creating Boot Images and Boot Media 117

140 Creating Boot Images (Floppies) for Windows Clients The Create Boot Floppy Image screen displays: This screen appears if the BMR main server does not have a DOS boot floppy image, because either this is the first time one is created, or the bmracceptfi command has not been run. If you see this screen on a second client (after successfully creating a network boot floppy) then you must cancel, run bmracceptfi, and restart the wizard. 19. Specify the location of the MS Client 3.0 files and click Create. Status screens for four automated procedures related to creating the boot floppy image on the BMR main server display. 20. After the floppy image is created on the BMR main server you are reminded to run the bmracceptfi command on the BMR main server. bmracceptfi enables the newly created floppy image to be accessed by other BMR clients and others running the BMR Boot Options Wizard. 118 VERITAS Bare Metal Restore System Administrator s Guide

141 Creating Boot Images (Floppies) for Windows Clients 21. Click OK. The Writing Floppy Image progress screen displays: This screen shows the progress of the floppy creation process. The activity currently in progress is displayed in the Details area, with a progress bar indicating the overall progress. The following confirmation screen displays after the boot floppy is successfully created: 22. Click OK. The custom boot floppy is now ready for use. 23. Remove the floppy from the drive and label it. Refer to Media Restore with Custom Boot Floppy on page 163 for details on how to use customized boot floppies to restore a Windows client. Running bmracceptfi on the BMR Main Server During the execution of BootOptions.exe, a boot floppy image is created. This image is written onto the floppy to make it bootable. Only one floppy boot image is needed for all your BMR Windows clients. So, after the first time BootOptions.exe is run the boot floppy image is created and pushed onto the BMR main server. bmracceptfi is run on the BMR main server to allow the other clients to use that boot floppy image when other boot floppies are created. On the BMR main server, change the current directory to the Bare Metal Restore directory for your platform: For HP-UX: /opt/baremetal/ For Solaris: Chapter 5, Creating Boot Images and Boot Media 119

142 Creating Boot Images (Floppies) for Windows Clients /opt/baremetal For AIX: /usr/lpp/baremetal and enter:./bmracceptfi [Client Name] Where Client Name is the name of the BMR client that has successfully run BootOptions.exe. If the Client Name is not specified, the program prompts for a client name by displaying a list of all clients that have generated a boot image. 120 VERITAS Bare Metal Restore System Administrator s Guide

143 Restoring a BMR Client 6 Before you perform a BMR client restore, you must have already performed the following: Install and configure BMR servers and clients Perform a complete client backup, including: True image restore enabled on the NetBackup policy Move-detection enabled on the NetBackup policy bmrsavecfg run as part of backup process Create network or media-based SRTs and boot images Prepare boot floppies for Windows clients Prepare CD images for media boot clients Create packages such as Service Packs or Drivers for Windows clients If you experience a system failure, and want to restore your BMR client, follow the platform-specific instructions in the following sections: Modifying Client Configuration Note The procedure above applies only to restores to systems that have a different configuration than the client originally had. Preparing to Restore a Client Restoring a Client 121

144 Modifying Client Configuration Modifying Client Configuration To restore a client to the same or similar system, it is not necessary to modify the client configuration before performing the restore. Proceed to the next section, Preparing to Restore a Client on page 136. Bare Metal Restore allows you to restore a client to a system with a different hardware configuration than was present at the last backup. To facilitate such recoveries, Bare Metal Restore provides the ability to save multiple named configurations for each client. These configuration copies must be modified prior to performing the Prepare to Restore operation. The different scenarios in which you would need to modify the configuration prior to the Prepare to Restore step are as follows: Restoring a client to the same hardware but slightly different network properties. Restoring a Windows client that requires a Service Pack during installation or restore. Restoring a client to a state that was saved in a backup prior to the last backup. For details, see Point in Time Restore on page 210 of the Advanced Features chapter. Restoring a client to a slightly different disk configuration. For details, see Dissimilar Disk Restore (DDR) on page 188 of the Advanced Features chapter. Restoring a Windows client to dissimilar hardware. For details, see Dissimilar System Restore for Windows Clients on page 167. The procedure for modifying client configuration takes place on the BMR main server. The following sections explain the procedure for modifying client configuration for UNIX and Windows clients. 122 VERITAS Bare Metal Restore System Administrator s Guide

145 Modifying Client Configuration BMR UNIX Clients To modify a configuration for a UNIX client 1. On the BMR GUI, click Clients. The Bare Metal Restore Client List displays: 2. Select the client you want to restore by clicking the radio button to the left of the client name. Click Configurations. The Configuration List for Client displays: 3. Select the latest configuration saved during the last backup, named current. Click Copy/Import. Chapter 6, Restoring a BMR Client 123

146 Modifying Client Configuration The Copy Configuration dialog displays: 4. In the Destination Configuration field, type a name for the new configuration copy. Click OK. Note Configuration names must be alphanumeric. No special characters are allowed. The Configuration List for Client displays, showing the newly-created configuration: 5. Select the new configuration by clicking the radio button to the left of the name. Click Edit. 124 VERITAS Bare Metal Restore System Administrator s Guide

147 Modifying Client Configuration The Summary tab of the Configuration Summary screen displays: The Servers to use list should display only one BMR Main Server and only one NetBackup Master Server. 6. Click the Edit Network tab. Chapter 6, Restoring a BMR Client 125

148 Modifying Client Configuration The Edit Network Configuration for Client tab displays: You can edit the following information on this screen: Servers to use: This list displays the servers that the BMR client will need to contact during the restore. IP Address: Supply an alternate IP address for the server, if needed. Gateway to Server: If the BMR client is not located on the same network as the server, specify the BMR client network Gateway here. BMR Client Interfaces: This list displays the interfaces for the BMR client captured during bmrsavecfg. Use DHCP: Check to use DHCP to configure the interface during the restore. IP Address: Supply an alternate IP address for the client to use during the restore, if necessary. Netmask: Supply an alternate network mask of the interface, if necessary. Gateway: Specify the value of the Gateway, if present. MAC Address: If the network interface card has been replaced, specify the new address of the card. 126 VERITAS Bare Metal Restore System Administrator s Guide

149 Modifying Client Configuration If a server will not be available during the restore, or if the list of network interfaces has changed since the last backup, you can delete existing entries and add new ones to both the Servers to use list and the BMR Client Interfaces list. This example illustrates replacing a server in the server list. a. In the Servers to use list, select the server you want to delete by clicking the radio button to the left of the server name. Click Delete Server. The screen refreshes. b. Click Add Server. Chapter 6, Restoring a BMR Client 127

150 Modifying Client Configuration The Add Host to Client Configuration dialog displays: c. In the fields provided, specify the server Name, IP Address, and Gateway. Note IP addresses must be dotted decimal, not hexidecimal. d. Choose the Role of the server from the dropdown menu. Click OK. 128 VERITAS Bare Metal Restore System Administrator s Guide

151 Modifying Client Configuration e. The Edit Network Configuration for Client tab displays, showing the added server: 7. When you have completed all necessary configuration changes, click OK to continue. The Configuration Summary screen displays the modified configuration: Chapter 6, Restoring a BMR Client 129

152 Modifying Client Configuration Use the Edit Volumes tab when you perform a Dissimilar Disk Restore (DDR). For details about DDR, see Dissimilar Disk Restore (DDR) on page 188. If you are ready to proceed with the restore, click Prepare to Restore. This begins the Prepare to Restore operation. For details on performing the Prepare to Restore procedure, see Preparing to Restore a Client on page 136. BMR Windows Clients To modify a configuration for a Windows client 1. On the BMR GUI, click Clients. The Bare Metal Restore Client List displays: 2. Select the client you want to restore by clicking the radio button to the left of the client name. Click Configurations. 130 VERITAS Bare Metal Restore System Administrator s Guide

153 Modifying Client Configuration The Configuration List for Client displays: 3. Select the latest configuration saved during the last backup, named current. Click Copy. The Copy Configuration dialog displays: 4. In the Destination Configuration field, type a name for the new configuration copy. Click OK. Note Configuration names must be alphanumeric. No special characters are allowed. Chapter 6, Restoring a BMR Client 131

154 Modifying Client Configuration The Configuration List for Client displays, showing the newly-created configuration: 5. Select the new configuration by clicking the radio button to the left of the name. Click Edit. The Summary tab of the Configuration Summary screen displays: The Servers to use list should display only one BMR Main Server and only one NetBackup Master Server. 6. Click the Edit Network tab. 132 VERITAS Bare Metal Restore System Administrator s Guide

155 Modifying Client Configuration You can edit the following information on this screen: Servers to use: This list displays the servers that the BMR client will need to contact during the restore. BMR Client Interfaces: This list displays the interfaces for the BMR client discovered during bmrsavecfg. Selected Mass Storage Drivers: This list displays all the mass storage drivers discovered during bmrsavecfg. Selected NIC Drivers: This list displays all the network interface card drivers discovered during bmrsavecfg. Selected Service Pack: This list displays the name of the package which contains the Service Pack. If a server will not be available during the restore, or if the list of network interfaces have changed since the last backup, you can delete existing entries and add new ones to both the Servers to use list and the BMR Client Interfaces list. This example illustrates replacing a server in the Servers to use list. a. In the Servers to use list, select the server you want to delete by clicking the radio button to the left of the server name. Click Delete Server. The screen refreshes. b. Click Add Server. The Add Host to Client Configuration dialog displays. c. In the fields provided, specify the server Name, IP Address, and Gateway. Note IP addresses must be dotted decimal, not hexidecimal. Chapter 6, Restoring a BMR Client 133

156 Modifying Client Configuration d. Choose the Role of the server from the dropdown menu. Click OK. e. The Edit Network Configuration for Client tab displays, showing the added server. 7. If you need to change the Service Pack level, click the Service Pack tab. The Service Pack Selection dialog displays: 8. Select the Service Pack from the dropdown menu. This list displays all Service Packs (that match the client OS level) previously created on the BMR main server. If you do not see the required Service Pack, refer to Service Packs for Windows Clients on page 214 of the Advanced Features chapter. 9. When you have completed all necessary configuration changes, click OK to continue. 134 VERITAS Bare Metal Restore System Administrator s Guide

157 Modifying Client Configuration The Configuration Summary screen displays the modified configuration: If you are ready to proceed with the restore, click Prepare to Restore. This begins the Prepare to Restore operation. For details on performing this procedure, see Preparing to Restore a Client on page 136. Chapter 6, Restoring a BMR Client 135

158 Preparing to Restore a Client Preparing to Restore a Client It is possible to prepare a client for restore any time after a server-initiated full backup. The backup policy used for the full backup must include True Image Restore (TIR) with Move Detection enabled. While you can perform the Prepare to Restore step at any time, we recommend preparing to restore immediately prior to performing a restore. This ensures that the restore will include the most recent data. The Prepare to Restore step takes place on the BMR main server. The following sections describe how to prepare BMR UNIX and Windows clients for restore. BMR UNIX Clients You can Prepare to Restore the BMR clients from the Configure Client dialog of the BMR GUI. For details on launching the BMR GUI, see BMR Graphical User Interface on page 6. Note Before performing this procedure, ensure that NFS is up and running on the BMR file server. To prepare a BMR UNIX client for restore 1. On the BMR GUI, click Clients. The Bare Metal Restore Client List displays: 2. Select the client you need to restore by clicking the radio button to the left of the client name. Click Prepare to Restore. 136 VERITAS Bare Metal Restore System Administrator s Guide

159 Preparing to Restore a Client 3. The Prepare to Restore Client dialog displays: Note If you have previously performed a Prepare to Restore operation on this configuration, your previous selections will be automatically selected for this instance. Select the appropriate choices for this restore: a. Select a Boot Image Name from the dropdown menu. b. For Logging, check the box to enable logging for the restore. Always enable logging if you have adequate space in /var/bmr/log on the BMR main server. A typical log file can grow as large as 15MB. c. Select the desired Restore Options from the following: Only system disks/volumes: restores only those disks necessary to recover a bootable operating system. For AIX, this is the rootvg volume group. For HP-UX, this is the default volume group (default name is vg00) For Solaris, this includes the filesystems defined within the root volume group. All disks/volumes: recovers all disks. 4. Verify the information on this screen. Chapter 6, Restoring a BMR Client 137

160 Preparing to Restore a Client 5. Click OK. After the command finishes, a message displays informing you that the client is ready to be restored. 6. Click OK. You are finished with the Prepare to Restore step, and ready to proceed to final restore. Note If you wish to cancel the client restore and purge the restore files after generating them, run the following command from the system command line interpreter while logged in as root on the BMR main server: bmrcleanup <clientname> <configname> BMR Windows Clients You will be preparing to restore the BMR clients from the Bare Metal Restore Client List in the BMR GUI. For details on launching the BMR GUI, see BMR Graphical User Interface on page 6. To prepare a BMR Windows client for restore 1. On the BMR GUI, click Clients. The Bare Metal Restore Client List displays. 138 VERITAS Bare Metal Restore System Administrator s Guide

161 Preparing to Restore a Client 2. Select the client you need to restore by clicking the radio button to the left of the client name. Click Restore. 3. The Prepare to Restore Client dialog displays: Note If you have previously performed a Prepare to Restore operation on this configuration, your previous selections will be automatically selected for this instance. Select the appropriate choices for this restore: a. Select a Shared Resource Tree Name from the dropdown menu. b. For Logging, check the box to enable logging for the restore. Always enable logging if you have adequate space in /var/bmr/log on the BMR main server. c. For Formatting, check Use Quick Formatting to remove all files from the disk without scanning the disk for bad sectors. Use this option only if the disk has been previously formatted and you are certain that the disk is not damaged. d. Select the desired Restore Options from the following: Only system disks/volumes: restores only those disks necessary to recover a bootable operating system. All disks/volumes: recovers all disks. Chapter 6, Restoring a BMR Client 139

162 Preparing to Restore a Client Dissimilar Disk Restore: enables recovery to a system that has a different disk layout than the original system. For details, see Dissimilar Disk Restore (DDR) on page 188 of the Advanced Features chapter. 4. Verify the information on this screen. 5. Click OK. The Prepare to Restore step involves restoring some configuration information from NetBackup which was collected by bmrsavecfg. There may be a delay if the data is retrieved from tape. After the command finishes, a message displays informing you that the client is ready to be restored. 6. Click OK. You are finished with the Prepare to Restore step, and ready to proceed to final restore. Note If you wish to cancel the client restore and purge the restore files after generating them, run the following command from the system command line interpreter while logged in as root on the BMR main server: bmrcleanup <clientname> <configname> 140 VERITAS Bare Metal Restore System Administrator s Guide

163 Restoring a Client Restoring a Client You must perform the Prepare to Restore procedure detailed in the previous section before you initiate a BMR client restore. The restore process takes place on the client, includes starting and booting the client, and in some cases providing input to the boot process. The BMR restore process then automatically accesses (for UNIX) or installs (for Windows) the operating system and NetBackup client, which restores the rest of the client files. This section details the platform-specific restore instructions according to the two options for BMR client restore, network boot and media boot: Restoring UNIX BMR Clients Using Network Boot Restoring UNIX BMR Clients Using Media Boot Restoring Windows Clients Network Restore With Generic Boot Floppy Network Restore with Custom Boot Floppy Media Restore with Custom Boot Floppy Restoring UNIX BMR Clients Using Network Boot To begin the restore process of a UNIX BMR client, boot the machine over the network. 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 When you are ready to restore your AIX client, you will need to have some information and resources on hand. This information varies according to architecture, but can include: IPL ROM emulation disk network adapter type BMR client IP address BMR client subnet mask BMR boot server IP address BMR client gateway address System Management Services (SMS) disk Chapter 6, Restoring a BMR Client 141

164 Restoring a Client Network Boot Procedures by AIX Client Architecture Use the appropriate method to network boot your architecture of AIX client. The options include: AIX Method A (Micro Channel-based RS/6000) AIX Method B (Micro Channel-Based, Symmetric Multiprocessor Systems) AIX Method C (RSPC Platform Machine) AIX Method D (updates the NVRAM) AIX Method E (IBM 7012 G30/G40 series Machines) To network boot with AIX Method A (Micro Channel-based RS/6000) 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 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. 142 VERITAS Bare Metal Restore System Administrator s Guide

165 Restoring a Client a. The client machine you are booting in the client address field. b. Your BMR boot server IP address in the bootp server address field. c. Your client s gateway in the gateway address field. Note If no gateway is used by the client, this field 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 restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To network boot with AIX Method B (Micro Channel-Based, Symmetric Multiprocessor Systems) 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. Chapter 6, Restoring a BMR Client 143

166 Restoring a Client 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 BMR boot server are on the same LAN, leave the IP address fields as zeros for the bootp request. If there are multiple BMR 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. 14. Follow the screen instructions to turn the hardware key to the normal position. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To network boot with AIX Method C (RSPC Platform Machine) Starting with the BMR client turned OFF, use the following procedure to network boot an RSPC platform machine: 144 VERITAS Bare Metal Restore System Administrator s Guide

167 Restoring a Client 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. Turn the BMR client ON. 3. When icons begin appearing on the bottom of the screen, press F4. If F4 is not pressed before the last icon displays, the client boots normally instead of using the SMS disk. 4. If you are using an ASCII terminal, press From the SMS menu, select Utilities. 6. From the System Management Services Utilities menu, select Remote Initial Program Load Setup. 7. From the Network Parameters screen, select IP Parameter. 8. 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. 9. If prompted, enter the subnet mask for the BMR client. All machines in the same subnet have the same subnet mask. 10. Press Enter. The settings are saved and the Network Parameters menu displays. 11. On the Network Parameters menu, select Ping. 12. Select the network adapter the client uses as its boot device. Chapter 6, Restoring a BMR Client 145

168 Restoring a Client 13. 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 To acknowledge successfully completing the ping test, press Enter. 15. From the System Management Services menu, select Select Boot Device. 16. Select the correct network adapter for your network. 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. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To network boot with AIX Method D (updates the NVRAM) 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 any time 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 restore using the BMR graphical user interface. Caution Do not perform this procedure unless you are intending to do a restore. Preparing a client for restore may result in a restore. 1. Log into the client as the root user. 2. Verify the firmware in the BMR client is capable of using the network adapter as a boot device using this command: bootinfo -q <network adapter device name> The output of this command is either 1 or 0. 1 indicates the network adapter is capable of network booting. 0 indicates the network adapter is not capable of network booting. If this command indicates the device is not capable of network booting, Method D is not appropriate for your hardware. 3. Type the following command and record the current boot list. For AIX 4.2: bootlist -m normal -o 146 VERITAS Bare Metal Restore System Administrator s Guide

169 Restoring a Client For AIX 4.1 or earlier: bootlist -m normal -r The output using the -r flag is hardware-platform dependent. The output can be a hexadecimal dump of the boot list or a list of device names. 4. Invalidate the current boot list. bootlist -m normal -i 5. Change the bootlist using the following command. Use the IP addresses of the gateway, BMR boot server, and client machine. bootlist -m normal <network adapter device name> gateway=<ip address> bserver=<ip address> client=<ip address> hdisk0 6. Reboot the client using the reboot command. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To network boot with AIX Method E (IBM 7012 G30/G40 series Machines) 1. Start with the machine power OFF. 2. Turn key to Service position, and press Enter. 3. At the BUMP prompt, type sbb and press Enter. 4. The STAND-BY menu displays. Choose 1 to Set Flags. 5. The SET FLAGS menu displays. Choose 2 to Disable Autoservice IPL. 6. Press x to exit. 7. Leave key in Service position and power on machine. 8. After a short wait, the Maintenance Menu displays. 9. Choose 6 for System Boot. 10. The System Boot menu displays. Choose 1 to Boot from Network. Chapter 6, Restoring a BMR Client 147

170 Restoring a Client 11. You are now in the Network Boot Menu. Follow the instructions starting with step 6 of the procedure To network boot with AIX Method A (Micro Channel-based RS/6000) on page 142 to complete the network boot. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. Solaris Network Boot When you are ready to restore your Solaris client, you will need to know the name of the device that directs the client to the correct BMR boot server. To network boot a Solaris client 1. Turn the client ON. 2. Terminate the boot process using the Stop+A key combination. 3. If the PROM monitor prompt displays < use the N command to get to the OK prompt. 4. Enter the following command: boot <network device> where network device is the device that points to the BMR boot server. When you enter this command, the system starts the network boot. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. HP-UX Network Boot When you are ready to restore your HP-UX client, you will need to have some information and resources on hand. This information can include: BMR client IP address BMR client gateway address BMR client subnet mask Ignite Server Address. This is typically the BMR boot server. To begin this procedure, the BMR client must be OFF. 148 VERITAS Bare Metal Restore System Administrator s Guide

171 Restoring a Client To network boot an HP-UX client 1. Turn the client ON. 2. Press any key when the following message displays: To discontinue, press any key within 10 seconds. The Main Menu opens. 3. Enter the following command: boot lan Note If there is more than one Ignite server on the subnet, or if you are using a boot helper to boot from an Ignite server on a different subnet, specify the Ignite server to boot from with the following command: boot lan.x.x.x.x.y.y where x.x.x.x is the IP address of the correct Ignite server and y.y is the Gateway. 4. Enter No when the prompt asks about interacting with IPL. 5. Select the operating system language, by number. For example, US English is After entering the language choice, press Enter twice to select and confirm the choice. The HP-UX Ignite menu opens. 7. Use the arrow key to scroll to Run a Recovery Shell. Wait 30 seconds. Do not interrupt DHCP searching. The Network Configuration menu opens. 8. Answer the following prompts: a. Hostname: b. Internet Protocol Address: c. Subnet mask: d. Ignite Server Address (this is typically the BMR boot server): 9. Use the arrow key to scroll to OK and press Enter. Chapter 6, Restoring a BMR Client 149

172 Restoring a Client The system boots from the network. After you have started a network boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. Restoring UNIX BMR Clients Using Media Boot To begin the restore process of a UNIX BMR client, boot the machine using the CD-based SRT you created using the directions in Creating a CD-Based SRT on page 80. The method of booting a machine using media varies depending on its manufacturer and model. Refer to the following sections to media boot your machine depending on architecture and platform. AIX Media Boot Note The network interface configuration, speed, and duplex mode during AIX booting (either network boot or media boot) may be set to auto-negotiate or 10 half duplex. This type of setting may cause the BMR restore to run much more slowly than expected. To achieve normal restore performance, manually set the network interface configuration through the firmware prior to a BMR restore. Use the appropriate method to media boot your architecture of AIX client. The options include: AIX - RS/6000 AIX - RSPC AIX - CHRP AIX - IBM 7012 G30/G40 series To media boot an AIX - RS/6000 client 1. Insert the CD-ROM containing the SRT into the CD-ROM drive. 2. Turn the switch to Service mode. 3. Turn the client power OFF, then ON. The machine boots off the CD. 4. Enter network and BMR main server information at the prompts. The restore proceeds. 150 VERITAS Bare Metal Restore System Administrator s Guide

173 Restoring a Client 5. After the machine finishes booting, but before the restore is complete, turn the switch to Normal mode. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To media boot an AIX - RSPC client Note 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. 1. Insert the CD-ROM containing the SRT into the CD-ROM drive. 2. Turn the client power OFF, then ON. 3. When icons begin to appear on the bottom of the screen, press F4 (or 4, if using ASCII terminal). If F4 is not pressed before the last icon appears, the client boots normally instead of using the SMS disk. 4. Select Select Boot Device from the System Management Services menu. 5. Select Boot Other Device from the menu. 6. Select SCSI CDROM from the menu. The machine boots from the CD. 7. Enter network and BMR main server information at the prompts. The restore proceeds. 8. After the machine finishes booting, but before the restore is complete, turn the switch to the Normal position. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. Chapter 6, Restoring a BMR Client 151

174 Restoring a Client To media boot an AIX - CHRP client 1. Turn the client power OFF, then ON. 2. When icons begin to appear on the bottom of the screen, press F1 (1 if using ASCII terminal). If F1 is not pressed before the last icon appears, the client boots normally instead of using the SMS disk. 3. Select the Multiboot to display its menu. 4. Select Install From (or from ASCII terminal, Select Install Device). A menu displays the operating system level for the BMR media boot CD. 5. Select that option. The machine boots off the CD. 6. Enter network and BMR main server information at the prompts. The restore proceeds. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. To media boot an AIX IBM 7012 G30/G40 series client 1. Start with the machine power OFF. The media must be installed in the boot device and ready prior to continuing. 2. Turn key to Service position, and press Enter. 3. At the BUMP prompt (>), type sbb and press Enter. 4. The STAND-BY menu displays. Choose 1 to Set Flags. 5. The SET FLAGS menu displays. Choose 2 to Disable Autoservice IPL. 6. Press x to exit. 7. Leave key in Service position and power on machine. 8. After a short wait, the Maintenance Menu displays. 9. Choose 6 for System Boot. 152 VERITAS Bare Metal Restore System Administrator s Guide

175 Restoring a Client 10. The System Boot menu displays. Choose 0 to Boot from List. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. Solaris Media Boot To media boot a Solaris client 1. Insert the CD-ROM that contains the SRT into the CD-ROM drive. 2. Turn the client OFF, then ON. 3. Terminate the boot process using the Stop+A key combination. 4. If the PROM monitor prompt displays <, use the N command to reach the OK prompt. 5. Enter the following command: boot cdrom The system boots from the CD-ROM and continues the restore process. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. HP-UX Media Boot To media boot an HP-UX client 1. Insert the CD-ROM containing the SRT into the CD-ROM drive. 2. Power OFF, then ON, the HP-UX client. 3. When prompted, press the Space bar within 10 seconds to stop the normal boot process. 4. Search for the location and name of the CD-ROM drive. The search utility may be useful in determining this information. 5. Find the CD-ROM drive from the list of devices and boot the machine using that device with the boot command. Chapter 6, Restoring a BMR Client 153

176 Restoring a Client 6. Answer No to the Interact with IPL prompt. 7. Answer Yes to the Run a Recovery Shell prompt. 8. Answer Yes to the Start Networking prompt. 9. Enter the default LAN device when prompted for Choose the network interface to boot from. The default LAN must be selected, because the firmware will use this address for retrieving the boot image from the Ignite server. Note that any NIC card can be used for accessing the SRT or backups, but the default LAN must be used for accessing the boot image. 10. Answer the following prompts: a. Hostname: b. Internet Protocol address: c. Default Gateway: d. Subnet mask: 11. Answer No at the Is this network information temporary prompt. 12. Use the arrow key to scroll to OK and press Enter. 13. Enter the IP Address of the BMR main server: Press Enter to accept the default value, which should already indicate the IP address of the BMR main server. 14. Enter the port number of the BMR main server: Press Enter to accept the default value which should already indicate the port number of the BMR main server. The system boots from the CD-ROM and continues the restore process. After you have started a media boot, the remainder of the restore process is automatic and requires no manual intervention. Once the client has finished and reboots itself, it is completely restored. Restoring Windows Clients Depending on the method you selected for creating your Windows boot floppies, there are three possibilities for restoring your BMR Windows client: 154 VERITAS Bare Metal Restore System Administrator s Guide

177 Restoring a Client Network Restore with Generic Boot Floppy Network Restore with Custom Boot Floppy Media Restore with Custom Boot Floppy The following sections provide instructions for initiating a Windows client restore with the method you selected. Network Restore With Generic Boot Floppy Generic boot floppies do not contain any client-specific information (except for the NIC driver). Hence, a series of prompts ask you to input client-specific information during this type of boot. If incorrect information is entered or if the information that is entered needs to be changed at any of the earlier screens, follow the instructions detailed in Recovering from Erroneous Input While Working with Generic Boot Floppies (Windows) on page 240. To network restore a Windows client with a generic boot floppy 1. Insert the generic boot floppy in the floppy drive, and reboot the system. The following status screen displays the progress of the restore process. A green check marks each activity as it is completed. Chapter 6, Restoring a BMR Client 155

178 Restoring a Client 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. 2. A series of prompts is displayed. For each prompt, provide the appropriate value(s) and press Enter: a. Does this client use DHCP (y/n)? Type Y or N, and press Enter. If you entered Y, go to Step e. b. Enter the IP address of the client: c. Enter the subnet mask of the client: d. Enter the default gateway of the client: e. Enter file server s name: f. Enter file server s IP address: g. Enter the SRT name: h. Enter the client configuration name: The restore process brings up the network and retrieves additional client information from the BMR main server. After Retrieving Client Information is completed, the following displays: i. Do you want to save a partition (y/n)? If you typed N, the restore process creates the required partitions. After repartitioning completes, the system reboots. Go to step 3. If you typed Y and if no partitions were found that can be saved, the following messages display: Could not find any partitions to save! Do you want to proceed (YES/NO)? To stop the restore process, type NO and press Enter. The Restore process is aborted. 156 VERITAS Bare Metal Restore System Administrator s Guide

179 Restoring a Client 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 3. If you typed YES 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 MB) is displayed. For example, you may see something similar to the following: The following prompt is displayed: Which partition do you want to save? (1, 3, or 0 if none): 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. The restore process creates the required partitions, and the system reboots. 3. After the system reboots, the following status screen is displayed. A check displays beside each activity as it completes: Chapter 6, Restoring a BMR Client 157

180 Restoring a Client After Copying BMR Files completes, Windows installation starts to install Windows into a temporary repair location. (Note that this is only a temporary installation, and will be removed from the system after the restore process completes.) This process typically takes minutes; the time can vary drastically depending on system speed and network behavior. Note Leave the boot floppy disk in the drive until prompted to remove it. After Windows installation completes, the system reboots into this temporary installation and BMR takes over the rest of the restore process. 4. 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 on the BMR Restore screen 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: From the Start menu, choose Programs > Administrative Tools > Event Viewer. In most cases, correcting the problem described in the event logs, and restarting the restore process is sufficient to effect a successful restore. If a problem persists, contact support. After all activities are completed the system reboots. For standard restores, this is the last step. 158 VERITAS Bare Metal Restore System Administrator s Guide

181 Restoring a Client 5. For Dissimilar System Restores, after the system reboots, an additional administrator logon may be required to finish configuring the network information. Perform the logon to complete the Dissimilar System Restore. Network Restore with Custom Boot Floppy If you wish to do a floppy boot of a specific Windows BMR client, first create a Windows boot floppy specific to that client. For options during the creation of your boot floppy, refer to Creating Boot Images (Floppies) for Windows Clients on page 98. While creating the boot floppy for your specific BMR client, you have the option of using safety prompts. These prompts allow the process to pause, and require 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. To network restore a Windows client with a custom boot floppy 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 displays: After Retrieving Client Information is completed, the following series of screens may appear, depending on how the boot floppy was created. If, during the boot floppy creation, you elected to save a partition and if no partitions were found that can be saved, the following screens are displayed Chapter 6, Restoring a BMR Client 159

182 Restoring a Client Could not find any partitions to save! Do you want to proceed (YES/NO)? 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, during the boot floppy creation, you elected 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: Which partition do you want to save? (1, 3, or 0 if none): 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 chose 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 chose to have a safety prompt and you typed 0, the following displays: All partitions will be erased. Type YES to confirm, or type NO to abandon. Proceed with repartitioning (YES/NO)? To stop the restore process, type NO, and press Enter. The restore process is aborted. To repartition the disk, type YES, and press Enter. After repartitioning completes, the system reboots. Go to step 2. If during the boot floppy creation you chose to have a safety prompt and you typed a number other than 0, the following displays: All partitions, except the saved partition, will be erased. Type YES to confirm, or type NO to abandon. Proceed with repartitioning (YES/NO)? 160 VERITAS Bare Metal Restore System Administrator s Guide

183 Restoring a Client To stop the restore process, type NO, and press Enter. The 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 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 installation starts to install Windows into a temporary location. (Note that this is only a temporary installation, and will be removed from the system after the restore process completes.) This process typically takes minutes; the time can vary drastically depending on system speed and network behavior. Note Leave the boot floppy disk in the drive until prompted 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. Chapter 6, Restoring a BMR Client 161

184 Restoring a Client 3. After the system reboots, the following screen displays: In this step, the BMR Restore Wizard creates all the required partitions, formats them, and restores the files in each of the partitions. The Details box on the BMR Restore Wizard screen 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: From the Start menu, choose Programs > Administrative Tools > Event Viewer. In most cases, correcting the problem described in the event logs, and restarting the restore process is sufficient to effect a successful restore. If a problem persists, contact support. 4. After all activities are completed, a screen displays asking you to confirm the system reboot, and the system reboots. 5. For Dissimilar System Restores, after the system reboots, an additional administrator logon may be required to finish configuring the network information. Perform the logon to complete the Dissimilar System Restore. 162 VERITAS Bare Metal Restore System Administrator s Guide

185 Restoring a Client Media Restore with Custom Boot Floppy To media restore a Windows client with a custom boot floppy 1. To begin a restore process using the customized BMR media boot floppy, complete the following: a. Insert the BMR media boot floppy into the floppy drive b. Insert the BMR media boot CD into the CD-ROM drive Note If the system has both a DVD drive and a CD-ROM drive, insert the media boot CD into the CD-ROM drive. c. Reboot the system. The following status screen displays: After Retrieving Client Information completes, the following series of screens may appear, depending on how the boot floppy was created: If, during the boot floppy creation, you elected to save a partition and if no partitions were found that can be saved, the following screens are displayed: Chapter 6, Restoring a BMR Client 163

186 Restoring a Client Could not find any partitions to save! Do you want to proceed (YES/NO)? 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, during the boot floppy creation, you elected 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: Which partition do you want to save? (1, 3, or 0 if none): 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 chose 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 chose to have a safety prompt and you typed 0, the following displays: All partitions will be erased. Type YES to confirm, or type NO to abandon. Proceed with repartitioning (YES/NO)? To stop the restore process, type NO, and press Enter. The restore process is aborted. To repartition the disk, type YES, and press Enter. After repartitioning completes, the system reboots. Go to step 2. If during the boot floppy creation you chose to have a safety prompt and you typed other than 0, the following displays: All partitions, except the saved partition, will be erased. Type YES to confirm, or type NO to abandon. Proceed with repartitioning (YES/NO)? 164 VERITAS Bare Metal Restore System Administrator s Guide

187 Restoring a Client To stop the restore process, type NO, and press Enter. The 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 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 installation starts to install Windows into a repair location. (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 prompted to remove it. 3. After Windows installation completes, the system reboots into this temporary repair installation and BMR takes over the rest of the restore process. Chapter 6, Restoring a BMR Client 165

188 Restoring a Client The BMR Restore Wizard screen displays: In this step, the BMR Restore Wizard 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 Restore Wizard screen 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: From the Start menu, choose Programs > Administrative Tools > Event Viewer. 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 Support. 4. After all activities are completed the system reboots. For standard restores, this is the last step. 5. For Dissimilar System Restores, after the system reboots, an additional administrator logon may be required to finish configuring the network information. Perform the logon to complete the Dissimilar System Restore. 166 VERITAS Bare Metal Restore System Administrator s Guide

189 Dissimilar System Restore for Windows Clients 7 Bare Metal Restore provides the capability to restore a Windows client backup image to hardware that is different from the hardware used at the time of the backup. A BMR Dissimilar System Restore handles differences such as disk controllers and network cards, as well as mother board changes that require a different Hardware Abstraction Layer (HAL) and/or kernel. This chapter covers the following topics: When to Use Dissimilar System Restore Understanding the Dissimilar System Restore Process Performing a Dissimilar System Restore DSR Restore Procedure: Adding New Drivers DSR Restore Procedure: Copying Another Client s Configuration Procedures Troubleshooting Common Problems 167

190 When to Use Dissimilar System Restore When to Use Dissimilar System Restore A Dissimilar System Restore (DSR) restores an original Windows client backup image to a new system with a different hardware configuration. For the purpose of explanation in this chapter, the hardware configuration that the original client had when the last backup occurred is the source system. The hardware configuration of the client to which the backup image will be restored is the target system. Performing a DSR would be useful in the following sample scenarios: You have changed the preferred vendor for a class of systems in your enterprise. You are migrating an application from older hardware to the latest available hardware. Your system has suffered critical hardware failure and similar hardware is not available for replacement (no longer provided by the vendor). Your disaster recovery provider does not have identical hardware to yours at the disaster recovery site. You are staging and verifying an application at a test site with different hardware from the production site (you can migrate the application from test to production). You should use DSR when any of the following conditions apply: The target system has a disk controller that the source system did not have. The source system had a disk controller that the target system does not have. The target system has a network card that the source system did not have. The source system had a network card that the target system does not have. The target system requires a different HAL/kernel than the source system required. The case of a different HAL/kernel requires special consideration when Windows Service Packs are installed on the client. A Service Pack must be used during the restore that exactly matches the Service Pack level of the client. The target system will have different TCP/IP settings than the source system had. Bare Metal Restore supports DSR for Windows 2000/NT clients only. Understanding the Dissimilar System Restore Process The DSR process has six basic steps: 168 VERITAS Bare Metal Restore System Administrator s Guide

191 Understanding the Dissimilar System Restore Process 1. Saving the client configuration on the source system. 2. Determining hardware differences of the target system as compared to the source system. 3. Adding necessary drivers to the source client s saved configuration on the BMR main server. 4. Adding the same Service Pack as the source client originally used to the source client s saved configuration on the BMR main server. 5. Restoring the source client to the target system. 6. Performing final Dissimilar System Restore cleanup on the first logon of the restored system. These steps are explained further in the following sections. Saving the Source Client Configuration DSR uses the configuration information saved by the normal bmrsavecfg process. bmrsavecfg runs with every server-initiated backup. If your clients are properly configured and backed up, this step is part of normal BMR operation. Note To use the Dissimilar System Restore feature, you must have upgraded your clients to BMR 4.6 or later. Determining Hardware Differences The most critical and difficult task in the DSR process is correctly determining the hardware differences between the saved source system and new target system. The hardware differences can include: disk controller network card HAL/kernel TCP/IP settings specific media (audio/video drivers) hardware (MAC) address Chapter 7, Dissimilar System Restore for Windows Clients 169

192 Understanding the Dissimilar System Restore Process Understanding these differences will help you determine what drivers you will need to add to the source client s saved configuration on the BMR main server before performing the restore. Note To perform a DSR, the exact hardware (MAC) address of the target system is required. Without this MAC address, the BMR restore procedure will not be able to restore the network properties of the target system to that of the source system. How you determine this information depends on the status of the target system. The following are examples: Target system is new from the factory: use the manufacturer s website to determine the drivers used by this machine. Target system has same base Operating System as the source client: install BMR client on the target system, register client with BMR main server, and run bmrsavecfg on the target client. This will capture the target system s configuration, including device drivers, on the BMR main server. Adding New Drivers Once you have determined the drivers that are necessary for the target system, you must add the drivers to the configuration of the source system saved on the BMR main server. There are two ways to add the necessary drivers to the source client s saved configuration: Adding individual drivers Copying another client s configuration Adding Individual Drivers To add an individual driver, you must locate the specific driver you require, on a CD-ROM, on a manufacturer s website, or on another BMR Windows client in your environment. On any BMR Windows client, use the Create Package Wizard provided by BMR to add a Mass Storage Device or Network Interface Card driver to the BMR main server. When you have added all the necessary drivers to the server, you can add the drivers to an editable copy of the source client s configuration. Use the BMR GUI to perform these tasks. For detailed instructions, see DSR Restore Procedure: Adding New Drivers on page 172. Copying Another Client s Configuration If you have another BMR Windows client with a hardware configuration that closely matches the configuration of the target system, you can copy that configuration to the source system configuration. Use the BMR Administration GUI to copy the desired 170 VERITAS Bare Metal Restore System Administrator s Guide

193 Understanding the Dissimilar System Restore Process configuration to the source client. Create an editable copy to add or remove individual drivers as necessary. For detailed instructions, see DSR Restore Procedure: Copying Another Client s Configuration on page 172. Adding a Service Pack In order for DSR to work successfully, the configuration used for the restore must have the same Service Pack as the original BMR client. If a Service Pack has already been added to a BMR file server, select the Service Pack in the configuration prior to the restore. If you did not create a Service Pack for the source client, but one is required, you can create the Service Pack from any BMR Windows client. Use the Create Package Wizard to add the Service Pack to a BMR file server. Then, select the Service Pack from the Edit Configuration screen. For detailed instructions, see Service Packs for Windows Clients on page 214. Restoring the Client After you have performed the previous steps, the Dissimilar System Restore process will proceed as a normal restore. Select the source client and its edited configuration from the BMR Administration GUI and click Restore. For detailed instructions, see To restore the configuration on page 183, below. First Logon After the system has been restored, an administrator logon is required to complete the DSR changes. BMR will display a DSR status box detailing the steps. While the DSR status box is visible, Windows may display a number of New Hardware Found wizards. Perform the following action depending on which wizard or message screen displays: On the Digital Signature Not Found screen, click Yes. On the Found New Hardware wizard screen, click Cancel. On the New drivers are installed, do you want to reboot? screen, click No. Note Do not reboot the system until the DSR status box has completed. Chapter 7, Dissimilar System Restore for Windows Clients 171

194 Performing a Dissimilar System Restore Performing a Dissimilar System Restore This section provides instructions for performing a DSR in two different ways: using added drivers, and copying an existing client configuration. It is possible that you will want to use a combination of these two methods to achieve the necessary DSR configuration. The procedures below are separated into sub-procedures. Use the sub-procedures to accomplish the Dissimilar Disk Restore preparation in one of the two ways discussed in Adding New Drivers on page 170, above. DSR Restore Procedure: Adding New Drivers When you restore by adding new drivers to the client configuration, use the listed procedures in the following order: To create the driver package on the server To add the driver to the source client configuration To restore the configuration Perform this procedure on a separate Windows client using a copy of the driver you need (from CD-ROM, manufacturer s website, or another BMR client) to add to the source client s configuration. createpkg will push the driver package to the BMR main server, where you can add it to the source client configuration. Perform this procedure on the BMR main server GUI. This will allow you to add the driver packages you created Perform this procedure to initiate the restore process. After the Prepare to Restore step, the restore proceeds like a standard restore. DSR Restore Procedure: Copying Another Client s Configuration When you restore by copying another client s drivers, use the listed procedures in the following order: To copy the configuration of the target hardware Perform this procedure on the BMR main server GUI. If you know a client with similar or identical hardware configuration to the target system, use this procedure to copy the separate Windows client configuration and assign it to the source client. 172 VERITAS Bare Metal Restore System Administrator s Guide

195 Performing a Dissimilar System Restore To add the driver to the source client configuration To restore the configuration Perform this procedure on the BMR main server GUI. After copying the hardware configuration from a separate Windows client and assigning it to the source client, you may need to add or remove drivers from the configuration. Perform this procedure to initiate the restore process. After the Prepare to Restore step, the restore proceeds like a standard restore. The procedures cover the preparation steps that lead up to the restore. After the completion of the Prepare to Restore step at the end of the restore procedure, a DSR restore functions according to the standard restore procedure. For more detailed instructions on the standard restore procedure, see Restoring Windows Clients on page 154. Chapter 7, Dissimilar System Restore for Windows Clients 173

196 Performing a Dissimilar System Restore Procedures If you are restoring by adding drivers to a client s configuration, complete this procedure first. To create the driver package on the server 1. On a Windows client with the drivers you need, click Start > Programs > VERITAS Bare Metal Restore > Create Package. The Create Package Wizard Welcome screen displays: 174 VERITAS Bare Metal Restore System Administrator s Guide

197 Performing a Dissimilar System Restore 2. Click Next. The Create Bare Metal Restore Packages screen displays: 3. Select either Mass Storage Driver or Network Interface Card Driver from the Package Type dropdown menu. 4. In the Description field, type a memorable name for the driver. 5. Enter the path of the Driver Installation (.inf) file. Alternatively, click Browse to locate the INF file. 6. Click Next. Chapter 7, Dissimilar System Restore for Windows Clients 175

198 Performing a Dissimilar System Restore The Select Driver screen displays: 7. Select the specific driver or drivers you want from the Driver list, and click Next. The Creating Package screen displays: 176 VERITAS Bare Metal Restore System Administrator s Guide

199 Performing a Dissimilar System Restore When the package creation is complete, the following dialog displays: 8. To create another package, click Yes. Create another package using step To finish package creation, click No. The Creating Package screen displays. 10. Click Finish. To add the driver you have created, skip to the following procedure: To add the driver to the source client configuration. If you are restoring by copying another client s drivers, first complete the following procedure, To copy the configuration of the target hardware. To copy the configuration of the target hardware 1. On the BMR Administration GUI main navigation, click Clients. The Bare Metal Restore Client List displays: 2. Select the client that will be restored by clicking the radio button to the left of the client name. 3. Click Configurations. Chapter 7, Dissimilar System Restore for Windows Clients 177

200 Performing a Dissimilar System Restore The Configuration List for Client screen displays: 4. If more than one configuration exists, select the current configuration by clicking the radio button to the left of the configuration. 5. Click Copy/Import to copy the current configuration to a configuration with a state of Editable. The Copy Configuration screen displays: 6. From the Source Client dropdown menu, select the name of the source client that will be restored with DSR. 7. Enter a name for the new configuration in the Destination Configuration field. 8. Click OK. If you need to add drivers to a client configuration, use the following procedure. 178 VERITAS Bare Metal Restore System Administrator s Guide

201 Performing a Dissimilar System Restore To add the driver to the source client configuration 1. On the BMR Administration GUI, click Clients. The Bare Metal Restore Client List displays: 2. Select the client that will be restored by clicking the radio button to the left of the client name. 3. Click Configurations. The Configuration List for Client screen displays: 4. If more than one configuration exists, select the configuration with the state of current by clicking the radio button to the left of the configuration. 5. Click Copy to copy the current configuration to a configuration with a state of Editable. Chapter 7, Dissimilar System Restore for Windows Clients 179

202 Performing a Dissimilar System Restore The Copy Configuration screen displays: 6. Enter the new name for the configuration in the Destination Configuration field. Note Configuration names must be alphanumeric. No special characters are allowed. 7. Click OK. 8. Back on the Configuration List for Client screen, select the newly copied configuration by clicking the radio button to the left of the new configuration name. 9. Click Edit. 180 VERITAS Bare Metal Restore System Administrator s Guide

203 Performing a Dissimilar System Restore The Configuration Summary screen displays: 10. Click the Edit Drivers tab. Chapter 7, Dissimilar System Restore for Windows Clients 181

204 Performing a Dissimilar System Restore The Edit Driver Configuration for Client screen displays: 11. From the Mass Storage Drivers and NIC Drivers panes, use Add or Remove to change which drivers are in the configuration. 12. Click OK to save the configuration changes and return to the Configuration Summary screen. 182 VERITAS Bare Metal Restore System Administrator s Guide

205 Performing a Dissimilar System Restore To restore the configuration 1. From the Bare Metal Restore Client List screen, select the source client to restore by clicking on the radio button to the left of the client name. 2. Click Restore. The Prepare to Restore Client screen displays: 3. On the Prepare to Restore Client screen, select the appropriate options. 4. Click OK. 5. Reboot the client according to the standard restore procedures. Chapter 7, Dissimilar System Restore for Windows Clients 183

206 Troubleshooting Common Problems For details, see Restoring Windows Clients on page 154. Troubleshooting Common Problems Different Service Pack Level Warning Problem Cause Solution Towards the end of the restore process, a warning about a different service pack level displays. The Service Pack level of the target system is different than was backed up for the client. If this is a non-dsr, click No. If this is a DSR, Prepare to Restore the client again with an appropriate Service Pack added to the configuration. For detailed instructions on adding Service Packs, see Service Packs for Windows Clients on page 214. Duplicate IP Addresses on Network Problem Cause Solution The client fails to start networking during DOS. The details show that the IP address is already in use. The source system may still be on the network when the target system is being restored. Disconnect the source system from the network. MAC Address Does Not Match Problem In some cases, the MAC address and TCPIP configuration may not match. 184 VERITAS Bare Metal Restore System Administrator s Guide

207 Troubleshooting Common Problems Cause Solution If you use the DSR Restore Procedure: Copying Another Client s Configuration method on a Windows client that has multiple NICs in the source and target system, the copy procedure will merge the MAC addresses of the target system with the TCP/IP properties of the source system. The assignment will be made in a sequential manner, and in some cases, this is not desirable. Edit the Network Properties using the Edit Network tab on the client s Configuration Summary screen. Change the MAC addresses to match the appropriate TCP/IP configuration. Chapter 7, Dissimilar System Restore for Windows Clients 185

208 Troubleshooting Common Problems 186 VERITAS Bare Metal Restore System Administrator s Guide

209 Advanced Features 8 The BMR features described in this chapter will not be applicable to every BMR system configuration. Read this chapter for information on the following advanced feature topics: Dissimilar Disk Restore (DDR) Storage Area Network (SAN) Co-Existence Point in Time Restore Service Packs for Windows Clients Multiple Network Interface (Multihomed) Considerations Restoring NetBackup Media Servers (Solaris Only) Restoring the BMR Server 187

210 Dissimilar Disk Restore (DDR) Dissimilar Disk Restore (DDR) Bare Metal Restore provides utilities that allow the restore 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 of disk space on one or more physical disks. When to Use Dissimilar Disk Restore 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 a client restore 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, Solaris with VERITAS Volume Manager and VERITAS File System, HP-UX, and Windows NT/2000. As examples, this guide uses AIX and Windows clients. BMR Dissimilar Disk Restore does not support VERITAS Volume Manager and VERITAS File System on HP-UX or AIX, or Solstice Disk Suite on Solaris. Understanding the Dissimilar Disk Restore Process In a standard BMR recovery, BMR uses the saved machine configuration to recreate the original system. This requires little or no intervention, because the original system is deployed onto the original disk configuration. In a Dissimilar Disk Restore, BMR requires two additional sources of input: First, a discovery boot conveys the new configuration of the restore target client to the BMR main server. 188 VERITAS Bare Metal Restore System Administrator s Guide

211 Dissimilar Disk Restore (DDR) Second, the BMR administrator must map the drives or logical volumes to be restored to the available disk configuration as determined by the discovery boot. To help you map the original drives or logical volumes to the new available disk configuration, BMR presents the information on the GUI. However, you must access the DDR GUI differently depending on client platform: For UNIX clients, you map volumes and drives on the Edit Volumes tab of the Edit Configurations dialog, through the BMR GUI on the BMR main server. For Windows clients, the Dissimilar Disk Mapping Assistant displays on the client, immediately after the client discovery boot. After the administrator maps the source client drives to the existing new available drives through the DDR GUI, the restore continues automatically. Dissimilar Disk Restore for UNIX Clients BMR provides a utility to help you perform a Dissimilar Disk Restore. For UNIX clients, you will access the utility to prepare for a discovery boot on the Configuration List for Client screen of the BMR GUI. The utility used to map the drives is accessed on the Edit Configuration for Client screen. Alternately, you can specify the option bmrdiscover and bmrmap utilities from the command line. For details on using bmrdiscover and bmrmap, see BMR Command Reference on page 291. During a Dissimilar Disk Restore, you will need to provide and verify the same information and details that you provide during a standard restore. For relevant details on the Prepare to Restore step, see Preparing to Restore a Client. Note that for this example, we present only the differences applicable to a Dissimilar Disk Restore. Chapter 8, Advanced Features 189

212 Dissimilar Disk Restore (DDR) To initiate a Dissimilar Disk Restore for UNIX 1. In the BMR main GUI, click Clients. The Bare Metal Restore Client List screen displays: 2. Click the button next to the name of the client you wish to restore, and click Configurations. The Configuration List for Client screen displays: 3. Click the button next the name of the configuration to use during the discovery, and click Discover. 190 VERITAS Bare Metal Restore System Administrator s Guide

213 Dissimilar Disk Restore (DDR) The Prepare to Discover Client screen displays: 4. Select a boot image from the Boot Image Name list. 5. Enter a name for the new configuration that you will save the discovered information to in the Discovered Configuration field. 6. Click OK. The Boot Client screen displays: 7. Boot the client to start the hardware discovery phase of the client restore. When the hardware discovery is complete, the client conveys this information according to platform type: An AIX client displays B55 on the LED display. Solaris and HP-UX clients display the following message: The Bare Metal Restore hardware discovery boot has concluded. Chapter 8, Advanced Features 191

214 Dissimilar Disk Restore (DDR) 8. On the Boot Client screen, click OK. The Configuration List for Client screen displays, showing the discovered hardware configuration from the discovery boot: You will now copy the appropriate source configuration to a new editable configuration. 9. Click the button next to the source configuration (in this case, current), and click Copy/Import. The Copy Configuration screen displays: 10. Pick the Source Client from the drop down list. This should be the client you are restoring. 11. Enter a new configuration name in the Destination Configuration field. Click OK. 192 VERITAS Bare Metal Restore System Administrator s Guide

215 Dissimilar Disk Restore (DDR) The Configuration List for Client screen displays the new editable configuration: 12. Select the new configuration name from the list by clicking the radio button next to it, then click Edit. The Configuration Summary screen displays: Chapter 8, Advanced Features 193

216 Dissimilar Disk Restore (DDR) 13. Click the Edit Volumes tab. The following screen displays: You will be using the information discovered from the client you are restoring to map the new configuration. 14. In the Discovered Client list, choose the name of the client you are restoring. 15. In the Discovered Configuration list, choose the name of the discovered configuration you specified in Step 5. Click OK. 194 VERITAS Bare Metal Restore System Administrator s Guide

217 Dissimilar Disk Restore (DDR) The Map Dissimilar Disk Restore screen displays: The lower portion of this screen displays the disk configuration information. The Available Disks column on the left displays a list of the disks that were discovered. One or more columns on the right display the configuration of the volume groups for HP-UX or AIX, VxVM disk groups for Solaris, or an unmanaged disk for Solaris. Each of these group columns (on the right) contains the following information: Original Disks Restore To MB Used File System A list of disks that were originally in the group A list of disks that will be used to recreate the group when the client is restored The amount of disk space used by the volumes or partitions in the group A list of file systems in the group and created on the volume or partition listed under Volume/Partition Chapter 8, Advanced Features 195

218 Dissimilar Disk Restore (DDR) Volume/Partition A list of logical volumes or partitions in the group. If a file system resides on the volume or partition, it is listed to the left. If the volume or partition does not have a file system, the file system column will show an ellipse:... From this screen, you can perform the following mapping and configuration: change the disks that make up a disk group control which file systems are restored control which logical volumes are created change the attributes of either a file system or a logical volume. 16. Map the new configuration: a. Check the box next to the name(s) of the logical volume(s) you want to restore. b. Check the box next to the name(s) of the file system(s) you want to restore. Note Given enough space, you can either select all the logical volumes and their file systems, or you can choose specific logical volumes/file systems. You do not have to restore all your logical volumes and file systems. For example, you may not have enough disk space with your new disk configuration. 196 VERITAS Bare Metal Restore System Administrator s Guide

219 Dissimilar Disk Restore (DDR) c. To add, replace, or remove a disk from a disk group, click the Change button. The following screen displays: To add a disk to the disk group, select the disk name in the Available Disks pane and click Add. The disk name will appear in the Current Disks pane. Note There are two cases where the partition information of a disk is important and must be retained: in the case of a Solaris basic disk (not managed by VxVM), and in the case of a Solaris VxVM managed disk that is encapsulated. In both cases, you must Replace the disk instead of using the Remove and Add functions. When a Remove function is performed, all partition information is lost. To replace a disk in a disk group, select a disk in the Available Disks pane, and select a disk in the Current Disks pane. Click Replace. The disk in the Current Disk pane will be replaced by the disk you chose in the Available Disks pane. To remove a disk in a disk group, select the name in the Current Disks pane, and click Remove to move it back to the Available Disks pane. d. Click Close to return to the main mapping screen. Chapter 8, Advanced Features 197

220 Dissimilar Disk Restore (DDR) e. To change the attributes of a file system or logical volume, click the name of the file system or logical volume in the group column. The following screen displays: f. Change the Disk Group or Size (MB) attributes. Click Close to return to the main mapping screen. 17. When you have finished mapping the disk configuration, click OK. 18. Prepare to Restore the client using the edited configuration. For details on the Prepare to Restore step, see Preparing to Restore a Client on page 136. Dissimilar Disk Restore for Windows Clients To perform a Dissimilar Disk Restore for a Windows client, you must complete additional configuration steps on the BMR main server GUI and on the restoring client. These additional steps enable you to map the saved configuration of the source client to the new disk configuration of the restore client. You will perform this step on the BMR main server GUI: Specify the Dissimilar Disk Restore option during the Prepare to Restore procedure. You will perform this procedure on the restoring client, during the restore: Map disk resources from the source client to the available drives on the restoring client. Use the following procedure to perform a Dissimilar Disk Restore for a Windows client. Note that the procedure takes place first on the BMR main server, then on the Windows client. 198 VERITAS Bare Metal Restore System Administrator s Guide

221 Dissimilar Disk Restore (DDR) To initiate a Dissimilar Disk Restore for Windows 1. In the BMR main GUI, click Clients. The Bare Metal Restore Client List screen displays: 2. Select the client you wish to restore by clicking the radio button to the left of the client name. Click Configurations. The Configuration List for Client displays: 3. Select the configuration to be used by clicking the radio button to the left of the name. Click Prepare to Restore. Chapter 8, Advanced Features 199

222 Dissimilar Disk Restore (DDR) The Prepare to Restore Client screen displays: 4. For Restore Options, click Dissimilar Disk Restore. Note For details on the other options available on the Prepare to Restore Client screen, see Preparing to Restore a Client on page Click OK. 6. On the BMR Windows client you wish to restore, load the boot floppy disk. 7. Reboot the client by turning the machine OFF, then ON. The restore begins. 200 VERITAS Bare Metal Restore System Administrator s Guide

223 Dissimilar Disk Restore (DDR) Near the beginning of the Windows phase of the restore process, the BMR Dissimilar Disk Restore Mapping Utility displays. Click Continue. The Mapping Utility displays the Original Disk Layout in the top panel, and the Mapped (New) Disk Layout in the bottom panel. When the Mapping Assistant first appears, the bottom panel represents the discovered empty disks on the restore target client. 8. Map each source client disk to the new disk layout. You can initiate the mapping step in two ways: Select the source client logical volume, in the top panel. Drag and drop the logical volume to the new disk in the bottom panel. or Right click the source client logical volume, in the top panel. Click Map. For partitions and single segment volumes, dropping on a destination disk completes the mapping step for that element. Chapter 8, Advanced Features 201

224 Dissimilar Disk Restore (DDR) For multi-segment volumes, such as mirrors or stripes, dropping on a destination disk invokes the Bare Metal Restore Disk Mapping Wizard: a. Click Next to continue. The Select New Partition or Volume Type screen displays: On this screen, you can change the partition or volume type. Note On Windows NT 4.0, only primary partitions may be selected. The mapping utility will automatically create logical drives and extended partitions as needed. 202 VERITAS Bare Metal Restore System Administrator s Guide

225 Dissimilar Disk Restore (DDR) b. Click Next. The Select Disks and Size screen displays: Use this screen to change the size of the partition or volume, and which disks it will be created on. Primary partitions and simple volumes require only one disk. Striped, mirror, and RAID5 volumes require multiple disks. Note that the wizard will not allow the size of a volume or partition to be reduced below the space required by all the files to be restored. Right click a partition or volume, then select Properties to display the Used filesystem space. c. Click Next. Chapter 8, Advanced Features 203

226 Dissimilar Disk Restore (DDR) The Format Partition screen displays: Use this screen to choose whether a partition is to be created and formatted, and whether files should be restored. The default is to create the partition, format it with a file system (for example, NTFS), and restore its files from NetBackup. NT 4.0 supports NTFS and FAT16 filesystems. Windows 2000 supports NTFS, FAT16, and FAT32 filesystems. The mapping wizard will automatically select the type of FAT filesystem based on the size of the partition. 204 VERITAS Bare Metal Restore System Administrator s Guide

227 Dissimilar Disk Restore (DDR) d. Click Next. The Completing the Map Volume Wizard displays a summary of the mapping you have chosen: Click Finish to return to the Dissimilar Disk Restore Mapping Utility window. e. Repeat step a through step d for each partition of the source client you wish to create or restore. Chapter 8, Advanced Features 205

228 Dissimilar Disk Restore (DDR) 9. When you have completely mapped all volumes and partitions, by simple drag and drop or using the wizard, the Mapping Utility screen will display your updated Mapped (New) Disk Layout. To continue the restore, click Done. 206 VERITAS Bare Metal Restore System Administrator s Guide

229 Storage Area Network (SAN) Co-Existence Storage Area Network (SAN) Co-Existence Bare Metal Restore provides the ability to recover a system attached to a Storage Area Network (SAN). BMR will restore any volumes on the internal (non fibre attached) disks. (System only restores of Solaris systems with internal FC-AL disks have been tested and are known to work.) Any volumes on SAN attached disks can be recovered through manual recovery procedures after BMR is used to recover the operating system and applications. With BMR there are two options to restore a system that has SAN attached devices: System only restore To achieve this type of restore, select Only system disks/volumes under Restore Options in the Prepare to Restore window. For details, see Preparing to Restore a Client on page 136. On AIX and HP-UX this will restore the root volume groups (rootvg and vg00 respectively). On Solaris this will restore all disks that have any of the root filesystems (/, /tmp, /var, /usr). On Windows 2000 and NT this will restore all disks that have %SystemRoot%, %SystemBoot%, and %TEMP%. Entire system restore To achieve this, select All disks/volumes under Restore Options in the Prepare to Restore window. Note For SAN attached systems this selection should be made with caution. If the HBA drivers and their configuration are not available in the SRT, BMR will not be able to restore the entire system. In these cases BMR will restore volumes on all internal disks and will not restore the SAN devices. On Windows platforms the SAN driver will be in the SRT and an attempt will be made to restore the SAN drives. Dissimilar System Restore Considerations If you are performing a Dissimilar System Restore on Windows, you will need to add the HBA drivers into the configuration. The HBA drivers can be added the same way as any other Mass Storage Driver. Please refer to DSR Restore Procedure: Adding New Drivers on page 172 of the Dissimilar System Restore chapter for details on how to add Mass Storage Drivers. In addition, when performing a Dissimilar System Restore you will need to reconfigure your SAN so that the HBA in the target system will be able to see the same devices as the HBA that existed in the source system. Chapter 8, Advanced Features 207

230 Storage Area Network (SAN) Co-Existence Dissimilar Disk Restore on UNIX Considerations If you are performing a Dissimilar Disk Restore on UNIX, remove the disks and do not restore the SAN Disk volume group. SAN Support Matrix The following support table shows the operating systems and HBAs that can co-exist with BMR. In other words, the (internal) system drives can be restored followed by a manual restore of the SAN drives as outlined above. Operating System Qlogic 2200 Emulex LP8000 JNI FCI-1063 Cambex PC1000 IBM 6228 HP A5158A Solaris X X X HP-UX X X AIX X X X Windows 2000 X X Windows NT X X Manual Recovery of Other Volumes After an AIX system is recovered using the "Only system disks/volumes" option you may need to perform the following steps for the SAN attached volumes: % redefinevg -d <device> <vgname> % varyonvg <vgname> % synclvodm <vgname> After a SAN attached HP-UX system is restored the following steps need to be performed to recover the SAN attached volumes. % vgimport -v <vgname> <pvpaths> % vgchange -a y <vgname> After a Solaris system is recovered using the Dissimilar Disk Restore feature, you may need to perform the following steps for SAN attached volumes. % diff /etc/vfstab /etc/vfstab.old.bmr.dmr 208 VERITAS Bare Metal Restore System Administrator s Guide

231 Storage Area Network (SAN) Co-Existence Review the changes. Make additional entries in /etc/vfstab that are related to the SAN devices that are listed in /etc/vfstab.old.bmr.dmr. At this point the file systems that were on the SAN devices are ready to be mounted. You can manually restore these file systems using NetBackup. Other Requirements In SAN environments, BMR requires the use of persistent bindings. You may need to modify the HBA driver configuration files to bind specific devices on the SAN to specific targets on the hosts. Known Issues with SAN Co-Existence: On AIX, the use of the IBM 6228 HBA requires the use of drivers that were supplied with the HBA. On SAN attached AIX systems, bmrsavecfg might produce warnings, if the SAN attached volumes are not available. These warnings need to be investigated as they might lead to BMR not being able to restore the SAN attached volumes. We highly recommend that you re-run bmrsavecfg after correcting the conditions that caused the warning. On Solaris, the use of the Qlogic 2200 HBA means that the drivers for this HBA should NOT be added to the SRT. Some Sun hardware comes with built-in Qlogic SCSI adapters and the Qlogic 2200 HBA driver is known to conflict with them. During a restore on Windows NT and Windows 2000, the BMR boot floppy may consider a SAN attached disk to be the first disk. By default BMR will use the first disk for the repair partition and will restore the operating system onto this SAN attached disk. Though this situation is possible, it has never been encountered. BMR does allow you the ability to select the disk to use for the repair and restore. To enable this selection, you will need to edit the BmrEnv.ini file that gets generated after a Prepare to Restore operation. The environment variable PICKBOOTDISK should be set to YES in the BmrEnv.ini file to enable this selection process. Chapter 8, Advanced Features 209

232 Point in Time Restore Point in Time Restore Bare Metal Restore provides the ability to restore a client to a state that was saved in a backup prior to the last backup. When to Use Point in Time Restore The ability to perform a Point in Time restore is useful when a recent software change has rendered the system unusable. Bare Metal Restore can be used, in conjunction with NetBackup, to restore the system state to some previous known working state. This is especially useful in cases where the most recent backup is of an unstable or undesirable system. The Point in Time (PIT) restore feature of BMR can be used when any of the following have occurred: A recent hardware change has destabilized the system. There may be cases where the software associated with the hardware cannot be cleanly removed. Instead of removing all the associated drivers and software, PIT can be used to recover the system to a known working state. A recent software addition has destabilized the system. Instead of finding a clean mechanism to de-install the software, PIT can be used to recover the system. A virus has attacked the system. Some critical system or application files have been accidentally deleted. Understanding the Point in Time Restore Process In a standard BMR recovery, BMR uses the saved machine configuration, the last full backup, and all incremental backups that occurred after the full backup to recreate the original system. In a Point in Time Restore, BMR can use a full backup older than the last full backup, and can control which incrementals are used. To restore the system to a known prior state, BMR requires one additional input, an end date for the restore. You specify this end date in a Retrieve from NetBackup window during the Prepare to Restore process. The following is the procedure for performing a Point in Time restore. The procedure is valid for both BMR UNIX clients and BMR Windows clients. You perform the procedure in the BMR Administration GUI. 210 VERITAS Bare Metal Restore System Administrator s Guide

233 Point in Time Restore To perform a Point in Time restore 1. On the main navigation bar, click Clients. The Bare Metal Restore Client List displays: 2. Select the client you want to restore by clicking the radio button to the left of the client name. Click Configurations. The Configuration List for Client displays: 3. Click Retrieve from NetBackup. Chapter 8, Advanced Features 211

234 Point in Time Restore The Retrieve from NetBackup screen displays: 4. Type in a name for the Destination Configuration. Supply an End Date for the retrieved configuration. Click OK. Note Configuration names must be alphanumeric. No special characters are allowed. The End Date entry should be in the format MM/DD/YYYY [HH:MM:SS], where the hours, minutes, and seconds are optional. BMR will use the End Date to retrieve a BMR configuration file from the client s NetBackup image. The retrieved configuration will be the last one that was backed up on or before the End Date. BMR creates a new configuration file each time a scheduled full, incremental, or server-initiated backup is started. The End Date is also used during the restore process. See step 5. Please note that retrieving the configuration from NetBackup may take a significant amount of time. The Configuration List for Client displays the newly retrieved configuration: 212 VERITAS Bare Metal Restore System Administrator s Guide

235 Point in Time Restore 5. Ensure that the timestamp associated with the Retrieved configuration is valid before proceeding. This retrieved configuration can be used to perform a Prepare to Restore operation. To perform a Prepare to Restore using this configuration, select the configuration using the radio button on the left column and click Prepare to Restore. The Prepare to Restore Client screen displays: The End Date that was used to retrieve the configuration is also used during the restore. BMR will automatically identify latest full backup that is earlier than the End Date. The Start Date of that full backup and the user-supplied End Date will become the restore window. The full backup and any incremental backups that fall within the restore window will be used to restore the client. For more details on the Prepare to Restore operation, see Preparing to Restore a Client on page 136. For more details on the restore process, see Restoring a Client on page 141. Chapter 8, Advanced Features 213

236 Service Packs for Windows Clients Service Packs for Windows Clients Some Windows NT/2000 clients may require a service pack during the restore process. For example, some clients have a network device that is only supported with a service pack. If this network device is used to do the restore, the service pack is required at restore time. Windows NT clients that require a service pack will need more reservation space (350 MB) as compared with clients that do not have a service pack (150 MB). For this reason, you must indicate whether a client requires a service pack when you configure the Windows NT client (see Configuring Windows Clients on page 55). If you have a Windows 2000 client that requires a service pack, skip to the section Creating a Service Pack, below. Including a Service Pack During Client Setup Specify that your client requires a service pack when setting up your client with the Client Setup Wizard. The process for client setup is explained in Configuring Windows Clients on page 55. The process for creating the service pack on the BMR file server is described in the next section, Creating a Service Pack on page 215. If your Windows client is already configured without the service pack option, you must rerun the BMR Client Setup Wizard. Specify whether a service pack is required on the following wizard panel (on NT): Service Pack Required is checked by default. If you have adequate space, we recommend accepting the default so that you have the option to use a service pack if it becomes necessary. 214 VERITAS Bare Metal Restore System Administrator s Guide

237 Service Packs for Windows Clients Note Only service packs that are required at restore time must be included on the BMR file server. However, the most flexible configuration is to select Service Pack Required. Creating a Service Pack To create a service pack on the Windows client 1. From the Start menu, click Programs>VERITAS Bare Metal Restore>Create Package. The following screen displays: Chapter 8, Advanced Features 215

238 Service Packs for Windows Clients 2. Click Next. The Create Bare Metal Restore Package screen displays: 3. Select Service Pack from the Package Type dropdown list. 4. Edit the Description to create a name that will help you identify this Service Pack. 5. From the File Server (hostname) dropdown list, choose the BMR file server that the Service Pack will be copied to. 6. In the Path to the Service Pack executable file field, specify the location of the service pack self-extracting executable file. Alternatively, use the Browse button to select the file from a browse window. 7. Click Finish. The service pack is copied from the specified location to the share directory on the specified BMR file server. This operation can be canceled at any time. 216 VERITAS Bare Metal Restore System Administrator s Guide

239 Service Packs for Windows Clients Note The share directory should be on the same file server as the SRT. The copy operation completes and the BMR database is updated. The Completed Successfully status screen displays : The service pack is successfully created. The Ok button becomes active. 8. Click Ok to end the Create Package wizard. 9. You will need to select in advance the Service Pack used during the Prepare to Restore step for this client. Refer to Modifying Client Configuration on page 122 for an example of how to add a service pack to a client configuration. Chapter 8, Advanced Features 217

240 Multiple Network Interface (Multihomed) Considerations Multiple Network Interface (Multihomed) Considerations From the perspective of the IP network and network interface cards, BMR recovery can be viewed as consisting of two parts: The interface and address to boot from (i.e., how to connect to the BMR Boot Server when network booting) The interface and address to restore from (i.e., how to connect to the NetBackup master and media servers to initiate file restore). These are referred to as the boot interface and the restore interface. Windows BMR clients don t actually network boot, but a boot interface must be configured to allow access to network SRTs on a BMR File Server. BMR Windows clients activate one interface during DOS time and are able to activate multiple interfaces during restore time. BMR UNIX clients must use a single interface to boot from and to restore through. This section describes the constraints and alternate approaches associated with multihomed environments. For the purpose of this discussion, the following definitions apply: BMR servers: includes BMR main server, BMR file servers, and BMR boot servers. NetBackup servers: includes NetBackup master servers, and any NetBackup media servers. Windows clients: BMR Windows NT and BMR Windows 2000 clients. General Constraints All BMR UNIX clients must communicate with BMR and NetBackup servers through one interface. That one interface must be the boot interface, which is the only one configured during a restore operation. All BMR Windows NT clients must communicate with all NetBackup servers through one interface called the restore interface. The restore interface can be different from the boot interface. The boot interface is specified during the Boot Options Wizard procedure and the restore interface is specified on the Prepare to Restore GUI screen. BMR servers must communicate with the BMR clients they are supporting through only one interface. This is the interface specified when the bmrsetupserver command is run. See below for potential workarounds to this constraint. The default route used during the restore is specified through the GUI, or with bmreditcfg. 218 VERITAS Bare Metal Restore System Administrator s Guide

241 Multiple Network Interface (Multihomed) Considerations The BMR gateway is specified through the GUI, or with bmreditcfg. The BMR gateway is used to establish host routes to the BMR main server and the BMR file server. The NBU gateway is specified through the GUI, or with bmreditcfg. Clients with Multiple Network Interface Cards (NICs) UNIX Clients In general BMR UNIX clients with multiple interfaces can network boot and restore over any one of the interfaces so long as the NetBackup and BMR servers are on a network reachable by that interface. One exception is the HP-UX BMR client, which (due to inherent Ignite-UX restrictions) must network boot and restore over the internal interface only. Windows Client Configuration The following diagram illustrates one of the many configurations that can occur with multihomed BMR clients. Network Network Chapter 8, Advanced Features 219

242 Multiple Network Interface (Multihomed) Considerations This configuration only works if BMR Client1 is a Windows (NT or 2000) machine. In this case you would create the boot floppy for Client1 with the Boot Options Wizard using the network interface on Network1. For NT clients you would specify the interface on Network2 as the Restore Interface specified on the Prepare to Restore Screen (not necessary for 2000 clients). UNIX clients will not work in this configuration because UNIX clients only use one network interface during the boot and restore operation. Client Configuration Using Gateways This section describes how to use BMR defined gateways. BMR clients can use gateways to communicate with BMR and NetBackup servers during a restore operation. The three BMR gateway attributes available are: BMRgateway NBUgateway DEFgateway Defines the gateway needed by the client to reach the BMR main server and the BMR file server during a restore. Defines the gateway to reach the NetBackup master server during restore. Defines the default gateway (default route) for the client during restore. 220 VERITAS Bare Metal Restore System Administrator s Guide

243 Multiple Network Interface (Multihomed) Considerations The following figure shows how BMR gateways can be used during a BMR client restore: The BMRgateway is used to define host routes to both the BMR main server and the BMR file server. (Only AIX supports BMR file servers on a different subnet than the BMR client.) The NBUgateway is used to define a host route to the NetBackup master server. The DEFgateway is set to the default route and can be used to reach multiple machines, for example, multiple media servers. If network3 contains NetBackup media servers then set the DEFgateway to G2. If network2 contains NetBackup media servers then set the DEFgateway to G1. Chapter 8, Advanced Features 221

244 Restoring NetBackup Media Servers (Solaris Only) Restoring NetBackup Media Servers (Solaris Only) You can use BMR to perform automated recovery of your NetBackup media servers on Solaris. Media servers may back up their data to local storage, or to storage that is available on another media server. BMR can restore either type of media server. BMR manages NetBackup media servers like other clients. However, using BMR to restore NetBackup media servers that back up their own data requires additional configuration steps. This section explains the differences in a media server recovery, and how to prepare your BMR configuration to perform this type of recovery. This section covers the following topics: Understanding NetBackup Catalogs and Catalog Backups Creating a Media Server Shared Resource Tree Performing a Media Server Restore Restrictions and Limitations Understanding NetBackup Catalogs and Catalog Backups NetBackup catalogs are internal databases that contain information about the NetBackup configuration and backups. Backup information includes records of the files and the media on which these files were stored. The catalogs also contain information about the media and the storage devices under the control of the media manager. Some parts of these internal databases are maintained on the NetBackup master server itself, and some parts are maintained on the NetBackup media servers. The parts that are maintained on the media server are called media server catalogs. For the purposes of explanation in this section, the word catalog will refer to the media server catalog only. NetBackup requires the catalog information in order to recover any backups that have been performed. Since the master server must be up and running to restore any NetBackup client, the parts of the catalogs that are present on a master server are always available. However, the media server catalogs, which are also required to restore the media server, will not be available on the media server that needs to be restored. This emphasizes the importance of catalog backups. The media server catalogs must be backed up regularly as recommended in the NetBackup System Administrator s Guide. BMR also saves its own backup of the media server catalogs to the BMR server. BMR uses the following terms to differentiate the two catalog backups: catalog backups: the catalog backups created by NetBackup cached catalogs: the catalog backups created by BMR 222 VERITAS Bare Metal Restore System Administrator s Guide

245 Restoring NetBackup Media Servers (Solaris Only) Catalog Backups: NetBackup NetBackup can be configured to back up the catalogs in three different ways: After each session of scheduled, user, or manual backups (recommended) After each session of scheduled backups Only when manually initiated Cached Catalogs: BMR To create the cached catalogs, BMR backs up the media server catalogs just before initiating the backup of the media server. The catalogs are also backed up along with the media server files (unless excluded). Depending which of the three catalog backup options is chosen, the cached catalogs can be newer or older than the catalog backups. BMR can use either of these backups while restoring the media server. The choice of which catalog backup should be used is made when the client is prepared for restore. See Selecting the Catalog Backup during the Prepare to Restore Process on page 229. Note If BMR is required to use the catalog backups instead of the cached catalogs, then the catalogs must be backed up to a media/master server other than the restoring media server. Creating a Media Server Shared Resource Tree An SRT for a standard BMR client has the NetBackup client software installed in it. However, an SRT used to restore media servers must have the NetBackup server software installed in it. Installing the NetBackup server software into an SRT is similar to installing the NetBackup server software on a real system; you are given the same prompts. However, since it is not required to do all the things that the install process would normally do on a real system, some of the responses to the prompts during the installation into the media server SRT are different. To create a media server SRT, use the standard SRT creation procedure as presented in Creating a Shared Resource Tree on page 66. The choice to create a media server SRT is made at the following prompt during the SRT creation procedure: You have the option to install the VERITAS NetBackup client software or the VERITAS NetBackup server sofware into the SRT. SRTs that contain the server software can be used to restore Media Servers as well as non Media Servers. SRTs that contain the client software can only be used to restore non Media Servers. If this SRT is to be used to Chapter 8, Advanced Features 223

246 Restoring NetBackup Media Servers (Solaris Only) recover Media Servers, you must install the VERITAS NetBackup server software into the SRT, and you need the VERITAS NetBackup server software for Solaris to do so. Do you want to install the VERITAS NetBackup server software [y/n]? [y]: The following procedure begins with this prompt. Many of the messages and errors that display during the process can be ignored, however, they are included in this procedure for clarity. User actions are denoted with a numbered procedure step. To create a media server SRT 1. During the SRT creation process, the following prompt will display: Do you want to install the VERITAS NetBackup server software [y/n]? [y]: Type y, and press Enter. The following prompt displays: Enter a [hostname:]/pathname containing VERITAS NetBackup server software [/export/share]: 2. Enter the device name or the path where the NetBackup install software is available. The following displays: Processing package instance <VRTSnetbp> from </tmp/bcreatesrt.bmr.nnn.mnt/solaris> Note All the pathnames in the following text that start with / are relative to the SRT path. Nothing in the actual system is changed by this installation process. Note sol8fs is the name of the BMR file server where this sample SRT is being created. Replace this name with the name of the BMR file server where you are creating the SRT. VERITAS NetBackup and Media Manager (sparc) 4.5,REV= Copyright VERITAS Software Corporation, All Rights Reserved. NetBackup and Media Manager binaries will be installed in /opt/openv and a link will be created from /usr/openv to /opt/openv 224 VERITAS Bare Metal Restore System Administrator s Guide

247 Restoring NetBackup Media Servers (Solaris Only) Is this okay? (y) [y,n,?,q] 3. Enter y. The following displays: The Solaris clients will be loaded. Do you want to load any other NetBackup clients onto the server? (y) [y,n,?] 4. Enter n. The following messages will be displayed, followed by a list of files being installed: Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. Installing VERITAS NetBackup and Media Manager as <VRTSnetbp> ## Executing preinstall script. Creating /opt/openv. Creating link from /usr/openv to /opt/openv. ## Installing part 1 of After the list of files is displayed, the following messages will be displayed. Copied files to /kernel/drv and to /kernel/drv/sparcv9. Doing add_drv of the sg driver drvconfig: modctl failed to add major number binding. No such device or address WARNING: /usr/sbin/add_drv failed. There may be no SCSI devices on this machine Media Manager configuration was NOT successful. 5. Ignore the error messages, but only if they are displayed exactly as shown. Any other informative messages can also be ignored. Chapter 8, Advanced Features 225

248 Restoring NetBackup Media Servers (Solaris Only) The following displays: The NetBackup and Media Manager binaries are installed. Read the release notes carefully. If you ran pkgadd instead of./install, you must run /usr/openv/netbackup/bin/install_bp to initiate NetBackup. Installation of <VRTSnetbp> was successful. Reboot client to install driver. 6. Ignore the message about rebooting the client. The following message displays: All additional keys should be added at this time. Do you want to add additional license keys now? (y/n) [y] 7. Enter n. The original client media server license keys will be used. The following displays: Use /usr/openv/netbackup/bin/admincmd/get_license_key to add, delete or list license keys at a later time. Installing NetBackup DataCenter version: 4.5GA Is sol8fs the master server? (y/n) [y] 8. Enter n. The following displays: What is the fully qualified name of the master server? 9. Enter the name of the machine where the SRT is being created, and press Enter. The following displays: Linking /usr/openwin/lib/app-defaults/xnb --> /usr/openv/netbackup/bin/xnb Checking for a bpcd entry in /etc/inetd.conf: Adding bpcd entry. Original /etc/inetd.conf saved as /etc/inetd.conf.nbu_ :42:50. Checking for a vnetd entry in /etc/inetd.conf: Adding vnetd entry. Checking for a vopied entry in /etc/inetd.conf: Adding vopied entry. Checking for a bpjava-msvc entry in /etc/inetd.conf: Adding bpjava-msvc entry. 226 VERITAS Bare Metal Restore System Administrator s Guide

249 Restoring NetBackup Media Servers (Solaris Only) Checking /etc/services for the needed NetBackup and Media Manager services. Copying original /etc/services file to /etc/services.nbu_ :44:03 Editing /etc/services to update NetBackup and Media Manager services. /etc/services will be updated to add the following entries for NetBackup/Media Manager. bprd 13720/tcp bprd bpcd 13782/tcp bpcd bpdbm 13721/tcp bpdbm vnetd 13724/tcp vnetd vopied 13783/tcp vopied bpjobd 13723/tcp bpjobd nbdbd 13784/tcp nbdbd visd 9284/tcp visd bpjava-msvc13722/tcp bpjava-msvc vmd 13701/tcp vmd acsd 13702/tcp acsd tl8cd 13705/tcp tl8cd tldcd 13711/tcp tldcd ts8d 13709/tcp ts8d odld 13706/tcp odld tl4d 13713/tcp tl4d tsdd 13714/tcp tsdd tshd 13715/tcp tshd tlmd 13716/tcp tlmd tlhcd 13717/tcp tlhcd lmfcd 13718/tcp lmfcd rsmd 13719/tcp rsmd To change these entries modify the file /tmp/services.ov_edited and enter <RETURN> when ready to continue: 10. Do not modify any of the entries. Press Enter. The following displays: /etc/services has been updated to contain NetBackup and Media Manager services. WARNING: ypwhich: the domainname hasn t been set on this machine. WARNING: ypcat: the domainname hasn t been set on this machine. Chapter 8, Advanced Features 227

250 Restoring NetBackup Media Servers (Solaris Only) Sending SIGHUP to inetd process. /usr/openv/volmgr/bin/update_services: usage: kill [ [ -sig ] id... -l ] 11. Ignore the above warnings and errors. The dialog continues as follows: To make NetBackup and Media Manager startup automatically when the system is restarted, the netbackup script found in /usr/openv/netbackup/bin/goodies/netbackup has been placed in /etc/init.d, with links to it placed in the /etc/rc2.d directory. To make NetBackup and Media Manager shutdown automatically when the system is restarted, the netbackup script found in /usr/openv/netbackup/bin/goodies/netbackup has been placed in /etc/init.d, with links to it placed in the /etc/rc0.d directory. Extracting NetBackup-Java product files. Installing NetBackup-Java, and the Java runtime environment for SunOS 5.8. Configuring NetBackup-Java runtime environment. The installation of the NetBackup-Java product on sol8fs is complete. Could not connect to vmd on host sol8fs (70) WARNING: Get global device configuration host failed. Enter global device host (default: sol8fs): 12. Ignore the error message. Press Enter. The following displays: Could not connect to vmd on host sol8fs (70) Set global device configuration host failed. The global device database version is incompatible 13. Ignore these error messages. The following prompt displays: 228 VERITAS Bare Metal Restore System Administrator s Guide

251 Restoring NetBackup Media Servers (Solaris Only) Do you want to start the Media Manager device daemon processes? (y/n) [y] 14. Enter n. The following prompt displays: Enter a patch or package name to install additional software in SRT, or nothing if done: []: This is the end of the SRT creation procedure that is specific to a media server SRT. For the rest of the SRT creation process, refer to Creating a Shared Resource Tree on page 66. Performing a Media Server Restore When you need to restore a media server, you must decide whether to use the cached catalogs created by BMR, or the catalog backups created by NetBackup. For a discussion of catalog backups, see Understanding NetBackup Catalogs and Catalog Backups on page 222. This section contains two subsections that explain the media server restore procedure. Selecting the Catalog Backup during the Prepare to Restore Process explains the criteria for choosing either the cached catalogs or catalog backups. Restore Time Actions explains how the process for a media server restore differs from the restore process for a standard BMR client. Selecting the Catalog Backup during the Prepare to Restore Process During the restore process, BMR can use either the cached catalogs created by BMR, or the catalog backups created by NetBackup. You choose which catalog to use at restore time on the Prepare to Restore screen. The Prepare to Restore screen has a checkbox called Use Cached Catalogs. If you check this box, BMR will use cached catalogs, and the restore process will be completely automated. If you leave this box unchecked, BMR will use the catalog backups. This introduces a manual step in the restore process. Refer to Restore Time Actions, below, for details on performing this step. The following discussion will help you to decide whether to use cached catalogs or catalog backups. Chapter 8, Advanced Features 229

252 Restoring NetBackup Media Servers (Solaris Only) Cached Catalogs: BMR To create the cached catalogs, BMR backs up the media server catalogs just before initiating the backup of the media server. The catalogs are also backed up along with the media server files (unless excluded). Catalog Backups: NetBackup NetBackup can be configured to back up the catalogs in three different ways: After each session of scheduled, user, or manual backups (recommended) After each session of scheduled backups Only when manually initiated Depending which of these three options is chosen, the cached catalogs can be newer or older than the catalog backups. When to Use Catalog Backups It is usually safe to use the cached catalogs, even if the cached catalogs are older than the catalog backups. This will preserve an automated restore process. However, there are instances where you might consider using the catalog backups, such as the following: New volumes are added to NetBackup between the time the catalogs are backed up by BMR and the time the catalogs are backed up by NetBackup, thus making the cached catalogs inconsistent with catalog backups. If BMR uses the cached catalogs to restore the media server, the catalogs that are restored from the media server s backup are retained on the system. This might result in outdated catalogs on the media server, if the catalogs that are in the media server s backup are not consistent with the catalog backups made by NetBackup (i.e., if cached catalogs are older than the catalog backups). However, if BMR uses the catalog backups, then these catalogs are copied to restored system, thus making the catalogs on the restored media server most current and consistent with the NetBackup master server. The cached catalogs are deleted or corrupted. Restore Time Actions The process for restoring a media server will be different from a standard restore based on whether you choose to use the cached catalogs or the catalog backup during the Prepare to Restore step. The procedure below reflects this difference. This procedure will only demonstrate the steps specific to restoring a media server. For details on the other steps in the Prepare to Restore and actual restore process, see Preparing to Restore a Client on page 136 and Restoring a Client on page VERITAS Bare Metal Restore System Administrator s Guide

253 Restoring NetBackup Media Servers (Solaris Only) To restore a media server 1. Choose whether to use the cached catalogs or the backup catalogs for the media server restore. See Selecting the Catalog Backup during the Prepare to Restore Process on page 229. Make your selection on the Use Cached Catalogs checkbox on the Prepare to Restore screen. If you choose to check Use Cached Catalogs, the rest of the Prepare to Restore process continues as for a standard restore. The restore process that follows is automated and requires no manual intervention. If you leave Use Cached Catalogs unchecked, you are specifying that you would like to use catalog backups for the restore. Proceed to step Complete the Prepare to Restore procedure as specified in Preparing to Restore a Client on page Perform the client restore process according to the platform of the media server, as specified in Restoring a Client on page 141. During the restore process, the following prompt will display on the console of the restoring media server: Media server catalogs are required to proceed further with the restore. When prepare to restore was done for this client, option was chosen to restore the catalogs manually. To restore the catalogs, please run the bprecover command on the NetBackup server where the catalogs for this media server are backed up. Restore process will continue after the catalogs become available. Chapter 8, Advanced Features 231

254 Restoring NetBackup Media Servers (Solaris Only) Waiting for the media server catalogs to become available At this point, run one of the following commands on the NetBackup server where the catalogs of this media server are backed up: If you know the id of the media where the catalogs are backed up, run bprecover r m media_id d density dhost destination_host where media_id is the id of the media where the catalogs are backed up, destination_host is the name of the media server. If the catalogs are backed up on a tape device, run bprecover r tpath raw_tape_device_path dhost destination_host where raw_tape_device_path is the raw device name of the tape device, destination_host is the name of the media server. If the catalogs are backed up to a directory, run bprecover r dpath directory_path dhost destination_host where directory_path is the pathname of the directory where the catalogs are backed up destination_host is the name of the media server. If the catalogs are backed up to an optical device, run bprecover r opath optical_device_path dhost destination_host where optical_device_path is the device name of the optical device, destination_host is the name of the media server. The -dhost option only indicates the name of the system where the catalogs are to be restored, not the name of the system whose catalogs are to be restored. Hence, the bprecover command will prompt the user for every catalog found in the catalog backups. 5. Select the catalogs that belong to the media server being restored. 232 VERITAS Bare Metal Restore System Administrator s Guide

255 Restoring NetBackup Media Servers (Solaris Only) To help you with the selection, the command prints the name of the catalog and the NetBackup server to which that catalog belongs. Be very careful to answer y to only those catalogs that belong to the media server being restored. If you answer y to a catalog that does not belong to the media server, the restore will most likely fail, and you have to start the restore process all over again by rebooting the client. Media server catalogs consist of three sets of files, so the name of the media server will appear three times when bprecover is run. Accordingly, you will be answering y three times when bprecover runs. Note that after you select the three sets of files by entering a y for each, bprecover may continue to present choices. 6. Enter n until bprecover exits, or press Ctrl+C. The restore process will automatically resume on the restoring media server. Restrictions and Limitations Please note the following important restrictions and limitations for a media server restore: If cached catalogs were used during restore, run the bprecover command on the NetBackup server where the catalogs are backed up (as explained in Restore Time Actions on page 230), after the client is successfully restored. This will ensure that the databases on the media server are up to date. Catalog backups cannot be used if the catalogs were backed up to the same media server that is being restored. In this scenario, use only cached catalogs for the restore. Catalog backups cannot be used if the media server is the robot control host. In this scenario, use only cached catalogs for the restore. The SRT OS level must be the same as the media server being restored. For example, a Solaris 8 SRT must be used to restore a Solaris 8 media server. For media server recovery to work, media server cannot be the volume database host, the gloabal device database host, or the device allocator (DA). If the robot control host is not in the bp.conf file on the media server, you must add it via the Edit Network screen in the BMR Administration GUI. Host names in the bp.conf file must match the names in the global device database. Media server recovery currently works with directly attached SCSI devices/robots (TLD, TSD, standalone, etc.). API robots are not yet supported. Chapter 8, Advanced Features 233

256 Restoring the BMR Server Restoring the BMR Server If disaster strikes and your BMR main server is dead, use the instructions in this section to get the BMR servers up and running so you can restore your BMR clients. There are many different ways to successfully back up and recover BMR servers. A less comprehensive backup may require a more detailed restore procedure. For example, the minimum that should be backed up for BMR servers would be: required: /var/bmr/* on the BMR server suggested: tftpboot/* or /opt/ignite/* on the BMR boot server suggested: all SRT paths on the BMR file server suggested: smb.conf on BMR file servers configured with SAMBA BMR server functions can then be manually transferred to another machine using the following procedure. (Depending on backup and recovery methods used, steps 1 to 6 and 9 to 10 may be unnecessary if the recovery procedure fulfills the equivalent requirement.) To restore the BMR servers 1. Install the OS on the BMR Server, if needed. 2. Install the BMR server software. 3. Install VERITAS NetBackup client software. 4. Recreate the bmradmin user and group. IDs must match the owner of files in /var/bmr or you should own the appropriate files and directories under var/bmr. 5. Restore the BMR databases that were backed up to NetBackup (/var/bmr). 6. Restart the BMR daemons. 7. If the BMR main server is also a BMR file server or BMR boot server, you must restore the SRTs. The definitions are in the BMR database (/var/bmr/conf/srt/*). 8. If SAMBA is used, you must re-install SAMBA from BMR. This should happen when you run bmrsetupserver after installing the BMR server code. Responses to questions should be the same as the original responses. 9. Re-create the SAMBA user in /etc/passwd (if it is not already there). 10. Restore the smb.conf file: On AIX: /usr/local/lib 234 VERITAS Bare Metal Restore System Administrator s Guide

257 Restoring the BMR Server On Solaris: /opt/samba/lib On HP-UX: /opt/samba/lib Chapter 8, Advanced Features 235

258 Restoring the BMR Server 236 VERITAS Bare Metal Restore System Administrator s Guide

259 Tips and Troubleshooting 9 This chapter provides additional tips on how to ensure smooth operation of BMR: Finding the Correct MSD Driver Identifying the Vendor Partition During a Client Restore Recovering from Erroneous Input While Working with Generic Boot Floppies (Windows) Removing BMR Servers AIX LED Progress Codes This chapter also provides some troubleshooting steps to take in the event that you experience problems during a restore process. The following sections present the problems you may encounter, along with steps to solve the problems: Solaris 2.6 Causing Panic on Net or CD-ROM Boot AIX Boot Failure Problems Booting from CD Long Restore Times on HP-UX Windows Media Boot Failure on Client with Multiple CD-ROM Drives Restore Failure of Windows BMR Clients with Multiple Identical NIC Cards The bmrd Daemon Does Not Start During bmrsetupserver Networking Problems at DOS Phase during Windows Client Restores Failed Restores after Changing the NetBackup Server Information 237

260 Tips Tips Finding the Correct MSD Driver When you add an MSD driver, bmrcreatepkg.exe may supply more than one option. The following procedure explains how to determine the correct name for the MSD driver you wish to add. Note This applies to Windows NT clients with BMR installations older than 4.5. To find the correct MSD Driver 1. Find the driver file name: a. Click Start > Settings > Control Panel > SCSI Adapter. b. Right click on the desired controller and click Properties. c. Select the Driver tab and note the driver file name (for example: cpqarry2.sys). 2. In the driver diskette (or CD), open the 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 Controllers [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 238 VERITAS Bare Metal Restore System Administrator s Guide

261 Tips [Files.SCSI.fbr_40] driver = d3,cpqsmgrk.sys,cpqsmgrk driver = d3,cpqfcalm.sys,cpqfcalm inf = d3,cpqfcalm.inf [Files.SCSI.ftr_40] 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 This option should be chosen when adding drivers. Identifying the Vendor Partition During a Client Restore 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. You indicated that a special partition must be saved when you created the boot floppy. 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): The vendor partition must be less than 1 GB. The vendor partition must start at the beginning of the drive. The vendor partition must not be recognized as a DOS primary partition. The partition type must be unique to other partitions on the drive. To identify the vendor partition to save During the client restore you are prompted for which partition to save: If there is more than one partition, choose the partition with a non-zero size. Chapter 9, Tips and Troubleshooting 239

262 Tips If more than one partition has a non-zero size, choose the one with 'Cylinder' zero Recovering from Erroneous Input While Working with Generic Boot Floppies (Windows) You can reboot the system while booting from generic boot floppies if: Erroneous data is entered. Data entered needs to be changed. To reboot the system: 1. Enter Ctrl+Alt+Delete (or Reset the system) 2. Immediately after the message Switching to GUI mode is displayed on the screen, press the Esc key until you see the message, Do you really want to quit (y/n)? 3. Type Y 4. Press Enter 5. At the DOS prompt, enter the following command: gui -s 0 6. Reboot the system. 7. Enter the correct data at the next series of prompts. Removing BMR Servers You may need to uninstall BMR from a particular machine. For example, if you installed BMR for evaluation and do not have a license key, you will want to uninstall BMR. The following procedure explains how to uninstall BMR. To uninstall a BMR server 1. Edit /etc/inittab. Remove the two 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 240 VERITAS Bare Metal Restore System Administrator s Guide

263 Tips The first is the httpd daemon, the second is the BMR daemon. 2. Stop the BMR related daemons; use ps -ef grep bmr. bmradmin :02:08? 0:00/opt/BareMetal/httpd/bin/httpd -d /var/bmr/httpd root :02:03? 0:00 /opt/baremetal/sol/bmrd-p 8362 root :02:07? 0:00 /opt/baremetal/httpd/bin/httpd -d/var/bmr/httpd bmradmin :02:08? 0:00/opt/BareMetal/httpd/bin/httpd -d /var/bmr/httpd Use kill -9 <PIDnumber> to stop the daemons. 3. If you have installed SAMBA, you can remove the SAMBA filesets if desired. See Step 5, below. You should also stop the nmbd daemon; use a ps -ef grep nmb. Use kill <SAMBA s PID number> to stop the daemon 4. Ensure that any file system(s) 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 (List: you should see a samba directory.) Use smitty to remove the fileset bmr.samba.rte. For Solaris: cd /var rm -R bmr (Be very careful with removal; check your command line before pressing Enter.) Chapter 9, Tips and Troubleshooting 241

264 Tips cd /export/srt rm -R * (Be very careful with removal; check your command line before pressing Enter.) Use pkgrm BMRserver to remove the BMR filesets: cd /opt ls (List; you should see a samba directory.) Use pkgrm to remove the filesets SAMBAusr and SAMBAroot. For HP-UX: 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 SAM to remove the BMR filesets cd /opt ll (List; you should see a samba directory.) Use SAM to remove the fileset BMRsamba. AIX LED Progress Codes AIX LED Progress Codes When an AIX system is network booting during BMR restore, or during BMR Dissimilar Disk Restore, the following LED codes are displayed to indicate the steps in progress. If an LED continually flashes with one of these codes, that step has failed. Another digit will also be flashed to indicate the failure reason. b11 relinkspotnet:cd /usr/lib/methods b12 relinkspotnet:ln /usr/lib/methods b13 relinkspotcd:mkdir /cdrom 242 VERITAS Bare Metal Restore System Administrator s Guide

265 Tips b14 b15 b16 b17 b18 B19 b20 b21 b22 b23 b24 b25 b26 b27 b28 b29 b31 b32 b33 b34 b35 b36 b55 relinkspotcd:umount /SPOT relinkspotcd:mount /cdrom relinkspotcd:rmdir /SPOT relinkspotcd:ln /SPOT relinkspotcd:cd /usr/lib/methods relinkspotcd:ln /usr/lib/methods relinkspotcd:cd /usr/sbin relinkspotcd:ln /usr/sbin relinkspotcd:cd /usr/bin relinkspotcd:ln /usr/bin relinkspotcd:cd /usr/lib/drivers relinkspotcd:ln /usr/lib/drivers relinkspotcd:overmount /usr MAIN:cp srcfile /etc/objrepos MAIN:cfginet MAIN:find network adapter MAIN:configure loopback MAIN:configure TCPIP MAIN:bmrcpull CLipaddr.info MAIN:bmrcpull CLname.conf MAIN:bmrcpull CLname MAIN:disk mapping complete MAIN:ready for mapping Chapter 9, Tips and Troubleshooting 243

266 Tips If you are unable to resolve the error indicated, please contact customer support. 244 VERITAS Bare Metal Restore System Administrator s Guide

267 Troubleshooting Troubleshooting Solaris 2.6 Causing Panic on Net or CD-ROM Boot Symptoms Certain Solaris systems can cause a panic when booting from some Solaris 2.6 boot images. The symptoms are that the network or CD-ROM 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. This may affect E3000-E10000 model machines, but could affect others as well. Problem The problem relates to 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 Bare Metal Restore SRTs built using those Solaris 2.6 CDs) will also have the panic problem. Solutions There are two possible solutions, with some variations: Approach 1: Use the limit-ecache-size Open Boot PROM (OBP) command approach. Approach 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 or later, but has not been thoroughly tested. Chapter 9, Tips and Troubleshooting 245

268 Troubleshooting 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. To test if the PROM supports limit e-cache size At the ok> prompt, type 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. To define the limit e-cache size 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 246 VERITAS Bare Metal Restore System Administrator s Guide

269 Troubleshooting 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. To test if the PROM forces hardware resets too often 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. To use the NVRAMRC to make limit-ecache-size persistent 1. Use the nvedit command at the ok> prompt: ok> nvedit (The current contents of NVRAMRC display.) 2. Use Control-N to move to the last line of NVRAMRC. Use Enter to start a new blank line. 3. 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 4. Use Control-C to exit nvedit. 5. Use the nvstore command to save the NVRAMRC contents: ok> nvstore 6. Test the current setting of use-nvramrc?: ok> printenv use-nvramrc? 7. 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 Bare Metal Restore. Chapter 9, Tips and Troubleshooting 247

270 Troubleshooting 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 remove the command, use the following procedure. To remove the limit-ecache-size command from NVRAMRC after the machine is restored 1. Use the nvedit command at the ok> prompt: ok> nvedit (Current contents of NVRAMRC displays) 2. 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.) 3. 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). 4. Use Control-C to exit nvedit. 5. 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 CD-ROM 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 and has not been as thoroughly tested. Sun has documented that patch or later (which almost certainly requires patch 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. 248 VERITAS Bare Metal Restore System Administrator s Guide

271 Troubleshooting To test if patch(es) are already in place 1. 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 2. Run: patchadd -p -d /cdrom/cdrom0/s0/solaris_2.6/tools/boot and look in the output for patch or later. If not present, either use Approach 1, or proceed with the following. Workaround 2.A: To use the full e-cache patch 1. Download and install the patch(es) needed in the SRT from sunsolve.sun.com. Locate the current version of patch and its prerequisites. Currently these would be and Note that the patches need to be in directory format, so unspool them if necessary after downloading using the patchadd -s option. 2. Add them to your SRT after NetBackup 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. AIX Boot Failure Problem AIX or greater booting from a boot image (BI) doesn't work. Solution AIX introduced 'chrp' support (devices.chrp.* filesets). So, if the client is a 'chrp' it must boot from a BI created from a or later. Chapter 9, Tips and Troubleshooting 249

272 Troubleshooting Problems Booting from CD AIX and Solaris platforms use a common bootable CD format (ISO-9660). HP-UX uses LIF. 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.) 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. 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. 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 successful burns that fail due to system load. Using the test after writing option offered by some CD writing software may help detect unsuccessful 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. A common cause of corruption is transferring the file with FTP in ASCII transfer mode. 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. Verify that you are using the correct procedures to boot the client machine from CD. 250 VERITAS Bare Metal Restore System Administrator s Guide

273 Troubleshooting Long Restore Times on HP-UX Symptom BMR users have found unusually long BMR restore times on some 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. You need to access the LAN Configuration commands to change the media speed. To change the media speed on HP-UX 1. From the boot console prompt Press any key... The Main menu displays. The Main menu has the following commands: Command BOot [PRI ALT [<path>] PAth [PRI ALT CON KEY] [<path>] SEArch [DIsplay IPL] [<path>] Description Boot from specified path Display or modify a path Search for boot devices COnfiguration [<command>] INformation [<command>] SERvice [<command>] Access Configuration menu/commands Access Information menu/commands Access Service menu/commands DIsplay HElp [<menu> <command>] RESET Redisplay the current menu Display help for menu or command Restart the system 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 Chapter 9, Tips and Troubleshooting 251

274 Troubleshooting...<snip>... LanConfig [<params>] Display or set LAN configuration...<snip> 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 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 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) 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 Restoring a BMR Client on page VERITAS Bare Metal Restore System Administrator s Guide

275 Troubleshooting Windows Media Boot Failure on Client with Multiple CD-ROM Drives Symptom During a media restore on a Windows client, booting from the floppy fails and the BMR DOS GUI does not display. Instead, the following message appears: Couldn t find any BMR CD in the drive(s) Please insert a correct BMR CD. Problem This boot failure will occur in Windows clients with more than three CD-ROM drives. The problem occurs because msdcdex is set to start setting drives with the letter X. As a result, only X,Y, and Z are available (one for each drive). Since there are no more letters to assign to the fourth drive, none of the drives will be set up (per normal mscdex operation). Solution To support a restore on a client with four or more CD-ROM drives, you must modify the autoexec.bat file in the custom boot floppy. The following procedure explains the steps for modifying the file. To modify the autoexec.bat file to allow more than three CD-ROM drives 1. Set the following INITLETTER=addedletter to enable the number of drives (X=3 W=4 V=5, and so on) 2. Add the comparison: if(%driveletter%)=(added letter) goto addedletterletter for each of the added letters (W, V, etc). 3. Add the following: :addedletterletter set DRIVELETTER=Next Letter goto START 4. Save autoexec.bat Chapter 9, Tips and Troubleshooting 253

276 Troubleshooting The following shows a sample autoexec.bat file with the appropriate changes made. Added or changed information, for the sake of this example, is bolded. set INITLETTER=W set DRIVELETTER=%INITLETTER% :START command /f/c vol %DRIVELETTER%: bmrfind label>nul if ERRORLEVEL 1 goto ADRIVE if ERRORLEVEL 0 goto NODRIVE :NODRIVE if (%DRIVELETTER%)==(W) goto WLETTER if (%DRIVELETTER%)==(X) goto XLETTER if (%DRIVELETTER%)==(Y) goto YLETTER if (%DRIVELETTER%)==(Z) goto EMPTYDRIVES :WLETTER set DRIVELETTER=X goto START :XLETTER set DRIVELETTER=Y goto START :YLETTER set DRIVELETTER=Z goto START Restore Failure of Windows BMR Clients with Multiple Identical NIC Cards Symptom The wrong network interface is activated and the client restore fails during the DOS portion of the recovery. Problem DOS does not always identify PCI slot numbers in the same way that Windows does. Therefore, during the DOS portion of the restore, DOS does not use the correct slot number for the NIC card specified for connection to the BMR file server. 254 VERITAS Bare Metal Restore System Administrator s Guide

277 Troubleshooting Solution There are two ways to resolve this problem. You can move the network cable to the NIC that is active during DOS time. Alternately, you can recreate the BMR DOS boot floppy using the BMR Boot Options Wizard, and specify another Slot Number on the Select Client screen. The bmrd Daemon Does Not Start During bmrsetupserver Symptom On a Solaris server, the bmrd daemon does not start during bmrsetupserver and the /var/bmr/log/bmrd.err file indicates that libucb.so is not found. Problem BMR main servers, file servers, and boot servers that run on a Solaris platform require libucb libraries. The libucb libraries are installed as part of the SUNWscpu package. Solution Install SUNWscpu on the BMR server in question. Networking Problems at DOS Phase during Windows Client Restores The following config.sys is used by BMR during the DOS phase while restoring a Windows client. files=30 SHELL=A:\COMMAND.COM /P /E:4096 DEVICE=A:\BIN\IFSHLP.SYS lastdrive=z DEVICE=A:\BIN\HIMEM.SYS DEVICE=A:\BIN\EMM386.EXE i=b000-b7ff NOEMS DOS=HIGH,UMB The sixth line from the top in this file has significant implications: DEVICE=A:\BIN\EMM386.EXE i=b000-b7ff NOEMS There can be three classes of machines in terms of how this line is used: Machines that will work with this line as it is. Chapter 9, Tips and Troubleshooting 255

278 Troubleshooting Most (more than 95%) of the machines belong to this class. Machines that will need additional options added to this line. On some machines, the DOS phase of the restore may fail, indicated by a red X next to the Loading NIC Drivers, Starting Networking, or Retrieving Client Information status lines. If this occurs, press F1 to view the details. Check the status window for the following error: Error 8: There is not enough memory available. This error indicates that there is not enough memory available to bring up the networking. On machines that exhibit this problem, change this line to the following: DEVICE=A:\BIN\EMM386.EXE i=b000-b7ff i=e000-efff NOEMS Machines that will need this line to be removed altogether. There are some BIOS + NIC driver combinations that do not work well with EMM386. Such machines may hang while booting the PC-DOS. The system will not respond to any key strokes or to Ctrl + Alt + Delete. If this problem is noticed, remove this line completely from the file. Failed Restores after Changing the NetBackup Server Information Symptom A client fails to restore, with the following error displayed on the client s console: Restoring files Restore FAILED Failed command: /usr/openv/netbackup/bin/bprestore -L... Problem The client's configuration on the BMR main server was edited to change the NetBackup master server information (name and/or IP address of the NetBackup server). 256 VERITAS Bare Metal Restore System Administrator s Guide

279 Troubleshooting Solution In such cases, check that the /usr/openv/netbackup/db/altnames directory on the NetBackup server has an entry for the host name (the canonical name) corresponding to the IP address of the client s boot interface. If it is not present, add the entry, then retry the restore. Chapter 9, Tips and Troubleshooting 257

280 Troubleshooting 258 VERITAS Bare Metal Restore System Administrator s Guide

281 Upgrades and the Patch Mechanism A This section describes the upgrade and patch mechanisms for Bare Metal Restore. Upgrades from BMR 4.5 are allowed. Upgrades from versions of Bare Metal Restore prior to 4.5 are not allowed. 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, use a patch. Check the VERITAS web site for patches. Patches can be downloaded from Click Support > Support Downloads. Note All BMR servers must be running the same version of BMR software. 259

282 Features Features Upgrades: installs a new version of the product, replacing the old. Patching: tracks and logs the 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. Upgrading from Bare Metal Restore 4.5 You can install Bare Metal Restore 4.6 as a brand new installation, or you can upgrade your existing Bare Metal Restore 4.5 installation. Upgrades from Bare Metal Restore versions prior to BMR 4.5 are not supported. Upgrade the BMR main server first, and then upgrade all of the file servers and boot servers in any order. All BMR servers must be upgraded for BMR to function correctly. It is not necessary to upgrade BMR clients. However, we recommend that you upgrade the clients when it is convenient to do so. Space Requirements for Upgrading BMR Main Servers Upgrading a BMR Main Server requires at least 15MB + (100K * Number of BMR clients) of free space in /var directory. Caution If there is not enough free space in the /var directory, the upgrade process may fail, leaving the BMR in an unusable state. If that happens, you must reinstall and reconfigure the BMR Main Server and rerun bmrsetupclient on all of the BMR clients. This requirement does not apply to upgrading BMR File Servers and BMR Boot Servers. Deletions Resulting from Upgrade Installation Performing an upgrade from BMR 4.5 to BMR 4.6 deletes the following Bare Metal Restore configuration components: All created Shared Resource Trees 260 VERITAS Bare Metal Restore System Administrator s Guide

283 Support for BMR 4.5 Clients Only the database entries are removed, but not the directories where the Shared Resource Trees are created. You must manually remove those directories. All created packages All created boot images All created media boot images You must recreate all Shared Resource Trees, packages, boot images, and media boot images for use with your BMR 4.6 installation. If the Prepare to Restore step has been performed on any BMR clients, this step must be repeated after the above components have been created with the BMR 4.6 system. Upgrade Installation Procedure The procedure for upgrading your BMR servers and clients from version 4.5 to version 4.6 is the same as for an initial installation, with one exception. During a Solaris server or client upgrade installation, you will use a different command string for pkgadd. This difference will be noted in the Solaris installation procedure in the server installation chapter and the client installation chapter. Use the instructions in these chapters, BMR Server Installation and Configuration on page 27 and BMR Client Installation and Configuration on page 43, to perform your initial or upgrade installation. Support for BMR 4.5 Clients Migrated Client Configurations Bare Metal Restore 4.6 introduces the concept of client configurations. A configuration is a set of data collected in the client and pushed to the server by bmrsavecfg. To support a BMR 4.5 client, the BMR 4.6 server must generate a new configuration based on the data collected by the 4.5 version of bmrsavecfg. BMR 4.6 calls this resulting configuration a migrated configuration. There are two ways to generate a migrated configuration: using the main BMR GUI, and running the bmrmigrate command on the BMR server. To generate a migrated configuration from the Bare Metal Restore Client List in the BMR GUI, click the radio button to the left of the client name and click Configurations. The migrated configuration is automatically generated. Appendix A, Upgrades and the Patch Mechanism 261

284 Support for BMR 4.5 Clients To generate a migrated configuration from the command line, run the following command from the BareMetal path, supplying the name of the client in hostname,netbackupserver pair format:./bmrmigrate sol37,sol12 where sol37 is the client hostname and sol12 is the NetBackup server. A migrated configuration will always be called migrated on the Configuration List for Client screen. It will be a Read-only configuration, and therefore not editable. Restoring a Client Using a Migrated Configuration In most cases, a migrated configuration can be used to restore a client like any other configuration: In the Configuration List for Client, click the radio button left of the name of the configuration ( migrated ), and click Prepare to Restore. Follow the further directions for a restore in Restoring a Client on page 141. The only exception to the above is when DNS and other advanced routing data is required for the environment. Since BMR 4.5 does not capture this information, the migration process is not able to generated it in the migrated configuration. In this scenario, use the following procedure to restore the client from the migrated configuration. To restore an advanced routing data client with a migrated configuration 1. From the Bare Metal Restore Client List, select the client to be restored and click Configurations. The Configuration List for Client screen displays. 262 VERITAS Bare Metal Restore System Administrator s Guide

285 Support for BMR 4.5 Clients 2. Click the radio button to select the migrated configuration, and click Copy/Import. The Copy Configuration screen displays. 3. Select the client to restore from the Source Client list. Ensure that the Source Configuration is migrated. Enter a name for the new Destination Configuration. Click OK. The Configuration List for Client displays the newly-created configuration. 4. Click the radio button to select the new configuration, and click Edit. Appendix A, Upgrades and the Patch Mechanism 263

286 Support for BMR 4.5 Clients 5. On the Configuration Summary screen, click the Edit Network tab. 6. Enter the DNS and other advanced routing data. If you are restoring a Windows NT client with multiple interfaces, remove all of interfaces but the one that will be used to restore (the one that communicates with the NetBackup server). Click OK. 7. From the updated Configuration Summary screen, click Prepare to Restore to proceed with the restore. Upgrading Migrated Clients to 4.6 If a 4.5 client that already had a migrated configuration is upgraded to BMR 4.6, the migrated configuration will remain in the BMR server. Delete any migrated configurations for the upgraded client, as well as any configurations copied/edited from the migrated configuration. Ensure that you are using a configuration that is current, or that has been copied/edited from a current configuration. 264 VERITAS Bare Metal Restore System Administrator s Guide

287 Using the Patch Mechanism Using the Patch Mechanism Every BMR patch consists of a patch file and a README file. The patch file follows the naming convention patch-bmr-<patchid> and must be accessible to the server or client machine that is being patched. The README file enumerates and describes the defects addressed by the patch, and also lists any special instructions for applying the patch. The <patchid> portion of the patch file name includes the BMR major release version and the specified patch number. For example, would indicate patch 3 for BMR release Normally, patching can be done either before or after bmrsetupserver or bmrsetupclient have been run. However, be sure to read any special instructions listed in the patch README file. BMR patches can be downloaded from the VERITAS Support web site at The server and client software for BMR may be temporarily unavailable during the application of software patches. A list of installed patches is archived in the file <BMRdataDir>/patches/applied. BMR program files that were replaced by the patch process are archived in the directory <BMRDIR>/<patchid>. Note Do not change or replace archived files. UNIX Platforms Note that you must be logged on as root when running the UNIX patch commands. Before applying any patch, read the patch README. Determining the Current Patch Level To determine the currently installed patch level, perform the following: On the BMR main server: Click the License Info tab on the BMR main server GUI. On UNIX clients or servers: Enter the following at the command line: $BMRDIR/bmrc -v Appendix A, Upgrades and the Patch Mechanism 265

288 Using the Patch Mechanism Applying a Patch To apply a patch to a UNIX BMR server the command is: bmrpatchserver f patch-bmr-<patchid> To apply a patch to a UNIX BMR client the command is: bmrpatchclient f patch-bmr-<patchid> For example, to apply patch 3 onto a UNIX server running BMR release 4.5.0, the command is: bmrpatchserver -f patch-bmr Windows NT and Windows 2000 Platforms Note that you must be logged on as administrator when applying patches for Windows clients. Before applying any patch, read the patch README. Determine the Current Patch Level To determine the currently installed patch level, click Programs >VERITAS Bare Metal Restore >About Client. Apply a Patch To apply a patch to a Windows BMR client 1. Click Programs >VERITAS Bare Metal Restore >Patch Client. 266 VERITAS Bare Metal Restore System Administrator s Guide

289 Using the Patch Mechanism The Patch Wizard screen displays: 2. Read the information about patching the client, then click Next. The Patch File Selection screen displays: 3. In the Patch File field, enter the full path and file name of the BMR patch file, or click Browse to locate the file. Click Next. Appendix A, Upgrades and the Patch Mechanism 267

290 Using the Patch Mechanism If the patch you specified is valid, the following dialog displays: 4. Click Yes to confirm that you want to install the patch you have entered. The status of the patch install is indicated on the final screen: 5. Click Finish. 268 VERITAS Bare Metal Restore System Administrator s Guide

291 Deployment Planning Resources B Considerations for deployment planning are covered in depth in Chapter 1. See Bare Metal Restore Components on page 17 for background information, considerations, and requirements. This Appendix provides technical details, such as sizing requirements and specifications. It also supplies worksheets to help you plan for your BMR deployment. 269

292 Specifications Specifications Sizing and Space Requirements BMR Component Quantity Rules of Thumb Sizes BMR Main Server Executables Usually 1 main server per site AIX 45 MB 2 Solaris 65 MB 2 HP-UX 55 MB 2 BMR Main Server Database 1 per main server Less than 1 MB per client BMR File Server Executables BMR File Server Samba Executables BMR File Server SRTs 1 per platform (AIX), Same as for BMR main server 2 1 per subnet (Solaris 1 and HP-UX) 1 per BMR file server AIX 7 MB Solaris 10 MB HP-UX 7 MB Varies by platform: NT MB Typically one SRT per OS level to MB be restored (e.g. AIX 4.2, 4.3) AIX MB Cross-level restores possible in Solaris MB some cases; (e.g. Solaris 7 and 8) HP-UX MB BMR Boot Server Executables 1 per platform (AIX), 1 per subnet (Solaris 1 and HP-UX) BMR 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 BMR Client Executables Varies per platform: UNIX has executables and meta-data Windows has executables, meta-data, and space reservation files BMR Client Data Files Varies per platform: UNIX has several files Windows has one file, contains device drivers Same as for BMR Main server 2 AIX Solaris HP-UX 3-6 MB per BI, max 72MB per SRT KB per BI, max.8mb per SRT MB per BI (and per SRT) NT 16 MB 5, 1-10 MB 6, MB MB 5, 1-10 MB 6, 500 MB 3 AIX 456 KB 5, <1MB 6 Solaris 264 KB 5, <1MB 6 HP-UX 251 KB 5, <1MB 6 NT/W2K AIX Solaris HP-UX 1-10 MB <1 MB <1 MB <1 MB 1 Unless using Solaris relay boot servers or DHCP 2 When main, file, and boot servers are colocated, only count once 3 Space Reservation File 4 Windows 2000 requires a minimum partition of 1.2GB. BMR requires 512MB free space to install and 500MB reservation 5 Executable 6 Meta-Data 270 VERITAS Bare Metal Restore System Administrator s Guide

293 Specifications Supported Operating Systems for BMR Servers and Clients Operating System Version BMR Compatible AIX , , , , , ML10, Server and Client Solaris 2.6, 7, 8 Server and Client HP-UX , 11.00, (11i) Server and Client Windows NT Server, 4.0 Workstation, 4.0 Server Enterprise Edition, 4.0 Terminal Server Client only Windows Professional, Server, Advanced Server 2 Client only 1 AIX , HP-UX support is with NBU 3.4 and only (see the NetBackup compatibility lists on support.veritas.com) 2 When installing BMR, both a Windows 2000 Advanced Server CD and a Windows 2000 Server CD will work 3 For all Windows machines, OEM CDs will not work Appendix B, Deployment Planning Resources 271

294 Specifications Supported File Systems and Volume Managers Platform File Systems Volume Managers RAID, Mirroring, Striping AIX Native AIX JFS Native AIX LVM LVM Striping LVM Mirroring Solaris UFS Solstice Disk Suite 4.2, SDS mirroring only, limited support 1 VERITAS File System 3.3.3, 3.4, 3.5 HP-UX Native HFS, JFS 3.3 (VERITAS VxFS ) VERITAS Volume Manager 3.1.1, 3.2, 3.5 Native HP LVM VxVM Striping, Mirroring, RAID LVM Striping, LVM Mirroring Windows NT FAT16, NTFS Windows Disk Administrator 3 Windows 2000 FAT16, FAT32, NTFS Windows Logical Disk Manager 1 Limited support: BMR breaks mirrored meta devices and restores all mount points and files to the broken mirror on the corresponding native partitions. Breaking the mirror is sufficient to restore a machine to a bootable state where SDS meta devices can be re-configured and the remaining filesystems restored. 2 JFS 3.3 is the version of the VERITAS File System (VxFS 3.3.2) shipping on HP-UX since December NT fault tolerant configurations (software RAID, mirroring, etc.) are not supported. Supported NetBackup Versions This version of BMR was designed to work with NetBackup BusinessServer and DataCenter versions 3.4, (for Windows clients), and 4.5. However, the NetBackup version must be appropriate to the supported platform. For example, AIX and HP-UX only work with NetBackup version 3.4. NetBackup Client 3.4 GA Cannot Be Used When Building SRTs Due to an issue in NetBackup 3.4 GA regarding setting the ownership and permissions for restored files, NetBackup client 3.4 GA can not be used for creating SRTs. This issue is resolved for Windows clients in NetBackup For UNIX clients, NetBackup 3.4 GA has a patch available. However, that patch does not have an automated mechanism for 272 VERITAS Bare Metal Restore System Administrator s Guide

295 Specifications inclusion in SRTs. In order to include the NetBackup 3.4 plus patch UNIX client in an SRT, you must create an installable image that includes the patch. The procedure below explains how to create this installable image. Note NetBackup clients and servers must be at the same patch level. To create an installable NetBackup UNIX client image 1. Copy the NetBackup 3.4 client installation image to your disk: cd /INSTALL (cd /cdrom ; tar cf -.) tar xvf - where /INSTALL is the desired location of the NetBackup installation image, and /cdrom is the location of the mounted CD. 2. Move the original NetBackup 3.4GA NBClients directory and copy it to create a new NBClients directory: mv NBClients NBClients.34 cp -R NBClients.34 NBClients 3. Replace the original usr directory in the NBClients directory with the appropriate files from the jumbo patch: cd NBClients/anb/Clients zcat /tmp/patchnb_34_1.tar.z tar xvf - where the updated patch files are included in patchnb_34_1.tar.z, located in /tmp. Note The jumbo patch is downloaded from the VERITAS support site. Note NetBackup clients and servers must be at the same patch level. Supported Hardware Components and Architectures Platform Network Cards Architecture Processors Disk Controllers AIX ethernet, token ring rs6k, rspc, chrp up/mp SCSI HP-UX ethernet series 700, series 800 up/mp SCSI Appendix B, Deployment Planning Resources 273

296 Specifications Platform Network Cards Architecture Processors Disk Controllers Solaris ethernet sun4c, sun4d, sun4m, sun4u, sun4us up/mp SCSI, IDE Windows NT Windows 2000 PCI ethernet cards with DOS drivers PCI ethernet cards with DOS drivers Intel and AMD based up/mp SCSI, IDE Intel and AMD based up/mp SCSI, IDE 274 VERITAS Bare Metal Restore System Administrator s Guide

297 Worksheets Worksheets The following worksheets and worksheet instructions are designed to help you plan your installation: NetBackup Server Network Interface Worksheet Instruction on page 276 NetBackup Server Network Interface Worksheet on page 277 Network Topology Worksheet Instruction on page 278 Network Topology Worksheet on page 279 BMR Server Candidate Worksheet Instruction on page 280 BMR Server Candidate Worksheet on page 281 BMR File Server Worksheet Instruction on page 282 BMR File Server Worksheet on page 283 Shared Resource Tree Worksheet Instruction on page 284 Shared Resource Tree Worksheet on page 285 Dissimilar System Restore Worksheet Instruction on page 287 Dissimilar System Restore Worksheet on page 288 Appendix B, Deployment Planning Resources 275

298 Worksheets NetBackup Server Network Interface Worksheet Instruction For each NetBackup server, complete a separate NetBackup Server Network Interface Worksheet. For each interface on the NetBackup 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 NetBackup 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 , and an IP network mask of , would have a Network Interface Address column entry of , and the Network Segment IP column would contain VERITAS Bare Metal Restore System Administrator s Guide

299 Worksheets NetBackup Server Network Interface Worksheet NetBackup Server Name: VERITAS NetBackup Master Server VERITAS NetBackup Media Server NetBackup Server Software Version and Release: Network Interface Name Network Interface Address Network Segment IP Appendix B, Deployment Planning Resources 277

300 Worksheets Network Topology Worksheet Instruction Use this worksheet to describe the network topology of the NetBackup environment. 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 and the netmask is , the network segment IP address is 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 NetBackup Server column is the IP address of a router in this segment that can be used to reach the NetBackup server. If the NetBackup server has a presence on this network (if there is a Network Segment IP match for this segment in the NetBackup 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. 278 VERITAS Bare Metal Restore System Administrator s Guide

301 Worksheets Network Topology Worksheet Page of Network Segment IP Gateway to NetBackup Server Gateways to other Networks Appendix B, Deployment Planning Resources 279

302 Worksheets 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 NetBackup 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.2.1, 4.3.1, 4.3.2, 4.3.3, or 5.1 Solaris 2.6, 7, or 8 HP-UX or 11.X 2. NetBackup client software must be installed: a. NetBackup client must be at the version level or higher than the version on any UNIX BMR client. b. BMR server candidate must have permission to retrieve files from the NetBackup server for any UNIX BMR client. 3. Candidate column: list all the candidates meeting the above criteria in the Candidate column of the BMR Server Candidate Worksheet. Use the NetBackup 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: NetBackup Servers Connectivity column: Use NetBackup Server Network Interface Worksheet on page 277. If the candidate is able to ping at least one of the Network Interface Address entries for every NetBackup server, place a check mark in the NetBackup Servers Connectivity column. If a candidate does not meet this requirement 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 NetBackup 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 requirement, 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 NetBackup Client Software and Version in the blanks provided. 280 VERITAS Bare Metal Restore System Administrator s Guide

303 Worksheets BMR Server Candidate Worksheet Candidate NetBackup Servers Connectivity Client Connectivity Selected BMR Server Operating System and Version: NetBackup Client Software and Version: AIX: uname -m Solaris: hostid HP: uname -1 Appendix B, Deployment Planning Resources 281

304 Worksheets BMR File Server Worksheet Instruction Use this worksheet to track your BMR servers and their corresponding operating systems. Make a copy of the form entitled BMR File Server Worksheet. For each Network Segment IP on the 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. 282 VERITAS Bare Metal Restore System Administrator s Guide

305 Worksheets BMR File Server Worksheet Page of Network Segment IP Link Speed AIX Solaris HP-UX Windows X NT 2000 Appendix B, Deployment Planning Resources 283

306 Worksheets 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 operating system level in the first two rows of the form. If the BMR file server will also be a BMR 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 operating system needed to create the SRT. This corresponds to the operating system level used by the BMR clients that use this SRT. The NetBackup Client Release and Version is the version of the NetBackup client software to be installed into the SRT. 284 VERITAS Bare Metal Restore System Administrator s Guide

307 Worksheets Shared Resource Tree Worksheet BMR File Server Hostname BMR File Server OS and Level BMR Boot Server Yes No Network Segment IP s Served SRT OS and Level NetBackup Client Release and Version Other Disk Device Driver and Volume Manager Information Other Software or Drivers Used by BMR Clients VERITAS Volume Manager VERITAS File System Version: Version: Third Party Disk Device Driver and Volume Manager Information Third Party OEM Network Drivers Software or OEM Disk Drivers Drivers Used by BMR Clients Other Location of Images for SRT Creation OS NetBackup Client Third Party Software Network Driver Disk Drivers Other: Other: Appendix B, Deployment Planning Resources 285

308 Worksheets NT/2000 License Key 286 VERITAS Bare Metal Restore System Administrator s Guide

309 Worksheets Dissimilar System Restore Worksheet Instruction Each time you perform a Dissimilar System Restore, complete a separate Dissimilar System Restore worksheet. To complete the worksheet, you will need to collect information about both the source system and the target system. For the source system, record the OS and Service Pack level. In addition, record the network (TCPIP) parameters of the BMR and NetBackup environment of the source system in the Servers Used and Client Interfaces tables. For the target system, record the name of the Shared Resource Tree and the target system Service Pack. As with the source system, record the network (TCPIP) parameters for the BMR and NetBackup environment of the target system in the Servers Used and Client Interfaces tables. Assigning TCPIP properties on the target system to individual network interface cards must be planned ahead of time. Use the Mass Storage Drivers and NIC Drivers tables to record the hardware configuration of the target system. Note that the information collected in the Drivers tables may not be needed if you choose to copy another client s configuration for the restore. For details on this method of Dissimilar System Restore, see DSR Restore Procedure: Copying Another Client s Configuration on page 172. Appendix B, Deployment Planning Resources 287

310 Worksheets Dissimilar System Restore Worksheet Source System Source System Operating System: Source System Service Pack Level: Servers Used: Role IP Address Gateway BMR Main Server NetBackup Server NetBackup Media Server DNS Server Alternate DNS Server Client Interfaces: Interface Name IP Address Netmask 288 VERITAS Bare Metal Restore System Administrator s Guide

311 Worksheets Target System Shared Resource Tree Name: Service Pack Name: Servers Used: Role IP Address Gateway BMR Main Server NetBackup Server NetBackup Media Server DNS Server Alternate DNS Server Client Interfaces: Interface Name IP Address Netmask MAC Address Mass Storage Drivers: Adapter Identification String Vendor User Description INF File Name INF Option Name Appendix B, Deployment Planning Resources 289

312 Worksheets Adapter Identification String Vendor User Description INF File Name INF Option Name NIC Drivers: Adapter Identification String Vendor User Description INF File Name INF Option Name 290 VERITAS Bare Metal Restore System Administrator s Guide

313 BMR Command Reference C This Appendix provides details on the following BMR commands: bmracceptfi bmrconfig bmrcreatesrt bmreditcfg bmrmap bmrmkcdimage bmrnewcfg bmrrestore bmrsavecfg bmrsetupclient lm_keyins 291

314 bmracceptfi bmracceptfi NAME bmracceptfi - Accepts a boot floppy image for other BMR clients to use SYNOPSIS bmracceptfi [Client Name] DESCRIPTION The bmracceptfi command takes a previously created boot floppy image and makes it available for other BMR clients to use. This command is run once after the first time the Boot Options Wizard is successfully executed on a Windows client. During the execution of the Boot Options Wizard, a boot floppy image is created. This image is written onto the floppy to make it bootable. Only one floppy boot image is needed for all your BMR Windows clients. After the first time the Boot Options Wizard is run, the boot floppy image is created and pushed onto the BMR main server. The bmracceptfi command is run to allow the other clients to use that boot floppy image when other boot floppies are created. OPTIONS clientname Specifies the name of the BMR client that has successfully run the Boot Options Wizard. If you do not specify a clientname, the program prompts you for one. 292 VERITAS Bare Metal Restore System Administrator s Guide

315 bmrconfig bmrconfig NAME bmrconfig - Executes BMR configuration actions SYNOPSIS bmrconfig [-h bmrserver [-p port]] -o {define query change create allocate deallocate verify destroy} -r {BI SRT FS BS BMR ESM CL CFG PKG RP} 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 main, file, and boot servers. See the -h flag below for more details. You must be the bmradmin user or root to run this procedure. OPTIONS -h -r -p Specifies the server name, overriding the value of BMRserver set in /var/bmr/etc/server_env if the command is run on the server or /var/bmr/etc/client_env if it is run on the client. BMR has 3 types of servers: A BMR main server. There is always only one. A BMR file server. There can be more than one. A BMR boot server. There can be more than one. The operation and resource determine which server you need to specify. For example, all database operations (define, query, and change) require the BMR server to be specified with the -h option. All operations on the shared resource tree (SRT) resource require the BMR file server and all operations on the boot image resource require the BMR boot server. Resource to perform the operation. Specifies the port number, overriding the value of BMRport set in /var/bmr/etc/server_env or /var/bmr/etc/client_env. Appendix C, BMR Command Reference 293

316 bmrconfig -o Specifies the operation to perform. When combined with r this determines the method to execute. The operations to perform are: define change query delete create destroy allocate deallocate verify creates a new resource updates the attributes of a resource returns the attributes of one or more resources deletes a resource creates a resource destroys the resource allocates the resource deallocates the resource verifies the resource Note 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 option is specified, host is assumed to be the BMR boot server associated with the specified arguments. If -p port is specified, 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 option is specified, host is assumed to be the BMR file server associated with the specified arguments. If -p port is specified, 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 bmrcreatesrt man page for more details. 294 VERITAS Bare Metal Restore System Administrator s Guide

317 bmrconfig 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 option is specified, host is assumed to be the BMR main server associated with the specified arguments. If -p port is specified, port is assumed to be BMRport. Otherwise, BMRhostname and BMRport are taken from the environment. bmrconfig -o define -r BMR BMRname define_args bmrconfig -o change -r BMR BMRname change_args bmrconfig -o query -r BMR BMRname query_args 4. Operations on the NetBackup resource: If the -h host option is specified, host is assumed to be the BMR main server associated with the specified arguments. If -p port is specified, 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 option is specified, host is assumed to be the BMR main server associated with the specified arguments. If -p port is specified, 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 definitions 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... ] Appendix C, BMR Command Reference 295

318 bmrconfig change_args query_args The arguments to the change operation are also one or more name=value constructs, as in name=value [ name=value... ] 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= Query the IP address and host name of the file server bmrfs : bmrconfig -o query -r FS bmrfs FShostname FSipaddr 3. Change the IP address of the same file server: bmrconfig -o change -r FS bmrfs FSipaddr= VERITAS Bare Metal Restore System Administrator s Guide

319 bmrcreatesrt bmrcreatesrt NAME bmrcreatesrt - Creates a BMR shared resource tree SYNOPSIS bmrcreatesrt 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 level and NetBackup client level. It uses the appropriate installation media. bmrcreatesrt prompts the user for the SRT name. This name can be any alphanumeric string the user defines. It is recommended that the SRT name describe the type of client that can use this SRT. SRTs are specific to client operating system level and NetBackup client level. The following operating system levels are supported for AIX: 4.2.x 4.3.x 5.1 The following operating system levels are supported for Solaris: The following operating system levels are supported for HP-UX: X bmrcreatesrt requires the NetBackup client or server installation software and any of its prerequisite file packages. Appendix C, BMR Command Reference 297

320 bmreditcfg bmreditcfg NAME bmreditcfg - Interactively modifies a BMR client configuration SYNOPSIS bmreditcfg -client client_name -config config_name DESCRIPTION The bmreditcfg command is used on the BMR main server to modify a configuration for a client. This configuration has to be an editable copy of a client s configuration that is generated by a copy operation. The copy operation can be performed either through the BMR GUI or with the bmrnewcfg command. You must specify a client and configuration to that you want to modify. The bmreditcfg command prompts for the operation that needs to be performed on the configuration. The valid operations are as follows: LIST Lists components of the selected configuration. ADD Adds a component to the selected configuration. DELETE Removes a component from the selected configuation. AVAILABLE Lists components available to be added. QUIT Exits the interface. Once the operation is specified bmreditcfg will prompt you with the component that you would like to modify. The valid components are: INTERFACE Interfaces that are available on the system to be restored. HOST Servers that will be contacted during the restore. MSD Mass Storage Drivers. NIC Network Interface Card Drivers. SP - For service packs. In addition to the interactive mode, bmreditcfg provides fast paths if the operation and component are specified. OPTIONS -client Name of the client associated with the configuration. 298 VERITAS Bare Metal Restore System Administrator s Guide

321 bmreditcfg -config Name of the configuration to modify. EXAMPLES 1. To delete a host definition from a client configuration: $ bmreditcfg client nt240,sol140 config netchanges delete host 2. To add a Mass Storage Driver to a client configuration: $ bmreditcfg client nt240,sol140 config msdchanges add msd 3. To list all available NIC Drivers: $ bmreditcfg client nt240,sol140 config nicchanges available nic 4. To list the existing interfaces in a client configuration: $ bmreditcfg client nt240,sol140 config netchanges \ list interface 5. To perform an interactive edit session: $ bmreditcfg client nt240,sol140 config netchanges Appendix C, BMR Command Reference 299

322 bmrmap bmrmap NAME bmrmap - Manipulates BMR client configuration for Dissimilar Disk Restore SYNOPSIS bmrmap -add disk -group group_name -unmanaged -sourceconfig config_name disk_identifier -config config_name -client client_name bmrmap -delete disk dg vg fs lv partition disk -group group_name -unmanaged -client client_name -config config_name object identifier bmrmap -modify fs lv sk -group group_name -unmanaged -client client_name -config config_name object identifier -attr attribute_name=value bmrmap -replace disk -group group_name -unmanaged -client client_name -sourceconfig config_name disk_identifier -config config_name disk_identifier bmrmap -list dg vg fs lv partition disk all config [-style 0 1 2] -group group_name -unmanaged -client client_name -config config_name 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 made available to this bmrmap command. The client will suspend the restore process until the BMR server passes back the remapped restore procedure. You can run the bmrmap command as many times as needed to arrive at the desired mapping. After you have finished the mapping, run bmrrestore with the -config config_name option. The config_name is the mapped configuration. 300 VERITAS Bare Metal Restore System Administrator s Guide

323 bmrmap OPTIONS -add disk -sourceconfig configname disk_identifier Adds to the restore procedure a disk that has the characteristics specified by the options group or unmanaged, config, and client. You also specify a source configuration from which to obtain the information about disk s configuration. -delete Deletes from the restore procedure any of the following operands that have the characteristics specified by the options group or unmanaged, config, and client: Specifying dg deletes a disk group Specifying vg deletes a volume group Specifying fs deletes a file system Specifying lv deletes a logical volume Specifying partition deletes a partition Specifying disk deletes a disk Specifying all deletes all settings -modify Modifies in the restore procedure either of the following operands that have the characteristics specified by the options group or unmanaged, config, and client: Specifying fs modifies a file system Specifying lv modifies a logical volume -replace disk -sourceconfig configname disk_identifier Replaces in the restore procedure a disk that has the characteristics specified by the options group or unmanaged, config, and client. You also specify a source configuration from which to obtain the information about disk s configuration. -list Displays from the restore procedure any of the following operands that have the characteristics specified by the options group or unmanaged, config, and client: Specifying dg displays a disk group Specifying vg displays a volume group Specifying fs displays a file system Specifying lv displays a logical volume Specifying partition displays a partition Specifying disk displays a disk Appendix C, BMR Command Reference 301

324 bmrmap Specifying all displays all settings Specifying config displays a configuration You can also specify a style for listing the options, as follows: -style group groupname Specifies a group on which to perform the add, delete, modify, replace, or list operation. -unmanaged Specifies that a group should be unmanaged in the restore procedure. -config configname [object_identifier] Specifies a configuration on which to perform the add, delete, modify, replace, or list operation. For delete and replace operations, you also specifiy an object ID from the configuration on which to perform the operation. -sourceconfig configname disk_identifier When you add or replace a disk in the configuration, you specify a source configuration and disk identifier from which to obtain the information about the disk. -client clientname Specifies a client on which to perform the add, delete, modify, replace, or list operation. EXAMPLES 1. To display a list of current volume groups for myclient: bmrmap -list volume_group -client -myclient -config myconfig 2. To display discovered disk info for myclient: bmrmap -list disk -client myclient -config discoveredconfig 3. To display configuration of myvg on myclient: bmrmap -list all -group myvg -client myclient -config myconfig 4. To display configuration of ssavg on myclient in format: bmrmap -list all -group ssavg -style 1 -client myclient \ -config myconfig 5. To delete oldvg from myclient's configuration: 302 VERITAS Bare Metal Restore System Administrator s Guide

325 bmrmap bmrmap -delete vg -config myconfig oldvg -client myclient 6. To remove logical volume testlv from volume group extravg for myclient s config: bmrmap -delete lv -group extravg -config myconfig testlv \ -client myclient 7. To remove file system ncfs from volume group dcvg for myclient s config: bmrmap -delete fs -group dcvg -config myconfig ncfs \ -client myclient 8. To change harddrive hdisk0 to hdisk3 on myclient s rootvg: AIX: bmrmap -replace disk -group rootvg -client myclient \ -sourceconfig discoveredconfig hdisk3 \ - config myconfig hdisk0 HP: bmrmap -replace disk -group rootvg -client myclient \ -sourceconfig discoveredconfig /dev/dsk/c0t6d0 \ - config myconfig dev/dsk/c0t5d0 Solaris: bmrmap -replace disk -group rootvg -client myclient \ -sourceconfig discoveredconfig c0t1d0 \ - config myconfig c0t0d0 9. To add harddrive hdisk11 to myclient s dbvg: bmrmap -add disk -group dbvg \ -sourceconfig discoveryconfig hdisk11 -config myconfig 10. To remove hard drive hdisk2 from myclient s slevg: bmrmap -delete disk -group slevg -client myclient \ -config myconfig hdisk2 Appendix C, BMR Command Reference 303

326 bmrmkcdimage bmrmkcdimage NAME bmrmkcdimage - Creates a raw cd image of a BMR shared resource tree (SRT) SYNOPSIS bmrmkcdimage DESCRIPTION bmrmkcdimage prompts the user for values including: the source SRT name, a name for the new SRT and boot image, pathname of a directory with sufficient space, 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 after booting off this CD. SEE ALSO bmrcreatesrt 304 VERITAS Bare Metal Restore System Administrator s Guide

327 bmrnewcfg bmrnewcfg NAME bmrnewcfg - Creates a new BMR configuration SYNOPSIS bmrnewcfg -copy -client client_name -newconfig config_name -sourceconfig config_name -sourceclient client_name bmrnewcfg -retrieve -client client_name -newconfig config_name -enddate end_date [end_time] DESCRIPTION The bmrnewcfg command is used on the BMR main server to create a new configuration for a client. This configuration can either be a copy of an existing configuration or a configuration that needs to be retrieved from NetBackup. For copying an existing configuration the following parameters need to be specified: -client -newconfig -sourceconfig -sourceclient For retrieving a configuration from NetBackup, the following parameters need to be specified. -client -newconfig -enddate (specifying the end_time is optional) OPTIONS -copy Make a copy of an existing configuration. -retrieve Retrieve a configuration from NetBackup. -client Name of the client associated with the new configuration. -newconfig Name of the new configuration. Appendix C, BMR Command Reference 305

328 bmrnewcfg -enddate A string that matches the NetBackup End Date format. -sourceconfig Name of the configuration to copy from. -sourceclient Name of the client to copy the configuration from. EXAMPLES 1. To retrieve a configuration from NetBackup: $ bmrnewcfg retrieve client aixc12,hpb70 \ newconfig beforemelissa enddate 02/28/ To make an editable copy of a client configuration: $ bmrnewcfg copy client aixc12,hpb70 newconfig networkchanges \ sourceconfig current -sourceclient aixc12,hpb70 3. To make an editable copy of a configuration from another client: $ bmrnewcfg copy client aixc12,hpb70 newconfig fromaixc15 \ sourceconfig current sourceclient aixc15,aixc3 306 VERITAS Bare Metal Restore System Administrator s Guide

329 bmrrestore bmrrestore NAME bmrrestore - Prepares a BMR client for the restore process SYNOPSIS bmrrestore -[saved options] [-bi BI_name] [-srt SRT_name] [[-restore systemonly all] [ddr]] [[-discover] [-discoveredconfig config_name]] [-quickformat] [-logging] [-cachedcatalogs] -client client_name DESCRIPTION The bmrrestore command prepares a client for the restore process. The command is run on the BMR server to restore any BMR client. The bmrrestore command allocates the assigned SRT (shared resource tree) and boot image to the specified client. OPTIONS: -savedoptions Use options saved in RP table for any unspecified options -bi BI_name Specifies the boot image -srt SRT_name Specifies the Shared Resource Tree -restore systemonly all Restore volume groups forming system or all volume groups; cannot be used with -discover -ddr Perform dissimilar disk tasks; cannot be used with -discover -discover Perform a hardware discovery; cannot be used with -restore or -dsr -discoverconfig config_name Name to give to a discovered configuration. The default is User/discovered. -quickformat Quick format Windows partition -logging Turn logging on Appendix C, BMR Command Reference 307

330 bmrrestore -cachedcatalogs Use cached catalogs to restore a NetBackup media server -config config_name Name of configuration to use in preparation; defaults to CLname, ReadOnly,current -client client_name Name of client to restore EXAMPLES 1. Prepare the client for restore with the discovered configuration: bmrrestore srt w2ksrt client w2k245, sol Prepare the client for restore using an edited configuration: bmrrestore -srt w2ksrt -client w2k245, sol137 -config newcfg VERITAS Bare Metal Restore System Administrator s Guide

331 bmrsavecfg bmrsavecfg NAME bmrsavecfg - Saves BMR client configuration information DESCRIPTION The bmrsavecfg command is used to save client configuration information to the Bare Metal Restore main server. During initial client configuration (bmrsetupclient) bmrsavecfg is automatically run for the first time. It also should exist in the NetBackup bpstart_notify script for the applicable policy. This will ensure that the latest client configuration has been saved to the Bare Metal Restore Server before a client backup is performed. For UNIX platforms SYNOPSIS bmrsavecfg [-e] OPTIONS FOR UNIX PLATFORMS -e By default bmrsavecfg will always terminate with an exit code of 0. This is because the NetBackup bpstart_notify script expects a 0 return code or the client backup will not be performed automatically. This option will allow termination with non-zero return codes. For Windows platforms SYNOPSIS bmrsavecfg [-background] OPTIONS FOR WINDOWS PLATFORMS -background This will run bmrsavecfg in the background without creating a new window. Appendix C, BMR Command Reference 309

332 bmrsetupclient bmrsetupclient NAME bmrsetupclient - Queries and gathers information for setting up the BMR client environment For UNIX platforms SYNOPSIS bmrsetupclient [-B -s -h BMRserver [-p port -n NLSdir -l NLSlang ]] DESCRIPTION The bmrsetupclient utility configures the Bare Metal Restore client software for use with a Bare Metal Restore server. The bmrsetupclient utility queries and gathers information which will be used to set up the environment for the BMR client. Environment information is set up in the /var/bmr/etc/client_env file. The client is registered with the specified BMR server and bmrsavecfg is run to save the known client configuration with the BMR server. -B Specifies background mode. In background mode, bmrsetupclient does not prompts for input. The default is background mode off. -s Sets the pre-schedule command in bpstart_notify. The default is off. BMRServer BMR server hostname port BMR server port number. The default is 8362 NLSdir Directory for BMR NLS catalogs. The default is /usr/lib/locale. NLSlang NLS language. The default is en-vs for AIX and C for Solaris and HP-UX) For Windows Platforms: SYNOPSIS bmrsetupclient [-B -h hostname -p port [ -S ]] 310 VERITAS Bare Metal Restore System Administrator s Guide

333 bmrsetupclient DESCRIPTION The bmrsetupclient utility configures the Bare Metal Restore client software for use with a Bare Metal Restore server. The bmrsetupclient utility queries and gathers information which will be used to set up the environment for the BMR client. Information is saved in the %BMRDIR\Data directory. The client is registered with the specified BMR server and bmrsavecfg is run to save the known client configuration with the BMR server. OPTIONS FOR WINDOWS PLATFORMS -B Specifies background mode. In background mode, bmrsetupclient does not prompts for input. The default is background mode off. -S Sets the pre-schedule command in bpstart_notify. The default is off. hostname BMR server hostname port BMR server port number Appendix C, BMR Command Reference 311

334 lm_keyins lm_keyins 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 program. License keys can be obtained from VERITAS Support for either purchased software or evaluation copies. License keys can only be used to generate a new license database within 60 days of issue. OPTIONS -k key -g The license key obtained from VERITAS. 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. 312 VERITAS Bare Metal Restore System Administrator s Guide

335 Glossary AIX A version of UNIX produced by IBM. BMR boot server The boot server provides the boot image to the client when it performs a network boot prior to the restore process. 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. bmrmkcdimage The bmrmkcdimage tool creates a final CD image file, which can be burned onto a CD to make the CD a bootable CD. BMR server The term BMR server refers to the server machine on which the BMR server software resides. bmrsetupserver The bmrsetupserver program configures the BMR server. This command must be run while logged in as the root user. bmrsetupserver must be run on the BMR main server, the BMR file server, and the BMR boot server. Boot Image A program or set of programs that give the machine enough intelligence to start functioning. A boot image is loaded during the initial program load to an operating system. 313

336 bootp bootparam 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. A Solaris protocol used for network booting. checksum 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. client/server An architecture in which one computer can get information from another. The client is the computer that asks for access to data, software, or services.the server, which can be anything from a personal computer to a mainframe, supplies the requested data or services for the client. daemon DHCP 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. A protocol for assigning dynamic IP addresses to devices on a network. ESM server The Enterprise Storage Management server used for normal backups and restores. This is your VERITAS NetBackup server. ethernet HP-UX A local-area network (LAN) protocol which sends its communications through radio frequency signals carried by a coaxial cable.each computer checks to see if another computer is transmitting and waits its turn to transmit. If two computers accidentally transmit at the same time and their messages collide, they wait and send again in turn. A version of UNIX produced by HP. 314 VERITAS Bare Metal Restore System Administrator s Guide

337 IP Address A unique number identifying a 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. MAC Address (Media Access Control) A hardware address that uniquely identifies each node of a network. mount To make a file system available. BMR media boot Refers to the process of using a CD-ROM that contains the SRT so that the client does not need network access to the SRT it is on the CD. The UNIX BMR media boot CD contains the boot image. The Windows BMR media boot CD requires a boot floppy that has been prepared with the BMR media boot option. NDIS NFS A Windows device driver interface that enables a single NIC to support one or more network protocols. NFS provides access to shared files through an interface called the Virtual File System (VFS) that runs on top of TCP/IP. SAMBA server The BMR file server running the SMB code. SAMBA The utility that allows UNIX to share server 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. Glossary 315

338 Solaris A version of UNIX produced by Sun Microsystems. Token Ring A local-area network (LAN) protocol in which computers are configured in a ring, and a message called a token is passed from station to station. vopie (VERITAS One-time Passwords in Everything) An authentication method for NetBackup. Windows NT An operating system by Microsoft intended for business workstations and servers. 316 VERITAS Bare Metal Restore System Administrator s Guide

339 Index A B C adding new driver 170 adding service pack 171 altnames directory 28 architectures supported 273 backup, make a complete 26 bmracceptfi 292 bmrconfig 293 bmrcreatesrt 297 bmreditcfg 298 bmrmap 300 bmrmkcdimage 304 bmrnewcfg 305 bmrrestore 307 bmrsavecfg 309 bmrsetupclient 310 client configuring UNIX 53 Windows 55 installing AIX using installp 49 AIX using smitty 48 HP-UX using swinstall 46 Solaris using pkgadd 47 Windows using InstallShield Wizard 49 client state 9 components boot server 17 file server 17 NetBackup server 18 configuration state 10 configuring a Shared Resource Tree 89 creating a Shared Resource Tree D F H I for media boot AIX 81 HP-UX 84 Solaris 82 Windows 85 for network boot AIX 66 HP-UX 75 Solaris 67 deployment planning worksheets 275 device driver 63 Dissimilar Disk Restore (DDR) 188 Dissimilar Disk Restore mapping utility 201 Dissimilar System Restore 167 documentation Bare Metal Restore xvii NetBackup xvii Support web page xviii File server selection AIX 22 HP-UX 23 Solaris 22 file systems supported 272 hardware components supported 273 installation requirements clients 44 server 28 installing the BMR client AIX using installp 49 AIX using smitty 48 HP-UX using swinstall 46 Solaris using pkgadd

340 L M N O P R S Windows using the InstallShield Wizard 49 installing the BMR server AIX using installp 33 AIX using smitty 32 HP-UX using swinstall 30 Solaris using pkgadd 31 lm_keyins 312 media boot AIX 81 HP-UX 84 Solaris 82 Windows media boot, creating a CD 80 modifying client configuration 122 multihomed considerations (multiple network interface) 218 multiple network interface (multihomed) 218 NetBackup catalogs 222 NetBackup versions supported 272 operating systems supported 271 Point in Time restore 210 port usage client 44 server 28 preparing to restore 136 restore time on HP 251 restoring a UNIX client media boot 150 network boot 141 restoring a Windows client custom media boot 163 custom network boot 159 generic network boot 155 restoring NetBackup media server 222 restoring the BMR server 234 SAMBA configuration file 37 SAN co-existence 207 T U SAN support matrix 208 server boot 17 file 17 installing on AIX using installp 33 AIX using smitty 32 HP-UX using swinstall 30 Solaris using pkgadd 31 Service Packs 214 Shared Resource Tree (SRT) configuring 89 creating AIX 66 HP-UX 75 Solaris 67 Windows 77 deleting 91 modifying 90 sizing requirements 270 space requirements 270 special partition 108, 116 system specifications 270 tips adding correct MSD driver 238 identifying vendor partition 239 recovering from erroneous input on Windows boot 240 removing BMR servers 240 uninstalling BMR 240 troubleshooting AIX boot failure 249 bmrd daemon does not start 255 Dissimilar System Restore 184 failed restores after changed NBU information 256 long restore times on HP-UX 251 network problems at DOS phase 255 Solaris 2.6 causing panic 245 UNIX boot from CD 250 Windows media boot failure with multiple drives 253 upgrading from 4.5 client 45 server VERITAS Bare Metal Restore System Administrator s Guide

341 V W Volume Manager 63 Volume Managers supported 272 Windows service packs 214 worksheets BMR File Server 283 BMR Server Candidate 281 Dissimilar System Restore 288 NetBackup Server Network Interface 276 Network Topology 279 Shared Resource Tree 285 Index 319