IBM Tivoli Storage Manager Bare Machine Recovery for Microsoft Windows 2003 and XP Redp3703

7/31/2019 IBM Tivoli Storage Manager Bare Machine Recovery for Microsoft Windows 2003 and XP Redp3703

1/76ibm.com/redbooks

Redpaper

Front cover

IBM Tivoli Storage Manager:

Bare Machine Recovery forMicrosoft Windows 2003 and XP

Barry Kadlec

David McFarlan

Pracha Pechsuksa

Wah Han Ta

Use built-in APIs provided by Windowsto protect your system

See how Windows ASR integrates

with ITSM

Learn how to configure your

system for recovery
http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/http://www.redbooks.ibm.com/


2/76


3/76

International Technical Support Organization

IBM Tivoli Storage Manager: Bare Machine Recoveryfor Microsoft Windows 2003 and XP

October 2003


4/76

Copyright International Business Machines Corporation 2003. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule

Contract with IBM Corp.

First Edition (October 2003)

This edition applies to IBM Tivoli Storage Manager V5.2 and above.

Note: Before using this information and the product it supports, read the information in Notices on page v.

Note: This book is based on a pre-GA version of a product and may not apply when the product becomes

generally available. We recommend that you consult the product documentation or follow-on versions ofthis redbook for more current information.


5/76

Copyright IBM Corp. 2003. All rights reserved.iii

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

The team that wrote this Redpaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 IBM Tivoli Storage Manager concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.2 IBM Tivoli Storage Manager functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.1 Restore and backup functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.2 Archive and retrieve functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.3 Managing backups, archives, other data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2.4 Administrative overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2.5 Hints and tips for command line, registration, and timeout . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Setting up IBM Tivoli Storage Manager for BMR . . . . . . . . . . . . . . . . . . . . . 11

2.1 Prerequisites and considerations in using ASR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.1 Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2.1.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1.3 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.2 Installation of the ITSM client on your Windows environment. . . . . . . . . . . . . . . . . . . . 13

2.3 Customization of the ITSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.3.1 TSM Backup/Archive Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.2 Online image support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.3.3 Open file support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4 Performing ITSM backups for ASR with Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4.1 ASR backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.4.2 SYSTEMOBJECT backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.4.3 Incremental backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.4.4 Copy ASR backup to diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.5 Performing ITSM backups for ASR with Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . 22

2.5.1 ASR backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.5.2 System services and system state backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.5.3 Incremental backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.5.4 Copy ASR backup to diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3. Microsoft Windows automated system recovery with ITSM . . . . . . . . . . . 31

3.1 Recovering a Microsoft XP image using ASR and ITSM . . . . . . . . . . . . . . . . . . . . . . . 323.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1.2 The Windows XP Professional recovery process . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.1.3 Windows XP Professional recovery example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.1.4 Common Errors in restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2 Recovering a Microsoft 2003 image using ASR and ITSM . . . . . . . . . . . . . . . . . . . . . . 46

3.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.2.2 The recovery process for Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.3 Windows 2003 recovery example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2.4 Common errors in restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


6/76

iv IBM Tivoli Storage Manager: Bare Metal Restore for Windows

Appendix A. Slipstreaming Windows XP Service Pack 1a . . . . . . . . . . . . . . . . . . . . . . 61Slipstreaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Slipstream Windows XP Service Pack 1a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


7/76

Copyright IBM Corp. 2003. All rights reserved.v

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consultyour local IBM representative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, to:IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions areinconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurringany obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate themas completely as possible, the examples include the names of individuals, companies, brands, and products.All of these names are fictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating platform for which the sampleprograms are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, anddistribute these sample programs in any form without payment to IBM for the purposes of developing, using,marketing, or distributing application programs conforming to IBM's application programming interfaces.


8/76

vi IBM Tivoli Storage Manager: Bare Metal Restore for Windows

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

IBM

pSeries

AIXGDPS

HACMP/6000

IBM

Rational

RedbooksSP1

SP2

Tivoli

TotalStorage

Redbooks(logo)

The following terms are trademarks of other companies:

ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the UnitedStates, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems,Inc. in the United States, other countries, or both.

C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

SET, SET Secure Electronic Transaction, and the SET Logo are trademarks owned by SET Secure ElectronicTransaction LLC.

Other company, product, and service names may be trademarks or service marks of others.


9/76

Copyright IBM Corp. 2003. All rights reserved.vii

Preface

This Redpaper will help you install, tailor, and configure Microsoft Windows Automated

System Recovery (ASR) features with IBM Tivoli Storage Manager (ITSM) to protect yoursystems from catastrophic failures.

The team that wrote this Redpaper

This Redpaper was produced by a team of specialists from around the world working at theInternational Technical Support Organization, San Jose Center.

Barry Kadleckis responsible for tape and Tivoli Storage projects at the International

Technical Support Organization, San Jose. He has a degree in Electronic Engineering and

joined IBM U.K. in 1985. He has been working with storage software and hardware for the last10 years. Before joining the ITSO in 2001, Barry worked at the Product Introduction

Consultancy in Hursley, U.K. as a Program Manager, introducing new Tivoli Storage productsinto Europe.

David McFarlane is a Technical Solutions Architect in Australia. He has 19 years ofexperience in the I/T industry. His areas of expertise include storage management, VTS, and

z/series solutions. He has participated in two other ITSO residencies: IBM TotalStorageVirtual Tape server: Planning, Implementing and Monitoring, SG24-2229-04, and produced

course materials for GDPS, XRC, PPRC,VTS Peer to Peer.

Pracha Pechsuksan is an I/T Specialist in Thailand. He has six years of experience in AIX

field and two years of experience in TSM field. He has worked at IBM for 12 years. His areasof expertise include AIX, TSM, SP2, and HACMP/6000.

Wah Han Tan is an IT Specialist with the pSeries services team in Singapore. He hasworked at IBM Singapore for seven years. His areas of expertise include AIX, TSM, SP2, and

HACMP/6000.

Become a published author

Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with

specific products or solutions, while getting hands-on experience with leading-edgetechnologies. You'll team with IBM technical professionals, Business Partners and/orcustomers.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus,

you'll develop a network of contacts in IBM development labs, and increase your productivityand marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!
http://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.htmlhttp://www.redbooks.ibm.com/residencies.html


10/76

viii IBM Tivoli Storage Manager: Bare Metal Restore for Windows

We want our papers to be as helpful as possible. Send us your comments about thisRedpaper or other Redbooks in one of the following ways:

Use the online Contact us review redbook form found at:

ibm.com/redbooks

Send your comments in an Internet note to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support Organization

Dept. QXXE Building 80-E2650 Harry Road

San Jose, California 95120-6099
http://www.redbooks.ibm.com/http://www.ibm.com/redbooks/http://www.redbooks.ibm.com/contacts.htmlhttp://www.redbooks.ibm.com/contacts.htmlhttp://www.ibm.com/redbooks/http://www.ibm.com/redbooks/http://www.redbooks.ibm.com/


11/76

Copyright IBM Corp. 2003. All rights reserved.1

Chapter 1. Introduction

The purpose of this book is to provide a guide to using the Bare Machine Recovery (BMR)

procedures with IBM Tivoli Storage Manager (ITSM) Level 5.2 for the following operatingsystems:

Microsoft Windows XP Professional Microsoft Windows 2003 Server

It should be first noted that this function also requires the Microsoft Windows AutomatedSystem Recovery (ASR). This is a facility provided by Microsoft to recover the above

mentioned operating systems in the event of a catastrophic system or hardware failure. Thepurpose of ASR is to return the operating system to the point of last backup.ITSMinterfaces with ASR to provide the data management functions and a repository for the data

that has been backed up.

In this chapter we introduce the basic concepts of IBM Tivoli Storage Manager (ITSM). Wewill focus our attention on the backup and restore functions of the product, and provide a brief

overview of the archive and restore and management aspects of ITSM. This guide is notintended to be a full introduction to ITSM.

In subsequent chapters, we discuss with examples how to do the following:

Install the ITSM client on your Microsoft Windows environment Customize the ITSM client to ensure that backups are going to take place Perform ITSM backups of the required data Overview of Microsoft Windows Automated System Recovery Initiate and complete the restore process using Bare Machine Recovery (BMR)

There will also be a section summarizing the tricks and traps we experienced so that you maygain from our experience in using the product.

1


12/76

2 IBM Tivoli Storage Manager: Bare Metal Restore for Windows

1.1 IBM Tivoli Storage Manager concepts

IBM Tivoli Storage Manager (ITSM) is a client server application designed to manage your

storage requirements. ITSM uses policies to manage the movement of data between clients,servers, and storage devices. There are two components required in any environment:

IBM Tivoli Storage Manager server IBM Tivoli Storage Manager client

IBM Tivoli Storage Manager can be used for backup and restore, and archive and retrieve. It

will manage backups and archives, and manage the movement of inactive data with themigrate and recall facility under HSM. ITSM will enable you to manage both the data and thestorage that they reside upon.

Figure 1-1 IBM Tivoli Storage Manager concepts

IBM Tivoli Storage Manager manages the movement and storage of data. The ITSM clientsoftware is installed on computers in your environment that require managing, and an ITSM

server is required to manage the metadata and the storage pools. Data can be backed up,archived, or moved from its primary location to storage devices used by ITSM; these locations

are calledstorage pools. ITSM can be set up to run in a local area network (LAN), wide areanetwork (WAN), or Storage Area Network (SAN) environments.

Note: As a general rule, the server version should be at a higher release level than theclient; please check release documentation for compatibility between specific releases and

combinations.

Clients

IBM Tivoli Storage Manager

Storage Pools

Server

migrate/recall

backup/restore

archive/retrieve

PoliciesandRequests

Network


13/76

Chapter 1. Introduction3

1.2 IBM Tivoli Storage Manager functions

The following sections outline the IBM Tivoli Manager functions.

1.2.1 Restore and backup functions

RestoreCareful planning must be undertaken when setting up any storage management application.ITSM is no different. It is far better to plan well in the beginning than wish you had at the end.

You should plan your systems to optimize the restoration functions, because they will alwaysbe required to operate within the most critical time scales when they are called upon. For

example, your restore requirements should always drive your backup objectives.

ITSM, or any backup application, is only as good as its restore function. A fast, reliable, and

efficient restoration process is the key. All the backups in the world will not help you if youcannot get the data back where you want it, when you want it, and in the form that it needs to

be in so that it can be used. ITSM fulfills all these requirements, and it is easy to use andunderstand.

BackupITSM utilizes aprogressive backup methodology. A full backup is done only once, after whichincremental backups are made only of files that have changed since the last backup. Themetadata associated with these backup copies are stored in the ITSM database. The number

of backup copies retained and the length of time they are retained for is specified by thestorage administrator, and also stored in the database.

This progressive backup methodology yields many benefits including the elimination of

redundant backups, reduction of data movement over your network, and an automatedmethod of backup and file retention.

In addition, backups may be performed on demand, either as full, incremental, or as a

selected set or subset of individual files. In any implementation of ITSM, the server will alwaysknow the location of the most recent copy of your file resides; this is crucial in the efficient andeffective recovery of your data.

1.2.2 Archive and retrieve functions

IBM Tivoli Storage Manager provides the archive and retrieve functions for the data that youneed to keep for long term storage. This data may be required for tax and legal purposes

such as a snapshot of the end of the month and fiscal year.

1.2.3 Managing backups, archives, other data

IBM Tivoli Storage Manager utilizes user written policies to manage the data written to, andread from the storage devices under its control. These policies manage.the data backups and

archives under the control of ITSM. Here are some of the data management issues for whichpolicies exist:

Version data exists Version data deleted Retain extra versions Retain only version Backup retention Archive retention


14/76


Copy frequency Copy destination

The metadata (data about the actual data) and media that it resides upon, exists within theITSM database, journals, and log files.

1.2.4 Administrative overview

IBM Tivoli Storage Manager Console

Figure 1-2 ITSM Console

The ITSM Console is the central server interface, all other server interfaces and the Web

backup-archive client can be accessed from the ITSM Console.

The ITSM Console is a Microsoft Management Console snap-in that provides the following

features:

A Microsoft Windows style tree view of network computers on which ITSM resources are

installed

Network scan utilities that can be used to locate ITSM client and server nodes for remote

management

A Net Send feature that can be used to notify operators of ITSM mount requests andstatus messages

ITSM server configuration and management wizards.

Command line and Web based interfaces for ITSM server management

A Web based interface that can be used to remotely backup and restore of client data

Reporting functions for ITSM server and client instances, device drivers, and schedules


15/76


IBM Tivoli Storage Manager WEB Interface

Figure 1-3 ITSM Web interface

The ITSM Web interface is intended to be the primary tool for ongoing ITSM server

administration.


16/76


IBM Tivoli Storage Manager server command line interface

Figure 1-4 IBM Tivoli Storage Manager command line interface

The ITSM server command line interface is useful for experienced ITSM administrators whoare familiar with the ITSM command set. Some administrators rely on the ITSM command lineas their primary configuration and management tool. This interface allows for the generation

of administrative scripts and macros, which can be scheduled to execute automatically.


17/76


IBM Tivoli Storage Manager client graphical interface

Figure 1-5 IBM Tivoli Storage Manager client graphical interface

The ITSM client graphical interface is designed to allow users to initiate on demand backup

archive and recovery functions from the client machine. The interface uses a familiarWindows-styled tree view to display the drives, directories, and files that can be manipulated

between the client and the server.


18/76


IBM Tivoli Storage Manager client Web interface

Figure 1-6 IBM Tivoli Storage Manager client web interface

The ITSM client Web interface is a graphical interface based on Java, and is included with theinstallation package, but must be manually installed and configured on each client node. The

ITSM client Web interface supports the following browser:

Microsoft Internet Explorer 5.0 or later with Java Runtime Environment (JRE) 1.3.1 Netscape Navigator 4.7 or later with Java Runtime Environment (JRE) 1.3.1 Netscape Navigator 6.0 or later

IBM Tivoli Storage Manager client command line interface

Figure 1-7 IBM Tivoli Storage Manager client command line interface


19/76


The ITSM client command line is a character based interface that provides comprehensivecontrol of ITSM client functions. This interface is installed as part of the ITSM client package.

1.2.5 Hints and tips for command line, registration, and timeout

When installing ITSM for the first time on multiple workstations, it may be a good idea to set

the following options. These options can be reset to the required permanent values once theinstallation has either been completed, or the value of their initial setting is no longer a distinctadvantage.

Web administrator Command line interfaceMany administrators find that the command line interface is easier to use than the GUI; theITSM Server Web Administration dialog will allow you to include the command line. Here arethe steps to include the command line:

1. Log on to the IBM Tivoli Storage Manager Server Web Administration interface.2. Choose Show command line from the Options drop down menu (see Figure 1-8).

Figure 1-8 ITSM Web administration Command Line tip

RegistrationWhen you first set up the clients for your installation, it may be advisable to allow openregistration. This will save you from registering each client from the server interfaceindividually. To do this, enter the following command from the command line interface:

set registration open


20/76


Timeout of server administrator

The Administrator timeout default is set to 5 minutes. This may not be the most effective timeperiod, especially if you are having to log in multiple times while performing other tasks on thesame machine. To alter this to not timing out, enter the following command from the command

line interface.

set webauthtimeout 0

This parameter should be set in line with your companys security policies.

Note: This command should be reset to closed once the initial setup of the clients hasbeen completed, since it will allow any client to register without being previously

authorized.


21/76


Chapter 2. Setting up IBM Tivoli Storage

Manager for BMR

This chapter describes the following:

Prerequisites and considerations in using Microsoft ASR for recovery Installation of the ITSM client in your Microsoft Windows environment Customization the ITSM client to ensure that backups are going to take place Performing ITSM backups of the required data

2


22/76


2.1 Prerequisites and considerations in using ASR

Automated System Recovery (ASR) is a backup and restore framework provided by Microsoft

to recover your Windows XP Professional or Windows 2003 Server system in the event of acatastrophic system or hardware failure. ITSM interfaces with this framework to provide

system recovery capability using ITSM as the data management vehicle.

Windows XP ASR recovers the target system in a two-step process:

1. The first step, termed the boot recovery process, requires a new copy of Windows to be

temporarily installed on the target system using the original distribution media.

2. The second step, called the OS restore process, restores the files of a previously saved

Windows installation using a backup-and-restore application (thus, deleting and writingover some of the files installed by the boot recovery process).

In the event of a system failure, the ASR can be used to restart the system, after which userscan begin a recovery from a backed up copy of a previously saved Windows installation.

The goal of ASR as stated by Microsoft is to return the operating system to the point of last

backup. ASR is not used to recover application or user data. Such data is recovered throughnormal ITSM restore procedures after successful completion of ASR recovery. You shouldcreate a new ASR set after any major change to the system, and also on a regular schedule

as part of a comprehensive backup plan.

2.1.1 Hardware requirements

1. The hardware configuration of the target system must be identical to that of the original

system, with the exception of the hard disks, video cards, and network interface cards.

2. The target system must have the same number of disks as the original system.

3. The size of each disk on the target system must be greater than or equal to the size of the

corresponding disk on the original system.

4. All disks must have 512 byte sectors.

5. All disks (and only such disks) that are available to ASR on which to perform a recoverymust be accessible.

6. The ASR files must be accessible from a local floppy drive.

7. The floppy and CD-ROM drives cannot be external PC-card drives.

8. The original system must be an x86 or an Itanium machine.

9. The original systems disks must have 512 byte sectors.

10.All basic volumes in the original system must be simple. Non-simple volumes are not

supported. If a volume is mirrored, it must be a dynamic volume, not a basic volume.

11.ASR supports FAT16 volumes up to 2.1 GB only. ASR does not support 4 GB FAT16

partitions that use a cluster size of 64K. If your system contains 4-GB FAT16 partitions,convert them from FAT16 to NTFS before using ASR.

Note: If there is a change in the video cards or networking cards, they must bemanually configured.


23/76

Chapter 2. Setting up IBM Tivoli Storage Manager for BMR13

2.1.2 Software requirements

These are the requirements:

1. Recovering a Windows XP SP1 system requires a Windows XP SP1 integrated(slipstream) installation CD. You cannot recover a Windows XP SP1 system using a base

Windows XP operating system installation CD. SP1 ASR references asr_pfu.exe, which is

not present on the base Windows XP installation. The base level Windows XP installationCD can be used to recover pre-SP1 Windows XP machines.

2. With the TSM client installation package used on the TSMCLI CD, your create for ASR

recovery must be at the same or higher level than the level of client used to create thebackups for the system being recovered. The details for creating the TSMCLI CD aredescribed later in this guide.

3. ASR requires a TSM v5.2.0 or newer client. Additionally, ASR for Windows 2003 requires

a v5.2.0 or a newer TSM server.

2.1.3 Supported configurations

The following table lists whether ASR is supported with the version of Windows XP at the time

of backup and at the time of restore.

2.2 Installation of the ITSM client on your Windowsenvironment

Please refer to the ITSM quickstart and administrator guides for the instructions on how toinstall the ITSM client on your Microsoft Windows environment.

Version of Windows at

Backup

Version of Windows at

Restore

Supported or Not

Supported

Windows XP Windows XP Supported (see Note)

Windows XP Windows XP Service Pack 1a Not supported

Windows XP Service Pack 1 Windows XP Supported (see Note)

Windows XP Service Pack 1 Windows XP Service Pack 1a Supported

Windows XP Service Pack 1a Windows XP Not supported

Windows XP Service Pack 1a Windows XP Service Pack 1a Supported

Windows 2003 Server Windows 2003 Server Supported

Note: The Japanese and Spanish versions of Microsoft Windows XP are not supported.


24/76


2.3 Customization of the ITSM client

Figure 2-1 Setup wizard selection from the main menu

Figure 2-2 Basic wizards required for ASR recovery

You must set up the wizards selected in Figure 2-2, if they have not already been set up to

enable ASR. In the following section, we provide an explanation of the purpose of theseoptions.

Other setup wizards can be completed, the three we have shown are the only ones requiredfor the ASR recovery process.


25/76


2.3.1 TSM Backup/Archive Client

Data is transmitted to the ITSM server using the ITSM Backup/Archive client. This client,

included with the server, provides the operational backup, and archival and recoveryfunctions. The following set of data about the client is required to be registered with the

server:

Node name Communications method the ITSM client will use when communicating with the ITSM

server

Details on how the communication method will be utilized

2.3.2 Online image support

Select this check box to set up the Logical Volume Snapshot Agent (LVSA) for an onlineimage backup. LVSA is a snapshot provider that is used for online image backup and open filesupport operations on the Windows 2003 and XP clients.

2.3.3 Open file supportSelect this check box to configure the Logical Volume Snapshot Agent (LVSA) to enable open

file support for backup and archive operations. This enables backup or archive of files that arelocked by other applications. During an open file support backup or archive operation, a

snapshot for each volume being operated on is created using the LVSA snapshot provider,and each snapshot is shown as a virtual volume to the client. After completion of thesnapshot, the client uses the virtual volume as the source for backing up or archiving files to

the server. This allows the original volume to be available for read and write operations duringthe backup or archive. Open file support is available for all types of backup (excluding backup

of Windows 2000 or XP system objects) and archive. Requires installation of the LVSA foropen file support through this client configuration wizard.

Note: After you have finished the initial set up of the options file, you can use thePreferences window to specify other client options. To open the Preferences window,select the Preferences item from the Edit menu.


26/76


2.4 Performing ITSM backups for ASR with Windows XP

Figure 2-3 ITSM startup panel

The ASR method for Bare Machine Recovery requires that the data be backed up in a certainorder. And at least that the ASR backup (not to be confused with creating the ASR recovery

diskette) be done prior to the latest incremental backup. The following is the order we used inthe testing:

ASR backup SYSTEMOBJECT backup Incremental backup Copy ASR backup to diskette

An example of each of these steps is provided in the following subsections.

2.4.1 ASR backup

Start up the ITSM Graphical User Interface (GUI) and click the backup button to back up theASR files. Follow the examples in Figure 2-4 and Figure 2-5.


27/76


Figure 2-4 Backup ASR files

A dialog will be presented to show the progress of this request.

Figure 2-5 Windows Automated System Recovery dialog

If you complete the incremental prior to doing the ASR backup, then the SMSS.asr and theNTDLL.ASR files will not be backed up on the incremental backup. Simply perform another

incremental backup prior to attempting to restore the system. Otherwise, if you are restoringthe system without the ASR files in the backup, the following error will occur:

Setup was unable to start the recovery application:

C:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error codereturned was 0x2.

This error can be fixed in the recovery process, See 3.1.3, Windows XP Professionalrecovery example on page 34.


28/76


2.4.2 SYSTEMOBJECT backup

Figure 2-6 SYSTEMOBJECT dialog

To back up the system objects using the GUI:

1. Click the Backup button from the GUI main window (see Figure 2-3 on page 16). TheBackup window appears.

2. Expand the directory tree by clicking the plus sign + To display files in a folder, click the

folder icon.

3. Locate the System Objects node in the directory tree and expand it.

4. Click the selection box for the system object(s) you want to back up.

5. Click Backup. The Backup Task List window displays the backup processing status. When

processing completes, the Backup Report window displays the processing details.

You can back up the Windows XP system objects together or individually. Microsoftrecommends that all system objects be backed up together to maintain a consistent systemstate. The following are valid system objects:

Active Directory (domain controller only) Certificate server database

Cluster Database (cluster node only) COM+ database Event logs (system, security, and application) Registry System and boot files System volume Removable Storage Management Database (RSM) Replicated file systems (FRS) Windows Management Instrumentation (WMI)


29/76


You can exclude system objects from backup processing using the exclude.systemobjectoption. See Exclude options in IBM Tivoli Storage Manager for Windows: Backup-ArchiveClients Installation and User's Guide Version 5 Release 2, GC32-0788-03, for more

information.

2.4.3 Incremental backup

From the startup panel (Figure 2-3) choose the Backup option. The first item to back up is thedata and operating system.

Figure 2-7 ITSM Backup selection panel

In our example we will be performing a backup and restore of a PC workstation. It is vital thatthe sequence presented here is followed. ITSM recovery with ASR is dependant upon thedata being backed up in a certain sequence, so that your system will be returned to a state

consistent with how it was backed up.

Select the Backup button to initiate the system backup; Figure 2-8 will appear showing youthat the backup is in progress.


30/76


Figure 2-8 Backup task list

If you wish to track the progress of the backup, click the Report button and Figure 2-9 willshow you the Detailed Status Report.

Figure 2-9 Backup report

If your network does not support DHCP, then you can use local backup sets containing thebackup of your system, boot drives, and SYSTEMOBJECT for Windows XP.

Use the GENERATE BACKUPSET command to generate a backup set for a backup-archive client

node. A backup set is a collection of a clients active backed up data, stored and managed asa single object, on specific media, in server storage. While the server allows you to create abackup set for any client node, a backup set can only be used by a backup-archive client. SeeIBM Tivoli Storage Manager for Windows Administrators Reference Version 5.2for the com-mands required to generate a backup set.


31/76


2.4.4 Copy ASR backup to diskette

Figure 2-10 Create ASR diskette

First copy the ASR files to a floppy disk: Select Utilities and then Create ASR Diskette fromthe command items (see Figure 2-10).

Figure 2-11 Create ASR diskette dialog

Insert Floppy, click Next; the files are copied to diskette and the following dialog will appear.(See Figure 2-12.)

Figure 2-12 ASR diskette confirmation


32/76


If ASR backup has not been done at all, and you attempt to copy the ASR files to a floppydisk, then the following error dialog box will appear. (See Figure 2-13.)

Figure 2-13 ASR error dialog

2.5 Performing ITSM backups for ASR with Windows 2003

Figure 2-14 ITSM startup panel

The ASR method for Bare Machine Recovery requires that the data be backed up in a certain

order. At least that the ASR backup (not to be confused with creating the ASR recoverydiskette) must be done prior to the latest incremental backup. The order used in the testing

we did was:

1. ASR backup

2. System services and system state backup3. Incremental backup

4. Copy ASR backup to diskette

An example of each of these steps is provided in the following subsections.


33/76


2.5.1 ASR backup

Start up the ITSM Graphical User Interface (GUI) and click the Backup button to back up the

ASR files. Follow the examples in Figure 2-4 on page 17, and Figure 2-5 on page 17.

Figure 2-15 Backup ASR files

A dialog will be presented to show the progress of this request.

Figure 2-16 Windows Automated System Recovery dialog

If you complete the incremental prior to doing the ASR backup, then the SMSS.asr and the

NTDLL.ASR files will not be backed up on the incremental backup. Simply perform anotherincremental backup prior to attempting to restore the system. Otherwise, if you are restoring

the system without the ASR files in the backup, the following error will occur:

Setup was unable to start the recovery application

C:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error code returnedwas 0x2.


34/76


This error can be fixed in the recovery process. See 3.1.3, Windows XP Professionalrecovery example on page 34.

2.5.2 System services and system state backups

Figure 2-17 Windows 2003 System Objects dialog

To back up system objects (for Windows 2003 these are split into system services and systemstate) using the GUI:

1. Click the Backup button from the GUI main window (see Figure 2-3 on page 16). The

Backup window appears.

2. Expand the directory tree by clicking the plus sign +. To display files in a folder, click the

folder icon.

3. Locate the system services and system state nodes in the directory tree and expand it.

4. Click the selection box for the system object(s) you want to back up.

5. Click Backup. The Backup Task List window displays the backup processing status. Whenprocessing completes, the Backup Report window displays processing details.

You can back up Windows 2003 system objects together or individually. Microsoftrecommends that all system objects be backed up together to maintain a consistent system

state. The following are valid system objects:

Active Directory (domain controller only) Certificate server database Cluster database (cluster node only) COM+ database Event logs (system, security, and application) Registry System and boot files


35/76


System volume Removable Storage Management Database (RSM) Replicated file systems (FRS) Windows Management Instrumentation (WMI)

You can exclude system objects from backup processing using the exclude.systemobjectoption. See Exclude options in the IBM Tivoli Storage Manager for Windows:Backup-Archive Clients Installation and User's Guide Version 5 Release 2, GC32-0788-03,

for more information.

2.5.3 Incremental backup

From the startup panel (Figure 2-3) choose the Backup option. The first item to back up is thedata and operating system.

Figure 2-18 ITSM Backup selection panel

In our example, we will be performing a backup and restore of a PC workstation. It is vital thatthe sequence presented here is followed. ITSM recovery with ASR is dependant upon thedata being backed up in a certain sequence, so that your system will be returned to a state

consistent with how it was backed up.

Select the Backup button to initiate the system backup, Figure 2-8 will appear showing youthat the backup is in progress.


36/76


Figure 2-19 Backup task list

If you wish to track the progress of the backup click the Report button, and Figure 2-9 willshow you the Detailed Status Report.

Figure 2-20 Backup report


37/76


Figure 2-21 Incremental backup complete

If your network does not support DHCP, then you can use local backup sets containing thebackup of your system and boot drives, system state, and system services.

Use the GENERATE BACKUPSET command to generate a backup set for a backup-archive client

node. A backup set is a collection of a clients active backed up data, stored and managed as

a single object, on specific media, in server storage. While the server allows you to create abackup set for any client node, a backup set can only be used by a backup-archive client. SeeIBM Tivoli Storage Manager for Windows Administrators Reference Version 5.2for the com-mands required to generate a backup set.


38/76


2.5.4 Copy ASR backup to diskette

Figure 2-22 Create ASR diskette

First copy the ASR files to a floppy disk, then select Utilities and then Create ASR Diskettefrom the command items. See Figure 2-10.

Figure 2-23 Create ASR diskette dialog

Insert the floppy then click Next. The files are copied to diskette and the following dialog will

appear. See Figure 2-12.

Figure 2-24 ASR diskette confirmation


39/76


If ASR backup has not been done at all, and you attempt to copy the ASR files to a floppydisk, the following error dialog box will appear. See Figure 2-13.

Figure 2-25 ASR error dialog


40/76



41/76


Chapter 3. Microsoft Windows automated

system recovery with ITSM

This chapter contains the instructions and examples for recovering a Microsoft Windows XP

Professional or Microsoft Windows 2003 Server system using ASR and ITSM BMR.

3


42/76


3.1 Recovering a Microsoft XP image using ASR and ITSM

Remember, this is a facility provided by Microsoft to recover the operating system in the event

of a catastrophic system or hardware failure. The purpose of ASR is ...to return the operatingsystem to the point of last backup.ITSM interfaces with ASR to provide the data

management functions and a repository for the data that has been backed up. Microsoft

recommendations for ASR use are:

Use ASR as a last resort in system recovery, only after you have exhausted other options

such as the startup options Safe Mode and Last Known Good Configuration.

3.1.1 Prerequisites

Before you begin to attempt to restore a Microsoft Windows XP Professional system with ASR

and ITSM, you must have the following items at hand:

ASR diskette Windows XP Professional operating system installation CD IBM Tivoli Storage Manager Client CD The ITSM node password

ASR disketteRefer to 2.4.4, Copy ASR backup to diskette on page 21 for information on how to create theASR diskette required for this recovery task:

These are the recovery steps if you did not create the ASR diskette prior to needing it for

ASR:

1. Create an ASR diskette for another machine through the virtualnode option.

2. Alter the files to point to the machine and filespace for the required restore.3. Label a diskette using the Windows command LABEL A: TSMASR

Refer to the detailed instructions for this task in No ASR diskette available on page 44.

Windows XP Professional operating system installation CDThis CD must have the identical operating system level as the systems that was backed up. If

you installed Microsoft Windows XP Professional from the original CD, and subsequentlyinstalled any service packs, then you will need a CD with the matching service pack on the

disk.

A Microsoft Windows XP Professional SP1 CD can be created for this purpose, Refer to the

Microsoft Web site to create an integrated installation of Windows XP and the service pack,

at:http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/spdeploy.asp#the_integrat

ed_installation_fmay

Additional information regarding the creation of a bootable CD-ROM containing a WindowsXP SP1 installable operating system can be found at:http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html

IBM Tivoli Storage Manager Client CDFinally, you will require an ITSM Client CD. The release version level of this CD must be at the

same or at a higher level of client than the client that was in use at the time of the backuprestoration.

The ASR for Windows XP requires that this client be at least v5.2.0.
http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/spdeploy.asp#the_integrated_installation_fmayhttp://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/spdeploy.asp#the_integrated_installation_fmayhttp://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.htmlhttp://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.htmlhttp://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/spdeploy.asp#the_integrated_installation_fmay


43/76

Chapter 3. Microsoft Windows automated system recovery with ITSM33

If you are going to create a CD for the restoration it will need to be created with TSMCLI asthe volume label and package must be renamed to TSMCLI.EXEand placed in the rootdirectory of the CD. The IBM Tivoli Storage Manager client software can be downloaded from

the following FTP site:

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r2/

You will need to select the TSMxxxx_GA_1_WIN32.exe file from the subdirectory appropriateto the version you require. Obviously for the ASR you will need at least the 5.2.0 version.

Prepare the TSM client package in package-for-the-web format burned onto a CD. This is the

single self-extracting installation package of TSM that IBM makes available through FTP.

1. Download the TSM client package (TSMxxxx_GA_1_WIN32.exe) where xxxx represents

the release number within the version.

2. Rename the package to TSMCLI.EXE. From a command prompt issue:

RENAME TSMxxxx_GA_1_WIN32.exe to TSMCLI.EXE

3. Using the method described by your CD-ROM burning software, specify the volume labelto be TSMCLI.

4. Insure the TSMCLI.EXE file path is designated as the root directory (\) in your CD-ROMburning software.

5. Burn the CD using the method described by your CD-ROM burning software.

A network connection which supports DHCPA network connection supporting DHCP is required for ASR recovery from TSM server

storage. If your network does not support DHCP, then you can use local backup setscontaining the backup of your system and boot drives; system state and system services

(Windows 2003, SYSTEMOBJECT for Windows XP). See Section 2.4.3, Incrementalbackup on page 19 for an description about backup sets.

The ITSM node passwordITSM requires the original node name and password as it was registered with the ITSMserver prior to the recovery point for the particular node you are recovering. This will be

required in order to establish a session with the server so that the server can authenticate therequest and restore the data.

3.1.2 The Windows XP Professional recovery process

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

2. Restart the computer. Press the appropriate key to boot from CD. Note, you may need toconfigure your computer BIOS to enable boot from CD. You may also need to be quick as

this option does not wait around too long before a normal startup is initiated.

3. Press F2 to enter ASR recovery mode during text mode section of Setup. This option also

does not wait for a response so you will need to be ready to press the F2 key.

4. Insert the TSM-created ASR diskette (labeled TSMASR) into the floppy drive when

prompted for the Windows ASR recovery diskette.

a. Windows reads the asrpnp.sif file from the diskette.

Note: For best performance, system objects backup should be generated in a backup set

separate from the boot and system drives.
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r1/Windows/WinNT/v515/ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r1/Windows/WinNT/v515/ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/


44/76


b. Windows reformats the boot volume and may reformat other partitions on the disk ifpartition layout is different than on the original system.

5. The nodes hard disk will be formatted and checked for errors, also certain files will becopied to the Windows installation folders.

6. Insert the Windows client installation package CD (labeled TSMCLI) into the CD-ROMdrive when prompted. The TSM client package (TSMCLI.EXE) is copied to the%SystemRoot%\temp directory

7. Insert the TSMASR diskette again into the floppy drive when prompted. The tsmasr.opt,

tsmasr.cmd, and waitforevent.exe files are copied to the %SystemRoot%\temp directory.

8. Remove the diskette when prompted prior to system reboot.

9. Insert the operating system CD into the drive when prompted.

10.After setup completes, a command window is opened, and the tsmasr.cmd file is run in

this window. A second command window is opened (and minimized), which can be usedfor diagnostic purposes.

11.The TSM client is silently installed.

12.You are prompted to choose whether you want to restore from a network connected TSM

server (press 1) or a local backup set (press 2).

13.TSM prompts for your ID and password if you are restoring from the TSM server. If

restoring from local backup set, you are prompted for the path to the local backup set, forexample, r:\backupsetfile1.ost. You will be prompted for subsequent volumes if you your

backup set occupies more than one volume.

14.TSM commands are issued to restore the system drive.

15.TSM commands are issued to restore system objects.

16.The command file exits and the machine reboots. Remove the TSMASR diskette from the

drive. After rebooting, the operating system will come up in a fully recovered state.

17.Recovery of user data and applications can now be performed using traditional TSMrestore facilities.

3.1.3 Windows XP Professional recovery example

Figure 3-1 Booting from CD

Insert the operating system CD into the CD-ROM drive.

Restart the computer.

Press the appropriate key to boot from CD.

Note: You may need to configure your computer BIOS to prefer boot from CD


45/76


You may also need to be quick to select the appropriate key to boot from CD as this optiondoes not wait around too long before a normal startup is initiated.

Figure 3-2 Press F2 for ASR

Press F2 to enter ASR recovery mode during text mode section of Setup. This option also


Figure 3-3 Insert ASR diskette into floppy drive

Insert the ASR diskette (labeled TSMASR) into the floppy drive when prompted for theWindows ASR recovery diskette.. This is the diskette which was created with the ITSM clientoption Create ASR Diskette refer to Figure 2-10 on page 21.


46/76


Figure 3-4 Setup is formatting the hard disk

The nodes hard disk will be formatted, if there was a previous version of Windows residing on

the target machine then you may need to delete the partition in order to install (recover) yourbacked up system. Follow the prompts and respond as you would for a new installation.Remember, however, that the new partition cannot have a drive space partition which is

smaller than the partition which was originally backed up.

Figure 3-5 Setup is checking the drive

The disks are then checked for errors using the Windows util ity.


47/76


Figure 3-6 Setup is copying the files to the installation folders

Certain files will be copied to the Windows installation folders.

Figure 3-7 Windows ASR requests the ITSM client CD

Insert the Windows client installation package CD (labeled TSMCLI) into the CD-ROM drive

when prompted. The TSM client package (TSMCLI.EXE) is copied to the%SystemRoot%\temp directory.


48/76


Figure 3-8 Windows ASR requests the TSMASR diskette

Insert the TSMASR diskette again into the floppy drive when prompted. The tsmasr.opt,tsmasr.cmd, and waitforevent.exe files are copied.

The prompt may appear three times, once for each file that is copied to the to the%SystemRoot%\temp directory. Press enter each time and the process will continue

Figure 3-9 Windows ASR requests removal of the floppy disk prior to rebooting the system

Remove the diskette when prompted prior to system reboot.


49/76


Figure 3-10 WIN XP Setup requires the XP operating system CD

Insert the operating system CD into the drive when prompted.


50/76


Figure 3-11 Windows ASR installs IBM Tivoli Storage Manager

After setup completes, a command window is opened, and the tsmasr.cmd file is run in thiswindow. A second command window is opened (and minimized), which can be used for

diagnostic purposes.

The TSM client is silently installed.


51/76


Figure 3-12 Decision point: restore from ITSM server or backup set

You are prompted to choose whether you want to restore from a network connected TSMserver (press 1) or a local backup set (press 2).


52/76


Figure 3-13 ITSM server: requests userid and password

TSM prompts for your ID and password if you are restoring from the TSM server. If restoringfrom local backup set, you are prompted for the path to the local backup set, for example,

r:\backupsetfile1.ost. You will be prompted for subsequent volumes if you your backup set

occupies more than one volume.


53/76


Figure 3-14 ITSM restores of multiple files

TSM commands are issued to restore the system drive.

TSM commands are issued to restore system state and system services on Windows 2003

(system objects on Windows XP).

The command file exits and the machine reboots. Remove the TSMASR diskette from the


Recovery of user data and applications can now be performed using traditional TSM restorefacilities.

3.1.4 Common Errors in restore process

Invalid order of backupIf you completed the incremental prior to doing the ASR backup then the SMSS.asr and the

NTDLL.ASR files will not be backed up on the incremental backup. The following error will

occur:

The setup was unable to start the recovery applicationC:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error code returnedwas 0x2.

Follow these instructions to recover the system from this error:

1. Find another machine running the same maintenance level of Windows as the system you

wish to recover.


54/76


2. Copy the SMSS.ASR and NTDLL.ASR files from the \WINDOWS\REPAIR directory of thatmachine to a diskette.

3. Re-run the ASR recovery process to the point where the TSM ASR recovery scriptprompts you for network or backupset recovery.

4. Use the minimized command window (shown at the bottom of Figure 3-14) to copy thefiles to the machine being recovered. For example, you may use the command:

COPY A:\*.ASR C:\WINDOWS\REPAIR

5. Return to the recovery window and resume the recovery process.

Figure 3-15 Diagnostic command window

The diagnostic command window is available if you need to display or edit files. This facility iswithin a DOS prompt, and is first available when Windows ASR installs IBM Tivoli StorageManager. See Figure 3-11 on page 40.

No ASR diskette availableIf you did not create the ASR diskette prior to needing it for the ASR then you will need tocreate a new ASR diskette on another machine and insert the virtualnodename parameter in

the tsmasr.opt file on the newly created diskette.

The virtualnodename option specifies the node name of your workstation when you want torestore or retrieve files to a different workstation.

Note: This error should only become an issue during testing as the normal state of events

will ensure that you have done an ASR backup once the files will have been created and

backed up.


55/76


When you use the virtualnodename option in your client options file, or with a command:

1. You must specify the name you specified with the nodename option in your client options

file (tsmasr.opt). This name should be different from the name returned by the hostnamecommand on your workstation.

2. Tivoli Storage Manager prompts for the password assigned to the node you specify, if apassword is required. If you enter the correct password, you have access to all backupsand archives that originated from the specified node.

When connecting to a server, the client must identity itself to the server. This login

identification is determined in the following ways:

If the nodename and virtualnodename options are not specified, or a virtual node name

is not specified on the command line, the default login ID is the name returned by thehostname command.

If the nodename option is specified, the name specified with the nodename optionoverrides the name returned by the hostname command.

If the virtualnodename option is specified, or a virtual node name is specified on acommand line, it cannot be the same name as the name returned by the hostname

command.

When the virtual node name is accepted by the server, a password is required (assuming

authentication is on), even if the passwordaccess option is generate. The password is notstored in the registry even when the passwordaccess option is set to generate. Once aconnection to the server is established, then access is permitted to any file backed up usingthis login ID.

Syntax

>>-VIRTUALNodename- nodename----------------------------------->nul@echo Do you wish to perform Automated Service Recovery (ASR) restore from the TSMserver or from a local backup set?@echo 1. Restore from the TSM server.@echo 2. Restore from a local backup set.:choiceset /P CH=if /I "%CH%"=="1" goto NETWORKif /I "%CH%"=="2" goto BACKUPSETgoto choice


56/76


:NETWORKdsmc restore \\IBM-BRETT\C$\ C:\ -subdir=yes -preservepath=complete -replace=all-tapeprompt=no -nodename=IBM-BRETT -optfile=tsmasr.optdsmc restore systemstate -asrmode=yes -nodename=IBM-BRETT -computername=IBM-BRETT-optfile=tsmasr.optdsmc restore systemservices -asrmode=yes -nodename=IBM-BRETT -computername=IBM-BRETT-optfile=tsmasr.opt

REM Diagnosticsdsmc query backup \\ibm-brett\c$\WINDOWS\repair\*.asr -asrmode=yes-nodename=IBM-BRETT -optfile=tsmasr.opt >tsmasrdiag.txtREM dsmc query backup \\ibm-brett\c$\WINDOWS\repair\*.asr -asrmode=yes-nodename=IBM-BRETT -optfile=tsmasr.opt >a:\tsmasrdiag.txt@GOTO DONE:BACKUPSETdsmc restore backupset TSMASR \\IBM-BRETT\C$\ C:\ -asrmode=yes -subdir=yes-preservepath=complete -replace=all -tapeprompt=no -nodename=IBM-BRETT-location=file -optfile=tsmasr.optdsmc restore backupset TSMASR systemstate -asrmode=yes -nodename=IBM-BRETT-location=file -replace=all -computername=IBM-BRETT -optfile=tsmasr.optdsmc restore backupset TSMASR systemservices -asrmode=yes -nodename=IBM-BRETT-location=file -replace=all -computername=IBM-BRETT -optfile=tsmasr.opt

:DONE@echo on

3.2 Recovering a Microsoft 2003 image using ASR and ITSM

Remember, this is a facility provided by Microsoft to recover the operating system in the event

of a catastrophic system or hardware failure. The purpose of ASR is to return the operatingsystem to the point of last backup.ITSM interfaces with ASR to provide the data

management functions and a repository for the data that has been backed up. The Microsoftrecommendation for ASR use is Use ASR as a last resort in system recovery, only after you

have exhausted other options such as the startup options Safe Mode and Last Known GoodConfiguration.

3.2.1 Prerequisites

Before you begin to attempt to restore a Microsoft Windows 2003 Professional system withASR, you must have the following items at hand:

ASR diskette Windows XP Professional operating system installation CD IBM Tivoli Storage Manager Client CD The ITSM node password

ASR diskette

Refer to 2.4.4, Copy ASR backup to diskette on page 21 as to how to create the ASRdiskette required for this recovery task.

How to recover if you did not create the ASR diskette prior to needing it for ASR:

1. Create an ASR diskette for another machine through the virtualnode option.

2. Alter the files to point to the machine/filespace for the required restore.3. Label a diskette using the Windows command LABEL A: TSMASR.

Refer to the detailed instructions for this task in No ASR diskette available on page 58.


57/76


Windows 2003 Server operating system installation CDThis CD must have the identical operating system level as the systems that were backed up. Ifyou installed Microsoft Windows 2003 from the original CD, and subsequently installed any

service packs, then you will need a CD with the matching service pack on the disk.

IBM Tivoli Storage Manager Client CD

Finally, you will require an ITSM Client CD, the release, version, and level of this CD must beat the same or at a higher level of client than the client that was in use at the time of thebackup that is being restored.

The ASR for Windows XP requires that this client be at least v5.2.0.

If you are going to create a CD for the restoration, it will need to be created with TSMCLI asthe volume label and package must be renamed to TSMCLI.EXEand placed in the root

directory of the CD. The IBM Tivoli Storage Manager client software can be downloaded fromthe following FTP site:

ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r2/

You need to select the TSMxxxx_GA_1_WIN32.exe file from the subdirectory appropriate to

the version you require. Obviously, for the ASR you need at least the 5.2.0 version.

Prepare the TSM client package in package-for-the-Web format burned onto a CD. This is thesingle self-extracting installation package of TSM that IBM makes available through FTP:

1. Download the TSM client package (TSMxxxx_GA_1_WIN32.exe) where xxxx representsthe release number within the version.

2. Rename the package to TSMCLI.EXE. From a command prompt issue:

RENAME TSMxxxx_GA_1_WIN32.exe to TSMCLI.EXE

3. Using the method described by your CD-ROM burning software, specify the volume labelto be TSMCLI.

4. Insure the TSMCLI.EXE file path is designated as the root directory (\) in your CD-ROMburning software.

5. Burn the CD using the method described by your CD-ROM burning software.

A network connection which supports DHCPA network connection supporting DHCP is required for ASR recovery from TSM server

storage. If your network does not support DHCP, then you can use local backup setscontaining the backup of your system and boot drives; system state and system services.

See 2.4.3, Incremental backup on page 19 for an description about backup sets.

The ITSM node passwordITSM requires the original node name and password as it was registered with the ITSMserver prior to the recovery point for the particular node you are recovering. This will be

required in order to establish a session with the server so that the server can authenticate therequest and restore the data.

Note: For best performance, system state/system services backup should be generated ina backup set separate from the boot and system drives.
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r1/Windows/WinNT/v515/ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v5r1/Windows/WinNT/v515/ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/


58/76


3.2.2 The recovery process for Windows 2003

Here are the steps:

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

2. Restart the computer. Press the appropriate key to boot from CD. Note, you may need to

configure your computer BIOS to enable boot from CD. You may also need to be quick as

this option does not wait around too long before a normal startup is initiated.

3. Press F2 to enter ASR recovery mode during text mode section of Setup. This option alsodoes not wait for a response, so you will need to be ready to press the F2 key.

4. Insert the TSM-created ASR diskette (labeled TSMASR) into the floppy drive whenprompted for the Windows ASR recovery diskette.

a. Windows reads the asrpnp.sif file from the diskette.

b. Windows reformats the boot volume and may reformat other partitions on the disk ifpartition layout is different than on the original system.

5. The nodes hard disk will be formatted and checked for errors, also certain files will becopied to the Windows installation folders.

6. Insert the Windows client installation package CD (labeled TSMCLI) into the CD-ROMdrive when prompted. The TSM client package (TSMCLI.EXE) is copied to the

%SystemRoot%\temp directory.

7. Insert the TSMASR diskette again into the floppy drive when prompted. The tsmasr.opt,

tsmasr.cmd, and waitforevent.exe files are copied to the %SystemRoot%\temp directory.

8. Remove the diskette when prompted prior to system reboot.

9. Insert the operating system CD into the drive when prompted.

10.After setup completes, a command window is opened, and the tsmasr.cmd file is run in

this window. A second command window is opened (and minimized), which can be usedfor diagnostic purposes.

11.The TSM client is silently installed.

12.You are prompted to choose whether you want to restore from a network connected TSM


13.TSM prompts for your ID and password if you are restoring from the TSM server. If

restoring from local backup set, you are prompted for the path to the local backup set, forexample, r:\backupsetfile1.ost. You will be prompted for subsequent volumes if you your

backup set occupies more than one volume.

14.TSM commands are issued to restore the system drive.

15.TSM commands are issued to restore system state and system services.

16.The command file exits and the machine reboots. Remove the TSMASR diskette from thedrive. After rebooting, the operating system will come up in a fully recovered state.

17.Recovery of user data and applications can now be performed using traditional TSMrestore facilities.

3.2.3 Windows 2003 recovery example

For the results of Figure 3-16, see the following steps.


59/76


Figure 3-16 Booting from CD

1. Insert the operating system CD into the CD-ROM drive.2. Restart the computer.

3. Press the appropriate key to boot from CD.

You may also need to be quick to select the appropriate key to boot from CD as this optiondoes not wait around too long before a normal startup is initiated.

Figure 3-17 Press F2 for ASR

Press F2 to enter ASR recovery mode during text mode section of Setup. This option also


Note: You may need to configure your computer BIOS to enable boot from CD.


60/76


Figure 3-18 Insert ASR diskette into floppy drive

Insert the ASR diskette (labeled TSMASR) into the floppy drive when prompted for theWindows ASR recovery diskette. This is the diskette that was created with the ITSM clientoption Create ASR Diskette. Refer to Figure 2-10 on page 21.

Figure 3-19 Setup is formatting the hard disk

The nodes hard disk will be formatted, if there was a previous version of Windows residing onthe target machine, then you may need to delete the partition in order to install (recover) yourbacked up system. Follow the prompts and respond as you would for a new installation.

Remember however that the new partition cannot have a drive space partition that is smallerthan the partition that was originally backed up.


61/76


Figure 3-20 Setup is checking the drive

The newly partitioned drive is then checked for errors.

Figure 3-21 Setup is copying the files to the installation folders

Also, certain files will be copied to the Windows installation folders.


62/76


Figure 3-22 Windows ASR requests the ITSM client CD

Insert the Windows client installation package CD (labeled TSMCLI) into the CD-ROM drive

when prompted. The TSM client package (TSMCLI.EXE) is copied to the%SystemRoot%\temp directory.

Figure 3-23 Windows ASR requests the TSMASR diskette

Insert the TSMASR diskette again into the floppy drive when prompted. The tsmasr.opt,tsmasr.cmd, and waitforevent.exe files are copied.

The prompt may appear three times, once for each file that is copied to the to the

%SystemRoot%\temp directory. Press Enter each time and the process will continue.


63/76


Figure 3-24 Windows ASR requests removal of the floppy disk

Remove the diskette when prompted prior to system reboot.

Figure 3-25 WIN 2003 Setup requires the operating system CD

Insert the operating system CD into the drive when prompted.


64/76


Figure 3-26 Windows ASR installs IBM Tivoli Storage Manager

After setup completes, a command window is opened, and the tsmasr.cmd file is run in this

window. A second command window is opened (and minimized), which can be used fordiagnostic purposes. The TSM client is silently installed.

Note: On Windows 2003 server the prompt message is not clear: Setup was unable [to]access files needed to continue. This could be caused by an error on the CD Mediaor the CD is no longer present in the drive. Reinsert the Windows 2003 installationCD and respond to the prompt.


65/76


Figure 3-27 Decision point: restore from ITSM server or backup set

You are prompted to choose whether you want to restore from a network connected TSM



66/76


Figure 3-28 ITSM server: requests userid and password

TSM prompts for your ID and password if you are restoring from the TSM server. If restoringfrom local backup set, you are prompted for the path to the local backup set, for example,r:\backupsetfile1.ost. You will be prompted for subsequent volumes if you your backup set

occupies more than one volume.


67/76


Figure 3-29 ITSM restores of multiple files

ITSM commands are issued to restore the system drive.

ITSM commands are issued to restore system state and system services on Windows 2003

(system objects on Windows XP).

The command file exits and the machine reboots. Remove the ITSM ASR diskette from the


Recovery of user data and applications can now be performed using traditional ITSM restore

facilities.

3.2.4 Common errors in restore process

Invalid order of backupIf you completed the incremental prior to doing the ASR backup then the SMSS.asr and the

NTDLL.ASR files will not be backed up on the incremental backup. The following error willoccur:

Setup was unable to start the recovery applicationC:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error codereturned was 0x2.

Follow these instructions to recover the system from this error:

1. Find another machine running the same maintenance level of Windows as the system youwish to recover.


68/76


2. Copy the SMSS.ASR and NTDLL.ASR files from the \WINDOWS\REPAIR directory of thatmachine to a diskette.

3. Re-run the ASR recovery process to the point where the TSM ASR recovery scriptprompts you for network or backupset recovery.

4. Use the minimized command window (shown at the bottom of Figure 3-29) to copy thefiles to the machine being recovered. For example:

COPY A:\*.ASR C:\WINDOWS\REPAIR

5. Return to the recovery window and resume the recovery process.

Figure 3-30 Diagnostic command window

The diagnostic command window is available if you need to display or edit files. This facility iswithin a DOS prompt, and is first available when Windows ASR installs IBM Tivoli Storage

Manager. See Figure 3-26 on page 54.

No ASR diskette availableIf you did not create the ASR diskette prior to needing it for the ASR, then you will need to

create a new ASR diskette on another machine, and insert the virtualnodename parameter inthe tsmasr.opt file on the newly created diskette.

IBM Tivoli Storage Manager Bare Machine Recovery for Microsoft Windows 2003 and XP Redp3703

Documents

Transcript of IBM Tivoli Storage Manager Bare Machine Recovery for Microsoft Windows 2003 and XP Redp3703