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. So the above command sets the maximum size on the E drive to 19GB. vssadmin resize shadowstorage /on=E: /For=E: /Maxsize=19GB That doesn't mean you couldn't still run out of disk space from shadow copies because it's a percentage of the volume and not a percentage of free space. If the VSS shadow copies of the D: drive will be stored on the C: drive and allowed to use up to 90 of the free disk space on C:, the command would look like: vssadmin add shadowstorage /ford: /onc: /maxsize90.
#Limit shadow copy space windows
Next I used the same command to raise the maximum space to be used again to a more suitable number. The default set by Windows for maximum shadow copy storage space allocation is 10 for all volumes. 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. In this case I used the available commands though. 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.
This got me some output and lets list here some stuff for the Log disk: Used Shadow Copy Storage space: 52.481 GB (52%)Īllocated Shadow Copy Storage space: 52.983 GB (52%) The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit. So hereby a few quick commands:įirst one to list the shadow copy space reserved and used for each disk: vssadmin list shadowstorage 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.
0 kommentar(er)
