3PAR Recovery Manager 3.0.2 for Microsoft SQL Server User’s Guide
The full recovery model allows you to restore a database to a specific point in time. For
example, you can restore a database to a specific time just before a failure occurs. With the full
recovery model, no data is lost because the transaction logs are saved until the failure occurs.
The bulk-logged recovery model is used for high-performance operations and involves bulk
copying and bulk data modification.
The Recovery Manager supports both recovery from Tape and from Virtual Copy directly. Point-
in-time recovery and point-of-failure recovery are only supported on recovery from Virtual
Copy.
The Recovery Manager does the restore through Volume Shadow Copy Service (VSS)
framework. Because the VSS framework takes the database offline and allows the requestor to
do a restore operation, placing the database in a single-user mode would no longer be
necessary.
WARNING: When taking the database offline, the SQL server writes a checkpoint
record in the database ID 9. When the log file is full, the database cannot be
taken offline. You need to back up the transaction log for the database to free up
some log space or you can detach the database and then perform the restore.
8.1.1 Point-In-Time Recovery
Point-in-time recovery is useful for recovering from logical errors. For example, if you
accidentally altered an entry or deleted a table, you can restore your instance or database back
to a consistent, known prior state with a snapshot. Point-in-time recovery restores the instance
or database to the state at the time of the last backup.
You can perform a file copy restore or a volume restore with Recovery Manager for SQL. Use
the RMSql restore command to perform restore operations. For details about the RMSql
restore command, see Recovery Manager Commands on page 7.3.
■
For standalone SQL production servers in a non-clustered environment, issue a file copy
restore or volume restore command to perform a point-in-time recovery. You will need to
schedule some downtime to perform this recovery because during the restore operation
the SQL services will be temporarily stopped.
■
Due to the sensitive nature of clustered environments, performing restore operations
within MSCS environments requires a set of procedures. Please carefully follow the step-by-
step instructions in sections 8.1.3 and 8.1.4 to perform restore operations in an MSCS
environment.
8.2
Recovery
3PAR Confidential

---

...

Otros modelos de este manual:
Software - HP 3PAR StoreServ Application Suite for Microsoft SQL Media (1.75 mb)