I'm using RealTimeSync to trigger my sync runs but these can run for many hours. By the end there have typically been more files changed within the scanned folders but these are "missed" and not picked up until the next change is detected.
Any way to force a further sync check at the end of the run?
Force re-run of the scan at end of sync?
- Posts: 29
- Joined: 9 Jun 2020
-
- Posts: 2450
- Joined: 22 Aug 2012
Instead of having RealTimeSync (RTS) directly launch a FreeFileSync (FFS) sync, you could try having RTS launch a script (e.g. a *.bat oe *.cmd file) that launches the FFS sync twice in succession, waiting for the first FFS run to end before launching the second FFS run.
But to be honest, I don't see how that is fundamentally going to solve your problem.
Also during the second FFS run files may get changed within the scanned folders but these are "missed" and not picked up until the next change is detected.
It may be better to, next to RTS launching a single FFS run upon detecting changes, run the same FFS sync as a scheduled task. Depending on your use-case, that FFS task may then run at log-off or shutdown, or at a fixed time, e.g. overnight at 1AM.
But to be honest, I don't see how that is fundamentally going to solve your problem.
Also during the second FFS run files may get changed within the scanned folders but these are "missed" and not picked up until the next change is detected.
It may be better to, next to RTS launching a single FFS run upon detecting changes, run the same FFS sync as a scheduled task. Depending on your use-case, that FFS task may then run at log-off or shutdown, or at a fixed time, e.g. overnight at 1AM.
- Posts: 29
- Joined: 9 Jun 2020
The above is very messy and is platform-specific.
Ideally the sync itself should pick up that there have been further changes and there'd be an option to re-run in this scenario.
Ideally the sync itself should pick up that there have been further changes and there'd be an option to re-run in this scenario.
-
- Posts: 4056
- Joined: 11 Jun 2019
Either increase your idle time for RTS or your scenario is better dealt with by a scheduled task and periodic syncing
- Posts: 29
- Joined: 9 Jun 2020
I'd have to increase my idle time to 14, 16 or more hours. That's not suitable at all.
Scheduled tasks completely negates the file monitoring capabilities. I want my files synced as soon as possible after I've changed them.
Scheduled tasks completely negates the file monitoring capabilities. I want my files synced as soon as possible after I've changed them.
-
- Posts: 4056
- Joined: 11 Jun 2019
If they are changing that often, then why does it matter if files may change during a sync, resulting in them not being synced? Won't another change be detected very soon after? FFS only syncs changes, so a sync that takes that long sounds very abnormal. What are you syncing from/to and how big with how many files?
- Posts: 29
- Joined: 9 Jun 2020
I have two primary use cases. Some examples:
1. I want to sync several large TV series or a 4K Movie - say 50GB+. This would take 5 hours+ with my max upload speed. This occurs every few days.
2. I upload a single TV ep (say 1GB or less) to a folder I share with a friend, for them to be able to watch or download. This occurs most days but usually no more than once per day.
When scenario 1 is in progress scenario 2 typically also occurs. So I leave the multi hour sync in progress, unattended. Then unless I remember to manually kick off another sync once it completes, the file in scenario two will just sit there until a further file change is detected, which could be hours or days.
I want the file in scenario 2 to be delivered ASAP and without manual intervention or scheduling. I guess I could try to somehow run a touch command to trigger an RTS run at the end of my batch. Is there a way to do this?
1. I want to sync several large TV series or a 4K Movie - say 50GB+. This would take 5 hours+ with my max upload speed. This occurs every few days.
2. I upload a single TV ep (say 1GB or less) to a folder I share with a friend, for them to be able to watch or download. This occurs most days but usually no more than once per day.
When scenario 1 is in progress scenario 2 typically also occurs. So I leave the multi hour sync in progress, unattended. Then unless I remember to manually kick off another sync once it completes, the file in scenario two will just sit there until a further file change is detected, which could be hours or days.
I want the file in scenario 2 to be delivered ASAP and without manual intervention or scheduling. I guess I could try to somehow run a touch command to trigger an RTS run at the end of my batch. Is there a way to do this?
-
- Posts: 4056
- Joined: 11 Jun 2019
I see... I can think of two options:
1) You could run a post-sync command that evaluates the exit code. This would only work if FFS would detect the change mid-sync and actually change the exit code to something other than 0 (success)
2) Have the post-sync command run the batch job it is called from and just have FFS running all the time, run after run
Better yet, I would guess, and hope, that the Movies and TV shows are in different folders, so you could set up sperate syncs and RTS sessions for each
1) You could run a post-sync command that evaluates the exit code. This would only work if FFS would detect the change mid-sync and actually change the exit code to something other than 0 (success)
2) Have the post-sync command run the batch job it is called from and just have FFS running all the time, run after run
Better yet, I would guess, and hope, that the Movies and TV shows are in different folders, so you could set up sperate syncs and RTS sessions for each
