Go Premium for a chance to win a PS4. Enter to Win

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

Restoring a Windows 2003 Server from backup

I have had a hard disk fail in a Windows 2003 server that is also an AD controller.  

I need to do a restore from a backup done with Windows Server 2003 backup.  

I have a current backup of all the work data (documents etc) but haven't done a system state backup for over a month.  



Can some one please explain (or point me to a document) the procedures for doing a full restore from a backup to an new empty disk?  

I will do a full restore of the older backup first with the system state etc and then restore the documents over the top of that.  However, I am not familiar with how I should start the process.  

Also, the server is in a domain with multiple servers (inc multiple ad controllers), so am I correct that if I restore with the old data, the active directory will automatically update off one of the other AD servers, or will this machine having an older version screw things up?

Thanks for your assistance.  

Andrew
0
totalcomputer
Asked:
totalcomputer
  • 7
  • 6
1 Solution
 
JamesDSCommented:
totalcomputer
OK, you are correct, restore the server and then restore the documents.

Unles you do an "authoritative" restore then yes, the other AD domain controllers will replicate the latest information over the top of the restored server.

To tell you how to start the process you will need to tell us what backup tool you are using!

Cheers

JamesDS
0
 
totalcomputerAuthor Commented:
I did the original backup with NTbackup in Windows 2003, selecting to backup all files and the system state.  

0
 
JamesDSCommented:
totalcomputer
Then you should be fine using a standard restore, including system state and all files

Cheers

JamesDS
0
Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

 
totalcomputerAuthor Commented:
So should I first install Windows Server 2003 in the new hard disk into the same place as it was on the old disk and do a restore over its self?  

If so, do I need to join the domain etc or just to a basic install with the same machine name and restore over that?
0
 
JamesDSCommented:
totalcomputer

As long as you can still run the restore tool on that server, then no, just restore straight over the top and reboot OFF THE LAN to check that it has all come back OK before re-connecting it.

Cheers

JamesDS
0
 
totalcomputerAuthor Commented:
Thanks - To get this straight, this is what I am going to do:

1.  Install a fresh install of Windows 2003 server from the CD to the new hard disk drive, into the same directory that it was installed on the old server.

2.  Boot off the new install.  

3.  Run the ntback restore function, restoring all data over the top of the new installation that I am currently running.  

4.  Reboot the server off the lan to make sure it all comes up OK.

5.  Attach the server to the lan and allow it to refresh the active directory.  

Does this sound like a plan?

Thanks!
Andrew
0
 
JamesDSCommented:
totalcomputer
Sounds good to me :)

IF the AD fails to come back then you may need to do a DCPROMO /forceremove and then DCPROMO again to add it back.

Cheers

JamesDS
0
 
totalcomputerAuthor Commented:
I am having trouble installing the fresh install to the same location as the last one.  The last one was installed to C:\WINNT (as it was originally a Windows 2000 server that was later upgraded to Windows 2003) and Windows Server 2003 automatically installs to C:\Windows.  Do you know a way to over ride this?

0
 
totalcomputerAuthor Commented:
I found the following KB article to the alternate directory question - its pretty crappy!

http://support.microsoft.com/default.aspx?kbid=811944&product=winsvr2003
0
 
JamesDSCommented:
totalcomputer
it shouldn't matter as everything will be overwritten by the restore anyway and everything will be pointing to \winnt.

You will be able to delete the \windows directory afterwards

Cheers

JamesDS
0
 
totalcomputerAuthor Commented:
The restore seems to have gone through OK - Thanks!

When I try to connect to the server from a workstation using its logical name EG \\servername\share$, I get the error  "\\servername is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.  Logon Failure: The target account name is incorrect."  

If I connect with the IP address is goes through OK.  

I tried to remove active directory on the server and I received the same message, "logon failure: the target account name is inncorrect".  

I first tried dcpromo /forceremove and it came up with a box that I could only use /anser or /adv so I ran it without the forceremove to get the error above.  

Do you have any suggestions?  
0
 
totalcomputerAuthor Commented:
I have gotten over the above problem with KB article 288167.  

I needed to use the netdom tool to reset the secure channels between this server and the PDC.  

This seems to have worked and everything appears to function OK.   I did not seem to have needed to do a dcpromo demotion and promotion over agian in the end.  

Thanks again for your invaluable assistance.  

Andrew
0
 
JamesDSCommented:
totalcomputer
Welcome, glad I could help

Cheers

JamesDS
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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