Comments
3 comments
-
Hi Kishore,
As the error messge says, there is an earlier log file that the tool believes can be restored and with this being log shipping, something would suggest to me that for whatever reason the transaction logs in the network share aren't being moved out of it when they have completed the restore.
Is the log with LSN 38052000000181500001 still in the network share? Also, have you specified the MOVETO command as somewhere on the target server that isn't a network share?
Pete -
Resolved
I have moved all log files to other folder except old tlog and forced restore job..Succesfull
Thanks -
Hi Kishore,
Glad this is all working now for you.
Pete
Add comment
Please sign in to leave a comment.
Got below alert, please letme know next steps
ERRORS AND WARNINGS
11/18/2009 5:33:00 PM: Warning 170: Log files are not in sequence: 'LOG_AM_MOS_20091118170000.sqb' and 'LOG_AM_MOS_20091118171800.sqb'
11/18/2009 5:33:00 PM: Restoring AM_MOS (transaction logs) from:
11/18/2009 5:33:00 PM: \\192.168.22.11\TranLogs\LOG_AM_MOS_20091118170000.sqb
11/18/2009 5:33:00 PM: RESTORE LOG [AM_MOS] FROM VIRTUAL_DEVICE = 'SQLBACKUP_A04EE669-990A-4461-AE4F-46B3CA9C3943' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , STANDBY = N'D:\MSSQL.1\MSSQL\Backup\UNDO_AM_MOS.dat'
11/18/2009 5:33:00 PM: SQL Server error
11/18/2009 5:33:00 PM: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
11/18/2009 5:33:00 PM: SQL error 4305: SQL error 4305: The log in this backup set begins at LSN 38052000000182100001, which is too recent to apply to the database. An earlier log backup that includes LSN 38052000000181500001 can be restored.