Home

Error 4305 - an earlier transaction log backup is required

Prev Page Next Page
Introduction
Recovery models
Main backup types
Backing up the database files by copying
The transaction log
Transaction log restore sequence
Log sequence numbers
Truncating and shrinking the transaction log
Backing up the tail
Inside the transaction log
So, what's in a backup file?
Test: A full backup does not contain deleted data
Verifying backup files
Verifying backup files on a budget
Cumulative backups
Recovering individual tables
Backup and restore history details
Backup reads and writes
Speeding up backups
Backup speed details
Speeding up restores
Restore state affects speed too
Backup and restore rights
Log shipping
Log shipping in SQL Server 2000
Setting up log shipping using Enterprise Manager
Checking the set up
Failover
Log shipping in SQL Server 2005
Setting up log shipping using Management Studio
Checking the set up
Log shipping status report
Failover
Log shipping in SQL Backup
Using the CopyTool utility
Failover
3rd party backup applications
VDI
VDI versions
VDI errors
SQL Backup - beyond compression
Restoring a chain of transaction log backups
Restoring to the latest possible state
Backing up multiple databases
Backup retention
Making a copy of the backup file
Backup file naming conventions
Restoring the latest backup set
Network resilience
Encryption
Integrated database verification
Database file relocation
Improved backup retention
RESTORE HELP
High-availability group support
Common SQL Backup issues
Installation checklist
Setting up rights
Configuring service rights
Backup data
Hanging issues
Common backup and restore errors
Error 3201 - when performing a backup to a network share
Full database backup file is larger than database size
Error 3205 - Too many backup devices specified for backup or restore
Error 4305 - an earlier transaction log backup is required
Bringing a database that is in recovery or read-only mode online
Using bulk-logged recovery model but transaction log backup is still large
Error 14274 - unable to delete SQL Server Agent job
Error messages when restoring from different versions of SQL Server.
Pending
vdi error codes
Restore speed details
Help, my transaction log file is huge!
Mirror or log ship




What

You attempt to restore a transaction log and you receive an error similar to the following:

Server: Msg 4305, Level 16, State 1, Line 1
The log in this backup set begins at LSN 188000000107200001, which is too late to apply to the database. An earlier log backup that includes LSN 188000000105900001 can be restored.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.


How

There are one or more transaction log backups that need to be restored before the current transaction log backup.  In the example above, you will need to first restore a transaction log backup that contains LSN 188000000105900001.

If you have access to the server where the backup was made, and assuming that the backup and restore history tables still contain the data, you can run the following query to list out the transaction log backups that need to be restored in sequence (replace the database name with your database name):

SELECT b.physical_device_name, a.backup_start_date
FROM msdb..backupset a
INNER JOIN msdb..backupmediafamily b ON a.media_set_id = b.media_set_id
WHERE a.database_name = 'pubs'
 AND a.type = 'L'
 AND a.first_lsn <= 188000000105900001
 AND a.last_lsn >= 188000000105900001
UNION ALL
SELECT b.physical_device_name, a.backup_start_date
FROM msdb..backupset a
INNER JOIN msdb..backupmediafamily b ON a.media_set_id = b.media_set_id
WHERE a.database_name = 'pubs'
 AND a.type = 'L'
 AND a.first_lsn > 188000000105900001
ORDER BY 2

If you do not have access to the backup history tables, or if the data has been purged, you'll need to inspect the header of each backup file in find out the LSNs that are contained therein e.g.

RESTORE HEADERONLY FROM DISK = 'g:\backups\pubs_log_20080521 1020.bak'

You will need to start restoring from the backup set where LSN 188000000105900001is backed up in.  You use the FirstLsn and LastLsn values for reference.

Document history
7/24/2008    Initial release.    
 
Copyright 2008 - 2017 Yohz Ventures Sdn Bhd. All rights reserved.
All product and company names are trademarks or registered trademarks of their respective owners.