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

by

Why This Error Happens

This error occurs because the BACKUP statement is pointing to a path or logical device that resides on a volume mapped to a FILESTREAM filegroup. SQL Server 2025 explicitly blocks FILESTREAM containers from being used as a backup target because the storage format for FILESTREAM data is incompatible with the standard backup media set structure. This typically happens when a DBA reuses a data drive letter/path for both FILESTREAM storage and ad-hoc backup scripts, or when a backup device was created against a folder that was later converted into a FILESTREAM container.

Step-by-Step Resolution Guide

Step 1: Identify the Conflicting Path

  • Run sys.database_files or sys.master_files to cross-reference the physical path used in your BACKUP DATABASE command.
  • Look for a type_desc of FILESTREAM on that same drive or directory path.
  • Confirm via SSMS: Right-click Database → Properties → Filegroups → check the “FILESTREAM” column for the path in question.

Step 2: Redirect the Backup Destination

  • Modify your T-SQL script to point to a standard NTFS path that does not host FILESTREAM data. Example:
  BACKUP DATABASE [YourDB] 
  TO DISK = N'D:\SQLBackups\YourDB.bak' 
  WITH INIT, COMPRESSION;
  • Ensure D:\SQLBackups is a dedicated backup volume, separate from E:\FILESTREAM_Data or similar FILESTREAM-mapped drives.
  • If using a Backup Device object instead of DISK, drop and recreate the device pointing to the corrected path using sp_addumpdevice.

Step 3: Audit and Correct Existing Backup Devices

  • Query sys.backup_devices to list all logical devices currently registered on the instance.
  • Cross-check each physical_name against your FILESTREAM filegroup paths identified in Step 1.
  • Remove any invalid devices using sp_dropdevice 'DeviceName' and recreate them with a clean, non-FILESTREAM path.

Step 4: Validate Windows Server 2025 / Windows 11 Storage Permissions

  • Confirm the SQL Server service account has Write/Modify NTFS permissions on the new backup path (D:\SQLBackups) via File Explorer → Properties → Security tab.
  • Verify the volume isn’t a ReFS volume formatted specifically for FILESTREAM (SQL Server 2025 enforces stricter volume-role checks on ReFS vs NTFS).
  • Restart the SQL Server (MSSQLSERVER) service via services.msc if permission changes were applied.

Alternative or Verification Steps

  • Re-run the exact BACKUP DATABASE or BACKUP LOG statement targeting the new path; a successful completion message (percentage processed to 100%) confirms resolution.
  • As an alternative, use the Maintenance Plan Wizard in SSMS to configure the backup task via GUI—this automatically filters out FILESTREAM-enabled paths from the destination picker, preventing recurrence of Error 3055.