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

by

Troubleshooting Guide: SQL Server Error 3008 – “The Specified Device Type Is Not Supported for Backup Mirroring”

Why This Error Happens

This error occurs when a BACKUP DATABASE statement attempts to use the MIRROR TO clause with a device type that does not support mirroring, such as tape devices, Azure Blob Storage URLs, or certain virtual device interfaces (VDI). SQL Server’s backup mirroring feature is restricted to disk-based devices only, meaning any attempt to mirror to unsupported targets will immediately fail at parse or execution time. This is typically a configuration/syntax issue rather than a permissions or corruption problem, often introduced when backup scripts are migrated from older environments or adapted for cloud storage without accounting for mirroring limitations.

Step-by-Step Resolution Guide

Step 1: Review the Backup Script Syntax

  • Open the T-SQL script or SQL Server Agent job step that triggered the error.
  • Look specifically for the MIRROR TO clause in the BACKUP DATABASE or BACKUP LOG command.
  • Confirm whether the destination specified is a URL (Azure), tape drive, or named pipe — all of which are invalid for mirroring.

Step 2: Replace Unsupported Devices with Local or Network Disk Paths

  • Modify the script so that both the primary TO DISK and MIRROR TO DISK clauses point to valid local or UNC disk paths.
  • Example corrected syntax:
  BACKUP DATABASE [YourDB]
  TO DISK = 'D:\Backups\YourDB_Primary.bak'
  MIRROR TO DISK = 'E:\Backups\YourDB_Mirror.bak'
  WITH FORMAT, MEDIANAME = 'YourDB_Mirror_Set';
  • Ensure the mirror destination resides on a physically separate disk or volume for redundancy purposes.

Step 3: Validate Disk and Folder Permissions

  • Confirm that the SQL Server service account has write access to both the primary and mirror backup folders.
  • On Windows Server 2025, check folder security via Properties > Security > Edit and ensure the NT SERVICE\MSSQLSERVER (or named instance equivalent) account has Write and Modify rights.
  • Run icacls "D:\Backups" from an elevated Command Prompt to verify effective permissions.

Step 4: Check for Mixed Device Types in the Same Backup Set

  • Ensure that all devices listed in the BACKUP statement (primary and mirrors) are of the same type — all disk, not a mix of disk and tape/URL.
  • Remove any mismatched device references and resubmit the job.

Step 5: Restart SQL Server Agent and Re-run the Job

  • After correcting the script, restart the SQL Server Agent service via services.msc or:
  Restart-Service -Name "SQLSERVERAGENT"
  • Re-execute the backup job manually to confirm the error no longer appears in the job history.

Alternative or Verification Steps

  • Run the corrected backup command manually in SQL Server Management Studio (SSMS) and confirm it completes without Error 3008, then check msdb.dbo.backupmediafamily to verify both primary and mirror files were registered successfully.
  • If mirroring to cloud storage is required, abandon the native MIRROR TO clause entirely and instead implement Always On Availability Groups or a secondary backup job that copies the .bak file to Azure Blob Storage after the local backup completes.