Administrator Guide

NOTE: In a clustered-server environment, transporting a restore point to a node in the same cluster is not supported.
1. In the Server Connections area of the navigation pane, connect to a server or host.
2. In the Backup Extensions area of the navigation pane, select a data source.
3. Select the restore point you want to transfer to another server.
4. In the Transfer Restore Points area of the action pane, click Transport to Server.
The Choose Target Server dialog box opens.
5. Select the server to transfer the restore point to, and click OK. The restore point is transferred to the target server.
NOTE: When the restore point is transported to another server, it is only available on that server even if the server is a
member of a cluster.
NOTE: After restore points are transported, the Restore option is not available in the Restore Points pane. In
addition, the Run Now option in the Backup Set pane is available only if the restore point was originally part of the
Local Volumes extension.
6. To view the transferred restore point:
a. In the Server Connections area of the navigation pane, connect to the server to which you transferred the restore
point.
b. In the Backup Extensions area of the navigation pane, click Local Volumes. The Restore point is displayed with
[Transported] added to the original backup set name.
Related concepts
Adding and Configuring Servers and Hosts on page 20
Related references
Transport-to-Server Scenarios on page 36
Advanced Recovery Scenarios for SQL Server
The following sections describe advanced recovery scenarios for Microsoft SQL Server databases.
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.
1. 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.
2. Restore transaction log backups for each recovered database.
a. Open the SQL Server Management Studio, and connect to the SQL Server instance.
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 documentation.
c. Complete the recovery process for each database using the following T-SQL command:
RESTORE DATABASE [ [database_name] ] WITH RECOVERY;
44
Backing Up and Restoring Data