Solved

How do I safely remove 600GB file from System Volume information folder?

Posted on 2011-03-04
5
9,267 Views
Last Modified: 2012-05-11
I have a 1.5TB volume on a Windows Server 2008 R2 system that has a 600GB file in its System Volume Information folder. This file is of the form:
FVE2.{GUID}

There are several other FVE2.* files but they are under 1MB. I searched for the GUID in the registry and found it in:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]
"FVE_Wipe"=\System Volume Information\FVE.{GUID}

It is not an exact match (FVE2 vs. FVE) but seems related. I searched the WWW for "FVE_Wipe" but could not find anything.

Shadow Copy is not (and has never been) enabled for any volumes on this system. Neither the GUI nor command line VSS tools (vssadmin list shadows, vssadmin list shadowstorage) report any shadow copies or associations. As a test, I enabled Shadow Copy on the volume and forced a snapshot. Then I deleted the snapshot and disabled Shadow Copy. I saw new files (with different names) appear and dissappear but the FVE2.* files were untouched.

We don't have any backup software installed on this server nor do we have the native Windows backup feature installed.

NOTE: The volume is encrypted with BitLocker.
0
Comment
Question by:CMT Michigan
5 Comments
 
LVL 23

Expert Comment

by:ComputerTechie
ID: 35043266
0
 
LVL 27

Expert Comment

by:davorin
ID: 35045060
http://www.theeldergeek.com/system_volume_information_folder1.htm

System Volume information folder is used for storing system restore points/information.
You can do a purge of this folder by simply disabling system restore and re-enabling it again.
If your system is working without problems it is good to create manually a system restore point manually as soon as possible.
You can also set the size of disk size used for it.
There is also an option to get access to that folder and delete the items you presumably don't need, but previously mentioned option is "cleaner".

0
 

Accepted Solution

by:
CMT Michigan earned 0 total points
ID: 35053340
This now appears to be related to the BitLocker encryption/decryption process, which was occurring at the time this file was discovered. When the process completed this file was removed.
0
 

Author Closing Comment

by:CMT Michigan
ID: 35107021
I'm accepting my answer because I discovered additional information that explained the behavior. I did not award any points for this.
0
 

Expert Comment

by:tommarsh
ID: 37798317
We have a similar situation with 2008 R2, but Bitlocker, VSS and System Restore have never (ever) been enabled on this system, and the drive in question is not a System drive. We're losing about 50gb out of 100gb to wasteful "system volume information" files, which are obviously a waste.

My question is this: I can't enable/disable System Restore (it is disabled by policy) and while I could pursue changing the policy, I'd prefer to know how to solve this problem without re-enabling arcane (and unwanted) portions of Windows which we intentionally shut-off.

Is their a method to cleanup this stuff? "Disk Cleanup" has been added per Microsoft's instructions, but doesn't "see" the naughty System Volume Information we need cleaned up, so it obviously doesn't delete it either.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question