Common errors in restore process

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.

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.

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

Chapter 3. Microsoft Windows automated system recovery with ITSM 59 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\"

@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

: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

© Copyright IBM Corp. 2003. All rights reserved. 61

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.

A

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 Microsoft’s 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).

Appendix A. Slipstreaming Windows XP Service Pack 1a 63 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.

® from around the world create timely technical information based on realistic scenarios.

Specific recommendations are provided to help you implement IT solutions more

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.

Back cover