What are the challenges you face when working across database platforms? Take the survey

can someone explain this error message...

randyvrandyv Posts: 166
edited April 4, 2007 11:23PM in SQL Backup Previous Versions
Hello -

I've had log shipping turned on for about 1 month now, with no error messages.

This morning I started getting the messages for the same database, like the one below... can someone explain what this is saying?

SQL Backup log file
4/4/2007 11:40:00 AM: Restoring wfr (transaction logs) from:

4/4/2007 11:40:00 AM: RESTORE LOG [wfr] FROM DISK = '\\Whaley03\SHIPPING\LOG_10.1.2.40_(local)_wfr_20070404_093001' WITH NORECOVERY, MAILTO = 'rvolters@whaleyfoodservice.com', ERASEFILES = 10, FILEOPTIONS = 1, MOVETO = 'E:\EPICOR_MDF\SHIPPING\PROCESSED\'

4/4/2007 11:40:00 AM: SQL Server error

4/4/2007 11:40:00 AM: Server: Msg 3013
RESTORE LOG is terminating abnormally.
4/4/2007 11:40:00 AM: Server: Msg 4326
The log in this backup set terminates at LSN 1197000006684500001, which is too early to apply to the database. A more recent log backup that includes LSN 1200000002173500001 can be restored.
What we do in life echoes in eternity <><
Randy Volters


  • Options
    peteypetey Posts: 2,358 New member
    It appears that the log file 'LOG_10.1.2.40_(local)_wfr_20070404_093001' has already been applied to the database. Try using a later log file.

    Actions which may have caused this situation include:

    - a recent full backup was restored, which made the need to restore earlier log files redundant

    - the log file was applied, but was not moved out of the \\Whaley03\SHIPPING folder to the 'E:\EPICOR_MDF\SHIPPING\PROCESSED\' folder. You would need to check the SQL Backup logs for any warnings that were raised at the time the log file was first restored.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.