NAS Codex › Synology › Synology Active Backup for Business error code 21 or 23
Synology Active Backup for Business error code 21 or 23
Active Backup for Business can stop a Windows device backup with error code 21 (0x8004231f) or error code 23. Synology publishes a fix article for each. Both point at the Windows device being backed up, not at the NAS: code 21 is about taking the Volume Shadow Copy Service (VSS) snapshot, and code 23 is about bad sectors on a disk selected for backup.
Written against: Active Backup for Business Agent on Windows, DSM 7 (Synology KB: error code 21 (0x8004231f) and error code 23 fix articles; Synology KB: Index of backup and restore error codes). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Code 21: run vssadmin list providers and vssadmin list writers in an administrator Command Prompt, remove extra VSS providers, restart any writer that is not Stable, and give shadow storage more space. Code 23: check Windows Event Viewer for a disk error, then run chkdsk /F /R X: on that volume or replace the failing drive. Both articles end with chkdsk /F /R.
What the two codes mean
- Error code 21 (0x8004231f): Synology lists three causes. Other applications are creating VSS snapshots at the same time, so the agent can't take its own. The reserved shadow copy storage for Windows VSS is insufficient. Or the system can't read the device's snapshot because of I/O errors caused by bad sectors on the disk.
- Error code 23: a disk selected for backup has bad sectors, so the backup agent shows an error when it reads the block data during upload.
Synology's index of backup and restore error codes lists both for Windows PCs and physical servers. It describes 23 as: the disk selected for backup has bad sectors.
Error code 21: check for other VSS providers
- Type
cmdin the Windows search bar, right-click Command Prompt and select Run as administrator. - Run
vssadmin list providers. - If there are providers besides Microsoft Software Shadow Copy Provider and Microsoft File Share Shadow Copy Provider, remove them before retrying the backup.
If only those two Microsoft providers are listed and the error remains, Synology says it may be a compatibility issue. It names Reboot Restore Rx, TuneUp Utilities 2009/2010/2011 and Kaspersky Removal Tools: remove them, or contact your service provider, before retrying. If Synology Drive Client is installed, run its backups in manual mode or schedule them when the Active Backup for Business Agent is not backing up. If Synology VSS HW Provider appears in the list, Synology says to uninstall Synology Storage Console for Windows before backing up again.
Error code 21: make sure the VSS writers are stable
- In an administrator Command Prompt, run
vssadmin list writers. - Every writer's status should be Stable. If one is not, go to Control Panel > System and Security > Administrative Tools > Services, right-click the service and select Restart.
- Run
vssadmin list writersagain and check the results.
Error code 21: reserve more space for shadow storage
To see whether more space is needed, open Windows Event Viewer and look at the entries from when the error happened. Synology says a Volsnap event with Event ID 35 means the system couldn't allocate more space for the shadow copy.
- Windows 11, 10 and 7: press Windows key + R, enter
systempropertiesprotectionand click OK. In System Protection, select the volume that couldn't be snapshotted and click Configure. Under Disk Space Usage, set Max Usage; Synology suggests trying 100% first. Back up again, then check whether Current Usage almost reaches Max Usage. If it does, switch to a larger drive and back up again. - Windows Server: in File Explorer, right-click any disk and select Configure Shadow Copies…. Select the volume, click Settings…, change Maximum size to No limit and click OK. Back up again.
Error code 21: free up the system reserved partition
If the problem persists, Synology says the system reserved partition may be running out of space. Press Windows key + R, enter diskmgmt.msc, right-click the system reserved partition and use Change Drive Letter and Paths… to give it a letter. Show hidden files in File Explorer (File > Options > View), delete some files from that partition, then remove the drive letter again in diskmgmt.msc and back up the device again.
Check and repair the volume (codes 21 and 23)
For code 23, Synology says to open Event Viewer (Start > Windows Administrative Tools > Event Viewer), expand Windows Logs, and if a disk error appears, run a full disk scan and repair the bad sectors, or replace the malfunctioning drive, before running the backup task. Both articles give the same command:
- Open Command Prompt.
- Run
chkdsk /F /R X:, replacing X with the letter of the affected volume. - If Windows says chkdsk can't run because the volume is in use and asks to schedule it for the next restart, enter Y.
Error code 21: find the file at the bad spot
If code 21 persists after chkdsk, Synology shows how to find the corrupted file. In the agent's log, find a line like Got error 21 0 at (661534015488, 1048576); the first number is the offset where the error happened. Divide the offset by the cluster size (4096 bytes is typical for NTFS) to get the Cluster ID, then run fsutil volume queryCluster D:<Cluster ID> in an administrator Command Prompt, replacing D: with your drive letter. The output names the file using that cluster. Remove that file and run the backup again.
Error code 21: test Windows snapshots
- Windows 10, 8 and 7: press Windows key + R, enter
systempropertiesprotection, and in System Protection click Create to see whether a snapshot can be taken. - Windows Server: right-click the volume in File Explorer, select Configure Shadow Copies…, confirm Shadow Copies are enabled and click Create Now.
If errors occur here, Synology says the Windows device may not be able to take snapshots and to contact Microsoft Support.
When to stop and get help
Both errors can come from bad sectors. Synology's code 23 article says to repair the bad sectors or replace the malfunctioning drive before running the backup task again.
Questions
What is Active Backup for Business error code 21 (0x8004231f)?
Synology says the agent can't take a VSS snapshot: other apps are taking snapshots at the same time, shadow copy storage is too small, or bad sectors cause read errors.
What causes Active Backup for Business error code 23?
Synology says a disk selected for backup has bad sectors, so the agent hits an error reading block data during upload. Check Event Viewer, then run chkdsk /F /R or replace the drive.
How do I give VSS more shadow storage for Active Backup?
On Windows 11, 10 or 7, open systempropertiesprotection, select the volume, click Configure and raise Max Usage. On Windows Server, set Shadow Copies Maximum size to No limit.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.