User's Manual

9.5
Recovering an SQL database from a Secondary Site
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
3PAR Confidential
9.4 Recovering an SQL database from a Secondary Site
In the event of an SQL database crash at a Primary site, you should have a dedicated target
server at the Secondary site, that is setup in an identical manner to the original SQL production
server for recovery purposes. (Same configuration includes: instance names, database names,
structures, and with Windows authentication mode set in the same way as well).
You can use the backup server of Recovery Manager for SQL at the secondary site with the
following procedure:
1 Mount the virtual copy to the production server.
2 Log onto the production server, stop the SQL instance and its dependent services.
3 From the mounted snapshot volumes, manually copy all necessary database and log files to
the corresponding database location.
4 Re-start the SQL instance and its dependent services.
5 Log back onto the backup server, unmount the virtual copy.