Article ID: 241871
Article Last Modified on 1/25/2005
APPLIES TO
- Microsoft BackOffice Small Business Server 4.0
- Microsoft BackOffice Small Business Server 4.0a
- Microsoft BackOffice Small Business Server 4.5
This article was previously published under Q241871
SUMMARY
The information in this article is designed to help you move a hard disk or tape backup to a computer with drastically different hardware, in the event of a major component failure on the existing production server.
MORE INFORMATION
The procedure outlined in this article is not the preferred method of restoring a server. It is provided only as reference for a possible disaster recovery scenario. In addition, this procedure is not recommended by Microsoft and, therefore, is not supported. Microsoft makes no warranty, implied or otherwise, regarding the performance, stability, or reliability of this procedure.
It is essential to plan for disaster recovery before it actually occurs. To increase your chances of recovery, use the following procedures before a disaster happens.
Planning
- Check the event logs on a regular basis. A regular check of the event logs can alert you to problems before they become severe. Correct problems as they occur and then back up the computer afterwards.
- Create a backup strategy. Nothing provides better recoverability than a good tape backup. Fault tolerant disk setups and imaging are also good solutions. If you create a tape backup and store the tape off-site, however, you have a better chance for recovery if the physical location of your server is damaged.
- Practice restoring the backup quarterly (or at least twice a year).
Steps to Perform Before Moving to New Hardware
- Clean up the event log.
Monitor the event log and clear up any red events. If any yellow warning events exist, determine if they could interfere with a restore to different hardware.
- Update the Emergency Repair Disk (ERD) and repair directory.
You can run the rdisk /s command to update the ERD and write critical information to the repair directory.
- Perform a full tape backup (including the registry).
Back up everything that pertains to the operating system and services. You must also back up the registry.
- Disable virus scanner software.
Before you disable virus scanner software, scan the disks or CD-ROMs on which your third-party drivers are stored.
- Disable third-party services.
This includes virus scanners, UPS software, remote administration programs, and tape backup software (you have already made the tape back up above)
- Remove existing video drivers.
Unless the new computer has the exact same video card, there could be enough of a difference in the hardware that the existing driver could generate an unrecoverable STOP error message. Remove the existing video driver, load the standard VGA driver, and set it to 16 colors (640x480).
- Install the hard disk controller driver.
Preload the hard disk controller that exists on the new computer. If you currently use IDE and the new system is SCSI, restoring a tape with only IDE drivers leaves the computer unbootable. The same applies if you are moving from SCSI to IDE. You may have to physically place the drive controller into the existing computer to load the driver. This is obviously not possible in situations where the controller is integrated.
- Remove the SCSI hard disk controller driver.
If the new computer does not have the same SCSI controller (or none at all), when you attempt to initialize the SCSI driver you may receive an unrecoverable STOP error message.
NOTE: You can usually leave IDE drivers in place, which only generates a STOP event in the event log.
- Install Microsoft Loopback.
This is in preparation to remove the existing network adapter. This gives the protocols something to bind to and the protocols and protocol-dependent services do not have to be reloaded after the restore.
- Remove the network adapter driver.
Unless the new computer has the exact same network adapter, there may be enough of a difference in the hardware that the existing driver could generate an unrecoverable STOP error message.
- Remove the sound card driver.
Unless the new computer has the exact same sound card, there may be enough of a difference in the hardware that the existing driver could generate an unrecoverable STOP error message.
- Remove any drivers for hardware that do not exist on the new computer.
Do not attempt to initialize drivers for non-existent hardware on the new computer. This may cause unrecoverable STOP error messages, as well as device driver conflicts.
Restore Options
Only perform the following restore options if you have completed all of the steps outlined above.
Option 1 (Preferred)
This solution leaves your existing server in place in the event you cannot restore the tape to the new hardware.
- Reload the tape backup software and make a new, separate tape backup of the existing computer.
- Restore the tape to the new computer.
- Load device drivers for the hardware on the new computer.
- Verify that the computer is functioning properly.
- Make a separate tape backup of the new computer.
Option 2
This solution moves the existing hard disk to the new computer and then changes the working system. Although this is a quicker solution, it is less desirable because the original drive is modified.
NOTE: A full tape backup as detailed above is critical if you use this option.
- Move the hard disk to a new computer.
- Start the computer and verify that the drive letter mappings are the same.
- Load device drivers for hardware on the new computer.
- Update the page file if the physical RAM has changed.
- Verify that the computer is functioning properly.
- Make a separate tape backup of the new computer.
REFERENCES
For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:
130928 Restoring a Backup of Windows NT to Another Computer
139822 How to Restore a Backup to Computer with Different Hardware
228980 Upgrading from SBS 4.0 to SBS 4.5 When Migrating from One Computer to Another
Additional query words: smallbiz migrate migration SBS sbs45 recovery SBSbestpractices
Keywords: kbinfo kbhardware kbenv KB241871
