Problem with restores

Hi,

I'm currently trialling SQL Backup, and am running through a number of standard operations to make sure everything works as expected. Twice now doing test restores on dbs in full recovery mode, the job has reported success but I see a failure in the Activity History for the final transaction log restore. The database in question ends up stuck at Restoring, until I issue a RESTORE DATABASE dbname WITH RECOVERY. The main error in the log for the transaction log restore seems to be 'Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)'

Thanks,

Jeremy
Tagged:

Answers

  • Full errors and warnings section of log:

    ERRORS AND WARNINGS



    15/12/2017 12:09:54: Restoring Twitter_Verification (transaction logs) from:
    15/12/2017 12:09:54: d:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Backup\LOG_(local)_Twitter_20171215_113103.sqb

    15/12/2017 12:09:54: RESTORE LOG [Twitter_Verification] FROM VIRTUAL_DEVICE = 'SQLBACKUP_75CF1613-98F2-4D6F-B4EA-92DFEAFD30BA', VIRTUAL_DEVICE = 'SQLBACKUP_75CF1613-98F2-4D6F-B4EA-92DFEAFD30BA01', VIRTUAL_DEVICE = 'SQLBACKUP_75CF1613-98F2-4D6F-B4EA-92DFEA
    FD30BA02' WITH BUFFERCOUNT = 18, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576 , RECOVERY, MOVE 'ADImport' TO 'd:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Data\Twitter_Verification_ADImport.mdf', MOVE 'ADImport_log' TO 'd:\Program
    Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Data\Twitter_Verification_ADImport_log.ldf', REPLACE

    15/12/2017 12:09:54: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
    15/12/2017 12:09:54:
    15/12/2017 12:09:54: Thread 1 error:
    Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
    15/12/2017 12:09:54:
    15/12/2017 12:09:54: Thread 2 error:
    Process terminated unexpectedly. Error code: -2139684860 (An abort request is preventing anything except termination actions.)
    15/12/2017 12:09:54:
    15/12/2017 12:09:54: SQL error 3013: RESTORE LOG is terminating abnormally.
    15/12/2017 12:09:54: 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.
  • Eddie DEddie D Posts: 1,733 Rose Gold 5
    Hi Jeremy,
    Thank you for your forum post.

    From the log information you kindly supplied, this SQL error appears to be the cause of this problem:
    15/12/2017 12:09:54: 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
    
    .

    Has the database Recovery model been changed back to Nonrecovery model before you executed the job? Or have you changed the recovery model to simple and back to full or bulk-logged? These actions will break the LSN (Log sequence number) sequence.

    When restoring the transaction log, it requires a continuous LSN. This is one possible cause for you issue. The database can be initialized by restoring a full backup of the database.

    Many Thanks
    Eddie
    Eddie Davis
    Senior Product Support Engineer
    Redgate Software Ltd
    Email: [email protected]
  • Thanks Eddie, I had been fiddling about with the recovery models of these databases to provide a variety of scenarios as part of my trial. All looks good now.
Sign In or Register to comment.