• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

help restoring 2k3 SBS to different hardware

skyking

skyking

Lifer
Original server has become unusable. It is a motherboard or other problem and I don't have another like it.
I have backups of system state, C:, and exchange on an external hard drive.
I tried doing a bare install of 2k3 on the replacement and restore, but that broke windows to a loop reboot condition.
In the Microsoft KB articles, they assume you are working with a functional "old" server.
Any ideas? I am on my own for a while on this one, so don't bother suggesting taking it to a "pro" first.
 
I have not done this on SBS.... but I would assume it is the same as any other domain controller / Exchange restore.

Install SBS / give it the same IP / Name... Restore the files. On 2k3 you reboot in to AD recovery mode and push the system state, maybe exchange at the same time.

*My raw server Exchange recovery experience is limited

I normally do files and security first because the system state will try to restore the file shares in the registry which gets wacky if the files are missing.

Files > AD > Exchange I would think for SBS at least.

-edit- noted the reboot thing

Before you restore a system state, you need to make sure to install all the apps and services. Since it is a solo DC you may need to set up AD with the old domain name, make sure daemons like DNS etc are there and ready. You may need to run the Exchange install process (pretty sure SBS doesn't preinstall it, again been a real long time...) Make sure the disk structure is the same. If the old machine had "C Q S" as internal HDDs, your replacement will need to have "C Q S" etc.

Pretty sure it is not officially supported. The reboot loop is likely registry issues and a missing driver for the boot disk. System state restores the old systems registry which may not include the driver that the new system needs.

MS posted this:

Restoring Your Server

After a system failure or other disaster, you can restore your server from your latest successful backup. In the event of a software failure, you can restore to the same computer or you can restore to new hardware. You can also restore individual files and e-mail messages if they were permanently deleted.

WARNING: If you are restoring to a different computer than that which was originally running Windows Small Business Server 2003, make sure that the following items are the same on the original and the new computer:

*

SCSI controller. You can restore to a computer that has an IDE controller if the original computer had SCSI.
*

Motherboard chip set.
*

Number of processors.
*

Hard disk size. The new computer's hard disk should contain matching volumes the same size or larger than those on the original computer.
*

Drive letter of the boot partition.

We recommend restoring to the same brand and model of the original computer.
 
Last edited:
Thank you. Yes, the MS articles basically state I'm out of luck, with different chipset, SATA controller, etc. I know there has to be a way to get it going.
 
Checked ebay for a similar motherboard? If it's a whitebox server you should be able to find the same motherboard or one with the same chipset at least.

Once you get it running, you should use a backup program that supports bare metal restores to different hardware, such as Acronis. Then restore to a newer server (HP or Dell) that has an active support contract so you don't have to worry about this happening again for another 5 or 6 years. 😀
 
Last edited:
If I can get it going again, it will get upgraded to new hardware and new server software. Sheesh what a hassle.
 
skyking said:
If I can get it going again, it will get upgraded to new hardware and new server software. Sheesh what a hassle.
Click to expand...

This is true on many versions of Windows. You get what you pay for. The company might think they want the "one magic box" and go with it because it is cheap. There is a reason it generally better to have 2 servers or a support contract.

What you are listing is the prime reason I say Dell/HP servers > Whitebox / random. Even a decade later there are parts on Ebay for them.
 
EVEN If you want a single SBS server, the cost of spare hardware is nothing. knowing what I learned these past 3 days, I would always have spare hardware.
 
Thank you Jack. Does it need to be resident and installed ahead of time, or can you purchase it after the lightning strikes?
 
It depends on the status of the HD and its content.

If it did not get corrupt in the crash then this process should work.

Hook the old HD to a new computer. Do not run it so it will not get trashed by the new chipset.

Boot the new computer (with the old HD) from the Acronis Boot disk.

The Boot disk would sense the NIC and a Network, or an Extrenal USB drive, if one is hooked directly to the computer.

Backup the Drive in normal mode to the space of your choice.

Keep the old HD on the side until the ordeal is over.

Boot the new Server with a clean new HD on it and Recover back the Backup using the Universal Restore option (it might be that they changed the name to something like Dissimilar hardware).

If every thing went OK you should have a basic server running. If the OS does not have the final Drivers, it can be installed at this point.

I have very high success with this process, however YMMV depending on your specific situation.

😎
 
Update:
I was able to get the box up on the original motherboard, with a new PS, reduced ram and a different drive. I had to do a fresh install, update , restore broke it again, did a repair install and updated again, restored the exchange files. The mobo still has some flakiness.
New 2008 server is on the way! I told them to get two while they were at it😀
 
Grats, that is the best way to do it. It is a major pain to restore other hardware. The best luck I have is with a separate SCSI card so I can move it to another machine if I really have to attempt this adventure. That seems to be the largest issue as you have seen by the cycling reboots.
 
We are getting two dells and one set of 2008 SBS. If the crap hits the fan, we can get them going on the spare hardware.
 
Install SBS within a virtual machine. Then, switching hardware a simply a matter of copying the virtual disk from one computer to another. You can even run it on a desktop machine in a pinch.

Unless you're running something that has special requirements (needs to interface with a particular hardware device, or requires substantial processor resources), there's no reason not to use a virtual machine these days.
 
If you just purchase the warranty you don't need to buy two servers. You can get 5 years on Dell poweredge and that should be plenty.
 
theevilsharpie said:
Install SBS within a virtual machine. Then, switching hardware a simply a matter of copying the virtual disk from one computer to another. You can even run it on a desktop machine in a pinch.

Unless you're running something that has special requirements (needs to interface with a particular hardware device, or requires substantial processor resources), there's no reason not to use a virtual machine these days.
Click to expand...
how does licensing work on something like that? A virtual hardware signature for Microsoft?

aE0n said:
If you just purchase the warranty you don't need to buy two servers. You can get 5 years on Dell poweredge and that should be plenty.
Click to expand...

I want to avoid any downtime.
 
I've not messed with virtual machines. When you move to new hardware with an MS operating system, it requires a re-activation in most cases. I wondered how moving the virtual disk to a different server would work.
 
skyking said:
I've not messed with virtual machines. When you move to new hardware with an MS operating system, it requires a re-activation in most cases. I wondered how moving the virtual disk to a different server would work.
Click to expand...

The only change the virtual machine would notice is a different processor type, if the new server has a different processor. That shouldn't trigger a re-activation.
 
Thanks, that would be a huge piece of mind for me and them. What OS would you use for the server? I am not an MS server guy if you did not already figure that out. I much prefer Debian or some other distro similar to it.
 
Time to read these technet pages on SBS 2008 and Hyper-V.

http://technet.microsoft.com/en-us/library/dd239207%28WS.10%29.aspx

Even with the standard version of SBS 2008, you are allowed to install on top of Hyper-V. This should negate the need for purchasing 2 servers as you can simply set aside an old desktop (or two - just in case) with hyper-v installed to use in the event the production server will be down for any period of time.
 
Lifted said:
Time to read these technet pages on SBS 2008 and Hyper-V.

http://technet.microsoft.com/en-us/library/dd239207%28WS.10%29.aspx

Even with the standard version of SBS 2008, you are allowed to install on top of Hyper-V. This should negate the need for purchasing 2 servers as you can simply set aside an old desktop (or two - just in case) with hyper-v installed to use in the event the production server will be down for any period of time.
Click to expand...

Assuming the server isn't down because of lost disk etc. Personally 2 servers really is better than one. I don't know how SBS works with AD but having two AD servers and 2 DNS will make any AD users life much better over all, even installed in Hyper-V / ESXi. PS I prefer ESXi still at this point. Hyper-V is getting there but has a ways to go.
 
imagoon said:
Assuming the server isn't down because of lost disk etc. Personally 2 servers really is better than one. I don't know how SBS works with AD but having two AD servers and 2 DNS will make any AD users life much better over all, even installed in Hyper-V / ESXi. PS I prefer ESXi still at this point. Hyper-V is getting there but has a ways to go.
Click to expand...

Agreed, but that would require another windows license or the purchase of SBS premium which includes a second Windows server license. I don't think he was looking to go that route though. I got the impression the second server was going to be sitting in a closet as a spare in case the primary server has hardware issues. With the SBS server being down, the only benefit a second DC/DNS server will offer is DNS, and enabling DHCP on the router should take care of that.
 
Lifted said:
enabling DHCP on the router should take care of that.
Click to expand...

That is a bad idea actually. DHCP should be hosted on Windows otherwise things like registered DNS and the like *may fail.*

I also have noticed that certain routers don't handle redundant DHCP as well as they should.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top