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

Front cover
IBM Tivoli Storage Manager: Bare Machine Recovery for Microsoft Windows 2003 and XP
Use built-in APIs provided by Windows to protect your system See how Windows ASR integrates with ITSM Learn how to configure your system for recovery
Barry Kadleck David McFarlane Pracha Pechsuksan Wah Han Tan
ibm.com/redbooks
Redpaper
International Technical Support Organization IBM Tivoli Storage Manager: Bare Machine Recovery for Microsoft Windows 2003 and XP October 2003
Note: Before using this information and the product it supports, read the information in Notices on page v.
First Edition (October 2003) This edition applies to IBM Tivoli Storage Manager V5.2 and above. 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 of this redbook for more current information.
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.
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 IBM Tivoli Storage Manager concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 IBM Tivoli Storage Manager functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Restore and backup functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Archive and retrieve functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.3 Managing backups, archives, other data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.4 Administrative overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.5 Hints and tips for command line, registration, and timeout . . . . . . . . . . . . . . . . . . . Chapter 2. Setting up IBM Tivoli Storage Manager for BMR . . . . . . . . . . . . . . . . . . . . . 2.1 Prerequisites and considerations in using ASR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 Hardware requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.3 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Installation of the ITSM client on your Windows environment. . . . . . . . . . . . . . . . . . . . 2.3 Customization of the ITSM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 TSM Backup/Archive Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Online image support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 Open file support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Performing ITSM backups for ASR with Windows XP . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 ASR backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.2 SYSTEMOBJECT backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.3 Incremental backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4.4 Copy ASR backup to diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Performing ITSM backups for ASR with Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 ASR backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.2 System services and system state backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.3 Incremental backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.4 Copy ASR backup to diskette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3. Microsoft Windows automated system recovery with ITSM . . . . . . . . . . . 3.1 Recovering a Microsoft XP image using ASR and ITSM . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 The Windows XP Professional recovery process . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 Windows XP Professional recovery example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.4 Common Errors in restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Recovering a Microsoft 2003 image using ASR and ITSM . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 The recovery process for Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.3 Windows 2003 recovery example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.4 Common errors in restore process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 3 3 3 3 4 9
11 12 12 13 13 13 14 15 15 15 16 16 18 19 21 22 23 24 25 28 31 32 32 33 34 43 46 46 48 48 57 iii
Copyright IBM Corp. 2003. All rights reserved.
Appendix A. Slipstreaming Windows XP Service Pack 1a . . . . . . . . . . . . . . . . . . . . . . 61 Slipstreaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Slipstream Windows XP Service Pack 1a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
iv
IBM Tivoli Storage Manager: Bare Metal Restore for Windows
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. Consult your local IBM representative for information on the products and services currently available in your area. Any reference 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 not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate 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. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, 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 are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "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 of express 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 made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials 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 incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities 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 them as 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 business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any 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 sample programs 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, and distribute 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.
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:
IBM pSeries AIX GDPS HACMP/6000 IBM Rational Redbooks SP1 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 United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United 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 Electronic Transaction LLC. Other company, product, and service names may be trademarks or service marks of others.
vi
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 your systems from catastrophic failures.
The team that wrote this Redpaper

This Redpaper was produced by a team of specialists from around the world working at the International Technical Support Organization, San Jose Center. Barry Kadleck is 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 last 10 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 products into Europe. David McFarlane is a Technical Solutions Architect in Australia. He has 19 years of experience 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 TotalStorage Virtual 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 areas of expertise include AIX, TSM, SP2, and HACMP/6000. Wah Han Tan is an IT Specialist with the pSeries services team in Singapore. He has worked 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-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. 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 productivity and 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!
vii
We want our papers to be as helpful as possible. Send us your comments about this Redpaper 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:

redbook@us.ibm.com
Mail your comments to: IBM Corporation, International Technical Support Organization Dept. QXXE Building 80-E2 650 Harry Road San Jose, California 95120-6099
viii
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 operating systems: Microsoft Windows XP Professional Microsoft Windows 2003 Server It should be first noted that this function also requires the Microsoft Windows Automated System 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. The purpose of ASR is to return the operating system 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. In this chapter we introduce the basic concepts of IBM Tivoli Storage Manager (ITSM). We will 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 not intended 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 may gain from our experience in using the product.
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 the migrate and recall facility under HSM. ITSM will enable you to manage both the data and the storage that they reside upon.
IBM Tivoli Storage Manager

Clients Policies and Requests Server
migrate/ recall backup/ restore archive/ retrieve
Network
Storage Pools
Figure 1-1 IBM Tivoli Storage Manager concepts
IBM Tivoli Storage Manager manages the movement and storage of data. The ITSM client software 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 called storage pools. ITSM can be set up to run in a local area network (LAN), wide area network (WAN), or Storage Area Network (SAN) environments. Note: As a general rule, the server version should be at a higher release level than the client; please check release documentation for compatibility between specific releases and combinations.
1.2 IBM Tivoli Storage Manager functions

The following sections outline the IBM Tivoli Manager functions.
1.2.1 Restore and backup functions

Restore
Careful 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 always be 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 you cannot 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 and understand.
Backup
ITSM utilizes a progressive backup methodology. A full backup is done only once, after which incremental backups are made only of files that have changed since the last backup. The metadata 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 the storage 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 automated method 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 always know the location of the most recent copy of your file resides; this is crucial in the efficient and effective 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 you need 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, and read 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 which policies exist: Version data exists Version data deleted Retain extra versions Retain only version Backup retention Archive retention
Chapter 1. Introduction
Copy frequency Copy destination The metadata (data about the actual data) and media that it resides upon, exists within the ITSM 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 and status 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
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.
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 who are familiar with the ITSM command set. Some administrators rely on the ITSM command line as their primary configuration and management tool. This interface allows for the generation of administrative scripts and macros, which can be scheduled to execute automatically.
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 familiar Windows-styled tree view to display the drives, directories, and files that can be manipulated between the client and the server.
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 the installation 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
The ITSM client command line is a character based interface that provides comprehensive control 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 the installation has either been completed, or the value of their initial setting is no longer a distinct advantage.
Web administrator Command line interface

Many administrators find that the command line interface is easier to use than the GUI; the ITSM Server Web Administration dialog will allow you to include the command line. Here are the 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
Registration
When you first set up the clients for your installation, it may be advisable to allow open registration. This will save you from registering each client from the server interface individually. To do this, enter the following command from the command line interface:
set registration open
Note: This command should be reset to closed once the initial setup of the clients has been completed, since it will allow any client to register without being previously authorized.
Timeout of server administrator

The Administrator timeout default is set to 5 minutes. This may not be the most effective time period, especially if you are having to log in multiple times while performing other tasks on the same 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.
10
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
11
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 a catastrophic 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 writing over 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 users can 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 through normal ITSM restore procedures after successful completion of ASR recovery. You should create 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. Note: If there is a change in the video cards or networking cards, they must be manually configured. 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 recovery must 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.
12
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 installation CD 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 the backups for the system being recovered. The details for creating the TSMCLI CD are described 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.
Version of Windows at Backup Windows XP Windows XP Windows XP Service Pack 1 Windows XP Service Pack 1 Windows XP Service Pack 1a Windows XP Service Pack 1a Windows 2003 Server
Version of Windows at Restore Windows XP Windows XP Service Pack 1a Windows XP Windows XP Service Pack 1a Windows XP Windows XP Service Pack 1a Windows 2003 Server
Supported or Not Supported Supported (see Note) Not supported Supported (see Note) Supported Not supported Supported Supported
Note: The Japanese and Spanish versions of Microsoft Windows XP are not supported.
2.2 Installation of the ITSM client on your Windows environment

Please refer to the ITSM quickstart and administrator guides for the instructions on how to install the ITSM client on your Microsoft Windows environment.
Chapter 2. Setting up IBM Tivoli Storage Manager for BMR
13
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 these options. Other setup wizards can be completed, the three we have shown are the only ones required for the ASR recovery process.
14
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 recovery functions. 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 online image backup. LVSA is a snapshot provider that is used for online image backup and open file support operations on the Windows 2003 and XP clients.
2.3.3 Open file support

Select 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 are locked 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 the snapshot, 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 during the 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 for open file support through this client configuration wizard. Note: After you have finished the initial set up of the options file, you can use the Preferences window to specify other client options. To open the Preferences window, select the Preferences item from the Edit menu.
15
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 certain order. 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 in the 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 the ASR files. Follow the examples in Figure 2-4 and Figure 2-5.
16
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 the NTDLL.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 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 returned was 0x2.
This error can be fixed in the recovery process, See 3.1.3, Windows XP Professional recovery example on page 34.
17
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). 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 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. Microsoft recommends 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 System volume Removable Storage Management Database (RSM) Replicated file systems (FRS) Windows Management Instrumentation (WMI)
18
You can exclude system objects from backup processing using the exclude.systemobject option. See Exclude options in 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.4.3 Incremental backup

From the startup panel (Figure 2-3) choose the Backup option. The first item to back up is the data 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 that the sequence presented here is followed. ITSM recovery with ASR is dependant upon the data 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 you that the backup is in progress.
19
Figure 2-8 Backup task list
If you wish to track the progress of the backup, click the Report button and Figure 2-9 will show 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 the backup 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 as a single object, on specific media, in server storage. While the server allows you to create a backup set for any client node, a backup set can only be used by a backup-archive client. See IBM Tivoli Storage Manager for Windows Administrators Reference Version 5.2 for the commands required to generate a backup set.
20
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 from the 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
21
If ASR backup has not been done at all, and you attempt to copy the ASR files to a floppy disk, 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 recovery diskette) must be done prior to the latest incremental backup. The order used in the testing we did was: 1. 2. 3. 4. ASR backup System services and system state backup Incremental backup Copy ASR backup to diskette
An example of each of these steps is provided in the following subsections.
22
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 another incremental 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 returned was 0x2.
23
This error can be fixed in the recovery process. See 3.1.3, Windows XP Professional recovery 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 system state) 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. When processing completes, the Backup Report window displays processing details. You can back up Windows 2003 system objects together or individually. Microsoft recommends 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
24
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.systemobject option. 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 the data 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 that the sequence presented here is followed. ITSM recovery with ASR is dependant upon the data 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 you that the backup is in progress.
25
Figure 2-19 Backup task list
If you wish to track the progress of the backup click the Report button, and Figure 2-9 will show you the Detailed Status Report.
Figure 2-20 Backup report
26
Figure 2-21 Incremental backup complete
If your network does not support DHCP, then you can use local backup sets containing the backup 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 a backup set for any client node, a backup set can only be used by a backup-archive client. See IBM Tivoli Storage Manager for Windows Administrators Reference Version 5.2 for the commands required to generate a backup set.
27
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 Diskette from 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
28
If ASR backup has not been done at all, and you attempt to copy the ASR files to a floppy disk, the following error dialog box will appear. See Figure 2-13.
Figure 2-25 ASR error dialog
29
30
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.
31
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 operating system 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 diskette
Refer to 2.4.4, Copy ASR backup to diskette on page 21 for information on how to create the ASR 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 CD

This 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 subsequently installed 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 Windows XP SP1 installable operating system can be found at: http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
IBM Tivoli Storage Manager Client CD

Finally, 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 backup restoration. The ASR for Windows XP requires that this client be at least v5.2.0. 32
If you are going to create a CD for the restoration it will need to be created with TSMCLI as the volume label and package must be renamed to TSMCLI.EXE and placed in the root directory 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 appropriate to 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 label to be TSMCLI. 4. Insure the TSMCLI.EXE file path is designated as the root directory (\) in your CD-ROM burning software. 5. Burn the CD using the method described by your CD-ROM burning software.
A network connection which supports DHCP

A 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 sets containing the backup of your system and boot drives; system state and system services (Windows 2003, SYSTEMOBJECT for Windows XP). See Section 2.4.3, Incremental backup on page 19 for an description about backup sets. Note: For best performance, system objects backup should be generated in a backup set separate from the boot and system drives.
The ITSM node password

ITSM requires the original node name and password as it was registered with the ITSM server 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 the request 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 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 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.
Chapter 3. Microsoft Windows automated system recovery with ITSM
33
b. Windows reformats the boot volume and may reformat other partitions on the disk if partition layout is different than on the original system. 5. The nodes hard disk will be formatted and checked for errors, also certain files will be copied to the Windows installation folders. 6. 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 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 used for 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, for example, 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 TSM restore 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
34
You may also need to be quick to select the appropriate key to boot from CD as this option does 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 does not wait for a response so you will need to be ready to press the F2 key.
Figure 3-3 Insert ASR diskette into floppy drive
Insert the ASR diskette (labeled TSMASR) into the floppy drive when prompted for the Windows ASR recovery diskette.. This is the diskette which was created with the ITSM client option Create ASR Diskette refer to Figure 2-10 on page 21.
35
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) your backed 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 utility.
36
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.
37
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.
38
Figure 3-10 WIN XP Setup requires the XP operating system CD
Insert the operating system CD into the drive when prompted.
39
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 this window. A second command window is opened (and minimized), which can be used for diagnostic purposes. The TSM client is silently installed.
40
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 TSM server (press 1) or a local backup set (press 2).
41
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 restoring from 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.
42
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 drive. After rebooting, the operating system will come up in a fully recovered state. Recovery of user data and applications can now be performed using traditional TSM restore facilities.
3.1.4 Common Errors in restore process

Invalid order of backup
If 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 application C:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error code returned 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 you wish to recover.
43
2. Copy the SMSS.ASR and NTDLL.ASR files from the \WINDOWS\REPAIR directory of that machine to a diskette. 3. Re-run the ASR recovery process to the point where the TSM ASR recovery script prompts you for network or backupset recovery. 4. Use the minimized command window (shown at the bottom of Figure 3-14) to copy the files 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 is within a DOS prompt, and is first available when Windows ASR installs IBM Tivoli Storage Manager. See Figure 3-11 on page 40. 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.
No ASR diskette available

If 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 in the tsmasr.opt file on the newly created diskette. The virtualnodename option specifies the node name of your workstation when you want to restore or retrieve files to a different workstation.
44
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 hostname command on your workstation. 2. Tivoli Storage Manager prompts for the password assigned to the node you specify, if a password is required. If you enter the correct password, you have access to all backups and 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 the hostname command. If the nodename option is specified, the name specified with the nodename option overrides the name returned by the hostname command. If the virtualnodename option is specified, or a virtual node name is specified on a command 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 not stored in the registry even when the passwordaccess option is set to generate. Once a connection to the server is established, then access is permitted to any file backed up using this login ID. Syntax
>>-VIRTUALNodename- nodename-----------------------------------><
You will also need to change the tsmasr.cmd file to ensure that the restore commands point to the correct filespaces for the machine that you are restoring. Here is an example of a TSMASR.CMD file that resores the nodename IBM-BRETT, each occurrence of this nodename would have to be altered to the nodename required for the machine restore:
@start "IBM Tivoli Storage Manager" /MIN cmd.exe @echo off @title IBM Tivoli Storage Manager @echo Windows ASR is installing TSM. Please wait for installation to complete. %SystemRoot%\temp\tsmcli.exe -s -e setup.exe -a /s /v"INSTALLDIR=\"%SystemRoot%\temp\~tsmasr\" ADDLOCAL=\"Client\" TRANSFORM=\"C:\tsm_images\TSM_BA_CLIENT\1033.mst\" /qn /l*v \"C:\WINDOWS\repair\tsmasrsetup.log\" RebootYesNo=\"No\" REBOOT=\"Suppress\" ALLUSERS=1 " %SystemRoot%\temp\waitforevent.exe 600 Diagnostics REM pause pushd %SystemRoot%\temp\~tsmasr\baclient copy %SystemRoot%\temp\tsmasr.opt >nul @echo Do you wish to perform Automated Service Recovery (ASR) restore from the TSM server or from a local backup set? @echo 1. Restore from the TSM server. @echo 2. Restore from a local backup set. :choice set /P CH= if /I "%CH%"=="1" goto NETWORK if /I "%CH%"=="2" goto BACKUPSET goto choice
45
:NETWORK dsmc restore \\IBM-BRETT\C$\ C:\ -subdir=yes -preservepath=complete -replace=all -tapeprompt=no -nodename=IBM-BRETT -optfile=tsmasr.opt dsmc restore systemstate -asrmode=yes -nodename=IBM-BRETT -computername=IBM-BRETT -optfile=tsmasr.opt dsmc restore systemservices -asrmode=yes -nodename=IBM-BRETT -computername=IBM-BRETT -optfile=tsmasr.opt REM Diagnostics dsmc query backup \\ibm-brett\c$\WINDOWS\repair\*.asr -asrmode=yes -nodename=IBM-BRETT -optfile=tsmasr.opt >tsmasrdiag.txt REM dsmc query backup \\ibm-brett\c$\WINDOWS\repair\*.asr -asrmode=yes -nodename=IBM-BRETT -optfile=tsmasr.opt >a:\tsmasrdiag.txt @GOTO DONE :BACKUPSET dsmc restore backupset TSMASR \\IBM-BRETT\C$\ C:\ -asrmode=yes -subdir=yes -preservepath=complete -replace=all -tapeprompt=no -nodename=IBM-BRETT -location=file -optfile=tsmasr.opt dsmc restore backupset TSMASR systemstate -asrmode=yes -nodename=IBM-BRETT -location=file -replace=all -computername=IBM-BRETT -optfile=tsmasr.opt dsmc 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 operating system 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 Microsoft recommendation 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 Good Configuration.
3.2.1 Prerequisites
Before you begin to attempt to restore a Microsoft Windows 2003 Professional system with ASR, 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 ASR diskette 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.
46
Windows 2003 Server operating system installation CD

This CD must have the identical operating system level as the systems that were backed up. If you 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 be at the same or at a higher level of client than the client that was in use at the time of the backup 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 as the volume label and package must be renamed to TSMCLI.EXE and placed in the root directory 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 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 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 label to be TSMCLI. 4. Insure the TSMCLI.EXE file path is designated as the root directory (\) in your CD-ROM burning software. 5. Burn the CD using the method described by your CD-ROM burning software.
A network connection which supports DHCP

A 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 sets containing 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. Note: For best performance, system state/system services backup should be generated in a backup set separate from the boot and system drives.
The ITSM node password

ITSM requires the original node name and password as it was registered with the ITSM server 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 the request and restore the data.
47
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 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. b. Windows reformats the boot volume and may reformat other partitions on the disk if partition layout is different than on the original system. 5. The nodes hard disk will be formatted and checked for errors, also certain files will be copied to the Windows installation folders. 6. 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. 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 used for 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, for example, 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 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 TSM restore facilities.
3.2.3 Windows 2003 recovery example

For the results of Figure 3-16, see the following steps.
48
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. Note: You may need to configure your computer BIOS to enable boot from CD. You may also need to be quick to select the appropriate key to boot from CD as this option does 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 does not wait for a response so you will need to be ready to press the F2 key.
49
Figure 3-18 Insert ASR diskette into floppy drive
Insert the ASR diskette (labeled TSMASR) into the floppy drive when prompted for the Windows ASR recovery diskette. This is the diskette that was created with the ITSM client option 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 on the target machine, then you may need to delete the partition in order to install (recover) your backed 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 smaller than the partition that was originally backed up.
50
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.
51
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.
52
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.
53
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 Media or the CD is no longer present in the drive. Reinsert the Windows 2003 installation CD and respond to the prompt.
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 for diagnostic purposes. The TSM client is silently installed.
54
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 server (press 1) or a local backup set (press 2).
55
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 restoring from 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.
56
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 drive. After rebooting, the operating system will come up in a fully recovered state. 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 backup
If 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:
Setup was unable to start the recovery application C:\windows\temp\tsmasr.cmd /sifpath=C:\windows\repair\asr.sif. The error code returned 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 you wish to recover.
57
2. Copy the SMSS.ASR and NTDLL.ASR files from the \WINDOWS\REPAIR directory of that machine to a diskette. 3. Re-run the ASR recovery process to the point where the TSM ASR recovery script prompts you for network or backupset recovery. 4. Use the minimized command window (shown at the bottom of Figure 3-29) to copy the files to the machine being recovered. For example:
COPY A:\*.ASR C:\WINDOWS\REPAIR
5. Return to the recovery window and resume the recovery process. Note: This error should only become an issue during testing as the normal state of events will ensure that once you have done an ASR backup once the files will have been created and backed up. It is, however, important to recognize this error.
Figure 3-30 Diagnostic command window
The diagnostic command window is available if you need to display or edit files. This facility is within 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 available

If 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 in the tsmasr.opt file on the newly created diskette. The virtualnodename option specifies the node name of your workstation when you want to restore or retrieve files to a different workstation. 58
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 hostname command on your workstation. 2. Tivoli Storage Manager prompts for the password assigned to the node you specify, if a password is required. If you enter the correct password, you have access to all backups and 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 the hostname command. If the nodename option is specified, the name specified with the nodename option overrides the name returned by the hostname command. If the virtualnodename option is specified, or a virtual node name is specified on a command 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 not stored in the registry even when the passwordaccess option is set to generate. Once a connection to the server is established, then access is permitted to any file backed up using this login ID: Syntax
>>-VIRTUALNodename- nodename-----------------------------------><
You will also need to change the tsmasr.cmd file to ensure that the restore commands point to the correct file spaces for the machine that you are restoring. Here is an example of a TSMASR.CMD file, which restores the nodename IBM-JAMES. Each occurrence of this node name has to be altered to the node name required for the machine restore:
@start "IBM Tivoli Storage Manager" /MIN cmd.exe @echo off @title IBM Tivoli Storage Manager @echo Windows ASR is installing TSM. Please wait for installation to complete. %SystemRoot%\temp\tsmcli.exe -s -e setup.exe -a /s /v"INSTALLDIR=\"%SystemRoot%\temp\~tsmasr\" ADDLOCAL=\"Client\" TRANSFORM=\"C:\tsm_images\TSM_BA_CLIENT\1033.mst\" /qn /l*v \"C:\WINDOWS\repair\tsmasrsetup.log\" RebootYesNo=\"No\" REBOOT=\"Suppress\" ALLUSERS=1 " %SystemRoot%\temp\waitforevent.exe 600 Diagnostics REM pause pushd %SystemRoot%\temp\~tsmasr\baclient copy %SystemRoot%\temp\tsmasr.opt >nul @echo Do you wish to perform Automated Service Recovery (ASR) restore from the TSM server or from a local backup set? @echo 1. Restore from the TSM server. @echo 2. Restore from a local backup set. :choice set /P CH= if /I "%CH%"=="1" goto NETWORK if /I "%CH%"=="2" goto BACKUPSET goto choice
59
:NETWORK dsmc restore \\IBM-JAMES\C$\ C:\ -subdir=yes -preservepath=complete -replace=all -tapeprompt=no -nodename=IBM-JAMES -optfile=tsmasr.opt dsmc restore systemstate -asrmode=yes -nodename=IBM-JAMES -computername=IBM-JAMES -optfile=tsmasr.opt dsmc restore systemservices -asrmode=yes -nodename=IBM-JAMES -computername=IBM-JAMES -optfile=tsmasr.opt REM Diagnostics dsmc query backup \\ibm-james\c$\WINDOWS\repair\*.asr -asrmode=yes -nodename=IBM-JAMES -optfile=tsmasr.opt >tsmasrdiag.txt REM dsmc query backup \\ibm-james\c$\WINDOWS\repair\*.asr -asrmode=yes -nodename=IBM-JAMES -optfile=tsmasr.opt >a:\tsmasrdiag.txt @GOTO DONE :BACKUPSET dsmc restore backupset TSMASR \\IBM-JAMES\C$\ C:\ -asrmode=yes -subdir=yes -preservepath=complete -replace=all -tapeprompt=no -nodename=IBM-JAMES -location=file -optfile=tsmasr.opt dsmc restore backupset TSMASR systemstate -asrmode=yes -nodename=IBM-JAMES -location=file -replace=all -computername=IBM-JAMES -optfile=tsmasr.opt dsmc restore backupset TSMASR systemservices -asrmode=yes -nodename=IBM-JAMES -location=file -replace=all -computername=IBM-JAMES -optfile=tsmasr.opt :DONE @echo on
60
Appendix A.
Slipstreaming Windows XP Service Pack 1a

In this appendix we will discuss the creation of a Windows SP1a bootable CD from your original Windows XP CD, and the Service Pack (SP1a) available on the Microsoft Web site. Slipstreaming a Service Pack is the process utilized to integrate the Service Pack into the installation, so that with every new installation the operating system and Service Pack are installed at the same time.
61
Slipstreaming
Slipstreaming is usually done on network shares or corporate systems. But with the advent of CD burners, it does actually make some sense for the home user or small business user to do the same. Microsoft added the ability to Slipstream a Service Pack to Windows 2000 and Windows XP. It not only has the advantage that when you (re)install your OS, you do not have to apply the Service Pack later, also, if you update any Windows component later, you will be sure that you get the correct installation files if Windows needs any.
Slipstream Windows XP Service Pack 1a

Copy and update the XP files
Download the (full) Network Install of the Service Pack (English version [125 MB]), and save it to a directory on your hard drive. Other languages can be downloaded from the Windows XP Web site. Microsoft recently released Windows XP SP1a. The only difference is that this Service Pack does no longer include Microsofts dated Java version. If you have already installed Windows XP SP1, there is no reason to install SP1a, but the older SP1 (with MS Java) is no longer available for download. Next, copy your Windows XP CD to your hard drive. Just create another folder and copy all the contents of your Windows XP CD in that folder. Now create a third folder to hold the Service Pack 1a (SP1a) files you are about to extract. Next, open a Command Prompt (Start -> Run -> cmd), and go to the folder where you downloaded SP1a. Type the command: servicepack filename -x. A small window will appear, and you need to point it to the folder where you want to extract the SP1 files. Click OK to start extracting the SP1a files.
Figure 3-31 Choose directory for extracted files
Once the SP1a files are extracted, change to the update folder of the SP1a files (cd update), and type the following command: update /s:path to WinXP CD files. In my example, the command is update /s:F:\WinXP-CD).
62
Figure 3-32 update command
Windows XP Update will update the files in the target directory F:\WinXP-CD.
Figure 3-33 Windows updating the XP directory with SP1a files
When ready, you will get a confirmation. Windows XP Service Pack 1a has now been Slipstreamed into your original Windows XP files.
Figure 3-34 Integrated XP install complete
Creating a bootable CD
There are many products on the market, which can be used to create a bootable CD. It is not our intention to go through the steps on any of these products, you will need to choose your own software package for this. There are, however, a couple of important things that should be taken into consideration when doing this exercise: Ensure that you choose the settings that will allow the CD to be a bootable CD. Keep the Volume Label the same as on your original Windows XP CD. Also remember, take a backup...please.
Appendix A. Slipstreaming Windows XP Service Pack 1a
63
64
Back cover
IBM Tivoli Storage Manager: Bare Machine Recovery for Microsoft Windows 2003 and XP
Use built-in APIs provided by Microsoft Windows to protect your system See how Windows ASR integrates with ITSM Learn how to configure your system for recovery
This Redpaper describes the use of IBM Tivoli Storage Manager (ITSM) V5.2 or above to perform Bare Machine Recovery of Windows XP and 2003 utilizing built-in APIs. Microsoft Windows provides an Automated System Recovery process for XP and 2003, and this process can be closely linked to IBM Tivoli Storage Manager to provide a straight-forward CD driven methodology to recover from catastrophic server failure. In this paper, we describe the steps to set up your systems to prepare for system recovery, and show examples of actual recovery scenarios.
Redpaper
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.
For more information: ibm.com/redbooks

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

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

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

Încărcat de

Drepturi de autor:

Formate disponibile

Front cover

Barry Kadleck David McFarlane Pracha Pechsuksan Wah Han Tan

Copyright IBM Corp. 2003. All rights reserved.

IBM Tivoli Storage Manager: Bare Metal Restore for Windows

Copyright IBM Corp. 2003. All rights reserved.

IBM Tivoli Storage Manager: Bare Metal Restore for Windows

The team that wrote this Redpaper

Become a published author

Send your comments in an Internet note to:

IBM Tivoli Storage Manager: Bare Metal Restore for Windows

Copyright IBM Corp. 2003. All rights reserved.

1.1 IBM Tivoli Storage Manager concepts