Rebuilding the Windows Operating System
Rebuild the operating system in the event of a disaster.
Before You Begin
- Install Microsoft .NET Framework 3.5 and 4 on the client computer. This is not required if the client computer has Windows 2003 or Windows XP.
- On a Windows 2003 Server, restore to the same platform that you used for performing the backup. For example, You cannot do a full system restore on an x64 platform if you are using a 32-bit iDataAgent for backup.
For a non-authoritative restore of Windows cluster, note the following:
- If you are restoring a cluster node running SQL or Exchange servers, see the Microsoft disaster recovery documentation for restoring SQL and Exchange servers before restoring the node.
- When you are recovering primary node, turn off all cluster nodes except the primary node to be recovered.
About This Task
If the operating system of your client is corrupted, you need to re-build the operating system.
During the rebuild you will be prompted for the following system information. 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.
How to Get It
|Windows Operating System||Use Windows installation discs, CD, required service packs (SPs) and Hot fixes to install the Windows Operating System.|
|Windows File System iDataAgent||Use Windows File System iDataAgent installation disc to install the Windows File System iDataAgent.|
|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.|
|Network Interface Card configuration and settings||
|TCP/IP Settings|| On the command prompt give following commands:
|Video settings||Note down the video settings if the resolution and color depth are important.|
|Domain information||Note down the domain in which this computer resides.|
|Domain password||Note down this information if you are restoring a domain controller.|
|Local admin password||Note down this information to log on to the computer once it is restored.|
- Rebuild the system hardware if necessary.
- Configure hardware devices such as disk arrays and ensure connectivity to all drives.
- Using the instructions provided with the software, install Windows operating system and include any previously installed Service Packs and Hot Fixes.
Do not install IIS Services. These services will be restored automatically during the restore.
- Format and partition the hard drives to match their previous configurations.
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 to avoid a naming resolution conflict when the client is restored.
- Add the IP address and the fully qualified domain name and a short name of the Client, MediaAgent and CommServe to the host file of the client in the following format:
<ip address> <fully qualified domain name> <short name>
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.
Similarly, add the CommServe, MediaAgent and Client names and their IP addresses to the Host file of the MediaAgent, and CommServe when restoring a Domain Name Server.
- Enable and configure TCP/IP support.
- Configure the Network Interface Card(s).
Ensure 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.
- Run the following command to verify network communications between the client computer and the CommServe:
ping <CommServe name>
- Run the following command to verify network communications between the client computer and the MediaAgent:
ping <MediaAgent name>
- Install the Windows File System Agent and all applicable updates on the default install partition of the client computer.
If you are restoring the domain controller, restart the computer in Directory Services mode after installing the Windows File System Agent.
- Disable backup jobs on the client
- From the CommCell Browser, right-click the <Client> and select Properties.
- Click the Activity Control tab.
- Clear the Enable Backup check box and click OK. This will disable backup jobs for the client and any scheduled backup jobs for the client will not start during the full system restore.