• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 192
  • Last Modified:

Moving Win2000 server (non Raid) to different server hardware with Raid

Here's our scenario, and I'd greatly appreciate any feedback or better methodologies:

We need to take an existing Win2k server (DC) with term services and financial DB on
it, (non SQL based) and essentially "image"  that intact to a new IBM server

This is a small business, so we can take them off the network after 4 pm.
The existing Dell was poorly built, no raid, volumes too small, etc.

The *Old server*
Dell 2600 series tower, 2 scsi drives, Win2k server SP4, * no raid*
C, D, and F drives locally.
We plan on using Backup Exec 10, to backup completely to new external AIT tape drive.

+New Server+
IBM X series 236 server with 6M raid card, 3 73 gig scsi drives & hot spare
Identical drive containers built on  the box before installation of OS takes place.
Will be same version of  win2k, SP4
(With a 2nd identical scsi card for the external  tape drive for restoring)

Procedure that I have in mind:
Install Win2k, SP4 server on new IBM server box to *temp* (as in \\2ktemp)  directory, local install only,
standalone server.  Create same logical volumes, C, D, and F as original box,
Make 2k  boot floppy with original boot.ini
Copy IBM raid driver including oem.inf file to boot floppy and to \temp
Copy IBM hal version from \winnt\system32  to \temp directory to have on hand.
copy native Nic drivers to \temp directory
Follow Backup exec standard procedure to restore data,   system state, etc
from AIT external tape drive

Once restored, boot first into local mode \2ktemp version from floppy, and
Copy scsi driver for new IBM raid card into \\winnt\system32\drivers
copy hal*.dll  version from the temp  installation   to \winnt\system32
Boot from Win2k server CD, press F6, and feed it the raid driver from floppy.
Choose to repair the restored install in C:\winnt
If necessary, use the Win2k server CD to boot  and use repair options
to let setup refresh  the  computer's hardware (including HAL) and perform an in-place upgrade while maintaining programs
and user settings. .

References for repairs I've used in the past, but have had mixed results using



Lastly, it would be great if someone has done this exact task, hands on,
and would write up a step by step for how to deal with possible issues
that will arise after a restore of this kind from tape.


1 Solution
Leandro IaconoSenior Premier Field EngineerCommented:
I think what you are doing is correct mate. I do not have much experience but it's exactly what you should do. I don't think your missing anything.

In any way, I am posting this as too follow up this post, because it's interesting to see how everything turns out.
LexjkAuthor Commented:
Thanks UICE, we'll be swapping servers tomorrow, April 18th, and I'll post results.
Leandro IaconoSenior Premier Field EngineerCommented:
Thanks mate. Really looking forward to see the results :D
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

LexjkAuthor Commented:
We were unable to build server on the 18th, due to wrong raid cables being shipped.
Leandro IaconoSenior Premier Field EngineerCommented:
I hate when that happens.

I'll be looking forward to know how everything turns out in the future mate. If posible please post ...

Thanks ...

I have moved Win2k AD machines to new hardware before (for DR test purposes) and used a similar methodology to the above.

The key I have found is when you use the in place repair of Win2k make sure you use the second repair option - ie chose install first, then when the CD finds a copy of Windows it will give you the option to repair.

I too would be interested to see how this shapes up.

LexjkAuthor Commented:
As often happens in IT work, the actual build for this server swap out took a different course.
We decided that due to the complexity of the raid, and other factors, we would do a clean install on the new IBM box.
In the long run, it's probably a better option, as there were issues with backup exec on the new server,
freezing Windows  at logout/reboot. Plus networking was not working right after BE 10 install.
Had to actually uninstall BE 10, and use the old server to keep the backup running for other servers
LexjkAuthor Commented:
Thanks RodLab and Uice, for your interest in this topic.
Leandro IaconoSenior Premier Field EngineerCommented:
Nooo .. thanks to you my friends ...
A request has been made to close this question.

Could Experts please leave their thoughts on the disposition of this question here.  If there are no objections in the next 4 days,  this Question will be finalised as follows:


Page Editor Windows Server 2003.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now