Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1407
  • Last Modified:

Windows Server 2008 Backup and Restore to Different Hardware

We are using the Server Backup feature in Windows Server 2008 standard editon with HyperV to do a "full server" backup of our production server. In the event of critical hardware failure (i.e., main system board for example), theft or fire, which requires the purchase of an entirely new server, is it possible to recover from these backups to an entirely new machine and for the subsequent recovered operating system to run smoothly. Also, if different hardware is used, must the hardware be very similiar or can it be markedly different, ie. different type of motherboard (and chipset), different number of processors, etc.
0
helgevestin
Asked:
helgevestin
1 Solution
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Yes:
http://wbadmin.info/blogs/support/esata-and-wbadmin-support/

The built-in backup has the ability to insert drivers into the OS being recovered to move it to different hardware.

Philip
0
 
helgevestinAuthor Commented:
Ok well I have restored from the backup to a different hardware environment and things look good except for one thing. There seems to be a serious DNS error of sorts. The TCP IPv4 values from the working primary server, from which the backup was made, no longer work when used on the restored server and I have tried reinstalling the network adaptor, reinstalling the DNS server and monkeying or shouild I say reconfiguring the DNS server (new forward and reverse zone entries), as well as trying to use a different set of TCP IPv4 values and NOTHING seems to work! The IP address for the network adaptor of the working primary server was originally 192.168.1.200, Now, if this is used, not only does the internet fail to work, but the AD services also fail, and when the IP address just mentioned is inserted and the restored server rebooted, the IP ALWAYS changes to 192.168.1.100! (The lowest possible IP addrsss for our domain) Again, I've tried everything mentioned above and nothing seems to help with this. Can you offer any helpful suggestions on what may be going on and how to correct it?
(Again, the working primary server's TCP IPv4 values work perfectly for it! But when put into the newly restored server's TCP IPv4 fields, they simply don't! Note also that the restored server's hardware is markedly different from the hardware on the working primary server from which that backup was made from.)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now