Fix SQL Server error 4214: no current database backup

Error 4214 means you asked for a transaction log backup, but the database has no full backup for the log chain to start from. Take a full backup and log backups will work again.

The error

Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.

Why it happens

Log backups contain only the changes since the previous log backup. To be restorable, they need a full backup to start from. You get 4214 when:

• The database is new and has never had a full backup.
• The recovery model was switched from SIMPLE to FULL (or BULK_LOGGED). The switch does not start a log chain until the next full backup.
• The database was just restored or recreated under that name.

The fix

BACKUP DATABASE [Sales]
TO DISK = N'D:\SQLBackups\Sales_FULL_20260927.bak'
WITH CHECKSUM, STATS = 10;

-- Log backups now succeed
BACKUP LOG [Sales]
TO DISK = N'D:\SQLBackups\Sales_LOG_20260927_1030.trn'
WITH CHECKSUM;

Check the recovery model and backup history

SELECT d.name, d.recovery_model_desc,
       MAX(CASE WHEN b.type = 'D' THEN b.backup_finish_date END) AS last_full,
       MAX(CASE WHEN b.type = 'L' THEN b.backup_finish_date END) AS last_log
FROM sys.databases d
LEFT JOIN msdb.dbo.backupset b ON b.database_name = d.name
WHERE d.name = N'Sales'
GROUP BY d.name, d.recovery_model_desc;

If the database is in SIMPLE recovery, log backups are not possible at all and you get error 4208 instead. Decide whether you need point-in-time restore. If you do, switch to FULL and take a full backup straight away. If not, stay on SIMPLE and remove the log backup job.

Keep it from coming back

• Have your schedule take a full backup of every new database automatically, not only the ones that existed when the job was created. The script in scheduling SQL Server backups loops over all databases for this reason.
• After changing a recovery model, always take a full backup.
• Avoid breaking the chain. Switching to SIMPLE even briefly breaks it. The next log backup then needs a new full or differential first.