Skip to main content
Solved

System volume information space filling up windows shadow copy settings

  • August 19, 2022
  • 8 replies
  • 1862 views

Forum|alt.badge.img+1
  • Bit
  • 4 replies

System volume information space filling up windows shadow copy settings set to no limit

There is a trick to clean it up but wondering why?

Best answer by Damian Andre

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

View original
Did this answer your question?

8 replies

Aplynx
Vaulter
Forum|alt.badge.img+13
  • Vaulter
  • 291 replies
  • August 19, 2022

That shouldn’t happen. Which products are installed? 


Mike Struening
Vaulter
Forum|alt.badge.img+23

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

Thanks!


Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Vaulter
  • 1301 replies
  • Answer
  • September 5, 2022

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


Forum|alt.badge.img+1
  • Author
  • Bit
  • 4 replies
  • September 6, 2022

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

 


Forum|alt.badge.img+1
  • Author
  • Bit
  • 4 replies
  • September 6, 2022

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


Mike Struening
Vaulter
Forum|alt.badge.img+23

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

Might be worth creating a support case here.


Forum|alt.badge.img+1
  • Author
  • Bit
  • 4 replies
  • September 13, 2022

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


Mike Struening
Vaulter
Forum|alt.badge.img+23

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 🤓


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings