User's Manual

8.3
Recovery
3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
3PAR Confidential
8.1.2 Point-Of-Failure Recovery
A point-of-failure recovery can be achieved when a full backup of the SQL database has been
performed and has been followed by a log backup. This type of recovery is useful for
customers who cannot afford to lose any data in the event of a system failure. As long as the
transaction logs were not damaged, this function can be used to recover the database up to
the point of the failure.
Recovery Manager provides manual procedures to perform the point of failure recovery. The
log backup needs to be taken by the DBA, using the SQL backup utility before this option can
be exercised. Applying the transactions log to snapshot backups, allows a database restoration
from a snapshot backup to be rolled-forward to an arbitrary point in time using the STOPAT
option. To roll forward the transaction log, the DBA can use either the SQL Server
Management Studio, or a command line tool such as OSQL. For more information on how to
roll forward with transaction log, see http://msdn.microsoft.com/en-us/library/ms189596.aspx.
Manual procedures to prepare point-of-failure recovery:
 Put the database into non-operation mode.
 Take the database offline.
 Perform a file copy restore on a database with Recovery Manager for SQL. For details about
the
RMSql restore command, see Recovery Manager Commands on page 7.3.
NOTE: Point-of-failure recovery only supports the database level restore and the
file copy restore.
NOTE: A transaction log backup is a copy of all the log records that were written
to the live transaction log after the last full database backup or the last
transaction log backup. Missing any transaction log backups within the sequence
would cause the full recovery to fail.