Hello,
We're looking for a way to transfer weblogs almost continually.
We want to be able to copy even partial files, so when the Amazon Auto Scale kills the machine, we won't loose that tracking data (which was in the currently written web log file).
Example situation:
weblog00001.log - 1MB, closed, ready to be moved.
weblog00002.log - 1MB, closed, ready to be moved.
weblog00003.log - 238kb, still open by IIS, can be copied, can't be moved.
We installed Syncovery in a test machine, and configured it to use continues synchronization. The profile was also configured to move the files to the log server share folder.
Syncovery does move the closed files, and copy the open partial file (which are still being used by IIS to add every few seconds new lines), and overwrites the destination file with the new larger version of that file on each synchronization cycle, but when IIS releases that file, for some reason Syncovery doesn't move it completely to the destination folder as we expect it to do.
Could it be that after the initial delete failure, Syncovery stops trying to delete the file (move = copy and then delete), and just keeps copying it?
Can you suggest a more optimal way to do this synchronization?
Thanks