System volume information space filling up windows shadow copy settings

@AMJ,

If system state is enabled then persistent shadow copies are created - otherwise non-persistent is created. If something in interrupting the job then perhaps VSS shadow storage would not be cleaned up, however I’m pretty sure the filescan process will check and clear any stale VSS snapshots we create.

Its unlikely that Commvault VSS snaps are the cause of the storage running out because shadow copies are not cleaned up - but you can identify the shadow ID in the filescan.log file for the job and see if that matches up to what you are seeing consume all the space.