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.

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.

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.

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.

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

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