White Papers

23 TR1081 | Microsoft SQL Server Database Protection Using EqualLogic Auto-Snapshot Manager / Microsoft Edition
Figure 12 Restore All – In-Place Restore Options
6.3 SQL Server database restore with Apply Logs option
Applying log file backups after a database Smart Copy restore operation is a manual process and is
therefore considered an advanced operation. For SQL Server databases running in the “Full Database
Recovery Model”, it is vital to maintain a regular database log backup schedule to control growth of the
database log file. For more information on database recovery models, see SQL Server Recovery Models at:
http://msdn.microsoft.com/en-us/library/ms189275.aspx.
1. Perform a tail log backup of the database being restored. You can do this with a normal log
backup command if the database is online. If the database is offline you may need to specify
additional clauses to complete the log backup and restore operations. For more information on
Tail-Log Backups see the Microsoft site: http://msdn.microsoft.com/en-us/library/ms179314.aspx
2. Determine the database Smart Copy closest to the time of the failure for the restore operation.
Once determined, use the most appropriate in-place restore method (Restore selected databases
or Restore All) and check the Apply Logs button to place the database into a “restoring” state after
the Smart Copy restore operation.
3. Starting with the first transaction log backup that was created after the Smart Copy was restored,
restore the logs in sequence with NORECOVERY. After the last log has been applied (tail-log from
step 1), completely restore the database WITH RECOVERY to bring the database online fully
restored. The following script is an example of this process.