Joe, We ran into this before. To start of with an important notice. Microsoft does not support this, and claims it is not possible to restore to different hardware. Having that said, i also want to mention that we do a periodical test at a disaster recovery site. At this site we do not have identical hardware, if possible at all.
Note: When restoring on a server using a separate partition or install directory, copy the boot.ini so you can edit it after the restore, making it matching for the installed OS and the restored one. If the restored OS does not boot, you can select the recovery OS in the boot.ini to boot to the recovery OS and try some more actions. One option is: Find out witch dll's represent the drivers for the installed hardware on the recovery machine. The one you installed the restore OS on. Restore the entire OS using a separate install directory or partition. Select the driver-dll's and overwrite the restored ones in the restored OS. Mostly these are drivers for the diskarray's. Try to use somewhat similar NIC's when doing this. This seems simple, but will be quite a hassle if it turns out to be the wrong driver. Our NT-admins tried this, and had it working in several occasions. THIS IS VERY HARDWARE DEPENDANT! The other option is: At our DR site this is the prefered method. Again, install a recovery OS on a separate partion, or in a separate directory. Restore the entire OS. Preserve the installed boot.ini. Reboot after the restore, but make sure it boots in setup mode, with the NT setup CD-rom in the drive. Select and perform the upgrade option in the setup menu. To get the upgrade option, the boot.ini should be at its original location, so i'm told. After the upgrade you can reboot, and run your prefered SP update. THIS IS LESS HARDWARE DEPENDANT! The second option is more work, but proved to be the more reliable one. Again, it is not supported by anyone. I hope your business continuity does not rely on this. GOOD LUCK. Ilja G. Coolen _____ ABP / USZO CIS / BS / TB / Storage Management Telefoon : +31(0)45 579 7938 Fax : +31(0)45 579 3990 Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Intranet : Storage Web <http://intranet/cis_bstb/html_content/sm/index_sm.htm> _____ - Everybody has a photographic memory, some just don't have film. - -----Oorspronkelijk bericht----- Van: Joe Cascanette [mailto:[EMAIL PROTECTED]] Verzonden: vrijdag 8 februari 2002 16:13 Aan: [EMAIL PROTECTED] Onderwerp: Re: Testing A WIN2k Server restore What happens when the hardware is different then the server restoring. Has anyone run into this?. I have playing with the Win2000 registry to find all the hardware items (so I can delete the key after restoring the registry and add the hardware key for the server we are using), but still no luck. Is there any other area I need to look at? Thanks Joe Cacsanette The Cumis Group Limited -----Original Message----- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Friday, February 08, 2002 8:44 AM To: [EMAIL PROTECTED] Subject: Re: Testing A WIN2k Server restore When you register the test box to TSM you can give whatever name you like ie testbox For recovery purposes, what you can do is change the nodename in the dsm.opt file on your test machine from "testbox" to the same name as the machine you are recovering from. Then you will be able to recover to the testbox. You will not be able to do any backups/restores on your production server while your test in in progress. "Amini, Mehdi" <[EMAIL PROTECTED]> on 02/08/2002 01:16:21 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: John Naylor/HAV/SSE) Subject: Testing A WIN2k Server restore Hi All, I have finally found a server that I can do a test restore. According to the Redbook SG24-6141-00 I have to Name the computer the same as the one I am trying to recover. My problem is that the recovering Server is still in production and I would like to do a test recovery of this server. I have installed Minimum OS on this second machine, and it is in its own work Group. But when I try to name the Server the same as the recovering server, I get a message that a duplicate name found on the Network. How can I name the second server as the same as the first server and at the same time be able to see the TSM Server without connecting the our main Network? Any help would be greatly appreciated. Mehdi Amini LAN/WAN Engineer ValueOptions 3110 Fairview Park Drive Falls Church, VA 22042 Phone: 703-208-8754 Fax: 703-205-6879 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ********************************************************************** ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************
