We have a setup where BestSync is used for transferring files from one network to another network over LAN-LAN VPN and then the files are further processed at a certain frequency from the target folders.
Right now, we have an issue where the files are being processed from the target folder even before they are copied to that location completely causing incomplete files.
Few years back, when we had a similar issue with BestSync we created a rule in our app to ignore files starting with _BS since we thought the temp files created by BestSync started with that naming convention. And that resolved the issue for us until we started using the latest version of BestSync and in this version it doesn't seem to create temp files in that naming convention.
Also to work around the issue, we checked the write option on the file in the target folder and it is returning true indicating that the file can be modified, so we assumed that the file copy is complete and so we can consider that file for processing. But even this resulted in incomplete files.
The Best Sync logs does not indicate any failures, so I think the files are copied correctly, it is just the further processing started before the files are copied completely.
Any ideas on how we can identify the files that are copied completely to avoid this issue.
Thanks in advamce.