The redbook was written based on the 4.1.2 client. With the 4.2.1 client, as you mentioned, you are no longer prompted with the 3 questions mentioned.
The error importing the RSM database is a bug in the client (APAR IC29545). This is supposed to be fixed in 4.2.2 and is also on the latest patches (4.2.1.15). The bypass is to exclude the RSM when restoring the System Ojbect. Then reboot and restore only the RSM. Note that the 4.2.1.0 client has a major bug for a lot of people, Scheduled events show as failed when files are in use (APAR IC31844) - also fixed in 4.2.1.15. Not sure about the IIS problems. Tim Rushforth City of Winnipeg -----Original Message----- From: Lilly, David [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 11, 2001 11:54 AM To: [EMAIL PROTECTED] Subject: Win2k Server Recovery using TSM 4.2.1.0 I am having a difficult time performing a complete recovery of a Win2k SP2 member server running IIS. I am using TSM client 4.2.1.0 (before and after) on the server. I located a Redbook, http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246141.html? Open <http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246141.html ?Open> , which was helpful, but seems to be out of date. For example, in section 6.2.3.5 Step 11, letter b. does not occur. Also, the restore does not run cleanly. I get one error, ANS1335E (Importing RSM database files failed...). In addition, the IIS services (FTP, WWW, SMTP) do not start after the reboot, Event ID 7023 An attempt was made to reference a token that does not exist. The DSM.OPT file referenced in the Redbook was used to back up the server. I have tried the Redbook procedure carefully three times without success. Is there another procedure available for recovering a Win2k server using TSM? Using TSM client 4.2.1.0? Any other suggestions? Thanks, David Lilly
