Versioning option not working

[halyee]

I have been able to use the versioning option in the past, but suddenly deleted/modified files are going to the recycle bin (according to the log). What is going on? I have checked that versioning is, indeed, ENABLED, with a valid folder path, 180 days retention, 20 versions maximum.

[halyee]

I reduced my retention to 45 days and was able to get overwritten files were being sent to the archive. Deletes were still being dispatched by FFS straight to the recycle bin.

Then, I turned off the database option for tracking files altogether, and that seemed to solve the problem. Now, both deleted and modified files are being archived. The only problem is that my archive is "somewhat" polluted because renames will get archived as a deleted file.

Is versioning only partially supported under database management? I am concerned about this apparent "silent-failure" where deleted files don't get archived if using database feature.

[xCSxXenon]

Are you sure the actual files are being sent to the Recycle Bin? Maybe FFS is cleaning up old versions of files that were outside the set parameters and sending those to the Recycle Bin?

[halyee]

Thanks for your idea...I am 100% sure the file being sent to the recycle bin is/was a live file and not an old version. It was part of a controlled test where I (a) created a file on the source drive, (b) ensured that the sync job had completed such that the new file was properly created on the target drive, then (c) deleted the file on the source drive and (d) ran the sync job again. Results: The log shows that the file on target drive was moved to the recycle bin. Important note: If I modified the file between steps (b) and (c), overwritten (interim) versions would properly appear in the archive.