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

by

Troubleshooting Guide: SQL Server Error 3011 – “All Backup Devices Must Be of the Same General Class”

Why This Error Happens

This error occurs when a single BACKUP or RESTORE statement references multiple backup devices that are not of the same physical type, such as mixing a disk device with a tape device, or combining a logical backup device with a URL (Azure Blob) target. SQL Server 2025 requires all devices listed in the TO or FROM clause of a backup/restore command to belong to the same “general class” (disk, tape, or URL) because the underlying I/O stream handler cannot interleave writes across heterogeneous media types. This often happens after a server migration to Windows Server 2025 where old scripts still reference legacy tape devices or mismatched UNC paths alongside local disk paths.

Step-by-Step Resolution Guide

Step 1: Identify the Backup Devices in the Failing Script

  • Open the T-SQL script or SQL Agent Job step that triggered Error 3011.
  • Look at the BACKUP DATABASE ... TO clause and list every device referenced (e.g., DISK = 'D:\Backups\file1.bak', TAPE = '\\.\Tape0', or URL = 'https://...').
  • Run EXEC sp_helpdevice; in SSMS to check if any referenced logical devices are mapped to inconsistent physical types.

Step 2: Normalize the Device Types

  • Rewrite the script so that all devices are the same class—preferably DISK, since tape hardware is largely deprecated on Windows Server 2025.
  • Example corrected syntax:
  BACKUP DATABASE [YourDB]
  TO DISK = 'D:\Backups\YourDB_1.bak',
     DISK = 'D:\Backups\YourDB_2.bak'
  WITH FORMAT, COMPRESSION;
  • If using Azure Blob Storage, ensure every device in the clause uses URL = exclusively—do not mix URL with DISK or TAPE.

Step 3: Update SQL Agent Jobs and Maintenance Plans

  • Navigate to SQL Server Agent > Jobs in SSMS and edit any job step containing the legacy backup command.
  • Open Maintenance Plans (if used) in SSMS, double-click the Back Up Database Task, and check the Destination tab to confirm only one device type is selected.
  • Remove any obsolete tape device references under Server Objects > Backup Devices in Object Explorer.

Step 4: Validate File Paths and Permissions on Windows Server 2025

  • Confirm the SQL Server service account has write access to the target disk path via icacls "D:\Backups".
  • If using a UNC path, ensure it is not accidentally mixed with a local path in the same statement, as SQL Server treats some UNC configurations differently under Windows Server 2025 hardening policies.

Alternative or Verification Steps

  • Run the corrected BACKUP DATABASE command manually in SSMS and confirm it completes with “Processed X pages” and no Error 3011.
  • As an alternative, split the backup into separate sequential statements per device class if mixed-media backup (disk + cloud) is a hard requirement, since SQL Server cannot combine them in a single striped set.