How to resolve SentinelOne Space issues (Shadow Copy)?

03/09/2023 4 People found this article helpful 275,908 Views

Description

Shadow copies can take up space. This is especially important in virtual systems. We recommend that you set the minimum VSS percent disk utilization to 10%. We highly recommend that it not be less than 5%. VSS space configuration changes the number of stored copies. When the allocated space is filled, the next VSS snapshot replaces older copies.

The Agent respects the limits set by the operating system and does not change the VSS configuration. It does not exceed the allocated space or maximum limit of stored copies (512).

Resolution

1. Retrieve the machine passphrase from the SentinelOne console

2. Open an administrative command prompt and run cd "c:\program files\sentinelone\sentinel agent *\"

3. sentinelctl.exe unprotect -k "passphrase"
4. sentinelctl.exe unload -slam -k "passphrase"

5. sentinelctl config -p vssConfig.vssProtection -v false

6. vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=10% (this will set the vss limit. percentage can be adjusted per your environment).

7. sentinelctl config -p vssConfig.vssProtection -v true

8. sentinelctl load -slam

9. sentinelctl load protect

This will resolve the SentinelOne space issues (shadow copy).

Not Finding Your Answers?

ASK THE COMMUNITY

Was This Article Helpful?

YES NO

How to resolve SentinelOne Space issues (Shadow Copy)?

Description

Resolution

Related Articles

Categories

Not Finding Your Answers?

Was This Article Helpful?

Article Helpful Form

Article Not Helpful Form

Follow Us

Subscribe to newsletter

Stay In Touch