Restore a damaged cluster node using Automated System Recovery

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

To restore a damaged cluster node using Automated System Recovery

  1. Make sure you have the following on hand before you begin the recovery procedure:

    • Your previously created Automated System Recovery (ASR) floppy disk and ASR backup media. The ASR disk and media contain the backed up cluster disk signatures, partition layouts, and cluster quorum (as part of the system state).

    • Your previously created backup media containing the data on the cluster nodes.

    • The original operating system installation CD.

    • If you have a mass storage controller and you are aware that the manufacturer has supplied a separate driver file for it (different from driver files available on the Setup CD), obtain the file (on a floppy disk) before you begin this procedure.

  2. Insert the original operating system installation CD into the CD drive of the damaged cluster node.


    • If you are restoring a disk signature to a damaged cluster disk, power down all other cluster nodes except the one on which you are performing the ASR restore. This cluster node must have exclusive rights to the damaged cluster disk.
  3. Restart your computer. If you are prompted to press a key to start the computer from CD, press the appropriate key.

  4. If you have a separate driver file as described in step 1, to use the driver as part of Setup, press F6 when prompted.

  5. Press F2 when prompted during the text-only mode section of Setup. You will be prompted to insert the ASR floppy disk you have previously created.

  6. Follow the directions on the screen.

  7. If you have a separate driver file as described in step 1, press F6 (a second time) when prompted after the system reboots.

  8. Follow the directions on the screen.

  9. Once you have completed all the restore steps, the restored node can rejoin the cluster.


  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

  • This procedure is useful if your cluster node is damaged because of corrupt or missing system files or Cluster registry files, hard disk failure, or changes to disk signatures due to a disk replacement (Event ID 1034 errors).

Information about functional differences

  • Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.

See Also


Restore a damaged cluster node using Automated System Recovery
Back up cluster disk signatures and partition layouts
Using Network Monitor
Checklists for Backing Up and Restoring Data