Administrator Guide
Table Of Contents
- Replay Manager Version 8.0 Administrator’s Guide
- About this Guide
- Overview
- Installing Replay Manager Components
- Licensing for Replay Manager
- Install Replay Manager Service for Windows
- Installing Replay Manager Service for VMware
- Install Replay Manager Management Tools
- Install Replay Manager Service for Windows on Windows Server Core
- Installing and Configuring the Verification Service for Exchange
- Using Replay Manager Service on Clustered Servers
- Configure an HTTP Proxy Service
- Getting Started
- Backing Up and Restoring Data
- Using the Replay Manager Explorer
- Understanding Backup Types
- Summary of Backup Set Actions
- Summary of Backup Set Options
- Creating and Running Backups
- Managing Existing Backup Sets
- Managing Restore Points and Restoring Data
- Restoring Data
- Display Restore Points for a Component
- Restore Data to its Original Location
- Restore SQL Server Components without Recovering the Database
- Rename and Restore SQL Server Components Stored on a Volume
- Rename and Restore SQL Server Components Stored on an SMB File Share
- Expose a Restore Point (Windows Extensions Only)
- Expose a Restore Point (VMware Extensions Only)
- Expose a Restore Point Stored on an SMB File Share
- Resync a Restore Point (Windows Extensions Only)
- Make an Exposed Restore Point Writable (Windows Extensions Only)
- Unmanage an Exposed Restore Point (VMware Extensions Only)
- Unexpose an Exposed Restore Point
- Add a Note to a Restore Point
- Edit a Note for a Restore Point
- Unimport a Restore Point
- Delete a Restore Point
- Prevent a Restore Point from Expiring (Force Keep)
- Allow a Restore Point to be Automatically Expired (Allow Auto-Deletion)
- Transport a Restore Point
- Advanced Recovery Scenarios for SQL Server
- Locating Replays on a Storage Center
- Working with Backup Set Jobs
- Viewing Backup Job Reports
- Replay Manager Best Practices
- Using Replay Manager Cmdlets
- Troubleshooting
Related tasks
Restore SQL Server Components without Recovering the Database on page 38
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 tasks
Expose a Restore Point (Windows Extensions Only) on page 40
Expose a Restore Point Stored on an SMB File Share on page 40
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.
● Expose: The Expose action functions the same in clustered and non‐clustered environments. However, in a clustered
environment, there are additional manual steps required before databases can be attached from the exposed volumes. To
attach a database in a clustered instance of SQL Server, the database files must reside on clustered disks that the SQL
Server instance is dependent on. Because the disks created by the Expose action are local disks, they must be manually
converted to clustered disks and a dependency on those disks must be added to the SQL Server application before
databases can be attached.
Use Restore to Recover Databases in a Clustered Instance of SQL Server
A clustered instance of SQL Server uses the restore action to recover databases.
NOTE: The new paths must reside on the SQL Server instance’s clustered disks.
Related tasks
Restore Data to its Original Location on page 38
Use Expose to Recover Databases in a Clustered Instance of SQL Server
Expose the restore point containing the databases to be recovered.
1. On the Expose dialog box:
a. Select Make exposed volumes writable.
Backing Up and Restoring Data
45