DR 1L: Recovering Your Windows 2000 Professional System (non-DSRM)

1. Contact Customer Service to inform them that you are starting a disaster recovery.

   Disaster recovery requires actions by both you and by Customer Service. Customer Service will discuss the situation with you and prepare a disaster recovery plan to meet your needs. For example, you will discuss:

1. Will the data and System State be delivered on media (Network Attached Storage or CD-ROM), or over the Internet? This depends on the amount of data being restored and your Internet connection bandwidth. In some instances, if the amount of data is small and your bandwidth is sufficient, you may have the data restored over the Internet.

   If your data and System State will be delivered over the Internet, then Customer Service will create a new LiveVault Agent kit for the failed system (as required to perform the Internet restores).

   Customer Service will request that you submit a media DR restore request if together you are unable to determine which delivery method to use. The initial processing of the restore request will provide additional information that they can use to help this decision.

2. Do you want to restore the most current version of the data or a historical version?

1. Hardware configuration of the recovering system compared to the original system.

   Windows 2000/2003/XP is not tolerant of hardware differences between the original computer and the computer you are recovering to during a disaster recovery. It may be possible for the disaster recovery procedure to handle hardware configuration differences; however, some differences are not tolerated. All changes must be discussed with Customer Service to ensure compatibility before proceeding with the recovery to avoid problems. In the event the configuration differences preclude a full disaster recovery, then you will need to build a new system, install and configure the operating system and your applications, then restore the computer's data.

   For example, Customer Service will want to know about the following:

   • Dual NICs on the original or recovering system.

   • Newer RAID device on the recovering system.

4. The version of the Agent software that will be recovered (note that this may not be the current version running on the original system). Customer Service will help you determine the version. If the Agent software that will be recovered as part of the data restore is pre-3.3.1 and the original system was previously running Windows NT 4.0 when it was backed up, then additional steps may be required during the data restore.

2. Suspend backup for the recovering system (so that backup does not start again until the disaster recovery is complete). Follow the steps in the help topic Suspending Backup.

3. If your data and System State will be delivered on media, or if the delivery method has not been determined, submit a Media disaster recovery request in MyLiveVault. Follow the steps in the help topic Restoring My Entire Computer on Media.

4. If the recovering system contains two Network Interface Cards (NICs), disable one of the NICs:

   • If the NIC is a separate card that can be removed, then remove the card.

   • If it is an onboard NIC, then disable the NIC using the BIOS interface. Refer to the hardware vendor’s documentation.

   • Otherwise, you must disable the NIC through the Windows Device Manager after installing the Windows operating system (in Step 5). There is no need to reboot after disabling the NIC.

5. Install the Windows operating system and service pack on the recovering system, according to the following requirements.

   Important: Install only those items specified below.

• Install the same version of Windows as existed on the original system. For example, if the original system was running Windows 2000 Professional, then you must install Windows 2000 Professional on the recovering system.

• Install Windows to the same directory on the recovering system as on the original system. For example, if the original system's installation directory was C:\Winnt, then install Windows to C:\Winnt on the recovering system.

• When prompted to specify the Windows components to install, clear the checkboxes for all components except Accessories and Utilities.

  Do not install the other Windows components (for example, Active Directory, Certificate Services, or Internet Information Services). All other components will be restored as part of the disaster recovery. If you install them, the restore and the disaster recovery can fail.

  Important: If you install the IIS components now, the IIS components restored by the LiveVault Online Backup Service will not work correctly. However, if you must install the IIS components now (for example, because you are using a system imaging solution which includes these components), you will remove them later in the process.

• Install the same version of the Windows Service Pack as existed on the original system (for example, Service Pack 1, or Service Pack 2).

  Important: Windows File Protection will not allow the restore of system files that do not match what is recorded in its File Protection database (even if the restored files are newer). A Service Pack mismatch may result in mismatched system files.

• Install the same Windows Hotfixes as existed on the original system.

  Important: Windows File Protection will not allow the restore of Hotfixes. However, the Hotfixes continue to be listed in the installed programs list.

• Make the recovering system a member of an NT Workgroup and specify the same computer name as that of the original system. For example, if the original system was named "corporate.megacompany.com", then you must assign the computer name "corporate" to the recovering system.

  Important: The correct system name must be assigned to the recovering system before the LiveVault Online Backup Service will allow the System State restore to run. If this is not done, the recovering system may not boot properly and the disaster recovery procedure would need to be repeated.

• After installing Windows, restart the recovering system.

6. Configure the disk drive letters and partitions on the recovering system to match those that existed on the original system:

• Use the same partitions. If the original system had partitions D: and E:, the recovering system must also have partitions D: and E:. Otherwise, data restores may fail.

• Ensure that the new partitions are adequately sized to handle the restored data. For example, the recovering system's C: drive must be at least as large as the original system's C: drive.

• Format the recovering system's partitions to be the same file system format as the original system's partitions (that is, NTFS, FAT, etc.).

7. Determine whether any Internet Information Services (IIS) components were installed during the Windows installation (in Step 5).

   Note: There are instances where the IIS components were not selected during the Windows installation, yet the components were installed.

   If IIS components are installed, you must remove them now:

1. Open the Control Panel.

2. Click Add/Remove Programs.

3. Click Add/Remove Windows Components.

4. In the Windows Components Wizard, locate the Internet Information Services item. If the IIS checkbox is selected, then IIS components are installed.

   If the IIS checkbox is selected, clear the checkbox and follow the instructions in the wizard to remove the IIS services components. There is no need to reboot.

   Important: If IIS components are installed and you do not perform this step, then the IIS components restored by the LiveVault Online Backup Service will not work correctly.

8. If your data and System State are to be restored over the Internet for this disaster recovery, then install the LiveVault Agent software on the recovering system. You will receive an e-mail from the LiveVault Online Backup Service when the LiveVault Agent software kit is available for you to download from MyLiveVault and install on the recovering system. Follow the instructions in the e-mail.

   If your data and System State are to be restored on media, skip this step.

9. Make a copy of the boot.ini file (located in the recovering system's root directory). We strongly recommend that you name the copy something similar to BootFromCD_101503.ini (where 101503 represents the current date) to ensure there is no confusion between the copy and the restored boot.ini file, and to differentiate this copy from any other copies you may make.

   Important:  This copy will be referenced later during the disaster recovery, so note the copy's name.

10. Modify the KeysNotToRestore registry key to avoid having the Plug and Play database being in an inconsistent state after System State restore:

1. Using REGEDT32.EXE, open the key:

   HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore

2. Select the Plug & Play entry.

3. From the Edit menu, select Multi-String.

4. In the Data field on the Multi-String Editor dialog box, change the text from:

   CurrentControlSet\Enum
   CurrentControlSet\Control\CriticalDeviceDatabase

   to:

   CurrentControlSet\Control\CriticalDeviceDatabase

For details about this issue, refer to Microsoft Knowledge Base article Q810161 at http://support.microsoft.com/default.aspx?scid=kb;en-us;810161. Note that the Microsoft article specifies that you can instead correct this issue by installing Windows 2000 SP4; however, that is not an option if your original system was running a different Windows 2000 SP (i.e., not SP4) or is a Windows 2003 or XP system as it would conflict with the data being restored to the recovering system.

Important: You must perform this step on the recovering system even if you have already performed this step on the original Agent.

11. Restore all the original system's data to the recovering system. The steps involved depend on how your restored data is being delivered:

• Restored on media: The media contains all the data and the System State from the original system.

  A document explaining how to restore from the media to your computer was provided in the media package (the document is also available from the help topic Restoring Your Data from Media). Follow the steps in that document except for the restore data option and do not restart the system. Instead, you must use the following restore option and restart option:

• On the Select Restore Data dialog, choose the Disaster recovery (restore the entire computer) option.

  This option will restore all of the data and the System State to the recovering system, putting the files/directories their original locations and overwriting any existing files on the recovering system (open files will be overwritten after the system is restarted later).

  Important: Failure to select this option could result in the disaster recovery failing.

• After the restore job (both data and System State) completes, do not restart the system.

• Contact Customer Service before proceeding.

• Restored over the Internet: Restore your data and System State over the Internet to the recovering system. This will be done in two steps.

1. Restore all the data (i.e., everything except the System State) over the Internet to the recovering system:

   1. Follow the steps in the help topic Restoring Files and Directories, or Databases, using these specific settings:

      • Select all the files and directories.

      • In the Delivery tab on the Computer Restore form, choose Network delivery.

      • In the Options tab on the Computer Restore form, choose the overwrite option Always overwrite existing file with restored file and select the corresponding Overwrite open files when system is rebooted check box.

        Important: Failure to select these options could result in many files and applications not being restored properly.

      • Use the default values for all other restore options or set as appropriate for your environment.

   2. You will receive an e-mail from the LiveVault Online Backup Service when the data restore job completes.

   3. After the data restore job completes, check the Agent's restore job log to verify the data restored correctly. See the help topic Viewing a Restore Job's Details to locate the restore job log.

   Important: After the data restore job completes, do not restart the system.

   Note: This step will replace the version of the LiveVault Agent software on the recovering system with the version previously backed up from the original system.

2. After the data restore completes, restore the original system's System State over the Internet to the recovering system. Follow the steps in the help topic Restoring System State for a Windows 2000 or 2003 System That Is Not a Domain Controller using these specific settings:

   • Specify the version of the System State to restore. This must be the same version as the data that was restored (i.e., if current data was restored, then the current System State must be restored).

   • In the Delivery tab on the Computer Restore form, choose Network delivery.

   Important: When the System State restore is complete, do not restart the recovering system.

12. Compare the restored boot.ini file and the copy of the boot.ini file:

1. Go to the computer's root directory, and open both the restored boot.ini file (e.g., boot.ini) and the copy of the boot.ini file (e.g., BootFromCD_101503.ini) that you made earlier in this procedure.

2. Compare the boot drive value (i.e., the number of the partition that the computer will boot from, for example partition(1)):

   • If the boot drive values in these files match, then skip to Step 13.

   • If the boot drive values in these files do not match, then continue this procedure.

3. The restored boot.ini file's (e.g., boot.ini) read-only attribute is set. Clear the read-only attribute:

1. In Windows Explorer, navigate to and select the file.

2. Right-click the file and click Properties on the short-cut menu.

3. In the Properties dialog box, on the General tab, in the Attributes group, clear the Read-only checkbox. Then click OK.

4. Change the value in the restored boot.ini (e.g., boot.ini) to match the value specified in the copy of the boot.ini file (e.g., BootFromCD_101503.ini).

   Depending on your boot.ini configuration, you may have to update the boot drive value for multiple lines in the restored boot.ini file.

   Important: If you fail to update the restored boot.ini file, you may be unable to restart the computer.

13. Restart the recovering system.

    If a Windows message is displayed indicating that you must restart the system because new devices were found, go ahead and restart the system again as specified.  For example, if you are running Windows 2000 SP4 or followed the procedure in Microsoft Knowledge Base article Q810161 (http://support.microsoft.com/default.aspx?scid=kb;en-us;810161), at restart Windows finds all devices as new hardware and some services may not restart. You will be prompted to restart the system again (possibly multiple times) as the new devices are found. In this case, do not restart the system each time you are prompted. After all devices are found, then go ahead and manually restart the system.

    Important: If the recovering system does not restart, contact Customer Service for assistance and see Disaster Recovery: If Your System Does Not Restart.

14. If the original system is a Primary Domain Controller, determine whether it is necessary to perform an authoritative System State restore. If the original system is not a Primary Domain Controller, skip this step.

    Important: In most cases, it is not necessary to perform an authoritative System State restore. Performing an authoritative System State restore is complex and if performed unnecessarily or incorrectly can make your computer unusable.

    Use the following table to help determine whether an authoritative restore may be necessary (if you have any questions, contact Customer Service for assistance):

    The original system is...	Backup domain DB is...	Authoritative restore needed?
    This is the only DC	N/A	No (no need to take over from another DC)
    This is a Backup DC; there is a Primary DC	N/A	No (it would overwrite the PDC)
    This is the Primary DC; there is a Backup DC	Good	No (backup DC has the latest updates; once the PDC reboots, it will get all the updates from the BDC)
    This is the Primary DC; there is a Backup DC	Corrupted	Yes; contact Customer Service and go to the topic Performing an Authoritative System State Restore for a Windows 2000/2003 Domain Controller

15. If you had to disable a NIC for the disaster recovery, enable that NIC:

    • If the NIC is a separate card that was removed, then insert the card.

    • If it is an onboard NIC, then enable the NIC using the BIOS interface. Refer to the hardware vendor’s documentation.

    • If you disabled the NIC through the Windows Device Manager, it may be automatically enabled for you. Check the NIC's status in Device Manager and enable it if necessary.

    After enabling the NIC, you may need to restart the recovered system and configure the NIC.

16. If this is an Exchange 2000/2003 Server, do the following:

1. After the recovering system restarts, start Exchange System Manger.

2. In Exchange System Manager, navigate to the Exchange 2000/2003 Server and check whether each Information Storage group is mounted.

If an Information Storage group is dismounted, mount the storage group:

1. Right-click on the storage group.

2. Click Mount on the shortcut menu.

If you want an Information Storage group to be mounted automatically, also do the following:

1. Right-click on the storage group.

2. Click Properties on the shortcut menu.

3. Click the Database tab, and clear the Do not mount this store at start-up option.

17. Test the recovered system. For example:

• Examine Event Viewer logs.

• Ensure the recovered system is on the network. If the recovered system is not visible on the network, do the following:

1. Right-click My Network Places on your Windows Desktop.

2. Click Properties.

3. Right-click your Local Area Connection.

4. Click Properties.

5. Click OK.

6. Repeat Steps a-e for each configured Local Area Connection as required.

7. Manually start those services, such as WINS, that depend on networking to be able to start.

• If this is an Exchange 2000/2003 Server, test the Exchange 2000/2003 Server functions.

• Load your applications on the recovered system and make sure they work.

18. Inform Customer Service that the disaster recovery is complete and that the recovered system is working successfully.

19. Resume backup for the recovered system, and verify that the backup configurations are running according to their schedules. Follow the steps in the help topic Resuming Backup.