Recover a Database Using
Replay Manager and Transaction Log Backups
Replay Manager Replays can be used with transaction
log backups to recover a Microsoft SQL Server database to a specific
point in time. Replay Manager provides a Do Not Recover Databases
option to restore a database and leave the database in an unrecovered
state. You can then apply transaction log backups to the restored
database.
Steps Restore a database, and leave the database
in an unrecovered state. Follow the instructions described in Restore SQL Server
Components without Recovering the Database . You can also rename
and relocate the databases. Restore transaction log backups for each recovered
database.
Open the SQL Server Management Studio, and
connect to the SQL Server instance.
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 documentation.
Complete the recovery process for each
database using the following T-SQL command:
RESTORE DATABASE [ [database_name ] ] WITH RECOVERY;
Data is not available for the Topic
All fields are required unless marked otherwise.
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.
Thank you for your feedback.