It gives us the ability to take the OS image from an existing server and restore to a completely different set of hardware.
This feature may be needed if the existing hardware is no longer good for production or it may have failed beyond recovery.
Another use we have for the HIR, is to restore a production SBS box on a dedicated Xeon 3000 box here in the shop for our Swing Migrations.
One should not expect the SBS OS to come up happy after the HIR process has finished though. Many components within the old box are no longer in existence!
There are a number of post restore steps that need to be accomplished:
- Remove the previous server's NICs in the Device Manager
- Configure the new server's NICs with the appropriate IPs and network settings
- Rerun the CEICW
- Restore the previous Drive Letter arrangement
- Restore the previous share setup (if needed)
Microsoft TCP/IPMany thanks to Chris Knight for pointing us in the right direction by commenting in a previous post SBS and Intel SE7520JR2 Warranty Replacement Experience about how to reveal hidden items in the Device Manager.
The IP address 192.168.xxx.xxx you have entered for this network adapter is already assigned to another adapter "The Previous NIC". "The Previous NIC" is hidden from the Network Connections folder because it is not physically in the computer. If the same address is assigned to both adapters and they both become active, only one of them will use this address. This may result in[sic] incorrect system configuration.
Do you want to enter a different IP address for this adapter in the list of IP addresses in the Advanced dialog box?
His comment with the methodology lead us to the following KB article: KB 31539: Device Manager does not display devices that are not connected to the Windows XP-based computer
To reveal the hidden NICs we need to get rid of:
- Start a command prompt
- set devmgr_show_nonpresent_devices=1 [Enter]
- start devmgmt.msc [Enter]
- View --> click on Show hidden devices
We right click on the old physical NIC which is greyed out and "Uninstall". Note that the Miniport will not uninstall due to services still being tied to it. We do this for any previous NICs in the old server.
Device Manager - Show hidden devices
Once we have configured the IPs, rerun the CEICW, and rebooted the server, we will be live!
Some things to keep an eye on when doing a HIR to new hardware that will go into production:
- Many new server boards do not have a parallel port on them, so one will need to remove the physical parallel port references in the registry to clear up the service did not start error associated with the Parallel Port service.
- Make sure to run the new motherboard's setup CD for drivers and monitoring software
- For Intel ProSet Adapter Teaming: Make sure to install the newest version of ProSet and validate or recreate the Team
If, however, as it is in our case, we only need the box for our SwingIt needs, we will not be activating the server. This gives us 72 hours to complete the portions of the Swing Migration that require the original SBS box. In most cases, that is lots of time! ;)
Oh, and one more thing: Crashing a newly configured SBS box after taking a full ShadowProtect image and restoring it to the same hardware and then putting it into production is good practice for your disaster recovery planning. Taking that same image and restoring it to different hardware is good preparation for the "phone call" and will greatly reduce the amount of stress in an already very stressful situation for the client.
UPDATE 2008-03-04: As a side-note observation: After firing up the temporary SBS box after the HIR, what a huge difference in performance there is between the same OS running on the old box and now on the temp one.
The old box is a P4 HT at 3.0GHz and the temp box is a Xeon 3070 at 2.66GHz.
The performance change really demonstrates how far superior the Core 2 technologies are over the old NetBurst ones.
Microsoft Small Business Specialists
*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.