04-25-2015 09:43 AM
Auto or manual, incremental or full backups of my system drive (C:) (has system protection turned on) is creating and editing the system restore files in the C:\System Volume Information directory. No restore points show as available restore points and this activity is chewing up disk space. Why is this being done and how do I turn it off?
4/22,/2015 12:51 PM = Creation of "1st point after deleting all" restore point
4/22/2015 5:00:50 PM = Auto Incremental of C: drive
4/24/2015 9:46 PM = Manual Incremental of C: drive
4/23/2015 5:00:58 PM = Auto Incremental of C: drive
So you can see where SSR is creating and editing the system restore files. It is chewing up unnecessary disk space and I cannot see how this would be useful for any kind of SSR image restore??? I would like to disable this "feature".
Thanks for your help -- David
Solved! Go to Solution.
07-02-2015 06:34 AM
This problem was solved via escalated support. Thanks for the help!
04-27-2015 12:24 AM
But you see the recovery points in the SSR console?
04-27-2015 05:56 AM
Yes. SSR recovery points are created. No problem there. Everything as normal. Only everytime a recovery point (incremental or full) is created on the system drive for which windows protections is turned on, SSR is editing/creating the windows sytem protection/restore files in the System Volume Information directory. This is chewing up disk space quickly. There is no windows restore point created that I can use for windows system restoration.
It is definitely SSR that is creating this activity (probably VSS thru SSR). Why is SSR doing this and how do I turn this off.
04-27-2015 11:07 PM
Have used the option full VSS backup in the backup job?
04-28-2015 06:59 PM
Perform Full VSS Backup is NOT checked.
04-28-2015 10:38 PM
Let my escalate this to support for you.
05-05-2015 03:08 PM
What's the status on this? Haven't heard anything.
05-05-2015 09:18 PM
Didn't support contact you? Sorry for that. Can you file a case for this?
05-06-2015 06:46 AM
I'll take it from here.
06-11-2015 04:37 AM
Any updates here?
07-02-2015 06:34 AM
This problem was solved via escalated support. Thanks for the help!