Thanks for your response. My problem is not boot.ini, but a registry setting that points to the old partition or possibly a driver issue...
Matt -----Original Message----- From: Michael Swinhoe [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 9:53 AM To: [EMAIL PROTECTED] Subject: Re: Suggestions for W2K recovery I use ERD Commander to manipulate/change the boot.ini file after the restore has been completed on the W2K server. Regards, Michael Swinhoe Storage Management Group Zurich Financial Services E-mail: mailto:[EMAIL PROTECTED] "Adams, Matt (US - To: [EMAIL PROTECTED] Hermitage)" cc: <[EMAIL PROTECTED] Subject: Re: Suggestions for W2K recovery ITTE.COM> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 04/09/2003 04:21 Please respond to "ADSM: Dist Stor Manager" Thanks for the reply, and your right it is not boot.ini But there has got to be a way around this. I did another test using ntbackup to restore the registry instead of TSM. The boot problem did not return. I have a dump of the registy both pre and post restore. I hope I can get MS or Tivoli to look at. -----Original Message----- From: Christian Svensson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2003 5:14 PM To: [EMAIL PROTECTED] Subject: Sv: Suggestions for W2K recovery Hi Matt! There is no problem with your boot.ini file. The problem is the Windows Registry. The boot device drivers in the registry point on one driver and the new Server use a newer or another driver to boot up your disk controller card. When you restore your files/images to a new hardware you need to be sure that the drivers who installed on the orginal machine is the same as new new one. There is only one way to sold your problem right now. That is to install the new drivers on the orginal machine and then backit up and restore it to the new machine. But we have a group at Cristie Data Products who looking to sold this kind of problem when you clone system or run a Disaster Recovery on new hardware. Good luck Christian ============================================================ Från: "Adams, Matt (US - Hermitage)" <[EMAIL PROTECTED]> Datum: 2003/09/03 Wed PM 04:52:42 CEST Till: [EMAIL PROTECTED] Ämne: Suggestions for W2K recovery All, I am looking for some suggestions on the best way to handle a W2K recovery to different hardware. It is not so much the different hardware I am battling, it is boot.ini. I am trying to find out at what point boot.ini gets put into place from the restored server. The current (old) server has the Compaq boot partition therefore the boot.ini looks like this: [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(2)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Server" /fastdetect C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows 2000 Recovery Console" /cmdcons The new server will not have that seperate Compaq/HP boot partition and should look like this: [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Server" /fastdetect I checked boot.ini both before and after the C: and System State restores. It remained the same, so I am assuming that at some point during the boot is when the old boot.ini gets put into place and causes the new server to come up with a BSOD for "Inaccessable Boot Device" Thoughts or suggestions? Regards, Matt This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ============================================================ This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ___________________________________________________________________________ The information contained in this message is confidential and may be legally privileged. If you are not the intended recipient, please do not read, copy or otherwise use it and do not disclose it to anyone else. Please notify the sender of the delivery error and then delete the message from your system. Any views or opinions expressed in this email are those of the author only. Communications will be monitored regularly to improve our service and for security and regulatory purposes. Thank you for your assistance. ___________________________________________________________________________ This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
