Summary
Block Level Backup on Windows fails with a VSS error (0x8004231f). When you run the vssadmin list writers command on the client node, most of the VSS writers are in an error timeout state. Error code 0x8004231f indicates VSS_E_INSUFFICIENT_STORAGE (Insufficient storage space for the shadowcopy). To resolve this issue, you have the following options: Increase shadow storage space Remove old VSS snapshots Redirect VSS shadow storage to another volume
Symptoms
Following is a sample of the error from the job report:
x.x.x.x 2/27/2013 5:56:55 am SNBSNP3069E 4260: MsSnapShot::do_snapshotset:QueryStatus error RC(0x8004231f) ()
x.x.x.x 2/27/2013 5:56:55 am SNBSNP3069E 4260: MsSnapShot::backup_components:do_snapshotset error(-4)
x.x.x.x 2/27/2013 5:56:55 am SNBAPH_381E BexException in message (BACKUP_VSS) to module (sssnap), reqrc (-16)
x.x.x.x 2/27/2013 5:56:55 am SNBAPH_126E Func(backup_): Exception (AHException: <AHExceptionxception instance at 1054507852> )
x.x.x.x 2/27/2013 8:57:00 am SNBSVH_990E APPH backup request failed with exception: <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>21001</CODE></EXCEPTION>
volsnap Windows system events on the client node display.
Windows system event:
Log Name: System
Source: volsnap
Date: 2/27/2013 5:56:54 AM
Event ID: 39
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: somenode.customer.com
Description:
When preparing a new volume shadow copy for volume \\?\Volume{ba68bcd2-c2db-11e0-a310-806e6f6e6963}, the shadow copy storage on volume D: could not be located in a non-critical space. Consider using a shadow copy storage volume that does not have any shadow copies.
Resolution
Solution 1 - Increase shadow storage space
To see the amount of storage space allocated and used for Volume Shadow Copies, run the following command from a command prompt with elevated privileges:
Vssadmin list shadowstorage
To allocate more storage, for example 20 GB, run the following command:
vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=20GB
Solution 2 - Remove old VSS snapshots
Catalogic Software data protection software should not be running in parallel with other data protection products or VSS snapshot automation. These snapshots consume space needed by Catalogic Software and Windows may remove shadows if volume space is low. If there are other shadows consuming space and they are not necessary, they can all be removed with the following:
vssadmin delete shadows /all
This removes all VSS snapshots on the system, prompting you first for confirmation. Running the command vssadmin list shadows displays a list of snapshots on your system along with the associated ID. Deletion by ID must specify a valid snapshot ID, deletion by volume must specify a valid Windows volume, for example the C drive.
The following Microsoft KB article provides further information regarding vssadmin list shadows:
http://technet.microsoft.com/en-us/library/cc788116%28WS.10%29.aspx
The following Microsoft KB article provides further information regarding vssadmin delete shadows:
http://technet.microsoft.com/en-us/library/cc788026%28WS.10%29.aspx
Solution 3 - Redirect VSS shadow storage to another volume
If there are other volumes that have ample capacity, the Windows VSS Shadow storage manager can be used to redirect shadow storage to another volume.