Log shipping restore fails

Forum for users of Red Gate SQL Backup tool

Moderator: Chris Auckland

Log shipping restore fails

Postby steiger » Fri Dec 17, 2010 5:10 am

Hi,

We have a scheduled job that's been running fine for quite awhile and now it fails, here's the error and the log file

Summary
The job failed. The Job was invoked by Schedule 205 (Every 15 minutes). The last step to run was step 1 (Step 1). NOTE: Failed to notify 'admin' via email.

Step 1
Executed as user: admin. Mail sent. [SQLSTATE 01000] (Message 17967) SQL Log Shipping Restore Check failed [SQLSTATE 42000] (Error 50000). The step failed.

**************************************************

SQL Backup log file 5.4.0.55

-SQL "RESTORE LOG [FNPRDDB] FROM DISK = '\\\\server\\LOG_20101217_143200.sqb' WITH MOVETO = '\\server2', ERASEFILES = 5, MAILTO_ONERROR = 'admin@contoso.com', NORECOVERY "

----------------------------- ERRORS AND WARNINGS -----------------------------


17/12/2010 2:53:08 PM: Restoring FNPRDDB (transaction logs) on FNDEV instance from:
17/12/2010 2:53:08 PM: \\\\server2\\LOG_20101217_143200.sqb

17/12/2010 2:53:09 PM: RESTORE LOG [FNPRDDB] FROM VIRTUAL_DEVICE = 'SQLBACKUP_6EF14CDB-EE54-4BD3-A50D-3E613E9B0F90' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 262144 , NORECOVERY

17/12/2010 2:53:39 PM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\\SOFTWARE\\Red Gate\\SQL Backup\\BackupSettingsGlobal\\[InstanceName]
17/12/2010 2:53:39 PM: Also check that the database is not currently in use.
17/12/2010 2:53:39 PM: SQL error 3013: RESTORE LOG is terminating abnormally.
17/12/2010 2:53:39 PM: SQL error 4306: The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence, specifying WITH NORECOVERY or WITH STANDBY for all but the final step.
17/12/2010 2:53:39 PM:
17/12/2010 2:53:39 PM: Memory profile
17/12/2010 2:53:39 PM: Type Maximum Minimum Average Blk count Total
17/12/2010 2:53:39 PM: ---------------- ----------- ----------- ----------- ----------- -----------
17/12/2010 2:53:39 PM: Commit 83189760 4096 47363 11611 549941248
17/12/2010 2:53:39 PM: Reserve 15294464 8192 233816 10571 2471673856
17/12/2010 2:53:39 PM: Free 178651136 4096 950213 210 199544832
17/12/2010 2:53:39 PM: Private 83189760 4096 135147 21482 2903244800
17/12/2010 2:53:39 PM: Mapped 29360128 4096 551948 85 46915584
17/12/2010 2:53:39 PM: Image 9928704 4096 116186 615 71454720
17/12/2010 2:53:39 PM:
17/12/2010 2:53:39 PM: Mail sent successfully to:admin

*************************

Thanks in advance
steiger
 
Posts: 1
Joined: Fri Dec 17, 2010 5:05 am

Postby Brian Donahue » Fri Dec 17, 2010 6:20 pm

Hello,

It looks like a simple matter of editing your job step using SSMS.
17/12/2010 2:53:39 PM: SQL error 4306: The preceding restore operation did not specify WITH NORECOVERY or WITH STANDBY. Restart the restore sequence, specifying WITH NORECOVERY or WITH STANDBY for all but the final step.


The script should be specifying the recovery level as one or the other during log shipping, the third option being WITH RECOVERY, which will bring the database back online, effectively ending the log shipping.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Backup Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests