Avoid joining a domain. This is the biggie. During the course of installing Windows, you'll be prompted for a computer name. Using the computer's original name is fine, but you do not want to join a domain. Why not? Because a computer account already exists in the domain. If you try to join a domain, you'll be forced to either rename the machine or delete the existing computer account. If you must join a domain in order to access the backup, you need to name the computer something besides its original name.
Restoring the backup
Just as you had to install Windows in a certain way, you must configure NTBACKUP in a manner appropriate for the task at hand.
By default, before NTBACKUP restores a file, it checks to make sure that the file does not already exist. If the file does exist, the backed-up version is not restored. In the case of a bare metal restore, this behavior is not desirable; it often leads to file version conflicts.
To change NTBACKUP's default behavior, select the Tools command from the Options menu. When you do, Windows will display the Options properties sheet. Go to the properties sheet's Restore tab, and you will see the three options shown in the figure below.
As you can see, the default option is to not replace any pre-existing files. However, this may lead to file version conflicts as a result of updates that have been applied to the operating system.
The second option is to replace only files that are older than the version that has been backed up. This is the option that works best when I perform a bare metal restore. Using the option to replace all files can lead to unsuccessful restores because critical operating system files are being replaced in the middle of the restore operation. Replacing only older files will result in some OS files being replaced during the restore, but not nearly as many as if you configured NTBACKUP to just replace everything.
Now you're ready to perform the restore operation. The thing to keep in mind about the restore operation is that when the restore completes, you must reboot your server to complete the process. When the reboot completes, your server should be back to normal.
About the author: Brien M. Posey, MCSE, is a Microsoft Most Valuable Professional for his work with Windows 2000 Server, Exchange Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. He writes regularly for SearchWinComputing.com and other TechTarget sites.
More information on this topic: