Performing a point-of-failure recovery – HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses User Manual
Page 67
Determining Whether You Can Perform a Point-of-Failure Recovery
You can perform a point-of-failure recovery, in which a database is completely recovered up to
the point of the failure, if the following are all true:
•
You have performed a full backup of the SQL database.
•
You have subsequently used the SQL backup utility to perform one or more transaction log
backups.
•
You have access to undamaged transaction log backups and active transaction logs (i.e.,
even if one or more transaction log backups are damaged, undamaged copies of these
backups exist).
NOTE:
A transaction log backup is a copy of all the log records written to the live transaction
log after the last full database backup or the last transaction log backup. If any transaction log
backups within the sequence are missing, the database can only be restored to the last consecutive
backup that exists in the sequence, and you cannot perform a full recovery.
For more information on how to roll a database forward using a transaction log, see:
Performing a Point-of-Failure Recovery
When you apply the backed-up transaction log to a database that has been restored using a virtual
copy, the system uses the STOPAT option to roll forward the database to a specific point in time.
To roll forward the transaction log, you can use either SQL Server Management Studio or a
command line tool such as OSQL. For example:
To perform a point-of-failure recovery:
1.
Locate the most recent consistent full backup and determine the following information:
•
Timestamp (e.g., 010106000000)
•
Server name (e.g., SQLserver01)
•
SQL instance name (e.g., SQLInstan01)
•
Database name (e.g., northwind)
2.
At the command prompt, enter the following:
RMSql.exe restore -s server name -i SQL instance name -d database
name -t timestamp -norecovery
For example:
RMSql.exe restore -s SQLserver01 -i SQLInstan01 -d northwind -t
010106000000 -norecovery
Recovering All Data with Point-of-Failure Recovery
67