Best answer by KitView original
Anyone know if the wrdata folder can be cleaned out or deleted? It grows to an enormous size over time.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Completely understand where you are coming from. Hopefully things will improve in that area in the future as I believe that the Development Team are looking at this whole area.
I try to temper things by remembering that the .db files in the WRData folder forma a valuable part of the insurance that WSA provides should an unknown fiel/app be found on your system and then prove to be malicious. ;)
I have posted this before but cannot find the thread to direct you to so I will repost the information here.
If you are technical (and I believe that you are) then are there are other ways that avoids the uninstall/reinstall, which involves the review of the 'dbnnnn.db files in the C:ProgramdataWRDATA folder, and then the deletion of selected ones of this file type. But I should stress at the outset that you need to be careful when employing these approaches.
The first is not ideal but it does avoid the uninstall/reinstall and also preserves to some extent the rationale for those files; as you may have surmised from the thread these files are the journal files produced when WSA sets a file/app to 'Monitor' and so are important in case WSA has detected a suspicious or an as yet undetermined (in terms of goodness/badness) file/app and then determines it is bad and then needs to roll back its activities, etc., in which case the relevant 'dbnnnn.db' file is required.
The problem is that we cannot easily tell which 'dbnnnn.db' relates to which file/app in the system (there is a way by looking in the Registry but I have lost my notes on that...must try to find them) so the best thing to do is to (i) check all places in WSA where files could be set to 'Monitor', decide whether they are OK or not (and if in doubt leave them as such), (ii) try to work out roughly when a file/app that is set to 'Monitor' was so set & (iii) then go to the C:ProgramdataWRDATA folder and carefully delete all 'dbnnnn.db' files that are either prior to a certain period, i.e., say more than 2 weeks old, on the basis that WSA should have been in a position to sort out if the journal is required or not, or delete everything except for the 'dbnnnn.db' files that are circa the dates that you believe that you 'Monitored' files/apps may have started to be monitored, etc.
The above may seem more convoluted that an uninstall/reinstall, but I have found that it seems to work well, and does give you a better chance of keeping 'dbnnnn.db' files that may be needed; after all an uninstall/reinstall should clear all the files in that folder regardless of whether they are needed or not.
A second, alternative way which may be more accurate but takes longer is to run Save a Scan Log and from the text file produced do a search for ‘(nnnn)’ (without the ‘’ marks) where ‘nnnn’ is the ‘nnnn’ portion of the ‘dbnnnn.db’ file(s) found in the C:ProgramdataWRDATA folder. This should find an entry in the Log from which you can identify the application/file that is being monitored and to which the journal file concerned belongs;
Sat 12-09-2015 10:21:40.0098 Monitoring process C:BrowsersMaxthonPortableBinMaxthon.exe [63D4BC1DABF35B13C94A9FAE02D7C0FF]. Type: 3 (1235)
relates to file ‘db1235.db in the C:ProgramdataWRDATA folder.
Of course, this is not ideal in terms of dealing with many ‘dbnnnn.db’ files but if one can identify the largest of these files and start with those then one can reduce (safely) the size of the folder.
Hope that helps you with your space issue and the size of your WRData folder.
FYI, Here is an updated shot of the main window; the list is sorted by total size of db files associated with each exe, the blue db items are to be left alone, the red db items are to be recycled, the gray db items are referenced in the log but do not exist on disk.
There is now also a filter which allows the user to show only excluded exe & db files and also db files which are associated with exes which have been deleted (marked with the (FILE NOT FOUND) suffix):
If something similar could be added to WSA, that would be great; otherwise, I'm going to be using this.
I still don't agree sorry! The Webroot Developers are more and capable of doing what needs to be done and keeping the client as small it can be. It's already on there list for WSA to clean up it's own files. This is the Webroot Product support Forum not a forum where someone can come by and make a utility and offer it to staff or it's members.
A good point well worth pointing out for those who might be confused or unsure. And use of this utility is very much on the basis that the user is warned that it could cause issues with the installation of WSA on their system, requiring a reinstall at the very least.
I intend to continue using WSA, so this will be an ongoing issue for me. That's why I'm doing this.
Just my opinion,
I am looking forward to it.
The only "destructive" action now performed is the moving of the dbNNNN.db files to the Recycle Bin.
I also added code to disable the scan if the WRSVC service is running; if WRSVC is running, the user is instructed to shut down WSA before scanning.
I have been absolutely slammed with work this week and I will try to finish this off with an explanitory doc on Saturday.
I cannot speak for Brad but I for one would say that if that is possible then it would be much appreciated.
I have often wondered whether or not they could produce something that, using the Registry entries that track what 'dbnnnn.db' relates to what file/app, could check for any journaling that was no longer required and then purge them, perhaps as part of the System Optimizer, and I know that there is a Feature Request along those line that is open and I believe under consideration.
But as with everything we cannot know how the Development team can or need to move forward etc....I am very sure that they have good reasons for doiing what they do and when..., but perhaps the two can come together to once and for all 'resolve' this small area of contention?
Well, I for one would be interested in seeing how this works and whether it is workable in terms of my system usage, even though I do very much subscribe to Daniel's view that the hidden Webroot folders are dangerous place to go if one does not know what one is doing...which is the case for most users.
And more importantly, I have 185 GB of unwanted dbNNN.db files in my Recycle bin :)
...and WebRoot came back up without any errors.
I need to put a few finishing touches on the util (along with a short write-up); if anybody is intereseted, I'll put it up for download in a day or so.
I am careful but also responsible, so I have daily restore points, image backups, file and folder syncs to fall back on. I don't believe in loosing data.
If you are going to gamble you need a fallback plan.