That shouldn’t happen. Which products are installed? 

@AMJ , following up.  Were you able to review the reply above?

Thanks!

@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.

@Aplynx Unfortunately this happened. if you mean Agents then filesystem and core. SP17

@Damian Andre I agree with you but we got to know that there is Microsoft code for VSS API’s had a bug which was observed in SP15 and fixed in Maintenance release but we still got the issue in SP17 and SP20 as well which is surprising.

@AMJ , were you able to cross reference the shadow IDs to the FileScan.log entries?

Might be worth creating a support case here.

@Mike Struening Yes we did but not progressing because we cannot reproduce the issue.

Appreciate the update.  Let’s give it another week before marking this as ‘solved’, though you can update the thread at any time after and I’ll be able to unmark it