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

by

Troubleshooting Guide: SQL Server Error 3078

Why This Error Happens

Error 3078 occurs when the BACKUP or RESTORE statement references a file path or device name that SQL Server cannot parse as valid for the specified device type (DISK, TAPE, or URL). This is typically caused by malformed UNC paths, incorrect or missing file extensions, illegal characters in the filename, or a mismatch between the device type keyword and the actual path format provided. It can also occur when a backup device alias was created incorrectly in sys.backup_devices or when attempting to use a URL path without the proper WITH FORMAT, MEDIANAME syntax for Azure Blob Storage backups.

Step-by-Step Resolution Guide

Step 1: Validate the File Path and Syntax

  • Confirm the BACKUP statement uses correct syntax: BACKUP DATABASE [YourDB] TO DISK = 'C:\Backups\YourDB.bak'
  • Ensure there are no illegal characters (such as *, ?, <, >, |) in the file name.
  • Verify the path uses a full, absolute path rather than a relative one.
  • If using a UNC path, confirm the format is \\ServerName\ShareName\FileName.bak with no trailing slashes or typos.

Step 2: Check Device Type Consistency

  • Ensure the device type keyword (DISK, TAPE, URL) matches the actual destination.
  • For local or network backups, always use DISK = 'path', never URL unless targeting Azure Blob Storage.
  • If backing up to URL (Azure), confirm the format is URL = 'https://<account>.blob.core.windows.net/<container>/<filename>.bak' and that a valid SQL credential and Shared Access Signature (SAS) exist.

Step 3: Verify Backup Device Registration (If Using Logical Devices)

  • Run SELECT name, physical_name FROM sys.backup_devices; to confirm the logical device name maps to a valid physical path.
  • If the mapping is broken or missing, drop and recreate the device:
  • EXEC sp_dropdevice 'OldDeviceName';
  • EXEC sp_addumpdevice 'disk', 'NewDeviceName', 'C:\Backups\NewDevice.bak';

Step 4: Confirm Folder Existence and Permissions

  • Open File Explorer or PowerShell on the Windows Server 2025 host and confirm the target directory (e.g., C:\Backups\) actually exists.
  • If it does not exist, create it manually since SQL Server will not auto-create missing directories.
  • Verify the SQL Server service account has Write permissions on the folder via Properties > Security tab.

Step 5: Test with a Simplified Path

  • Temporarily run the BACKUP command using a simple local path like C:\Temp\Test.bak to isolate whether the issue is path-specific or syntax-specific.
  • If the simplified path succeeds, the original issue is confirmed to be in the complex path/UNC structure, not permissions.

Alternative or Verification Steps

  • Run RESTORE VERIFYONLY FROM DISK = 'C:\Backups\YourDB.bak'; to confirm the backup file is valid and readable after the fix.
  • If the error persists only on UNC paths, switch the SQL Server service account from “Local System” to a domain account with explicit network share permissions, as Local System often cannot authenticate against network shares.