Solved

Windows Server 2008 Backup and Restore to Different Hardware

Posted on 2009-06-30
2
1,391 Views
Last Modified: 2013-11-11
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
Comment
Question by:helgevestin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 39

Accepted Solution

by:
Philip Elder earned 250 total points
ID: 24745926
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
 

Author Comment

by:helgevestin
ID: 24758334
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

Featured Post

Enroll in July's Course of the Month

July's Course of the Month is now available! Enroll to learn HTML5 and prepare for certification. It's free for Premium Members, Team Accounts, and Qualified Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

OfficeMate Freezes on login or does not load after login credentials are input.
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
Suggested Courses

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question