Versioning - New versions when file not deleted

[Houseton]

Hi,

Having an odd issue. New versions of files are being made even when the files are not being deleted. I have my synch variant set to update instead of mirror. Is this why this would be happening?

My versioning is set to Timestamp and my comparison is set to Date and Size.

What I'm looking for is if a file is deleted, not modified, for it to be versioned with the date. Files like PST and database files, do they make new files when they are used (different CRC?) so FFS thinks it's a new file and the old file is gone?

Any information on this would be truly amazing. My JBOD is filling up with redundant version files of files that still exist.

[Houseton]

So, I may have figured it out. Files that are containers (such as database files and PST files) might not change in size when things are removed but the modification date does change. Still doesn't explain why FFS thinks this means the old file was deleted and then Versions it.

I think for versioning it should also look at the filename. If the filename hasn't changed but the modification and/or size has, do not version. If running another synchronization, the file is not there version it.

Again maybe I have versioning wrong but it shouldn't be versioning files that aren't deleted.

edit:
I am an idiot. So versioning is backup up previous backup copies. When a new version of the backup shows up, instead of deleting the old version, it versions it. Makes sense now why it is doing what it's doing...
There should be a way to limit the amount of them it makes though. I saw another thread asking for this feature, but Zenju seemed against it.

[DrLove73]

Btw. Outlook changes the file headers even if there was no change in e-mails. So only relevant info in this case is modification date.