Recovering both a failed storage system and a failed SQL Server computer

If both the storage system and the SQL Server computer fail, in most cases you should recover the storage system first so that the data--or the space to recover the data--is available.

Successful recovery of the SQL Server computer depends on the existence of the following components:

Archives of the SnapManager backup sets containing all the LUN objects
Note
For detailed information describing how to prepare for the loss of an SQL Server environment in a disaster, see the Microsoft SQL Server Administrator's Companion or the Microsoft SQL Server Operations Guide for your supported Windows operating system.
Recent, usable backups of the SQL Server 2000 or 2005 databases contained in the restored backup sets

Use the recovery procedure in this section as a guideline for your own recovery plan. For complete information about how to recover an SQL Server and storage system, read Microsoft SQL Server documentation and the appropriate Data ONTAP documentation.

To recover both the storage system and the SQL Server, complete the following steps.

Step	Action
1	Recover the storage system and bring it online. See the Data ONTAP System Administrator's Guide for your version of Data ONTAP for information and the Data ONTAP System Administration Data Protection Guide for instruction.
2	Unless you are restoring from a tape, perform the following steps: Install Windows 2000 Server or Windows Server 2003 and load all of the appropriate service packs. Install SQL Server 2000 or 2005 and load the same service pack that was on the system prior to the crash. Install SnapDrive and connect to the same drive letters that your LUNs were connected to prior to the crash. Assuming you backed up your system databases, install SnapManager for SQL Server and migrate your system databases to the same LUNs that they were migrated to prior to the crash.
3	Using SnapManager for SQL Server, recover your SQL Server system databases (master and msdb) from the archived LUN. See Recovering SQL Server databases using archives.
4	Using SnapManager for SQL Server, recover the user databases.