How to resolve Error Code [7:112]: Failed to back up critical system state component; Check client logs for details?

  • 30 December 2020
  • 1 reply

Userlevel 2
Badge +5

Seeing multiple system state failures nightly, need assist in determining why these are failing!


Best answer by Aristo 31 December 2020, 00:10

View original

1 reply

Userlevel 1
Badge +1

Hi Vsicherman, 


Check out the information and instructions below


The System Protected Files or the Registry will appear in the failed files list following a File System iDataAgent (iDA) backup that includes the System State. The failure will happen sporadically as subsequent System State jobs may backup these components without an issue.

While there are many causes of this problem, a common issue is when the system runs out of VSS shadow storage space. If a Windows server has a high rate of change it requires larger than normal disk space for the Shadow Copy Storage.

You can follow this guide from Microsoft for Calculating Capacity Requirements for VSS space.

Check the space currently allocated for the Shadow Copy Storage. The Client server System State files can be 15-20GB for Windows® server 2008 and newer Operating Systems. Microsoft provides a guide for VSS space located here.


1. Determine the current Shadow Storage setting.

From an admin command prompt run:

                      vssadmin list shadowstorage


The command displays the current configuration:

Shadow Copy Storage volume: (C:)

Used Shadow Copy Storage space: 4.066 GB (4%)

Allocated Shadow Copy Storage space: 4.394 GB (4%)

Maximum Shadow Copy Storage space: 4.878 GB (5%)


2. Based on the displayed current configuration settings determine whether the disk is low on space or more space can be allocated for Shadow Storage.

If the current drive does not have enough free space available to allocate for the Shadow Copy Storage:

Example switches the Shadow Copy Storage from C: drive to D: drive and increases the Shadow Copy Storage space allocated:

                      vssadmin resize shadowstorage /for=C: /on=D: /maxsize=25GB


I hope this was useful