Log Shipping error

warnerrwarnerr Posts: 2
edited June 16, 2014 8:34PM in SQL Backup Previous Versions
On three databases, I have received this error message:
SQL Backup log file 6.5.2.18
 
-SQL "RESTORE LOG [PayCentre] FROM DISK = 'F:\SQL Backups\LogShipping\PayCentre.SQL02.LOG.*.sqb' WITH ERASEFILES = 12h, FILEOPTIONS = 1, MAILTO_ONERRORONLY = XX@XXXXXX.co.uk', PASSWORD = 'XXXXXXXXXX', STANDBY = 'F:\SQL Backups\UNDO_PayCentre.dat', 
 MOVETO = 'F:\SQL Backups' "
 
-----------------------------  ERRORS AND WARNINGS -----------------------------
 
 
15/06/2014 13:20:03: Restoring PayCentre (transaction logs) from: 
15/06/2014 13:20:03:   F:\SQL Backups\LogShipping\PayCentre.SQL02.LOG.20140615.131500.sqb
 
15/06/2014 13:20:03: RESTORE LOG [PayCentre]  FROM VIRTUAL_DEVICE = 'SQLBACKUP_67EB36D9-145E-4B29-B21B-522FF52BD946' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , STANDBY = N'F:\SQL Backups\UNDO_PayCentre.dat'
 
15/06/2014 13:20:03: Thread 0 error: 
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
15/06/2014 13:20:03: 
15/06/2014 13:20:03: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
15/06/2014 13:20:03: SQL error 4326: SQL error 4326: The log in this backup set terminates at LSN 3523000000143800001, which is too early to apply to the database. A more recent log backup that includes LSN 3523000000145300001 can be restored.
 
 
 
-----------------------  PROCESSES COMPLETED SUCCESSFULLY   --------------------
 
15/06/2014 13:20:03: Warning 470: Transaction log has already been restored.
15/06/2014 13:20:03: Moved PayCentre.SQL02.LOG.20140615.131500.sqb to F:\SQL Backups\.
 
15/06/2014 13:20:13: Deleting old backup file: F:\SQL Backups\PayCentre.SQL02.LOG.20140615.011500.sqb

I am now also getting this error: 
16/06/2014 09:35:07: Restoring PayCentre (transaction logs) from: 
16/06/2014 09:35:07:   F:\SQL Backups\LogShipping\PayCentre.SQL02.LOG.20140615.211500.sqb
 
16/06/2014 09:35:07: RESTORE LOG [PayCentre]  FROM VIRTUAL_DEVICE = 'SQLBACKUP_CDB7AABC-9F88-4E76-AB63-6A29257EBCC3' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , NORECOVERY
 
16/06/2014 09:35:07: Thread 0 error: 
Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
16/06/2014 09:35:07: 
16/06/2014 09:35:07: SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
16/06/2014 09:35:07: SQL error 4330: SQL error 4330: This backup set cannot be applied because it is on a recovery path that is inconsistent with the database. The recovery path is the sequence of data and log backups that have brought the database to a 
 particular recovery point. Find a compatible backup to restore, or restore the rest of the database to match a recovery point within this backup set, which will restore the database to a different point in time.  For more information about recovery 
 paths, see SQL Server Books Online.

Any ideas on how to get around this? What does this mean?

Many thanks in advance.
· Share on Twitter

Comments

  • peteypetey Posts: 2,358 New member
    The first error indicates that the particular trx log backup has already been restored. SQL Backup then raises a warning, and moves the file to the MOVETO location accordingly. This could happen if the previous restore process restored that file, but failed to move the file out to the MOVETO folder, or if another process restored that file without then moving that file out of the folder.

    The second error indicates that the database needs to be on a different recovery path. Which version of SQL Server are you using?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
Sign In or Register to comment.