-
Title
Error: "The restore operation cannot proceed because the secondary database is not in NORECOVERY/ -
Description
Eror may display:
"10/10/2011 10:20:00,LSRestore_SERVERNAME_AdventureWorks,Error,1,SERVERNAME\INST1,LSRestore_SERVERNAME_AdventureWorks,Log shipping restore log job step.,,Executed as user: SERVERNAME\SYSTEM. The step failed.,00:00:03,0,0,,,,0
10/10/2011 10:20:00,LSRestore_SERVERNAME_AdventureWorks,Unknown,1,SERVERNAME\INST1,LSRestore_SERVERNAME_AdventureWorks,Log shipping restore log job step.,,2011-10-10 10:20:03.59 *** Error: The restore operation cannot proceed because the secondary database 'AdventureWorks' is not in NORECOVERY/STANDBY mode.(Microsoft.SqlServer.Management.LogShipping) ***<nl/>2011-10-10 10:20:03.62 Deleting old log backup files. Primary Database: 'AdventureWorks'<nl/>2011-10-10 10:20:03.62 The restore operation completed with errors. Secondary ID: '3fb8605f-6027-496a-822c-ddbf932a57a5'<nl/>2011-10-10 10:20:03.62 ----- END OF TRANSACTION LOG RESTORE -----<nl/><nl/>Exit Status: 1 (Error),00:00:03,0,0,,,,0"
-
Cause
The restored (Subscriber or destination) database is not in recoverymode/standby mode.
-
Resolution
WORKAROUND:
In SSMS, Object explorer is the pane in left hand side of the SQL Server Management Studio, where you see the list of databases. Tight click on the Database | Properties | options verify the recovery model of the Subscriber or destination database. It must be in NORECOVERY/STANDBY mode. -
Additional Information
While this error may appear during LiteSpeed Log Shipping, the root cause is the configuration in SQL Server.