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

by

Troubleshooting Guide: SQL Server Error 3024 — Differential/Transaction Log Backup Not Permitted on Master Database

Why This Error Happens

SQL Server Error 3024 occurs because the master system database only supports full database backups — it does not support differential backups or transaction log backups. This restriction exists because master operates in the SIMPLE recovery model by design (even if it appears otherwise), meaning SQL Server does not maintain the log chain required for point-in-time or incremental backup operations. The error is typically triggered when a maintenance plan, scheduled job, or manually-run T-SQL script mistakenly applies a BACKUP LOG or BACKUP DATABASE ... WITH DIFFERENTIAL command against master instead of a user database.

Step-by-Step Resolution Guide

Step 1: Identify the Source of the Incorrect Backup Command

  • Check SQL Server Agent Job history in SSMS under SQL Server Agent > Jobs for the specific job step that failed with Error 3024.
  • Review any Maintenance Plans (right-click Maintenance Plans > Reports > View History) to confirm whether master was included in a “Differential Backup” or “Transaction Log Backup” task.
  • If using a custom script, locate the .sql file or SQL Agent job step text and search for BACKUP LOG master or BACKUP DATABASE master ... WITH DIFFERENTIAL.

Step 2: Correct the Backup Script or Maintenance Plan

  • Open the Maintenance Plan in SSMS and remove master from the database selection list under the Transaction Log Backup Task or Differential Backup Task.
  • Ensure master is only included in Full Backup Task plans, scheduled at least daily.
  • If scripting manually, replace the invalid command with a correct full backup syntax:
  BACKUP DATABASE master 
  TO DISK = 'C:\SQLBackups\master_full.bak' 
  WITH INIT, COMPRESSION;
  • Save the corrected plan and redeploy it via SQL Server Agent > Jobs.

Step 3: Verify Backup File Paths and Permissions on Windows Server 2025

  • Confirm the SQL Server service account has write access to the target backup directory (e.g., C:\SQLBackups\) via File Properties > Security tab.
  • Ensure the path exists and is not blocked by Windows Defender or Controlled Folder Access, which can silently fail backup jobs on Windows Server 2025/Windows 11.
  • Restart the SQL Server Agent service from services.msc if job definitions were recently modified, to force a configuration reload.

Step 4: Reschedule master Database Backups Correctly

  • Set up a dedicated Full Backup Only job for master, independent from user database backup plans, since it generally changes infrequently (only after logins, linked servers, or configuration changes).
  • Recommended schedule: nightly or immediately after any server-level configuration change (new login creation, server role changes, etc.).

Alternative or Verification Steps

  • Run RESTORE HEADERONLY FROM DISK = 'C:\SQLBackups\master_full.bak'; to confirm the backup file is valid and was created as a Full backup type (BackupType = 1).
  • If the error persists after correcting the job, run SELECT name, recovery_model_desc FROM sys.databases WHERE name = 'master'; to confirm master is still in SIMPLE recovery model — if it shows FULL or BULK_LOGGED, revert it immediately using ALTER DATABASE master SET RECOVERY SIMPLE;, as this misconfiguration can also contribute to backup confusion.