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

by

Troubleshooting Guide: SQL Server Error 3053 — Backup Detected a Page Error

Why This Error Happens

Error 3053 occurs when SQL Server’s backup process encounters a damaged or unreadable page in the database file, typically caused by underlying disk corruption, a failing storage subsystem, or an improperly shut down database. This can also result from bit-level corruption introduced by faulty I/O drivers, antivirus interference, or power loss during a write operation. In most cases, this indicates that CHECKSUM or TORN_PAGE_DETECTION has flagged inconsistencies between the expected and actual page content on disk.

Step-by-Step Resolution Guide

Step 1: Run DBCC CHECKDB to Identify Corruption Scope

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Execute: DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Review the output for specific page IDs and allocation unit errors to determine severity.

Step 2: Verify Storage and Hardware Health

  • Check Windows Event Viewer under Windows Logs > System for Disk or NTFS warnings (Event ID 7, 11, or 51).
  • On Windows Server 2025 / Windows 11, run chkdsk C: /f /r (replace drive letter as needed) during a scheduled restart.
  • Confirm SAN/RAID controller firmware and drivers are up to date, especially if using virtualized storage (Hyper-V or VMware).

Step 3: Restore from a Clean Backup

  • Locate the last known good full backup file, typically stored in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Backup\.
  • Execute: RESTORE DATABASE [YourDatabaseName] FROM DISK = 'C:\Backup\YourDatabase.bak' WITH REPLACE, RECOVERY;
  • If differential or log backups exist, apply them sequentially using WITH NORECOVERY until the final restore.

Step 4: Repair Corruption if No Clean Backup Exists

  • As a last resort, run: DBCC CHECKDB ('YourDatabaseName', REPAIR_ALLOW_DATA_LOSS);
  • Ensure the database is set to SINGLE_USER mode first using: ALTER DATABASE [YourDatabaseName] SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
  • Revert to MULTI_USER mode once repairs are complete.

Alternative or Verification Steps

  • Re-run the original BACKUP DATABASE command and confirm it completes without Error 3053 or related checksum warnings.
  • If corruption persists after repair, consider migrating the database to new storage hardware and performing a full DBCC CHECKDB scan before re-enabling production workloads.