#DPM SHADOW COPY SPACE FREE#

Sure got rid of the problem of Exchange management pack telling us during each day the Log disk was running below 50% free space already. The steps to configure shadow copies varies between operating systems. So the above command sets the maximum size on the E drive to 19GB. VSS requires space allocated to each volume to be able to create and store snapshots.

Vssadmin resize shadowstorage /on=E: /For=E: /Maxsize=19GB Next I used the same command to raise the maximum space to be used again to a more suitable number. The Volume Shadow Copy Service (VSS) service is a great feature that allows for an added layer of data recoverability in your backup plan. Tried by disabling and enabling the Backup (Volume shadow copy) in the Hyper-V Integration Services of the VM by following the below steps. and removal and re-adding from protection group was performed after following the below steps. First I set the amount of disk space to use as maximum to only a few GB, which causes the old files to be deleted. The issue seems to be resolved after removing and re-adding the VM to the protection group twice. In this case I used the available commands though. Shadow copy job failures can be caused by issues with Volume Shadow Copy Service (VSS), by insufficient disk space allocated in the storage pool, and by an. You can also open the Explorer and take the properties of the disk and look for the Shadow Copies tab. By the way the data disk was a factor 10 bigger in size and also had well over half the disk size used by only this stuff. Maximum Shadow Copy Storage space: UNBOUNDED (100%)Īha, so it had no limit and was already occupying over half the disk space and 52 GB. Used Shadow Copy Storage space: 52.481 GB (52%)Īllocated Shadow Copy Storage space: 52.983 GB (52%) This got me some output and lets list here some stuff for the Log disk: So hereby a few quick commands:įirst one to list the shadow copy space reserved and used for each disk: Thing was most of these files were older than a year. After short investigation it turned out to be the System Volume Information directory causing this and it had a lot of big files in it with a number of several GB each. But the backups were OK and there was only a few hours of data on the disk. First thing to check if backups have run on the machine, because if those fail the log disk tends to fill up quickly. Was monitoring an Exchange machine today and got a message that the Log disk contained less than x percent of storage.

Dpm shadow copy space