NetWorker: File system Backup Failure "Insufficient storage available to create either the shadow copy storage file or other shadow copy data"

Summary: Windows client backup fails with the following Volume Shadow copy Service (VSS) error "Insufficient storage available to create either the shadow copy storage file or other shadow copy data" ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

NetWorker backups of a Microsoft Windows client fail with the following error:
VSS OTHER: ERROR: VSS failed to process snapshot: 
90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot.
 
7259:save: VSS reports adding volume [C:\] <file:///C:/]> to snapshot set failed for both hardware/software provider.VSS OTHER: ERROR: VSS failed to process snapshot: Unexpected VSS provider error.

VSS OTHER: ERROR: VSS failed to process snapshot: Insufficient storage available to create either the shadow copy storage file or other shadow copy data. (VSS error 0x8004231f)

90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot.

Cause

VSS is a Windows operating system function. VSS is required for SYSTEM STATE or DISASTER RECOVERY:\ save sets or when completing Block-Based Backups (BBB). VSS must be stable and working correctly on the host operating system before it can be used with NetWorker backups.

This issue can appear for multiple reasons; however, VSS fails when there is not enough free space to create or grow the shadow copy "diff area."

The required size varies depending on:

  • Volume size
  • Snapshot max size is on a different drive that also has no free space.
  • I/O rate during snapshot
  • Size of changed blocks while the snapshot is active
  • Whether diff area is autosized or constrained

The other potential causes are:

  • Corrupt VSS writers (vssadmin list writers shows errors)
  • A previous snapshot is stuck.

Resolution

WARNING: The actions outlined in this article must be performed by the client host's System Administrator.
  1. Check if the writers are stable or not using the below command:

Syntax:

vssadmin list writers
Example: 
c:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {34a07e16-fcdb-4ab0-b603-d58c0f741c9a}State: [1] Stable
Last error: No error
WARNING: if VSS writers are not in a stable state, Microsoft support must be engaged for further analysis of the VSS writers.
  1. Check to see if there are any snapshots, if so remove them:
vssadmin list shadows
vssadmin delete shadows /all
  1. Try to create a shadow using the below command:

Syntax:

vssadmin create shadow /for=DRIVE_LETTER
Example: 
c:\>vssadmin create shadow /for=C:\
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Successfully created shadow copy for 'C:\'
    Shadow Copy ID: {1f6a1448-daad-4e68-a334-31dd40a64dd9}
    Shadow Copy Volume Name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
  1. If the snapshot is successful, delete it using the commands from step 2. Test a NetWorker backup again to see if the backups succeed.
  2. If the VSS snapshot fails with the same space-related error, perform one of the following options:

Change the VSS Snapshot Size Limits.

Syntax:

vssadmin add shadowstorage /For=DRIVE_LETTER /On=DRIVE_LETTER /MaxSize=10%

Or:

vssadmin add shadowstorage /For=DRIVE_LETTER /On=DRIVE_LETTER /MaxSize=20GB
NOTE: The above are examples only, you can increase or decrease the limits as per your discretion. The sizing allotted cannot be determined by NetWorker support, this must be determined by the system administrator.
Example: 
C:\>vssadmin add shadowstorage /For=C: /On=C: /MaxSize=10%
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Successfully added the shadow copy storage association

The snapshots can also be sent to another volume instead; for example:

C:\> vssadmin add shadowstorage /For=C: /On=S: /MaxSize=10%
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Successfully added the shadow copy storage association
 

Remove VSS Snapshot Size Limits:

NOTE: Disabling the size limit is safe for most backup workflows (since the snapshot is temporary), but not ideal for production servers with tight space. The above approach is safer.

Syntax:

vssadmin add shadowstorage /For=DRIVE_LETTER /On=DRIVE_LETTER /MaxSize=UNBOUNDED
Example:
C:\> vssadmin add shadowstorage /For=C: /On=C: /MaxSize=UNBOUNDED
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Successfully added the shadow copy storage association
Alternatively, if there is another (noncritical) drive, you can redirect the snapshots (unbounded) from a critical drive (such as C:\) to the noncritical drive. For example:
C:\> vssadmin add shadowstorage /For=C: /On=S: /MaxSize=UNBOUNDED
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Successfully added the shadow copy storage association
NOTE: To change shadow storage, you can use the options Delete ShadowStorage or Resize ShadowStorage. For more information, consult vssadmin man pages or Microsoft documentation.

Additional Information

Affected Products

NetWorker Family, NetWorker
Article Properties
Article Number: 000438396
Article Type: Solution
Last Modified: 13 مارس 2026
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.