On a computer with the Symantec Endpoint Protection (SEP) 12.1 client installed, the Windows Server Backup Utility (WSBU) fails to complete a full system back up due to insufficient free disk space on the System Reserved partition. Restarting the computer allows the backup to complete.
The following error appears in the error details in the WSBU console:
There is not enough disk space to create the volume shadow cop on the storage location. Make sure that, for all volumes to be backed up, the minimum required disk space for shadow copy creation is available. For the optimal experience, we recommend at least 1 gigabyte of free disk space on each volume being backed up. Detailed error: The volume shadow copy operation failed with error 0x8004231F. View the event log for more information.
The following error is found in the Windows Application Log:
The backup operation that started at '?2013?-?01?-?28T15:43:10.746000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348249'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
This problem occurs when there is not enough disk space on one or more of the partitions to create a volume snapshot using the Volume Shadow Copy service. The Volume Shadow Copy service needs approximately 30 MB of free disk space on each partition to create this snapshot. This generally occurs on the hidden System Reserved partition. On Windows Vista, 2008, 7 and 2008 R2 this partition defaults to 100 MB.
The Symantec Endpoint Protection (SEP) 12.1 client writes file usage data to the System Volume Information folder on all drives on the computer, including the System Reserved partition. In some circumstances, these temporary files grow large enough to prevent the Volume Shadow Copy service from creating snapshots of this volume.
Note: It is possible for this problem to occur without SEP installed on the computer.
This issue is fixed in Symantec Endpoint Protection 12.1 Release Update 4 (SEP 12.1.4). Please upgrade to take advantage of this and many other important enhancements and improvements.