File Recovery. Simply put, if you use Windows XP or later, Recuva will work for you. Tablet Edition, Media Centre Edition, 64-bit); Windows 2003 Server.
Server 2003 system restore overview
During the daily use of Windows Server 2003, we can't avoid the disaster. The operating system may crash because of Hardware conflict, Bad Ram, hard disk drives overload, viruses attack, software conflict, power supply problems. But if you have backed up the system before, it is not a problem.
You can easily restore Server 2003 system from the backup file. In this page, we will introduce you how to restore Windows Server 2003 using System Restore and EaseUS Server backup software. You can try these two Server 2003 systems restore solutions to protect your system and data from unexpected disaster.
Server 2003 system restore via System Restore
Windows 2003 does not come with an automatic system restore feature like XP, Vista and 7 do. Because of this, a system operating with Windows 2003 does not automatically create a restore point for the computer's current state. That means that a user cannot return the computer to that state at a later date. One option to work around this is to download System Restore. However, a second option involves manually creating a restore point for the computer's current state using Windows 2003's System State.
1. Find and click the 'Start' button, then highlight 'All Programs' from the Start menu.
2. Highlight 'System Tools' from the All Programs menu and select 'Backup.'
3. Select the 'Advanced Mode' link from Backup, then click the 'Restore and Manage Media' tab.
4. Check the box next to the 'System State' option.
Restore Server 2003 system with EaseUS Server backup software
EaseUS Server backup software is a reliable Windows Server backup & disaster recovery, system migration solutions for both physical and virtual Windows Server 2003/2008/2012. With powerful backup capacity and advanced backup & recovery features, the program will simplify both basic and advanced server backup & recovery management while minimizing server downtime as well as ensuring business continuity. So if your Server 2003 crashed, you can use this tool to rebuild the system easily from the previous backup image.
1. Create a bootable CD/DVD. (For detail steps, please refer to How to create a bootable disk?)
2. Follow the wizard to do Windows Server 2003 restore.
I have a user that has a Windows 2003 Server. Unfortunately he did not install the software on it nor does he know how it was configured. He is worried that it will fail and leave his clients without service. I was thinking instead of trying to guess all of this info is it possible to image the old hardware and then put this image on different hardware.
I am aware there will be diferences that need to be taken into consideration (I.e. Drivers , CPU, etc) but is there not a way to incorporate that somehow?
Hopefully there is a free / near free solution for this?
Thanks
5 Answers
Move the hard drive to the new Server (make a backup image of this drive before you do), or
Image the old hard drive to the new hard drive in the new server
Then, before you ever boot into windows on the new Server:
scroll down to 'replace a failed motherboard' follow the instructions.
You will need to use a Windows 2003 install disk of the same version and Service Pack level to do the repair.
Here is a free disk imaging programhttp://www.macrium.com/reflectfree.asp
.
Again it's not Free but Acronis Backup & Recovery is fantastic for this. I have used it moving many servers to new hardware. Also to do offsite app testing, upgrade testing etc. It can do a lot more too so worth looking at. Although the price could be a factor, its not cheap.
Not free but it works and will save you serious grief. What is the cost if the server fails? Backup Exec System Recovery works very well for taking an image and restoring to different hardware. Have used it many times without issues. There is a demo located at BESR2010
After doing the disk imaging, recommend to him that he migrate the at-risk server to a virtual machine on a VMWare Server or some other product. He'll save on power, rack/floor space, and if he ever needs to move it again, its elementary. Its a good solution for customers with several older at-risk systems set up by vendors that have since vanished.
I've moved severs to virtual hardware without a problem, which is nice to have as a backup solution for if the real server fails. Sysprep and vmware converter have worked fine.
Also, shouldn't this be on Serverfault?