0X00000FA4 Backup Fails on SQL Server 2019 – Fix Now

You're running a full backup on SQL Server 2019, maybe on a weekend maintenance window, and bam — error 0X00000FA4. The backup fails with the message ERROR_FULL_BACKUP. I know this one's a pain. It tripped me up the first time when a scheduled backup to a network share failed at 3 AM. The trigger is almost always the backup destination — either the drive ran out of space during the write, or the file system on that disk has corruption that blocks new writes.

What Causes Error 0X00000FA4?

In plain English: SQL Server's VSS (Volume Shadow Copy) writer or the backup operation itself tries to write the full database file to the destination. If the destination has less than 10% free space, or if the NTFS file system has bad sectors or a corrupted MFT entry, the write fails with this error. It's not a SQL Server bug — it's the OS saying "I can't write to that location." I've also seen it when the backup path is a mapped drive that disconnects mid-backup, or when the target disk has file-level encryption turned on and the backup service doesn't have the right permissions.

The Fix — Step by Step

Don't waste time reinstalling SQL or running DBCC CHECKDB. The real fix is on the destination side.

1. Check free disk space on the backup destination.
   Open File Explorer or run fsutil volume diskfree C:\backups (replace with your path). If free space is under 10% of total capacity, free up space or move the backup to another drive. SQL Server needs room for the snapshot and temp files during backup.
2. Test the drive with chkdsk.
   Open an elevated Command Prompt and run chkdsk X: /f /r where X is the backup drive. This scans for file system corruption and bad sectors. I usually do this after hours because it takes time on large drives. If errors are found, the backup will likely fail again.
3. Change the backup path to a local drive temporarily.
   If the destination is a network share (UNC path), SQL Server VSS backup might fail if the share isn't configured for VSS. Switch to a local folder like C:\TempBackup and run the backup again. If it succeeds, the issue is the network path — reconfigure the share with proper VSS settings or use a different method (like backup to SMB share with continuous availability).
4. Disable file encryption or compression on the destination folder.
   Right-click the backup folder > Properties > Advanced. Uncheck "Encrypt contents to secure data" and "Compress contents to save disk space." These interfere with SQL Server's write operations. Then retry.
5. Run the backup under a different service account.
   If the SQL Server service runs as NETWORK SERVICE, it might not have write permissions to the backup folder. Grant the account full control to the destination. Or switch to a domain account with explicit permissions.

If It Still Fails

Check the Windows Application Event Log for VSS or volsnap errors around the time of the backup. That points directly to a volume shadow copy issue. If you see VSS errors, restart the Volume Shadow Copy service (VSS in services.msc) and retry. Also verify that the target drive isn't full on system space — sometimes the backup drive has space, but the system drive where VSS stores shadow copies is full. Run vssadmin list shadowstorage to see. If that's the problem, resize the shadow storage with vssadmin resize shadowstorage /on=C: /for=C: /maxsize=10GB.

I've seen this error vanish after a simple reboot of the backup server, too. If you're in a hurry, reboot and try once more — but the steps above are the lasting fix.