Migrate main DC and file server to new hardware

[kulvinder]

I currently have a win 2000 server which is a domain controler and dns server and is used as our main file server. I have a new server that I want to replace our current one with.

What is the best way to tackle this bearing in mind that the new server needs the same network/domain settings so that user shares remain intact.

I have heard that a product like 'Ghost' can be used or is it just as easy to remove the old server from the domain and the network and then add the new one with the same name and ip addresses? Any help/advise/experices would be greatly appreciated.

 

[Jpoandl]

There are many different ways to do this. The most difficult part is making sure that the server will boot once your move the data.

If you can, the easiest thing is to make sure that you move to a similar RAID/SCSI controller. For example, if you are using RAID on your server. Try to see if you can use the same controller on the new server. (Pull out the RAID card on the old server and move it to the new server). This will garrentee that the servers boot process will remain the same. Or, for example, if your source and destination servers are both Compaq (and your know the RAID cards are compatible), just simply move the hard drives to the new server.

However, if you do not have similar hardware, the task is much more difficult. Again, the most complicated part is getting the server to boot on the new hardware.

I've performed this a few times but it requires some testing and planning. Basically, I backed up the server using NTbackup (turn all services off ..including AD). Then I installed the same OS on the new server with the same Service pack. Then restore the entire backup tape on the new server (There are some options that will let you skip overwritting BOOT drivers) Then boot the system...

As far as using Ghost, I don't know...Probably will work if your boot drivers can get updated before the Os comes online for the first time...

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[kulvinder]

Thanks for the responce. The hardware on both servers is completely different and backup devices are different as well. I have done a disaster recovery restore to the same server using the method you described above and it worked quite well, but not to different hdware.

Is it therefore feasable to demote current server from being a domain controller and then remove from the domian. Add the new server and promote to to domain controller. The shares are essentially quite easy to setup so as long as the server name is the same then existing shares on peoples machines should be ok - is that right? I'm guessing this would be 'cleaner' although longer than the other option.

Thanks agian for your help/advise.

 

[Claudek]

Any ideas why something like this wouldn't work:
* Install Windows 2000 on the new server and dcpromo it to join current domain. This ensures you have a Active Directory replication happening.
* Install DNS and change your DNS to Active-Directory integrated. This way both servers are of "equal level" in resolving DNS queries.
* Copy across all the data using Restore or Robocopy with the security and timestamp options. Once the main copy is done, keep the data synchronised by using robocopy with the /XO option (The /MIR is an option as well but I prefer /XO which only copies across files that are new or have been modified)
* Create the shares the same way as in the 1st DC
* Create Printers the same as in the 1st DC
* Seize all the FSMO roles. Make sure the New server is also a GC.
* Demote the 1st DC and disconnect it from the network.
* IN DNS remove the A record for the 1st DC. Create a CNAME record with the old Servers name and point it to the Ip of the new server (Now if someone tries to connect to //oldserver/share for eg, it will resolve to the new server.
* Change DHCP to have the gateway IP to the new server (while references to the old server by name should be fine, any direct references to the IP address may be an issue)


You may have other clean up tasks after this but the above is an interesting way to get this done with minimum fuss.



Claudius (What certifications??)

http://www.iteq.com.au

 

[kulvinder]

Thanks again - Thats an interesting way of doing it. Whichever way I decide is going to involve more testing so I'd best get on with it.