Moving W2k3 File Server to new hardware and keeping the same name

[mofusjtf]

I have a W2k3 file server running DNS (no AD, only DNS) that is constantly running out of space. I have an avaialble server not in use with more than double the storage space available. The current FS and the available server are both identical hardware with different size hard drives. I would configure a RAID 5 to maximize storage capacity. The current FS is also a RAID 5 (Data Storage) and RAID 1 (OS Drive). There are some OS misconfiguration issues that I don't want to replicate on the new server so an IMAGE is out. What is the best way to go about moving the role of a FS to new hardware and keep the same machine name?

 

[pgaliardo]

Not sure what you are using as a backup solution. We use Symantec Backup Exec and to do this we would configure the new server with the RAID cofiguration that you wish, install Windows 2003, install Backup Exec, then do a full restore of all partitions and the system state. This should work fine especially if the hardware is similar. This would restore the file server with the same name, etc. but will allow you to configure the hard drives the way you want.

Symantec has complete directions for restoring a Windows Server on it's website. Again, not sure what backup solution you are using.

 

[mrdenny]

Upgrading a file server is pretty easy. I assume that you want to keep the old box as a DNS server.

Ahead of time
1. Send out an email saying that all files must be closed by X time on the day of the upgrade. (Send a lot of these emails to get the point across.)
2. Install Windows on the new machine. Give it a temp name.

Upgrade Day
1. Rename the old machine to it's new name.
2. Rename the new machine to it's new name (the old machines name).
3. Use robocopy to copy over all the files and NTFS permissions. (Your backup and recovery software will work fine for this as well.)
4. Setup the network shares.
5. Send out an email saying that all is done.

If you want to move the DNS server as well, the new machine needs to have the IP address of the old machine as well as have the zone files restored to it.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[mofusjtf]

Thanks for the prompt feedback.

We use backup exec on a dedicated backup server. Thus I would just install the remote agent for BE and restore via the network.

So it would go as follows?
1. confgure RAID
2. Install W2k3
a. Give system temp name
b. Join Domain
3. Install BE Remote AGent
4. Restore from tape
a. Files & System State

This will resotre the machine name and all the other settings for network sharing, file services, DNS, etc.?

 

[pgaliardo]

Don't join the domain. The restore will do that. Check out the following. I know it says Windows 2000, but I've used it for Windows Server 2003.

http://seer.entsupport.symantec.com/docs/236286.htm