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

by

Troubleshooting Guide: SQL Server Error 3045 — BACKUP/RESTORE Requires NTFS File System

Why This Error Happens

This error occurs when SQL Server 2025 attempts to perform a backup or restore operation targeting a path that resides on a non-NTFS file system (such as FAT32, exFAT, or a ReFS volume without proper configuration), which does not support the file system security descriptors and alternate data streams required by FILESTREAM and Full-Text Search. It can also surface if the target path points to a mapped network drive, a UNC path misconfigured for block-level access, or a removable/external drive formatted incorrectly. Additionally, corrupted NTFS metadata on an otherwise valid NTFS volume can trigger this error even when the file system type is correct.

Step-by-Step Resolution Guide

Step 1: Verify the File System Type of the Target Drive

  • Open File Explorer, right-click the target drive (e.g., D:\SQLBackups), and select Properties.
  • Confirm the File System field reads NTFS. If it shows FAT32, exFAT, or ReFS, this is the root cause.
  • Alternatively, run this command in PowerShell or Command Prompt:
  fsutil fsinfo volumeinfo D:

Step 2: Reformat the Drive to NTFS (If Necessary)

  • Back up any existing data on the drive before proceeding, as formatting is destructive.
  • Open Disk Management (diskmgmt.msc), right-click the target volume, and select Format.
  • Choose NTFS as the file system and complete the format process.
  • Alternatively, use the command line:
  format D: /FS:NTFS /Q

Step 3: Correct the Backup/Restore Path in SQL Server

  • Ensure the backup destination path used in your BACKUP DATABASE or RESTORE DATABASE statement points to a local NTFS volume or a properly configured UNC path on an NTFS share.
  • Example of a corrected command:
  BACKUP DATABASE [YourDB]
  TO DISK = N'D:\SQLBackups\YourDB.bak'
  WITH FORMAT, INIT;
  • Avoid using mapped network drives (e.g., Z:\) for SQL Server service accounts, as these are session-specific and may not resolve correctly; use UNC paths instead (\\ServerName\ShareName\).

Step 4: Check and Repair NTFS Volume Integrity

  • If the drive is already NTFS but the error persists, run a file system integrity check:
  chkdsk D: /f /r
  • Restart the server if prompted, and allow the check to complete before retrying the backup/restore operation.

Step 5: Validate FILESTREAM and Full-Text Filegroup Locations

  • Confirm that any FILESTREAM filegroups or Full-Text catalogs referenced in the database are also stored on NTFS volumes.
  • Query the current filegroup paths:
  SELECT name, physical_name FROM sys.database_files;
  • Relocate any filegroups pointing to non-NTFS paths using ALTER DATABASE ... MODIFY FILE.

Alternative or Verification Steps

  • After applying the fix, re-run the original BACKUP or RESTORE command and confirm it completes without Error 3045.
  • As a quick verification, use fsutil fsinfo volumeinfo <DriveLetter>: to confirm NTFS is active on all paths referenced by the SQL Server instance, including backup destinations, FILESTREAM containers, and Full-Text catalog folders.