Recovering a failed SQL Server computer

To recover a failed SQL Server computer, you must use NTBackup or a third-party backup and restore application, relying on its documentation for direction.

Existing backups

This scenario assumes that backups of the SQL Server computer were made; it also assumes that the most recent backup includes the system state of the SQL Server just before the disaster occurred. At a minimum, the following data should be captured on the backup media:

SQL Server data
- Any dynamic data on the SQL Server
- Data that is difficult or impossible to re-create
  Examples include custom scripts, Web pages, and other mission-critical data.
- Windows backup set: boot partition, system partition, and system state.
Windows system state
- Windows 2000 registry
- Windows 2000 boot files
- Windows 2000 protected operating system files
Cluster service registry checkpoints and quorum disk resource data (if you are running cluster service)

Requirements for restoring to a different server

If you are restoring to a different server, that server's hardware must be identical to that of the original server, including the interface cards, hard drives, and firmware versions.

Procedure

To recover a failed SQL Server computer, complete the following steps.

Step	Action
1	Ensure that the storage system is online and that the volumes containing the LUN objects are available over the CIFS protocol. There must be a CIFS share on the volume on which the LUN resides. See the Data ONTAP System Administrator's Guide for your version of Data ONTAP for details about general storage system administration.
2	Perform a full restore of the SQL Server computer, without the SQL Server databases, using NTBackup or the third-party backup application you used to create the backup. See the documentation for your backup software and the Microsoft disaster recovery documentation for Microsoft SQL Server 2000 or 2005.
3	If...	Then...
	Your backup software was configured to back up SnapDrive	Continue with Step 4.
	Your backup software was not configured to back up SnapDrive	Reinstall the same version of SnapDrive used before the disaster occurred. For information about installing and configuring SnapDrive, see the SnapDrive Installation and Administration Guide for your version of SnapDrive.
4	Using the SnapDrive MMC, connect the LUNs or ensure that they are connected, and ensure that you are using the same drive letters used before the disaster.
5	If...	Then...
	Your backup software is configured to back up the entire SQL Server computer less the databases	Perform a complete recovery of your SQL Server computer using the same backup application. Databases are later restored with SnapManager.
	You are not backing up the SQL Server computer other than using SnapManager to back up the databases	Reinstall the SQL Server software and apply any necessary service packs.
6	Launch SnapManager and run the SnapManager Configuration Wizard to ensure that the correct configuration is used. If necessary, modify the configuration so that it exactly matches the configuration before the failure.
7	Restore the most recent backup using SnapManager Restore. Do not select the Point-in-Time restore option. See Chapter 10, Restoring Databases Using SnapManager.
8	Confirm the operation of the SQL Server.