Basic Full Ida Restore Walk-Through of a Windows System

Total Page:16

File Type:pdf, Size:1020Kb

Basic Full Ida Restore Walk-Through of a Windows System

Galaxy 7.0 - Basic Full System Restore Walk Through and FAQ of Windows (XP, 2000, 2003) Systems.

Overview:

This guide is meant to show the basic steps for a Full System Restore of a system. If the System is a Domain Controller, a Clustered System, or a completely different system such as new hardware, please consult the official Galaxy documentation for the correct procedures as they are outside the scope of this document.

 Full System Restore - Windows 2000, XP, and Server 2003 - Overview  Full System Restore - Windows 2000, XP, and Server 2003 - How To

Preface:

A Full System Restore is designed to restore a machine back to a previous state in the event of a disk failure or disk corruption. Because it restores the Windows Registry which contains machine specific information, it is designed to go back to the same system. If anything has changed on the system besides just replacing the disk drive, they may be extra considerations that you have to make in order to successfully restore the system. This guide should only be used to perform a restore back to the same machine where no hardware has changed except the disk drive(s). If hardware has changed, please consult the official Galaxy documentation.

Important Considerations on Full Restores:

Note: If these considerations are not met, your restore may fail.

 The OS must be the same version on the target system as it was in the backup.  The Windows HAL (Hardware Abstraction Layer) must be the same on source and target systems (IE – Uniprocessor or Multiprocessor)  The Windows install directory (%systemroot%) must be the same as it was in the backup.  The operating system should be at the same service pack and hotfix level as it was at the time of the backup to ensure that the restored components are compatible with the versions running on the target system. For Windows 2000 please see the “Why is my Windows 2000 restore failing at 80%” question below.  The disk configuration and layout (what drive letters the volumes are mounted as) must be the same or those drives filtered from the restore.  All devices and drivers should be installed and functioning in Windows before you start the restore.  Any software that was running on the system at the time of the last backup, that uses a kernel level or file system filter driver should be reinstalled before starting the restore (examples: CommVault QSnap or OFH, Open File Managers, Anti-Virus, Undelete software, Disk Snapshot or replication software, Dell Open Manage, ect)  If Windows was installed in to a different partition, or to a disk on a different controller channel, the Boot.ini must be filtered! This will prevent the Boot.ini from the backup from overwriting the current one. If the disk layout is different and you don’t filter this, the ARC path in the file will point to the wrong location of the Windows install and you will get the NTOSKRNL missing or corrupt error. See below for more details. Rebuilding the Operating System:

1. Rebuild and configure the system hardware if necessary.

2. Reinstall the SAME version of Windows that the computer was running during the backup.  Windows MUST be installed into the same directory as the original computer.  Leave the server in a workgroup and do not join it into the domain (so the SID does not change)  Do not install IIS; this will be restored with the system.  Be sure to enter the correct time and time zone.

3. Install any Windows Service Packs and Hotfixes that were on the system at the time of the backup. The restore may fail if this is not done.

 Note: For Windows 2000 Systems, You MUST install the update 828741 if this was installed at the time of the backup or the restore WILL FAIL! Please see the “Why is my Windows 2000 restore failing at 80%” question below for details.  See MS Article: http://support.microsoft.com/default.aspx?scid=kb;en-us;871169

4. Format, partition and configure the hard drive to match their previous configuration.  Note: the drives or partition sizes can be larger than before, but the drive letters and configurations must match.

5. Install any other hardware drivers and/or necessary software and verify that all the devices on the system are functioning properly.

6. Enable and configure TCP/IP support:  Configure the Network Interface Card(s).  Confirm that the Network Interface Card that Galaxy uses 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.

7. Restart the client computer for the changes to take place.

8. 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 (where is the name of the CommServe computer). (Skip this step if the CommServe is installed on the same computer.)

9. Use the ping command to verify network communications between the client computer and the MediaAgent. For example, ping (where is the name of the MediaAgent computer). Skip this step if the MediaAgent is installed on the same computer.

10. Install the Windows File System iDataAgent. See the Windows File System iDataAgent Deployment Guide for detailed instructions on installing the software. 11. Install all applicable Galaxy Updates on the client computer.

Performing the Full System Restore

1. Open CommCell Console.

2. 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.

3. Start the CommCell Browser and right-click the BackupSet containing the data you want restored. Click All Tasks, and then click Browse Backup Data.

4. From the Browse Options dialog box, select the point-in-time (and copy precedence in the Advanced tab if necessary) from which you want to restore your data. Click OK to continue. 5. Choose what needs to be restored from the Browse. Typically a Full System Restore requires that the system drive (where Windows is installed) and the System State be restored. You can check DefaultBackupSet to restore everything. Alternately, you can uncheck any drives that you want to excluded from the restore. Hit Recover All Selected when finished. 6. From the Restore Options dialog box, select the restore options that you wish to apply. If you wish to restore out of place, choose a different destination client (note the hardware MUST be compatible) 7. Filtering Hosts file or Boot.ini - If you are using a host file for name resolution, or need to filter Boot.ini, you can exclude these from the restore. Click on the Advanced button, Paths/Filters Tab and, then click Add on the Filters Paths box.

 To filter Boot.ini add “*boot.ini” to the filters (no quotes).  For hosts file, add the path to your hosts file (typically C:\WINDOWS\system32\drivers\etc\hosts) 8. Click OK to start the restore process. As the restore proceeds, the system displays a Restore Progress bar.

9. When the restore is finished, you will be prompted to restart the computer. Click OK to restart the computer. Note: if you had issues with a previous restore attempt, please gather the Galaxy log files BEFORE the machine is rebooted.

10. 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.

11. Re-install any agents that were previously installed on the restored client computer. See QiNetix Deployment for specific installation procedures for each agent. Tip:

Disaster Recovery - Windows File System http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/prod_info/windows.htm? var1=http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/products/windows/dr.htm

 Click Compare to view the Service Pack information of source and destination computer. Frequently Asked Questions about System Restores

Q. Where is the official Galaxy Full System Restore documentation? A. This can be found on the QiNetix Books Online CD by going to Common Technology Engine -> Disaster Recovery -> iDataAgents – Full System Restore -> Windows File System or on the Maintenance Advantage Website at the link below:  http://documentation.commvault.com/commvault/release_7_0_0/books_online_1/ english_us/features/disaster_recovery/windows/disaster_recovery_windows.htm

Q. Can I restore to a machine with a different name? A. Yes, Galaxy 7.0 allows a Full System Restore to a machine with a different name as long as that machine has the File System Agent installed. Note that the machine MUST have compatible hardware, or it may not be able to boot. After the machine reboots it will assume the same configuration (name, IP, SID, ect) that it had at the time of the backup.

Q. Can I restore the backup data out of place? A. You can restore the Files system, System State or a Full System Restore to a different client, as long as it has the Galaxy File System agent on it. Files and some System State components can be restored out of place as a flat file.

Q. I restored System State data out of place, but nothing is in the folder? A. By default, Windows Explorer hides system protected files. To see these files, from within Windows Explorer, go to Tools -> Folder Options -> View and uncheck “Hide protected operating system files” and select “show hidden files and folders.

Q. Can I perform a Full iDA Restore to a machine that has different hardware? A. This will depend on how different the hardware is. If the hardware is compatible then you may be able to this, and may have to take extra steps in the restore to get this to work such as un-checking the “Unconditional Overwrite” option. If the hardware or drivers from the original system are incompatible with the hardware/drivers on the current system, the machine may not boot and/or you may get a Stop Error. Although Galaxy will be able to restore the data to the new machine, the computer may not boot properly since the restored data will be incompatible with the current hardware. This is similar to taking the hard disk out of the original system and plugging it into the new system and turning the power on. If the computer won’t boot, chances are the Full iDA restore will not work either. Note that this is not a Galaxy limitation (we CAN put the data back) but rather a limitation on how Microsoft Windows and the hardware drivers restored from the backup handle the different (unexpected) hardware.

 Here is Microsoft’s article on restoring Windows to different hardware: http://support.microsoft.com/default.aspx?scid=kb;en-us;249694

Q. How can I filter the Windows kernel files from the restore? A. The following files are automatically filtered from the restore when performing a Full iDA restore (no manual steps required for these). You may still need to preserve the Boot.ini however, see question for this below.

 C:\WINDOWS\system32\hal.dll  C:\WINDOWS\system32\ntoskrnl.exe  C:\WINDOWS\system32\ntkrnlpa.exe  C:\WINDOWS\system32\kernel32.dll  C:\WINDOWS\system32\ntdll.dll  C:\WINDOWS\system32\win32k.sys  C:\WINDOWS\system32\winsrv.dll  C:\WINDOWS\system32\bootvid.dll  C:\WINDOWS\system32\kdcom.dll  C:\WINDOWS\Driver Cache\i386\driver.cab

Q. What am I supposed to do if the hardware is incompatible? A. Do not do a System State restore, just restore the file system data. The Windows Registry and System Protected Files will restore hardware specific entries and drivers. If the hardware is incompatible, you cannot restore the System State. You may also want to look into Microsoft (or other software vendor’s) procedures on how to migrate various types of data to a new machine as they may have specific tools to do this without restoring the entire system. Another alternative is to restore the registry from the backup out of place, take the pieces out of it that you need, and manually import them into the new system’s registry. You will need to consult Microsoft or the application vendor to find out if this possible and if so, what you will need to export from the old registry.

Q. The disks on the rebuilt system are not the same size, is this problem? A. As long as the new volumes are large enough to hold the data that was backed up, this is not a problem. As a rule of thumb, the volumes should be sized the same size or larger than the original volumes.

Q. What do I do if the original system was a Multiprocessor system and the target is Uniprocessor? A. You must build the target system with the same HAL as the source. You can select the correct Multiprocessor HAL during the Windows install by pressing the F5 key. See the link below for instructions.  http://support.microsoft.com/default.aspx?scid=kb;en-us;216251

Q. What do I do if the original system was a Uniprocessor system and the target is Multiprocessor? A. You must build the target system with the same HAL as the source. You can select the Uniprocessor HAL during the Windows install by pressing the F5 key. See the link below for instructions. After the restore is complete, you can then change the HAL back to Multiprocessor so that all the processors get used.  http://support.microsoft.com/default.aspx?scid=kb;en-us;216251

Q. Why is the restore of a server that was upgraded from Windows 2000 to 2003 failing? A. Most likely this is because the %systemroot% directory has changed when the server was rebuilt. Windows 2000 uses WINNT for the default %systemroot% folder whereas Windows 2003 automatically uses WINDOWS during install. See the following links for more info on how to correct this issue:  https://www.commvault.com/mainadv/view_article.asp?id=10745  http://support.microsoft.com/kb/235478 Q. How do I know what updates were installed on the system at the time of the backup? A. Galaxy 6.1 and above will keep track of this for you and display the updates on the “Restore Options” window. You must check the “Include HotFix Information” box on your backup or schedule options for this to occur (off by default). For previous versions of Galaxy, the easiest way to get a good idea of what updates were installed is to browse the backup data of the server and check the WINNT or WINDOWS folder for the update’s uninstall folders. These will look like $NtUninstallKB######$ where the #’s represent the Microsoft update number. There should also be files named “KB######.log” in the WINNT or WINDOWS folder.

Q. Why is my restore of a Windows 2000 system hanging or failing at 80%? A. The original system that was backed up had Microsoft update MS04-012: Cumulative Update for Microsoft RPC/DCOM (Article ID:828741) installed and the target server did not have this updated installed. If this update was installed on the source server, it must be installed on the target before the restore is attempted. See the following links for more details:  http://support.microsoft.com/default.aspx?scid=kb;en-us;871169  https://www.commvault.com/mainadv/view_article.asp?id=10083  http://support.microsoft.com/kb/828741/

Q. Why do I need to Filter the Boot.ini file? A. The Boot.ini file tells the system where to find the Windows installation (which disk, partition, ect). If Windows is installed into a different partition (possibly because the original server had an OEM partition on the disk from the factory) or because the disk was moved to a different controller or channel, the ARC path for the current install of Windows will be different from the one in the backup. During the restore the Boot.ini will be overwritten with the one from the backup which will contain an incorrect ARC path. Filtering the Boot.ini will allow you to keep the current version if necessary. For more information on this see the following links:  https://www.commvault.com/mainadv/view_article.asp?id=10743  http://support.microsoft.com/kb/102873/

Q. After I performed a Full iDA Restore and rebooted I got the following error: “Windows NT could not start because the following file is missing or corrupt: \System32\Ntoskrnl.exe” A. The Boot.ini from the restore has an incorrect ARC path meaning the disk layout must be different. You can filter the boot.ini to prevent this, see the question above for more details. See the following link for more info on this error:  http://support.microsoft.com/default.aspx?scid=kb;en-us;124550

Q. After I performed a Full iDA Restore and rebooted I got the following error: "Windows could not start because the following file is missing: \system32\drivers\ntfs.sys" A. The most likely cause is that rebuilt system and the system at the time of the backup are at different service pack or hotfix levels. Make sure the rebuilt system has the same service pack and hotfixes that the system did at the time of the backup.

Q. After I performed a Full iDA Restore and rebooted I got the following error: " Windows could not start because of an error in the software. Please report this problem as : load needed DLLs for kernel. Please contact your support person to report this problem." A. The most likely cause is that rebuilt system and the system at the time of the backup are at different service pack or hotfix levels. Make sure the rebuilt system has the same service pack and hotfixes that the system did at the time of the backup.  http://support.microsoft.com/kb/914049/

Q. After I performed a Full iDA Restore and rebooted I got a 0x0000007B Stop error. A. The most common causes are:

 The server has an Upper Filter driver(s) installed on the source. Check the following keys on the source machine:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71A27CDD-812A -11D0-BEC7-08002BE2092F}\UpperFilters

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325 -11CE-BFC1-08002BE10318}\UpperFilters

If this is the case, you may either need to uninstall that software from the souce machine, reboot and take a new backup, or install that software on the destination before you run the restore so the drivers are on that target server.

 Filters were used on the backup such as *:\**\drivers*\** or *:\win*\inf*\** that filter out necessary drivers from the backup.

 The disks on the original system were configured as Dynamic disks, but the rebuilt server had the disks configured as Basic. The disks on the rebuild system should be upgraded from Basic to Dynamic in Windows Disk Manager before the restore is performed.

Q. After the Full iDA Restore the IIS services wont start. A. Mostly likely the IIS services were installed during the Windows install. This causes the machine crypto keys to change and not match those in the restored IIS files. If you want to restore a system running IIS you must make sure that you do NOT install IIS during the Windows install and you perform a Full iDA restore which will bring back the IIS service during the restore.

Q. My restore said completed with errors, is the restore bad? A. Galaxy may report an error during the restore for a number of reasons such as a tape drive or resource reservation issue, or because some component was in use and the system must first be rebooted. This does not necessarily mean that the restore itself was bad or encountered a real error. The way to tell would be to check the Galaxy logs on the client (usually the w2dbrestore.log or clrestore.log). If you are concerned, please get the Galaxy logs from the client machine BEFORE you reboot and send them to CommVault Support.

Q. How do I perform a Full iDA Restore of a SQL 2000 server? A. Please follow the instructions in the official Galaxy documentation. See the link below:  http://documentation.commvault.com/commvault/release_7_0_0/books_online_1/ english_us/features/disaster_recovery/sql_server/disaster_recovery_sql.htm Q. How do I perform a Full iDA Restore of an Exchange 2000/2003 server? A. Please follow the instructions in the official Galaxy documentation. See the link below:  http://documentation.commvault.com/commvault/release_7_0_0/books_online_1/ english_us/features/disaster_recovery/exchange_2000_2003/exchange_2000_2 003.htm

Q. How do I perform a Full iDA Restore of a clustered system? A. Please follow the instructions in the official Galaxy documentation. See the link below:  http://documentation.commvault.com/commvault/release_7_0_0/books_online_1 /english_us/features/disaster_recovery/windows/disaster_recovery_windows_ho w_to.htm#Restore_a_Clustered_Client  If the shared disk that was the quorum and was replaced or if the machine is being rebuilt at a DR site, you may have to repair the cluster disk after the Full iDA Restore so that the disk signature matches that of the original computer. Failure to do so will result in the cluster service not starting (event id 1034 in System Event Logs) and authorutil.exe to fail. o http://support.microsoft.com/kb/305793/ o http://support.microsoft.com/kb/280425

Q. How do I perform a Full iDA Restore of a Domain Controller? A. Please follow the instructions in the official Galaxy documentation. See the link below:  http://documentation.commvault.com/commvault/release_7_0_0/books_online_1/ english_us/features/disaster_recovery/windows/disaster_recovery_windows.htm #Restoring Domain Controllers

Recommended publications