Hi,
Thank you for the terrific application. As a long-time user (and multi-time donator), I appreciate the work that has gone into this!
My organization has a policy to convert all files >1 year since last modified into 0 KB .symlinks. The .symlinks retain the file name and last-modified info but lose all of the file content. Is there a way that I can compare files solely based on the last-modified date/time?
Thank you!
Ramin
Compare files by timestamp only
- Posts: 2
- Joined: 27 Oct 2020
-
- Posts: 2451
- Joined: 22 Aug 2012
Your use case is not exactly clear.
Converted into symlinks at the source side or the destination side? And what about the backup(s)?
Nevertheless, files >1 year since last modified should also have been synced at least a year ago (assuming running daily or weekly FFS syncs).
Would exluding all files modified > e.g. 6 months ago from the FFS sync not do the job?
This could be achieved by setting the upper limit of the time span far in the future, and the lower limit 6 month ago (and update the low limit at least twice per year).
As soon as such a >1 year old file gets modified, it will then automatically be included in the sync again.
Converted into symlinks at the source side or the destination side? And what about the backup(s)?
Nevertheless, files >1 year since last modified should also have been synced at least a year ago (assuming running daily or weekly FFS syncs).
Would exluding all files modified > e.g. 6 months ago from the FFS sync not do the job?
This could be achieved by setting the upper limit of the time span far in the future, and the lower limit 6 month ago (and update the low limit at least twice per year).
As soon as such a >1 year old file gets modified, it will then automatically be included in the sync again.
- Posts: 2
- Joined: 27 Oct 2020
Hi,
Thanks for the info. On the destination side, the files are converted to .symlinks. I believe my organization moves the core data to tape backup which can be manually requested later. Nonetheless, the data is not immediately available for comparison. So FFS thinks there are terabytes to upload because the files differ in size and content.
I wasn't aware of the time span option. That's very helpful. It took much longer to compare but it did the job I needed it to do.
Ramin
Thanks for the info. On the destination side, the files are converted to .symlinks. I believe my organization moves the core data to tape backup which can be manually requested later. Nonetheless, the data is not immediately available for comparison. So FFS thinks there are terabytes to upload because the files differ in size and content.
I wasn't aware of the time span option. That's very helpful. It took much longer to compare but it did the job I needed it to do.
Ramin
