Having automated backup is a true blessing!
BUT !!!....
I am having doubts on how well the feature is currently implemented: My current backup grew to 120,000 files and 140MBytes.
In hindsight, I am pretty sure I didn't need all the AppData in my Vista 64bit setup, but this is beside the point. So now I want to
clean things up, and the problems begin... 
Following are a mixed bag of what I believe are problems (or bugs) and what I feel are badly missing functionalities:
- it takes forever to simply browse thru the DefaultSet using Norton Backup Drive (backup on a locally attached SATA drive)
- once one is in a folder, there is no way of knowing the properties of the file (using Norton Backup Drive)
- if one is sneaky and look directly at the drive/folder (let's call it Z:\N360_Backup\), one cannot make sense of the files in the folder. I didn't even want to delete them directly from 'explorer' as that would mess the backup DB, just wanted to know which ones are the BIG ones.
- Browing the folders using Norton Backup Drive almost always requires 2 clicks to drill down a folder (or 2 'enter' from the keyboard)
- Using Norton Backup Drive and trying to delete eventually work... after _minutes_ of wait, explorer pegged at 100% CPU (I am thinking this might be one of the plusses of having 4 cores) and eating up 1.5GBytes of RAM (I am thinking SYMC makes sure I use all of the hardware I purchased!)
Any pointers/help/feedback would be greatly appreciated =)
Chris.
[Config: N360 V3.0.0.134 / Vista Ultimate 64bit / intel Q6600 @ 3GHz 
/ 8GB DDR2 / backup drive SATA1 250GB NTFS non indexed or compressed]
Hi drchris32 -
An alternative for using the Norton Backup Drive is you can go to the "Delete previously backed up files" page.
This page can be found by navigating to the Manage Backup Settings link from the main Norton 360 window and then going to the Where tab and clicking the Delete previously backed up files" link for the desination (in this case your SATA drive).
Let us know if this works for you.
Thanks.
HI John...
Many thanks for your input on this... even tho I ran into another problem: now it is ccSvcHst that hogs ~50% of the CPU (or 2 cores stuck at 100% on the quad-core)... and between the 2 processes, 1GB of RAM seems WAY OVER THE TOP ! And while this happens, N360 becomes "non-responding"... and stays that way for ??? I don't really know how long: I don't think I should be waiting more than a minute in front of a screen that shows ZERO progress. Something is WRONG !
I did some extra investigation in the backup files themselves: I managed to understand the format of the files (nothing ground breaking in that), but I am wondering why it is I have files from NB20 as well as files from NB107 or NB10H ? I am guessing this happened when I moved from V2 to V3... Am I correct?
Also: it seems that whenever Norton Backup crashes with explorer.exe, the DB and files are left totally out of sync! I could identify some files present on the N360 backup folder that clearly didn't appear any longer on the list you provide (either in "Norton Bakcup Drive" in explorer, or on the N360 page you mention). As such, it becomes clear that the only way to remove files from an old backup set is to KILL the backup set altogether and run a brand new backup. But then you lose any advantage of having a bakcup solution in the first place! I am quite glad that I am only using a local drive: with an online option, you guys would have kept on charging me over and over and over for files I can no longer access because N360 crashed... This is not right !
With all this said, and with 3.5 being almost ready to be released, I am guessing there is no hope there will be a fix in place before 4.0 in April 2010... The backup capabilities of 360 made the scale tip in its favor (as opposed to NIS): I am guessing that I was wrong, and that I could have stayed with the Vista backup option.
Unless you have a workaround/solution/fix for this somewhere in your sleeve =)
Chris.
Hi again...
I forgot to mention one thing you might have known already: once N360 is "Not Responding", I basically have to reboot as there is no way to kill the window. Cannot kill ccSvcHst.exe for obvious reasons...
Chris.