It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda RMM
formerly Managed Workplace

System State Troubleshooting

  • Last updated on

Commonly, there are a few reasons System State backups will fail. This article will give an overview of the System State backup process and explain the common points of failure.


The general process flow of a system state is as follows:

  1. The Backup Agent signals Windows Server Backup to create a system state backup on the scratch drive specified in the backup set.
  2. When (1) is finished, the Backup Agent zips and encrypts the system state backup in its temporary folder.
  3. The packaged system state backup is uploaded and/or sent to the Local Vault.

Often, the backup may fail on step (1) or (2). If the backup fails on step (1), this is usually due to an issue with the scratch drive used. Backups will fail if the scratch drive does not meet the eligibility criteria. Ensure the scratch drive is non-critical and meets Microsoft's requirements for storing a backup made with Windows Server Backup. Those requirements are summarized below:

  • The location must be NTFS-formatted.
  • USB pen drives or flash drives are not supported
  • Tape drives cannot be used.
  • There must be enough space in the location to accommodate the backup.

Assuming there are no issues with the scratch drive, backups that fail during step (2) usually do so because there is insufficient free space at the temporary location. You will need at least as much free space as the size of the system state backup produced by Windows Server Backup.


Windows Server Backup Troubleshooting

To test if Windows Server Backup can create the system state on the scratch drive you are using for the backup set, run the system state backup outside the Intronis software. Do this using the following command:

wbadmin start systemstatebackup -backupTarget:x: -quiet

...where x: is the scratch drive you use for the System State backup. You can rule out this step as a fault point if this operation is completed successfully. To see the status of the operation, use:

wbadmin get status

If the Windows Server Backup fails, look in the Event Viewer or Windows Server Backup logs to find its reason. Whatever error or message for the failure you find there should give you enough information to continue troubleshooting.

Temporary Folder Troubleshooting

If you can create a system state backup using Windows Server Backup but cannot complete a system state backup, the next thing to check would be the temporary folder.

  1. First, edit the System State backup set and go to the "Settings" page to see what folder the backup set uses for temporary space.
  2. To determine how much space you need, run the command above to create the Windows Server Backup system state. The size of the files produced will be the minimum amount of temporary space needed.
  3. If your temporary folder is on a different drive than the scratch drive, check to see if there is free space equal to or greater than the amount determined in step (2).
  4. If your temporary folder is on the scratch drive, you will need free space on the scratch drive equal to or greater than twice the size determined in step (2). This is because the system state files will duplicate during the backup job.

If you can create a Windows Server Backup system state and verify your temporary location has enough free space, but the backups still fail, you may need to contact Intronis Support to resolve that problem.