Administrator Guide

b. Open a query window and use the following T-SQL command to restore transaction logs to each
database:
RESTORE LOG [ [database_name] ] FROM DISK = ’ [log_backup_file] ’ WITH NORECOVERY;
In addition, the following optional clauses can be used:
• To recover the database to a point in time between transaction log backups, use the STOPAT
clause.
• To recover the database to a specific log sequence number (LSN), use the STOPATMARK or
STOPBEFOREMARK clause.
NOTE: Transaction log backups must be restored in order.
For more information on restoring transaction log backups, see the Microsoft SQL Server Books
Online documentation.
c. Complete the recovery process for each database using the following T-SQL command:
RESTORE DATABASE [ [database_name] ] WITH RECOVERY;
Related links
Restore SQL Server Components without Recovering the Database
Recover System Databases
The Expose action in Replay Manager can be used as part of a recovery plan for the following system
databases: master, model, and msdb. Use Replay Manager to recover these system databases by
manually copying system database files from exposed volumes back to their original location.
NOTE: This method will recover the system databases back to the point in time that the restore
point was created. Any modifications to the system databases (such as adding or removing users)
performed after the restore point was created will need to be manually repeated. In addition, any
databases created after the restore point will be missing. You can reattach these databases.
1. Expose a restore point that contains the system databases to recover.
NOTE: Do not select the Make exposed volumes writable option.
2. Shut down the SQL Server service.
3. Using the Windows Explorer, copy the files from the exposed volumes or SMB file shares containing
the system database files to the original location, replacing any existing files.
4. Start the SQL Server service.
Related links
Expose a Restore Point (Windows Extensions Only)
Expose a Restore Point Stored on an SMB File Share
Recovering Databases in a Clustered Instance of SQL Server
Replay Manager can be used to recover databases that are part of a clustered instance of SQL Server.
When using Replay Manager in a cluster, recovery must be performed on the node that owns the
instance of SQL Server.
There are two ways to recover databases in a clustered instance of SQL Server:
• Restore: The Restore action functions the same in clustered and non‐clustered environments.
However, if the rename and relocate functionality is used, the new paths must reside on the SQL
Server instance’s clustered disks.
53