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

Error restoring empty log

theit8514theit8514 Posts: 8
edited October 14, 2014 12:41AM in SQL Backup Previous Versions
I am experiencing an issue with restoring log files for a relatively inactive database. The database gets updates 3-4 times a day and the rest of the hourly log files have minimal transactions.

This is an older log, but the same error is coming across. When we delete the offending file, the restore continues without error:
SQL Backup v7.3.0.57                                                                                                                                                                                                                                           
Warning 170: No LSN information contained in file: 'LOG_(db)_2014092205.SQB'
Warning 170: Log files are not in sequence: 'LOG_(db)_2014092205.SQB' and 'LOG_(db)_2014092206.SQB'
Restoring (db) (transaction logs) from: 
SQL Server error
SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
SQL error 3254: SQL error 3254: The volume on device 'SQLBACKUP_9F133746-0E9B-4B18-A45C-4CB17CD76E9F' is empty.
SQL Backup exit code: 1100
SQL error code: 3254


  • Options
    peteypetey Posts: 2,358 New member
    SQL Backup generates a log file for each process that it runs. The default folder where the logs are stored is C:Documents and SettingsAll UsersApplication DataRed GateSQL BackupLog<instance name> on Windows 2003 and older, and C:ProgramDataRed GateSQL BackupLog<instance name> on Windows Vista and newer.

    Could you please post the contents of the log file for the backup process that created the file 'LOG_(db)_2014092205.SQB'?

    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.