How to fix Error 3129 on Windows Server 2025 / Windows 11

by

Why This Error Happens

Error 3129 occurs when SQL Server detects that a backup file’s internal structure or sequence header does not align with the expected state for continuing a restore operation (such as attempting to apply a differential or log backup out of order, or against a database not currently in the RESTORING state). This typically stems from a corrupted or truncated backup file, an incorrect restore sequence (e.g., applying a log backup before the full backup with NORECOVERY), or the target database having already exited recovery mode. It can also occur if the backup file (%ls) was overwritten, moved, or written by an incompatible/mismatched SQL Server version.

Step-by-Step Resolution Guide

Step 1: Verify the Restore Sequence Order

  • Confirm the full backup was restored first using WITH NORECOVERY.
  • Check that differential and transaction log backups are being applied in the exact chronological order they were created.
  • Run RESTORE HEADERONLY FROM DISK = 'C:\Backups\YourFile.bak' to inspect the BackupType and Position columns and validate sequence integrity.

Step 2: Check Database Recovery State

  • Query SELECT name, state_desc FROM sys.databases WHERE name = 'YourDB'; to confirm the database is still in RESTORING state.
  • If the state shows ONLINE, the recovery chain was already completed or broken — you must restart the restore sequence from the full backup.
  • On Windows Server 2025, ensure no automated maintenance plan or Agent Job triggered an unintended RESTORE WITH RECOVERY mid-sequence.

Step 3: Validate Backup File Integrity

  • Run RESTORE VERIFYONLY FROM DISK = 'C:\Backups\YourFile.bak'; to check for corruption.
  • If the command fails, the file is likely truncated or damaged — locate a fresh copy from your backup repository or Azure Blob storage target.
  • Check file permissions under C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Backup\ to ensure the SQL Server service account has Read access (NTFS permissions issue can cause partial reads that mimic corruption).

Step 4: Restart the Restore From a Clean Full Backup

  • Drop the partially restored database using DROP DATABASE YourDB; if it’s stuck in an inconsistent state.
  • Re-initiate the full restore chain: RESTORE DATABASE YourDB FROM DISK = 'FullBackup.bak' WITH NORECOVERY;
  • Reapply each subsequent differential/log backup individually, verifying success at each step before proceeding to the next file.

Step 5: Check for Version or Compatibility Mismatch

  • Confirm the backup file was created on SQL Server 2025 or an older, compatible version (SQL Server cannot restore backups from a newer major version onto an older instance).
  • Review the SQL Server Error Log (C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for additional context tied to Error 3129.

Alternative or Verification Steps

  • After completing the sequence, run RESTORE DATABASE YourDB WITH RECOVERY; and confirm the database status changes to ONLINE via sys.databases.
  • If the error persists despite a clean sequence, use DBCC CHECKDB on the source database (if still accessible) to rule out corruption at the source, and consider re-generating the backup chain entirely with BACKUP DATABASE ... WITH CHECKSUM to catch future corruption early.