Moving or renaming a backed up file creates a copy in the backup set

Like many users, I use NSS Backup to archive picture and video files.  I typically copy these from my devices to a directory on my hard drive that is in the backup set, and then at a later time rename or move these files to other locations (also within the backup set) once they are organized and categorized (e.g. by date, event, etc.).  I've observed that renaming or moving files in the backup set has the effect of creating additional copies in the archive, which amounts to a lot of wasted storage.  I understand that these can be deleted manually (Manage Backup Sets -> Where -> Delete Backed Up Files) however this process is very slow and depends upon one remembering the names and locations of the original files.  It would be better if Backup provided a configuration option allowing the user to specify how to handle moved / renamed files (i.e. keep original or only new file), or perhaps a feature that could list all files in the backup set that no longer exist in their original locations and then provide the user with an option to restore or purge these from the archive.

In lieu of these options, going forward the only workaround I've been able to determine is to stage the files into a temporary directory until they are categorized and then delete the contents of this directory from the backup set periodically.  This workaround does not provide a solution for cleaning up the many existing redundant copies of files residing in my backup set from years of using the product before making this discovery.  I'd appreciate any other suggestions.

I have the same problem.  The only work around I have is to create new full backups each week, month or quarter, etc.. 

I then delete the old backup set from the Norton backup disk directory using Windows in one go and reboot the system so Norton can see that the backup set is no longer available.  Be careful you delete the correct backup if you have several! You will see the key name Norton uses not the name you called the backup set.  So you may need to identify the correct one by it's created date. This is quicker than letting Norton Backup program delete the backup set. Norton tries to protect all the files and delete each file one at a time from the backup set in case there is a power failure or you want to cancel.  As a result this can take many hours or days to complete with large backups!

This approach is good for managing backups and ensures that if you regularly rename of move files you backup sets have the latest file names and locations.  However there is one word of WARNING.   You back up your data to protect it.  If you have an original file that gets damaged, and you are unaware of this, you could delete the only good copy by constantly deleting old out of date backup sets.  If you keep the old backup sets and just create new ones each month you could end up with masses of disk space with effectively many copies of the same files.

I tend to keep my old backup sets for a year, If I have not found any problems with the original files missing or damaged in that time, then I just delete the old backup set.  This means I have taken reasonable precautions and saved on space.