Skip to main content
Solved

System State Backups

  • 18 August 2021
  • 6 replies
  • 14034 views

RHITSec
Bit
Forum|alt.badge.img+2

Hi Folks,

I am constantly battling the error System State Backup error below on many of my windows hosts:

 

ERROR CODE [6:64]: System state backup of component [System Protected Files;] failed.
Source: servername, Process: clBackup

 

What is everyone doing to automate the remediation of this problem on your hosts? I have a moderate sized environment (~1500 hosts) so handholding each one when it pops up is a time consuming and arduous process. 

Thanks in advance!

Sean

Best answer by MichaelCapon

I’d suggest checking the usual:

  • VSS Writers State (Ensure System Writer is present also)
  • Disk Space / Configured Shadow Storage Limits

For the above, refer here: https://ma.commvault.com/Article/Details/5460

 

The Application event Log at the time of the issue may show VSS related events also.

 

Best Regards,

Michael

View original
Did this answer your question?

6 replies

Aplynx
Vaulter
Forum|alt.badge.img+13
  • Vaulter
  • 291 replies
  • August 18, 2021

Depends on what the cause of the failure is. What is causing the System Protected Files to fail? 


MichaelCapon
Vaulter
Forum|alt.badge.img+14
  • Vaulter
  • 349 replies
  • Answer
  • August 23, 2021

I’d suggest checking the usual:

  • VSS Writers State (Ensure System Writer is present also)
  • Disk Space / Configured Shadow Storage Limits

For the above, refer here: https://ma.commvault.com/Article/Details/5460

 

The Application event Log at the time of the issue may show VSS related events also.

 

Best Regards,

Michael


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

@RHITSec , were the above replies helpful, or are you looking for something that more automated?  The challenge with automating this is that the cause for a given System State failure can and will differ greatly between clients.


Forum|alt.badge.img+7
  • Byte
  • 36 replies
  • September 7, 2021

@RHITSec Everytime i have a backup with that error, the only way i find to resolve it is to reboot the backed up machine.

Best regards,

Amaral 


Forum|alt.badge.img
  • Bit
  • 1 reply
  • May 10, 2023

I’m facing the same issue. Many of our windows clients are getting this error and reboot fixes it temporarily but the error occurs again. It would be very helpful if someone can provide a permanent fix for this.

Thanks in advance


Scott Moseman
Vaulter
Forum|alt.badge.img+18

There’s no permanent fix for System State issues (well, maybe Linux...).

Critical and Non-Critical System State Components for Windows File System
https://documentation.commvault.com/2022e/expert/62528_critical_and_non_critical_system_state_components_for_windows_file_system.html

Excluding System State Components from Windows File System Backups
https://documentation.commvault.com/2022e/expert/18491_excluding_system_state_components_from_windows_file_system_backups.html

If you’re seeing “non-critical” items currently as the issue, you can exclude them.

Thanks,
Scott
 


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