asked on

Migrating all network services to a new server...

Hello -

Here is my issue.. I am currently running a dual P2 450mhz server for a small company. This one server is providing the followng network services to 10 people:

Windows 2000 Active Directory/DNS (AD integrated zone)
Exchange 2000
File Server
Print Server
MSFT PPTP VPN

I recently noticed the disk is starting to go bad (Many bad block and I/O errors). Unfortunately all this is running on a single 9 GB SCSI HDD with no fault tolerence at all.

So my questions are:

How do I migrate all this to a new server?
What disk configuration should I setup on the new server? (software mirror, raid 0,1,5)
Is it ok to run all these services on the same server?

I am looking for a detailed step-by-step process if possible. I also would like the new server to be a new name, but if it makes the migration more complex, I am will to keep the name the same.

Thanks,

Justin

PaulADavis

it would be simple to invest in a copy of ghost....make an image of the old disk, then restore the image to the new....

as you have seen, it's a great idea to have some sort of fault tolerance set up..... ghost could also assist you since you can use it to keep a complete image of your server.

first thing though.... get all your important files unto another disk immediately

that p2 450 is a little stressed out huh? any chance the company can spring for a new computer? :-)

ASKER CERTIFIED SOLUTION

msice

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Justin Durrant

ASKER

Thanks guys --

The PII actually doesn't run too bad.. There are only 10 people so it doesn't get hit too hard. I was considering ghost, But I am thinking it mail fail do to the disk errors.

I guess it is worth a shot though.

Anyone else?

josephcn

If you use ghost, you could always try using the -fro option when backing up. This will ignore bad sectors and backup what it can. Then after reinstalling the new hard drive, make sure to run the latest service pack for windows to verify all your system files are ok.

If you setup a new server side by side, make sure you switch the operations masters roles to the new server before turning off the old one. There are six, I think. Also switching over DNS, AD, and DHCP while the other server is on will help you unavoid any unnecessary event log errors in the feature.