Restore Data - Windows File Systems - Full System Restore - How To

Topics | How To | Full System Restore | Related Topics

Rebuild the Operating System

Perform a Full System Restore of a Non-Domain Controller

Perform a Full System Restore of a Domain Controller

Restore a Clustered Client

Windows Server 2000 and 2003
Windows Server 2008

Other Restore Scenarios

Restore to a Rebuilt or New System
Restore to a Computer with a Different Hardware Configuration
Restore Teaming Network Adapters

Rebuild the Operating System

If the operating system of your client is corrupted, follow this procedure. Otherwise skip to one of the following:

Perform a Full System Restore of a Non-Domain Controller
Perform a Full System Restore of a Domain Controller

When rebuilding an entire computer, it is required that the Windows service pack and hotfixes in the backup are also applied on the target computer. The service pack on the target must always match the backup prior to a restore.
- The hotfixes can be restored without being applied to the target only by using the Overwrite files, unconditional overwrite restore option.
- The hotfixes will not be restored if the Overwrite files, Overwrite if file on media is Newer restore option is selected, and this will produce the following Windows Vista or Server 2008 login error: An unauthorized change was made to Windows. The solution is to apply matching hotfixes to the target prior to the restore.
- If the backed up computer had Internet Explorer 8.0 and the current computer has Internet Explorer 7.0, then the Overwrite files, unconditional overwrite restore option must be selected when performing a restore operation.
If the Windows product license key is not activated on the target computer prior to a full restore, you will receive the following message, and you will be required to provide the product license key after the restore: An unauthorized change was made to Windows. You must retype your Windows Service Product Key to activate the license.
A restore of System State components requires that the Job_Results folder should reside on the same drive as Microsoft Windows.
If the Job_Results folder is not on the same drive, you can use the CommCell Console to change the location prior to performing restore. To do this:
- Right-click the client and select Properties.
- Select the Job Configuration tab in the Client Computer Properties dialog box.
- Click Browse under the Job Results Directory and change the drive to where Windows is installed.
When restoring a SIS managed volume, the source and target drive letter must be the same.
To successfully restore a volume managed by Single Instance Storage, the SIS/Groveler must be running and attached to the volume to which you are restoring data. If it is not, any non-SIS-linked files will still be accessible, but SIS-linked files will not be accessible, and they will appear to be corrupted. The name and size of a SIS-linked file will appear as normal. However, the file will be a zero-length file because it will not have access to the data it should contain. For more information on How to restore a volume that is managed by Single Instance Storage, refer the KB 263027 Microsoft Knowledge Base article on http://support.microsoft.com/.

Before You Begin:

During the client rebuild you will be prompted for system information, depending upon the system setup. Since the computer will be down during the operating system rebuild, you may not be able to access necessary information about the system. It is important to record such information before a disaster occurs.

Software	Windows installation discs, CD, required service packs (SPs) and Hot fixes that were installed. Windows File System iDataAgent installation disc
Drives	Use the Disk Management utility to record the volumes and sizes of the hard drives in the system, which are needed to recreate the disk configuration in case of hard drive failure. Hard drives must be configured before restoring System State or file system data.
Computer name	Use the same computer name and avoid changing other configuration settings.
TCP/IP	Record the Network Interface Card configuration and settings Record the fully qualified network name and IP address if the computer uses a static IP address. Subnet mask for your network IP address of the network router used by the client computer TCP/IP domain name for the network (e.g., computer.company.com) IP address of the domain name server (DNS) settings
Video settings	Record the video settings if the resolution and color depth are important.
Domain information	Record the domain in which this computer resides.
Domain password	Record this information if you are restoring a domain controller.
Local admin password	Record this information or you will not be able to log on to the computer once it is restored.

To rebuild the operating system:

Rebuild the system hardware if necessary.
Configure hardware devices such as disk arrays and confirm connectivity to all drives.

Using the instructions provided with the software, install Windows and include any previously installed Service Packs and hot fixes (i.e., the service packs and hot fixes that were installed prior to the operating system rebuild). Leave the server in the workgroup and do not include it in the domain.

Windows must be installed in the same directory as that of the original computer; otherwise, full system restores will not work. For machines that have been upgraded to Server 2003 from Windows 2000, Windows must be installed in the WINNT directory.

You can find the exact Service Pack level of your backup in the Comparison of Service Pack Information screen for source and destination machines during a restore operation. (See Perform a Full System Restore of a Non-Domain Controller on this page.) If the HotFix Information advanced backup option was selected for backups, then the applied Microsoft hot fixes will also be specified in the dialog. (See Start a Backup with Hotfix Information.)

When re-installing the Windows operating system, do not install IIS services prior to running the Full System restore. IIS will be restored by the system.

When installing Windows, be sure to enter the correct time and to select the proper time zone.

Format and partition the hard drives to match their previous configurations before attempting the restore. If they already match their previous configuration, skip to the next step.

When recreating partitions, you can Browse the backup data to determine the previous size of the partitions. When you browse the backup set, each drive letter will have its size noted in the Browse window.

If the client was installed with a Fully Qualified Domain Name, perform the following tasks, otherwise, skip to the next step.
- Change the Computer name to the Fully Qualified Domain Name. Entering the Fully Qualified Domain Name will avoid a naming resolution conflict the client is restored.
- Add the CommServe, MediaAgent and CommClient names and IP addresses to the Host file of the client MediaAgent, and CommServe when restoring a Domain Name Server.
- Each entry added to the Host file consists of an IP Address, a Fully Qualified Domain Name and a Short Name, which should match the names that will be restored. Until the DNS server is restored, there is no domain name resolution and the client will be unable to communicate with the CommServe and MediaAgent computers unless this information is added to the Host file.
Enable and configure TCP/IP support:
- Configure the Network Interface Card(s).
- Confirm that the Network Interface Card used is the first card listed in the network binding order when restoring a client with multiple Network Interface Cards.
- Enable and Configure Teaming Network Adapters, if applicable. After performing a full system restore, see Restore Teaming Network Adapters.
If the client is not a cluster node, skip to the next step. Otherwise, perform the following tasks.
- Bind the public Network Interface Card before the Private network interface card.
- Configure all disk array devices with access to the shared array.
- If you are restoring a single cluster node running SQL or Exchange servers, see the Microsoft disaster recovery documentation for restoring SQL and Exchange servers before restoring the node.
If you plan to perform a full system restore on a Windows 2008 Domain Controller, either install the Active Directory Domain Services Role or run DCPROMO and cancel it when the wizard appears. DCPROMO will check to see if the AD binaries are installed, and if they are not, it will install them.
Verify network communications between the client computer and the CommServe. To do this, open an MS-DOS window on the client computer and use the ping command. For example, ping <CommServe> (where <CommServe> is the name of the CommServe computer). (Skip this step if the CommServe is installed on the same computer.)
Use the ping command to verify network communications between the client computer and the MediaAgent. For example, ping <MediaAgent> (where <MediaAgent> is the name of the MediaAgent computer). Skip this step if the MediaAgent is installed on the same computer.

Install the Windows File System iDataAgent and CommCell Console with all applicable patches on the client computer. See the Deployment - Windows File System iDataAgent for detailed instructions on installing the software.

When restoring from a backup that was run when QSnap was installed, install the Windows File System iDataAgent and QSnap before performing the full system restore.
When restoring your machine from a backup that was run before QSnap was installed (QSnap had since been installed), install the Windows File System iDataAgent and then run the full system restore. Then install QSnap after the client is restored and has rebooted.
When restoring your machine from a backup that was run before QSnap was installed (QSnap had since been installed), but not rebuilding the operating system, uninstall QSnap, restore the registry, and then reinstall QSnap.
A restore of System State components requires that the Job_Results folder resides on the same drive as Microsoft Windows.

Once the installation is complete, open the CommCell Console.

The CommCell Console requires 256 colors to run. You may need to install the correct video driver to increase the color depth of the client computer or run the console from another computer.

Ensure that backup jobs are disabled on the client computer. This prevents any backups, which may have been previously scheduled for the client computer, from starting while the restore is in progress. You can disable backups from the Activity Control tab of the File System Properties dialog box.

Perform a Full System Restore of a Non-Domain Controller

After rebuilding the operating system and re-installing the iDataAgent software, use the following procedure to restore a non-domain controller.

To restore a non-domain controller:

Start the CommCell Browser and right-click the backup set that contains the data you want restored. Click All Tasks, and then click Browse Backup Data.

Choose your Browse Options and click OK.

The Client Browse dialog opens, allowing you to select everything to be restored.

The CommCell Console requires 256 colors to run. You may need to install the correct video driver to increase the color depth of the client computer or run the console from another computer.

Select the backup set box along with the boxes for the data drives to be restored.
Deselect items that must be excluded from the restore by drilling down in the folders and deselecting the appropriate boxes.
- If you are using a host file for name resolution, exclude the host file folder from the restore.
- If the disk partition configuration or order is different on the target computer, exclude the %systemdrive%\:boot.ini file from the restore.
NOTES:
- When restoring encrypted data, refer to Data Encryption.
Click the Recover All Selected button at the bottom.
Accept the settings in the Restore Options dialog and click OK.
A Warning box appears, requiring you to click one of three buttons: Yes, No, or Comparison.
- Click Comparison to bring up a dialog that shows a comparison of service pack information for the source and destination computers. To see hot fix information, select the Include Hotfix box at the top of the destination and/or source list(s). Click Close after reviewing the information.
  NOTES:
  
  The Include Hotfix box and option will be available for the source machine ONLY if you have chosen the Include Hotfix Information option during backup. See Start a Backup with Hotfix Information.
- Click No if the service pack information is different (whether you know this initially or discover it after viewing Comparison data). Cancel the restore and update the service packs until the source and destination service packs match.
- Click Yes to confirm that the source and destination information is the same (whether you know this initially or discover it after viewing Comparison data), and to proceed with the restore.
The restore proceeds after you click Yes in the Warning box at this stage in the procedure. When the restore completes, you will be prompted to restart the computer.
Click OK to restart the computer.
After a full system restore, the Windows security ID (SID) of the rebuilt system may not match the corresponding SID on the primary domain controller. To resolve this conflict, remove the computer from the domain by joining a workgroup. Then add the rebuilt computer back into the domain by joining the domain.
Re-install any agents that were previously installed on the restored client computer. See Installation for specific installation procedures for each agent.

After a 2008 Server Restore is complete, From the Server Manager main page, select Configure refresh on the bottom of the screen to update Features and Roles restored. A restart does not accomplish this.

Perform a Full System Restore of a Domain Controller

After rebuilding the operating system and re-installing the iDataAgent software, use the following procedure to restore a domain controller.

To perform a Full System restore of a Domain Controller:

Restart the system in Directory Services Restore mode.
Start the CommCell Browser and right-click the backup set that contains the data you want restored. Click All Tasks, and then click Browse Backup Data.

Choose your Browse Options and click OK.

The Client Browse dialog opens, allowing you to select everything to be restored.

The CommCell Console requires 256 colors to run. You may need to install the correct video driver to increase the color depth of the client computer or run the console from another computer.

Select the backup set box along with the boxes for the data drives to be restored.
Deselect items that must be excluded from the restore by drilling down in the folders and deselecting the appropriate boxes.
- If you are using a host file for name resolution, exclude the host file folder from the restore.
- If the disk partition configuration or order is different on the target computer, filter *boot.ini from the restore.
NOTES:
- When restoring encrypted data, refer to Data Encryption.
Click the Recover All Selected button at the bottom.
The Restore Options dialog opens. Make selections as desired, paying particular attention to the selections that are explained in the next step.
In the General tab of the Restore Options dialog, go to the Restore option for SYSVOL field, and make selections based on whether you are restoring a standalone or non-standalone domain controller.
- For a standalone domain controller or the first domain controller restored in the network, select Primary in the pull-down dialog box.
- For other domain controllers, choose Authoritative or Non-Authoritative as follows:
  - To render the domain controller operational again without replicating any changes to the other domain controllers on the network, select Non-Authoritative.
  - To render the domain controller operational again and to also replicate any changes to the other domain controllers on the network, select Authoritative and complete the restore by running the NTDS restore utility.
The chosen restore type for the SYSVOL applies only to the SYSVOL and will not affect the restore operations of other domain controller components. For example, a choice of Authoritative for SYSVOL does not change the Active Directory's Non-Authoritative default setting.
After making all your selections for restore options, click OK to close the Restore Options dialog.
A Warning box appears, requiring you to click one of three buttons: Yes, No, or Comparison.
- Click Comparison to bring up a dialog that shows a comparison of service pack information for the source and destination computers. To see hot fix information, select the Include Hotfix box at the top of the destination and/or source list(s). Click Close after reviewing the information.
  NOTES
  
  The Include Hotfix box and option will be available for the source machine ONLY if you have chosen the Include Hotfix Information option during backup. See Start a Backup with Hotfix Information.
- Click No if the service pack information is different (whether you know this initially or discover it after viewing Comparison data). Cancel the restore and update the service packs until the source and destination service packs match.
- Click Yes to confirm that the source and destination information is the same (whether you know this initially or discover it after viewing Comparison data), and to proceed with the restore.
The restore proceeds after you click Yes in the Warning box at this stage in the procedure. When the restore completes, you will be prompted to restart the computer.

For Server 2003 and below:

At the Restart Computer prompt:

If you are performing a Non-authoritative or Primary restore, click OK and restart in Normal Mode. Skip to Step 13.

If you are performing an Authoritative restore of the SYSVOL and Active Directory, click OK and restart the computer in Directory Services Restore mode and continue on to the next step.

When performing an Authoritative restore of the SYSVOL without performing a Full system restore, you must run the ntdsutil in order for your policies and scripts to be accessible from Active Directory Users and Computers.

Restore the Active Directory and SYSVOL using an Authoritative Restore as follows:
1. Restart the computer in Directory Services Restore mode.
2. From the Start Menu, click Programs->Accessories->Command Prompt.
3. At the command prompt, type ntdsutil.
4. At the ntdsutil prompt, type Authoritative Restore.
5. At the Authoritative Restore prompt, type Restore Database. You will be prompted to confirm this operation. Click Yes to continue.
6. When done, exit the Authoritative Restore prompt by typing quit. End the ntdsutil session by typing exit. Exit the command prompt by typing exit.
7. Restart the computer in normal mode and allow time for replication to complete.
  
  It is highly recommended that you review all Microsoft instructions and methods for recovering objects and domain controllers.
To restore user or group objects in a forest that has more than one domain, perform the following steps on a domain controller in another domain. These steps may vary based on the environment, refer to http://technet2.microsoft.com/windowsserver/en/library/690730c7-83ce-4475-b9b4-46f76c9c7c901033.mspx for more information.
1. Restart the domain controller in Directory Services Restore Mode locally.
2. Restore from backup media.
3. While still in Directory Services Restore Mode, use Ntdsutil to create an LDIF file for recovering back-links for authoritatively restored objects.
4. Restart the domain controller in normal mode.
5. Run an LDIF file to recover back-links in this domain on a different domain controller than the one on which you created the LDIF file.
Re-install any agents that were previously installed on the restored client computer. See Installation for specific installation procedures for each agent.

If Certificate Server is installed, ensure that the Certificate services are back online after the previous restart step. The Certificate Services will not accept any certificate requests until its restore functions have completed. A full system restore operation restores only certificates issued before the last backup. You can be leave these certificates orphaned, or you can revoke and reissue them.

NOTES

Deleted scripts are placed in \WINDOWS\SYSVOL\domain\NtFrs_PreExisting_See_EventLog\, for manual movement to prevent data loss.
Copy policies and scripts to \WINDOWs\SYSVOL\Sysvol\your.domain.com\and they replicate to other DCs too.
Delete \WINDOWS\SYSVOL\domain\NtFrs_PreExisting_See_EventLog\ and it also gets deleted from \WINDOWs\SYSVOL\Sysvol\your.domain.com\.

For Server 2008 at the 2008 Domain Level using the Non-Authoritative mode:

If you plan to perform a full system restore on a Windows 2008 Domain Controller, either install the Active Directory Domain Services Role or run DCPROMO and cancel it when the wizard appears. DCPROMO will check to see if the AD binaries are installed, and if they are not, it will install them.

Restart the computer in Directory Services Restore mode.
Run a full restore of the computer using the Non-Authoritative mode.
Restart the computer and allow replication to occur.

For Server 2008 at the 2008 Domain Level using the Authoritative mode:

Restart the computer in Directory Services Restore mode.
Run a FULL restore of the computer using the Authoritative mode.
Restart the computer in Directory Services Restore mode.
At the command prompt, type ntdsutil.
At the ntdsutil prompt, type Activate instance NTDS.
At the ntdsutil prompt, type Authoritative Restore.
At the Authoritative Restore prompt, type Restore Subtree DistinguishedName (where DistinguishedName is the name of the subtree that is to be marked authoritative). You will be prompted to confirm this operation. Click Yes to continue. For example, restore subtree: DC=DomainName,DC=COM means you are restoring (domainname.com).
The restore process will complete and a message confirming the creation of one text and 2 LDAP Data Interchange Format (LDIF) files will be displayed.
Restart the computer in normal mode and allow time for replication to complete.
Restart the computer in Directory Services Restore mode.
To run an LDIF file to recover back-links, type the following command at the command prompt.
ldifde -i -k -f FileName (where the FileName is the name of the LDIF file)

It is highly recommended that you review all Microsoft instructions and methods for recovering objects and domain controllers.

To restore user or group objects in a forest that has more than one domain, perform the following steps on a domain controller in another domain. These steps may vary based on the environment, refer to http://technet2.microsoft.com/windowsserver/en/library/690730c7-83ce-4475-b9b4-46f76c9c7c901033.mspx for more information.
1. Restart the domain controller in Directory Services Restore Mode locally.
2. Restore from backup media.
3. While still in Directory Services Restore Mode, use Ntdsutil to create an LDIF file for recovering back-links for authoritatively restored objects.
4. Restart the domain controller in normal mode.
5. Run an LDIF file to recover back-links in this domain on a different domain controller than the one on which you created the LDIF file.
Repeat step 10 for each additional domain.
Re-install any agents that were previously installed on the restored client computer. See Installation for specific installation procedures for each agent.

Restore a Clustered Client

Windows Server 2000 and 2003

To restore a clustered client environment, you would do the following:

Restore the entire cluster or restore the primary node and quorum disk.
Restore program files for the virtual server.
Restore any passive nodes.

Restore an Entire Cluster

To restore an entire cluster, refer to the information for the nDisableGalaxyMerge registry key.

Restore the Primary Node and Quorum Disk (Authoritative Restore)

To restore the primary node and quorum disk:

Turn off all cluster nodes except the primary node to be recovered.
Rebuild the active node. (The active node is the node that owns the quorum disk.) Refer to Rebuild the Operating System.
Perform a Full System Restore of a Non-Domain Controller or Perform a Full System Restore of a Domain Controller, depending on your environment.
Enter y (yes) when the following message appears:
Full iDataAgent Restore job completed. Do you want to reboot?
Enter y (yes) if the following message appears:
New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?
Restart the computer.
After the computer restarts, go to the \base folder and enter the following command at a command prompt:
authorutil.exe -cluster

If the cluster disks were repartitioned, a failure message may appear because the disk GUIDs for the quorum have been changed. If the cluster service does not start, or if you see Event ID 1034 in the System Event Log, reference the KB 305793 and KB 280425 Microsoft Knowledge Base articles on http://support.microsoft.com/ to get the cluster service back online.

Restore Program Files for the Virtual Server

After performing the procedures in Restore an Entire Cluster or in Restore the Primary Node and Quorum Disk, the cluster will be available. Use one of the following procedures, depending on which of the above procedures you used for the restore.

If the registry key nDisableGalaxyMerge was used for the restore:

Although the Bull Calypso Communications Service (GxCVD) and Bull Calypso Client Event Manager (GxEvMgrC) cluster resources are restored, the program files required to start and run these resources must be restored to the virtual server's disk on which they resided.
You must restore the program files for the virtual server to the physical node that owns the virtual disk since the virtual server's services are not yet running. Restore virtual server data in one of the following two ways:
- Select all the virtual disk data and restore it.
- Restore only the program files in order to get the services started. Then restore the rest of the data using the virtual server's File System iDataAgent.

If the registry key nDisableGalaxyMerge was not used for the restore:

Uninstall and reinstall all iDataAgents to the virtual server.
Restore the virtual server's data using the virtual server's File System iDataAgent.

Restore a Passive Node (Non-Authoritative Restore)

To restore a passive node:

Rebuild the active node. (The active node is the node that owns the quorum disk.) Refer to Rebuild the Operating System.
Perform a Full System Restore of a Non-Domain Controller or Perform a Full System Restore of a Domain Controller, depending on your environment.
Enter y (yes) when the following message appears:
Full iDataAgent Restore job completed. Do you want to reboot?
Enter y (yes) if the following message appears:
New Hardware found. Windows has finished installing new devices.... Do you want to restart your computer now?
Restart the computer.
After the computer restarts, go to the \base folder and enter the following command at a command prompt:
authorutil.exe -cluster

NOTES

If the cluster service does not start automatically, start it manually in the service control manager.

Windows Server 2008

In most scenarios the cluster service will heal itself. Some of these scenarios with the corrective steps are listed below.

Cluster files on witness disk (previously called 'Quorum Disk') are corrupt
- Files in the \Cluster directory will be re-created.
- Cluster configuration will be �pushed� to the Witness Disk.
Cluster database (ClusDB) on a single node is missing or corrupt
- Healthy nodes will be contacted and an updated ClusDB will be downloaded.
All nodes are functional but a complete loss of Witness Disk/LUN occurs
- Cluster will start once majority of nodes is reached. Unless using Disk Only quorum model you may need to use /ForceQuorum recovery switch.
- Use Cluster Quorum Wizard to change quorum disk designation.

Perform an Authoritative Restore

An authoritative restore is only performed if the administrator accidentally alters the cluster configuration or deletes a large number of resources and needs to revert to a previous cluster configuration.

To perform an authoritative restore of the cluster configuration database:

All cluster nodes and services should be running.
Cluster must have quorum (a majority of votes through nodes and a possible witness).
Perform a Full System Restore of a Non-Domain Controller or Perform a Full System Restore of a Domain Controller, depending on your environment.

Ensure that the Authoritative Restore for Cluster DB is selected from the Restore Options screen.
Verify that the cluster services are stopped on all the other nodes of the cluster. If not, stop the cluster services on all the other nodes.
Enter y (yes) when the following message appears:
Full iDataAgent Restore job completed. Do you want to reboot?

Cluster services for the node where the restore was performed needs to be started first.
Start the services on all the other nodes in the clusters.

Perform a Non-Authoritative restore

A non-authoritative restore is performed in the scenarios listed below.

Single node in a cluster fails completely (no boot) and the shared disks are still functional
Complete loss of all nodes and storage

To perform a non-authoritative restore of the cluster configuration database:

When entire cluster is down, perform a non-authoritative restore of the first node and then start adding nodes to the cluster. This is essentially a non authoritative restore and the cluster service doesn�t need to be running when this is performed.

Perform a Full System Restore of a Non-Domain Controller or Perform a Full System Restore of a Domain Controller, depending on your environment.

Ensure that the default (non-authoritative restore) for Cluster DB is selected from the Restore Options screen.
Enter y (yes) when the following message appears:
Full iDataAgent Restore job completed. Do you want to reboot?
If the restored node shows unavailable in the failover cluster, evict and add the restored node.

It is recommended that you do not perform an authoritative restore of the cluster after this procedure, without performing a full backup.

Other Restore Scenarios

The full system restore function and (in one case) 1-Touch for Windows can also be used in the following disaster recovery situations.

Restore to a Rebuilt or New System

If you are restoring to a different computer, make sure the target computer is as similar to the original as possible.

Make sure the target computer has the same fully qualified network name as the original.
Try to match the general hardware configuration (i.e., IDE, SCSI) of the original computer.
Match the local disk drive configuration as closely as possible to that of the client being restored.
Make sure the computer's disk(s) can accommodate the quantity of data being restored.
If possible, use the same network interface card (NIC) as that of the client being restored.

Restore to a Computer with a Different Hardware Configuration

If you are performing a full system restore or a 1-Touch recovery to a computer with a different hardware configuration (mass storage device, network interface card, video card, etc.) from the backed up client, you may need to perform the following procedure.

Before You Begin

The software makes a best effort to reconcile hardware differences at the time of restore or recovery. There are no guarantees since some hardware differences may cause issues that are beyond the software's control.
If the target computer's hardware configuration is drastically different from the hardware at the time of backup, consider installing the Windows Operating System, configuring the hardware and applications, and performing a File System Restore with the unconditional overwrite option deselected.
Do not restore the system state data. Restoring system state data includes restoration of the hardware entries in the registry.

Perform the full system restore or 1-Touch with the unconditional overwrite option cleared.
If the disk partition configuration or order is different on the target computer, exclude the %systemdrive%\:boot.ini file from the restore.
Check the TCP/IP and video configurations. If they are incorrect, perform the following steps.
Re-install the appropriate Network Interface Card drivers.
Uninstall the Network Adapters and Display Adapters (using the Hardware Uninstall Wizard or Windows Device Manager).
Restart the computer when prompted.
Your hardware should be re-discovered by Windows and the appropriate drivers restored.
Reconfigure your TCP/IP and Display Adapter settings.

Restore Teaming Network Adapters

After performing a Full System Restore, follow these steps:

Uninstall the teaming software.
Restart the computer.
Install the teaming software.