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

by

Troubleshooting Guide: Error 3201 – Cannot Open Backup Device

Why This Error Happens

This error typically occurs when the SQL Server service account lacks the necessary NTFS permissions to read or write to the specified backup file path or network share. It can also result from an invalid or unreachable UNC path, a full disk volume, or the backup directory being removed or renamed after the job was scheduled. In some cases, the underlying operating system error (such as “Access is denied” or “The system cannot find the path specified”) appended to the message reveals the exact Win32-level cause.

Step-by-Step Resolution Guide

Step 1: Verify the Backup Path Exists and Is Reachable

  • Confirm the target directory (e.g., D:\SQLBackups\) or UNC path (e.g., \\FileServer\SQLBackups\) actually exists.
  • Try manually navigating to the path using File Explorer or cmd with dir \\FileServer\SQLBackups\.
  • If using a network share, ping the server and confirm SMB connectivity is not blocked by Windows Firewall on Windows Server 2025.

Step 2: Check and Correct NTFS/Share Permissions

  • Identify the SQL Server service account via SQL Server Configuration Manager (e.g., NT Service\MSSQLSERVER or a custom domain account).
  • Right-click the backup folder, go to Properties > Security, and ensure the service account has Modify and Write permissions.
  • If using a network share, also verify Share-level permissions (Properties > Sharing > Advanced Sharing > Permissions) grant Change access to the same account.
  • Run this command to test write access as the service account using PsExec:
  psexec -u DOMAIN\SQLServiceAccount cmd /c "echo test > D:\SQLBackups\test.txt"

Step 3: Confirm Disk Space and File Lock Status

  • Check available free space on the target volume using Get-PSDrive D in PowerShell.
  • Ensure no other process (e.g., antivirus or a prior stuck backup job) has an exclusive lock on the .bak file using Resource Monitor > CPU > Associated Handles.
  • Delete or rename any orphaned .bak files blocking the write operation.

Step 4: Validate the Backup Device Configuration in SQL Server

  • Re-run the backup command specifying an explicit, freshly tested path:
  BACKUP DATABASE [YourDB] TO DISK = N'D:\SQLBackups\YourDB_Full.bak' WITH INIT;
  • If a backup device object is used, drop and recreate it to ensure the path reference isn’t stale:
  EXEC sp_dropdevice 'YourBackupDevice';
  EXEC sp_addumpdevice 'disk', 'YourBackupDevice', 'D:\SQLBackups\YourDB.bak';

Alternative or Verification Steps

  • After applying permissions, run the BACKUP DATABASE command again and check SQL Server Error Log (EXEC xp_readerrorlog) for successful completion without Error 3201.
  • As an alternative, temporarily redirect the backup to a local, non-network path (e.g., C:\Temp\test.bak) to isolate whether the issue is permissions-based or network-related.