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

by

Troubleshooting Guide: Error 3069 – Striping Not Permitted for File Snapshot Backups

Why This Error Happens

This error occurs because SQL Server’s file-snapshot backup feature (used for instant file snapshot backups on supported storage, such as those leveraging VSS or volume-level snapshot technology) is architecturally limited to a single backup device target. When a backup command specifies multiple TO DISK = or TO URL = clauses in an attempt to stripe the backup set, SQL Server 2025 rejects the operation because snapshot-based backups require a one-to-one mapping between the database and a single snapshot-capable volume or device. This is by design and is not caused by corruption or permissions issues, but rather by an unsupported syntax/configuration combination.

Step-by-Step Resolution Guide

Step 1: Review the Backup Command Syntax

  • Open the T-SQL script or job step that triggered the error.
  • Check for multiple DISK = or URL = arguments inside a single BACKUP DATABASE statement, for example:
  BACKUP DATABASE MyDB TO DISK = 'E:\Backup\file1.bak', DISK = 'F:\Backup\file2.bak'
  • Confirm whether the WITH FILE_SNAPSHOT option is being used alongside this striped configuration, as this combination is what triggers Error 3069.

Step 2: Modify the Backup Statement to Use a Single Device

  • Rewrite the backup command to target only one file or URL destination when using FILE_SNAPSHOT.
  • Example corrected syntax:
  BACKUP DATABASE MyDB TO DISK = 'E:\Backup\MyDB_snapshot.bak' WITH FILE_SNAPSHOT;
  • If backing up to Azure Blob Storage, ensure only a single URL = target is specified in the WITH FILE_SNAPSHOT backup command.

Step 3: Adjust Backup Strategy for Large Databases

  • If striping was being used to manage large database sizes across multiple volumes, evaluate switching to standard (non-snapshot) backups, which support striping.
  • Alternatively, use SQL Server’s native support for Storage Spaces Direct (S2D) or SAN-level snapshots on Windows Server 2025 to handle large volumes without needing multiple backup files.
  • Update any SQL Server Agent Job steps or Maintenance Plan tasks that reference the old multi-device syntax.

Step 4: Validate Storage Configuration

  • Confirm that the underlying storage volume supports file-snapshot technology (e.g., ReFS with Storage Spaces Direct, or a supported SAN snapshot provider) in Windows Server 2025.
  • Check the SQL Server error log and Windows Event Viewer (Application log) for any additional context tied to Event ID 3069 that might indicate a misconfigured snapshot provider.

Alternative or Verification Steps

  • Run the corrected BACKUP DATABASE command manually in SSMS or Azure Data Studio and confirm it completes successfully without Error 3069 appearing in the Messages pane.
  • If a striped backup set is strictly required for performance or storage reasons, remove the WITH FILE_SNAPSHOT clause entirely and perform a traditional multi-file backup instead, since striping is only restricted for snapshot-based backups.