I'm running RealTimeSync.
Whenever a backup is created on the computer (Win11), it is of course locked by another process (backup software) during the creation time.
I keep getting the annoying message with the sound from FreeFileSync about the locked file (once a minute).
Can't you set it somewhere/somehow so that these error messages...
1. ...don't come up so often in a row?
2. ...locked files only trigger an error message after a certain time?
The problem is that if I set 60 repetitions and 60 seconds wait in the global settings, for example, the entire synchronization job (several folder pairs) is blocked by the locked file and nothing is synchronized anywhere near as quickly as possible.
Please don't give the tip to use multiple FreeFileSync instances, that's bullshit and it's extremely annoying in the taskbar with the constantly popping up sync activity messages (even in the background).
I would expect synchronization software to let me set for each folder pair after what time errors are raised, what should be done how often in the event of errors, etc.
Reducing warnings about locked files
- Posts: 6
- Joined: 18 Oct 2024
-
- Posts: 4270
- Joined: 11 Jun 2019
I would look into the "Copy locked files" option, which uses VSS to copy locked files
- Posts: 6
- Joined: 18 Oct 2024
Thank you very much for the information, I know, but unfortunately that is not a solution.
The problem is that the file is created over a period of time and is therefore constantly changing.
There is no point in constantly synchronizing the file even though it is not yet finished.
And unfortunately this backup takes quite a long time and is done twice a week.
The problem is that the file is created over a period of time and is therefore constantly changing.
There is no point in constantly synchronizing the file even though it is not yet finished.
And unfortunately this backup takes quite a long time and is done twice a week.
- Posts: 1092
- Joined: 8 May 2006
How about the Ignore Errors (option, in the Comparison tab).
Would that blanket ignore all errors, & just proceed to the next file.
(Which I guess would relegate you to actually checking the Log...)
But that's not the issue, particularly, is it...
RTS, so it's polling & it sees the file changing, continually, over time.
So it wants to copy the new, changed file, again & again & again...
Where you're saying, the file is still being written to all during that time & all you're wanting is that last, final version?
So how does FFS know if the file is "finished" or not?
It knows it cannot copy the file, cause the file is in a "locked" state.
And because you're using RTS, it is polling, & trys again & again, & notifies you each time it does...
If it wasn't RTS, it would attempt the copy once, fail, notify, & that would be that, it would just go on to the next file.
So... ?
Would that blanket ignore all errors, & just proceed to the next file.
(Which I guess would relegate you to actually checking the Log...)
But that's not the issue, particularly, is it...
RTS, so it's polling & it sees the file changing, continually, over time.
So it wants to copy the new, changed file, again & again & again...
Where you're saying, the file is still being written to all during that time & all you're wanting is that last, final version?
So how does FFS know if the file is "finished" or not?
It knows it cannot copy the file, cause the file is in a "locked" state.
And because you're using RTS, it is polling, & trys again & again, & notifies you each time it does...
If it wasn't RTS, it would attempt the copy once, fail, notify, & that would be that, it would just go on to the next file.
So... ?
