SQL Server Recovery Issues
Applies To: System Center Data Protection Manager 2010
The following table provides troubleshooting guidance on recovery issues for computers running SQL Server.
SQL Server Recovery Issues
| Issue | Possible Cause | Resolution |
|---|---|---|
Unable to recover from secondary server because replica is in inconsistent state. |
If the database you are trying to recover was collocated, and protection for one of them was stopped on the primary server and its data deleted, then you cannot recover the deleted database from the replica on the secondary. |
Run a consistency check on the replica volume. |
The database recovery fails. |
If you recover a SQL Server database by selecting the latest recovery point and then perform another recovery using the latest recovery point, the database recovery will fail. |
When you recover a SQL Server database using the latest recovery point, DPM performs the recovery using the SQL Server logs that are available on the protected server. After you recover the database, you cannot perform another recovery using the latest recovery point until you perform a synchronization with consistency check. However, you can recover to a recovery point listed just prior to the latest recovery point. In this case, you will recover the database to the latest available recovery point on the DPM server; however, the logs on the SQL Server will not be utilized. This is because the logs on the SQL Server were already used as part of the latest point recovery that you performed earlier. |