As part of the manual recovery process, you must reinstall Windows, including the last service pack applied before the failure.
To recover the entire cluster manually
On the first node you want to recover, reinstall Windows, including the last service pack applied before the failure.
On the other nodes you want to recover, reinstall Windows, including the last service pack applied before the failure.
Reinstall the cluster services and bring the cluster online.
Do the following:
If you are recovering a Veritas Cluster Server, install the Storage Foundation for Windows High Availability server components, which include Volume Manager, and then use Volume Manager to create disk groups and volumes that match the original cluster configuration.
If you are recovering a Microsoft Cluster Server, after booting the nodes in a cluster, make sure that the drive letters match the original cluster configuration. If the original configuration does not match, then to a certain extent, you can control the hard drive numbering scheme that Windows devises by using the Disk Administrator.
Do one of the following:
If you are recovering a Veritas Cluster Server, re-install Backup Exec.
See Installing Backup Exec with the CASO option on a Veritas Cluster Server.
If you are recovering a Microsoft Cluster Server, use the Cluster Wizard to reinstall Backup Exec for Windows Servers on the cluster. You must use the same settings used during the initial installation.
On the Backup Exec navigation bar on the active node, click Restore.
In the Restore selections pane, select the last full backup sets made of the active node, and then select System State.
For each node that you need to recover, repeat step 6 through step 10.
After all nodes are recovered, restore the Backup Exec data files, and all other data files, to the shared disks.
To restore a database to the shared disks, use the appropriate Backup Exec agent.
More Information
Disaster recovery for Exchange Server 5.5