Hyper-V backup job fails to create shadow copy with default shadow storage limit

Increase the shadow copy storage area for the volume listed in the error event, or set the maximum size to “No limit.”

To identify the volume listed in the event, run “mountvol” from a command prompt; below the usage information will be a list of volume GUIDs and their associated mount points, if any.

This size of the shadow storage area can be changed in the Shadow Copies utility, or from the command line.

Note: By default, each volume stores its own shadow copy. For example, a shadow copy of a CSV mapped to C:\ClusterStorage\Volume8 would also be stored on C:\ClusterStorage\Volume8. Do not change the location of the shadow copy storage area on a Hyper-V host server.

Shadow Copies Utility

To access the utility, right click any volume and choose Configure Shadow Copies.

In the Shadow Copies utility:

1. Select the volume with insufficient space;
2. Click Settings…
3. In the “Maximum size” box, either increase the limit, or choose “No limit”.

Command Line

All commands below should be run from an administrator command prompt.

Use vssadmin list shadowstorage to view existing shadow storage associations. If no association exists for any volume, the command response will be “No items found that satisfy the query.”

If no association is listed for the volume, run vssadmin add shadowstorage to set the size of the shadow storage area. For example, on a 1 TB volume labeled D:

vssadmin add shadowstorage /for=D: /on=D: /maxsize=200GB

If a shadow storage association already exists, run vssadmin resize shadowstorage to set the size of the shadow storage area. For example, on a 1 TB volume labeled D:

vssadmin resize shadowstorage /for=D: /on=D: /maxsize=200GB

The /maxsize parameter is not optional, but can be set as /maxsize=UNBOUNDED