Restoring databases from other SQL Server backups

You can restore databases to the current SQL Server using SnapManager backup sets that were created for a different SQL Server. If the original SQL Server fails, this feature enables you to recover its databases using a different SQL Server.

To use this feature, you must first remap the source LUNs to the current SQL Server, using the same drive letter assignments that were used for the original SQL Server. After you attach the database, use SnapManager to perform either an up-to-the-minute restore or a point-in-time restore of the newest full database backup.

You can perform a restore from other SQL Server backups using the SnapManager Restore tab or the SnapManager Restore Wizard. For detailed information, see one of the following topics:

Restoring from other SQL Server backups using the SnapManager Restore tab

To use the SnapManager Restore tab to restore databases to this SQL Server using backup sets created for other SQL Servers, complete the following steps.

Step	Action
1	If the source LUNs for the failed databases are still online and mapped on the primary storage, do the following: Note the LUN drive letter assignments. Unmap the LUNs using FilerView or the `lun` command on the storage system console. In MSCS configurations, remove any cluster resource dependencies you might have configured on these LUNs.
2	On the Windows host system, reconnect the restored LUN objects with the SnapDrive MMC interface, using the original drive letters. Consult the SnapDrive documentation for details. Ensure that the LUNs are accessible on the hosting SQL Server.
3	Use SQL Server Enterprise Manager or SQL Server Management Studio to attach the database located on the LUNs.
	If...	Then...
	You succeeded in attaching the database	Complete this procedure as described beginning with Step 4.
	It is not possible to attach the database	Complete this procedure as described beginning with Step 10.
If you attached the database...
4	Start the SnapManager for Microsoft SQL Server application.
5	Click to activate the SnapManager Restore tab.
6	Go to the menu bar and select Action > Restore from Other SQL Server Backups. Result The Restore from Backup dialog box appears.
7	In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server.
8	In the SnapInfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets. Note Leave the "Use this Server's SnapInfo Directory" option deselected. Result The SnapManager Restore tab is updated to list the backup sets for the other SQL Server you specified.
9	Use the SnapManager Restore tab to perform an up-to-the-minute restore or a point-in-time restore of the newest full database backup: For an up-to-the-minute restore, SnapManager automatically backs up the last active transaction log before performing the restore. For a point-in-time restore, select the backup set, a combination of transaction log backups to be restored, or both. For detailed information, follow the steps in Restoring using the SnapManager Restore tab, continuing at Step 11 on page 233. For background information, see the following topics: For information about identifying the most recent full database backup, see SnapManager backup set names. For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup. The procedure is now finished.
If you did not attach the database...
10	If you cannot attach the database, then--to reduce the loss of data--ensure that the last active transaction log of the database is automatically backed up by SnapManager Restore: See Microsoft KB article 253817, "HOW TO: Backup the Last Transaction Log When the Master and the Database Files Are Damaged." This article describes how you can back up the currently active transaction log even if the SQL Server 2000 database file is damaged, provided that the transaction log file is still accessible. Use this same Microsoft KB article as a general guide for gaining access to the last active transaction log of the database. While referring to the steps in that article, observe the following key points: When you create a similar database that contains the same number of data and transaction log files as the original database, you are creating the database you will be restoring using SnapManager. Instead of using the SQL Server `Backup Log` command to back up the transaction log (as described in the Microsoft article), proceed to the next step in this procedure. For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup. Attention Do not use SQL Server Enterprise Manager or SQL Server Management Studio to back up the last active transaction log. Due to file formatting differences between SnapManager backups and Enterprise Manager or Management Studio backups, SnapManager cannot perform a restore operation using transaction logs that were backed up using Enterprise Manager or Management Studio.
11	Start the SnapManager for Microsoft SQL Server application.
12	Click to activate the SnapManager Restore tab.
13	Go to the menu bar and select Action > Restore from Other SQL Server Backups. Result The Restore from Backup dialog box appears.
14	In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server.
15	In the Snapinfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets. Note Leave the "Use this Server's SnapInfo Directory" option deselected. Result The SnapManager Restore tab is updated to list the backup sets for the other SQL Server you specified.
16	Use the SnapManager Restore tab to select the newest full database backup, and then perform an up-to-the-minute restore or a point-in-time restore to the new database you created in Step 10. SnapManager Restore will automatically back up the last active transaction log before actually performing the restore portion of the operation. For information about identifying the most recent full database backup, see SnapManager backup set names. For information about performing a restore operation, see Performing a restore operation.

Restoring from other SQL Server backups using the SnapManager Restore Wizard

To use the SnapManager Restore Wizard to restore databases to this SQL Server using backup sets created for other SQL Servers, complete the following steps.

Note
Before you can restore databases to the current SQL Server using backups created for a different SQL Server, you must first remap the source LUNs to this SQL Server, using the same drive letter assignments that were used for the original SQL Server.

Step

Action

1
If the source LUNs for the failed databases are still online and mapped on the primary storage, do the following:

Note the LUN drive letter assignments.
Unmap the LUNs using FilerView or the lun command on the storage system console.
In MSCS configurations, remove any cluster resource dependencies you might have configured on these LUNs.

2
On the Windows 2000 Server or Windows Server 2003 host system, reconnect the restored LUN objects with the SnapDrive MMC interface using the original drive letters.

Consult the SnapDrive documentation for details. Ensure that the LUNs are accessible on the hosting SQL Server.

3
Use SQL Server Enterprise Manager or SQL Server Management Studio to attach the database located on the LUNs.

If...

Then...

You succeeded in attaching the database

Complete this procedure as described beginning with Step 4.

It is not possible to attach the database

Complete this procedure as described beginning with Step 12.

If you attached the database...

4
Start the SnapManager for Microsoft SQL Server application.

5
Make sure that all other Windows Explorer windows are closed on the SQL Server computer running SnapManager.

6
Disable any SnapManager operations that are scheduled to run against the SQL Server data you are restoring, including any jobs scheduled on remote management or remote verification servers.

7
To launch the SnapManager Restore Wizard, go to the SnapManager menu bar and select Wizard > SnapManager Restore.

Result

The SnapManager Restore Wizard appears and displays the Welcome screen.

8
In the Welcome screen, click Next.

Result

The Which SQL Server Created the Backups screen appears.

9
In the Which SQL Server Created the Backups screen, do the following:

Select the "Restore SnapManager backups that were created on a different SQL Server" option.
Click Next.
Result

The SQL Server Where the Backups were Created screen appears.

10
In the SQL Server Where the Backups were Created screen, do the following:

In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server.
In the SnapInfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets.
Leave the Use this Server's SnapInfo Directory option deselected.
Click Next.
Result

The Backup to Restore screen appears and lists the backup sets for the other SQL Server you specified.

11
Follow the instructions in the Restore Wizard screens to perform an up-to-the-minute restore or a point-in-time restore of the newest full database backup:

For an up-to-the-minute restore, SnapManager automatically backs up the last active transaction log before performing the restore.
For a point-in-time restore, select the backup set, a combination of transaction log backups to be restored, or both.
For detailed information, follow the steps in Restoring using the SnapManager Restore Wizard, continuing at Step 8 on page 238.

For background information, see the following topics:

For information about identifying the most recent full database backup, see SnapManager backup set names.
For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup.

The procedure is now finished.

If you did not attach the database...

12
If you cannot attach the database, then--to reduce the loss of data--ensure that the last active transaction log of the database is automatically backed up by SnapManager Restore:

See Microsoft KB article 253817, "HOW TO: Backup the Last Transaction Log When the Master and the Database Files Are Damaged." This article describes how you can back up the currently active transaction log even if the SQL Server 2000 database file is damaged, provided that the transaction log file is still accessible.
Use this same Microsoft KB article as a general guide for gaining access to the last active transaction log of the database. While referring to the steps in that article, observe the following key points:

When you create a similar database that contains the same number of data and transaction log files as the original database, you are creating the database you will be restoring using SnapManager.
Instead of using the SQL Server Backup Log command to back up the transaction log (as described in the Microsoft article), proceed to the next step in this procedure.

For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup.

Attention
Do not use SQL Server Enterprise Manager or SQL Server Management Studio to back up the last active transaction log. Due to file formatting differences between SnapManager backups and Enterprise Manager or Management Studio backups, SnapManager cannot perform a restore operation using transaction logs that were backed up using Enterprise Manager or Management Studio.

13
Start the SnapManager for Microsoft SQL Server application.

14
Make sure that all other Windows Explorer windows are closed on the SQL Server computer running SnapManager.

15
Disable any SnapManager operations that are scheduled to run against the SQL Server data you are restoring, including any jobs scheduled on remote management or remote verification servers.

16
To launch the SnapManager Restore Wizard, go to the SnapManager menu bar and select Wizard > SnapManager Restore.

Result

The SnapManager Restore Wizard appears and displays the Welcome screen.

17
In the Welcome screen, click Next.

Result

The Which SQL Server Created the Backups screen appears.

18
In the Which SQL Server Created the Backups screen, do the following:

Select the "Restore SnapManager backups that were created on a different SQL Server" option.
Click Next.
Result

The SQL Server Where the Backups were Created screen appears.

19
In the SQL Server Where the Backups were Created screen, do the following:

In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server.
In the SnapInfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets.
Leave the "Use this Server's SnapInfo Directory" option deselected.
Click Next.
Result

The Backup to Restore screen appears and lists the backup sets for the other SQL Server you specified.

20
Follow the instructions in the Restore Wizard screens to select the newest full database backup, and then perform an up-to-the-minute restore or a point-in-time restore to the new database you created in Step 12.

SnapManager Restore automatically backs up the last active transaction log before actually performing the restore portion of the operation.

For information about identifying the most recent full database backup, see SnapManager backup set names.

For information about performing a restore operation, see Performing a restore operation.

Step	Action
1	If the source LUNs for the failed databases are still online and mapped on the primary storage, do the following: Note the LUN drive letter assignments. Unmap the LUNs using FilerView or the `lun` command on the storage system console. In MSCS configurations, remove any cluster resource dependencies you might have configured on these LUNs.
2	On the Windows 2000 Server or Windows Server 2003 host system, reconnect the restored LUN objects with the SnapDrive MMC interface using the original drive letters. Consult the SnapDrive documentation for details. Ensure that the LUNs are accessible on the hosting SQL Server.
3	Use SQL Server Enterprise Manager or SQL Server Management Studio to attach the database located on the LUNs.
	If...	Then...
	You succeeded in attaching the database	Complete this procedure as described beginning with Step 4.
	It is not possible to attach the database	Complete this procedure as described beginning with Step 12.
If you attached the database...
4	Start the SnapManager for Microsoft SQL Server application.
5	Make sure that all other Windows Explorer windows are closed on the SQL Server computer running SnapManager.
6	Disable any SnapManager operations that are scheduled to run against the SQL Server data you are restoring, including any jobs scheduled on remote management or remote verification servers.
7	To launch the SnapManager Restore Wizard, go to the SnapManager menu bar and select Wizard > SnapManager Restore. Result The SnapManager Restore Wizard appears and displays the Welcome screen.
8	In the Welcome screen, click Next. Result The Which SQL Server Created the Backups screen appears.
9	In the Which SQL Server Created the Backups screen, do the following: Select the "Restore SnapManager backups that were created on a different SQL Server" option. Click Next. Result The SQL Server Where the Backups were Created screen appears.
10	In the SQL Server Where the Backups were Created screen, do the following: In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server. In the SnapInfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets. Leave the Use this Server's SnapInfo Directory option deselected. Click Next. Result The Backup to Restore screen appears and lists the backup sets for the other SQL Server you specified.
11	Follow the instructions in the Restore Wizard screens to perform an up-to-the-minute restore or a point-in-time restore of the newest full database backup: For an up-to-the-minute restore, SnapManager automatically backs up the last active transaction log before performing the restore. For a point-in-time restore, select the backup set, a combination of transaction log backups to be restored, or both. For detailed information, follow the steps in Restoring using the SnapManager Restore Wizard, continuing at Step 8 on page 238. For background information, see the following topics: For information about identifying the most recent full database backup, see SnapManager backup set names. For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup. The procedure is now finished.
If you did not attach the database...
12	If you cannot attach the database, then--to reduce the loss of data--ensure that the last active transaction log of the database is automatically backed up by SnapManager Restore: See Microsoft KB article 253817, "HOW TO: Backup the Last Transaction Log When the Master and the Database Files Are Damaged." This article describes how you can back up the currently active transaction log even if the SQL Server 2000 database file is damaged, provided that the transaction log file is still accessible. Use this same Microsoft KB article as a general guide for gaining access to the last active transaction log of the database. While referring to the steps in that article, observe the following key points: When you create a similar database that contains the same number of data and transaction log files as the original database, you are creating the database you will be restoring using SnapManager. Instead of using the SQL Server `Backup Log` command to back up the transaction log (as described in the Microsoft article), proceed to the next step in this procedure. For information about identifying the transaction logs, see SnapInfo subdirectory names and Transaction log backup. Attention Do not use SQL Server Enterprise Manager or SQL Server Management Studio to back up the last active transaction log. Due to file formatting differences between SnapManager backups and Enterprise Manager or Management Studio backups, SnapManager cannot perform a restore operation using transaction logs that were backed up using Enterprise Manager or Management Studio.
13	Start the SnapManager for Microsoft SQL Server application.
14	Make sure that all other Windows Explorer windows are closed on the SQL Server computer running SnapManager.
15	Disable any SnapManager operations that are scheduled to run against the SQL Server data you are restoring, including any jobs scheduled on remote management or remote verification servers.
16	To launch the SnapManager Restore Wizard, go to the SnapManager menu bar and select Wizard > SnapManager Restore. Result The SnapManager Restore Wizard appears and displays the Welcome screen.
17	In the Welcome screen, click Next. Result The Which SQL Server Created the Backups screen appears.
18	In the Which SQL Server Created the Backups screen, do the following: Select the "Restore SnapManager backups that were created on a different SQL Server" option. Click Next. Result The SQL Server Where the Backups were Created screen appears.
19	In the SQL Server Where the Backups were Created screen, do the following: In the Backup Server Name box, select the SQL Server whose backup sets you want to use to restore databases to this SQL Server. In the SnapInfo Directory Path box, enter or browse to the name of the SnapInfo directory for those backup sets. Leave the "Use this Server's SnapInfo Directory" option deselected. Click Next. Result The Backup to Restore screen appears and lists the backup sets for the other SQL Server you specified.
20	Follow the instructions in the Restore Wizard screens to select the newest full database backup, and then perform an up-to-the-minute restore or a point-in-time restore to the new database you created in Step 12. SnapManager Restore automatically backs up the last active transaction log before actually performing the restore portion of the operation. For information about identifying the most recent full database backup, see SnapManager backup set names. For information about performing a restore operation, see Performing a restore operation.