I jsut started using RTS to mirror the content of 2 folders in my PC. For that I created the batch job in FFS and loaded it into RTS and then I put the RTS file in shell:startup (Win10) as per the video tutorial.
I set a "long" idle time of 1h (3600 seconds). It is my understanding that the way it works is like this:
When a change in the source is triggered, the timer starts. If 3600 pass with no additional changes in the folder, then they are mirrored to the destination folder. If more changes are registered after the 1st, the timer restarts.
my question is this: what happens if the PC is restarted or shutdown half way to the idle time? say 1000 seconds into the 3600 timer. Are the files still gonna be copied after the PC is restarted? or that batch of changes are lost because the triggering was skipped?
folder mirror RTS job. How does it behave if PC is restarted before meeting idle time?
- Posts: 1
- Joined: 6 Nov 2024
-
- Posts: 2450
- Joined: 22 Aug 2012
Your understanding of how/when RTS will launch an FFS synchronization seems correct.
If you restart your computer before reaching the full idle time, no FFS sync has been launched yet.
Because you restart your RTS job via your startup folder, RTS will restart, but the pre-restart trigger of a change in a RTS monitored folder will be lost. So, RTS will then not launch a sync until it detects at least one new change and the idle time expires.
The change(s) that triggered RTS less than your idle time before your restart, will only be synced during the first FFS sync after your restart, after detecting one or more new changes following your restart.
By the way:
Setting your idle time to 1hr is quite extreme, and seems out of line with the purpose of the idle time, as described on the RTS manual page.
If you restart your computer before reaching the full idle time, no FFS sync has been launched yet.
Because you restart your RTS job via your startup folder, RTS will restart, but the pre-restart trigger of a change in a RTS monitored folder will be lost. So, RTS will then not launch a sync until it detects at least one new change and the idle time expires.
The change(s) that triggered RTS less than your idle time before your restart, will only be synced during the first FFS sync after your restart, after detecting one or more new changes following your restart.
By the way:
Setting your idle time to 1hr is quite extreme, and seems out of line with the purpose of the idle time, as described on the RTS manual page.
-
- Posts: 4055
- Joined: 11 Jun 2019
Just a note, when a RTS configuration is launched, it runs an initial sync automatically. I don't if that is documented, but every time I have ever started an RTS session, it runs the command once, no matter what.
Quick edit: I just tested this. It is true in my testing. Although, it does seem to have waited for the idle time before running. It would be at least an hour before the OP would see the sync occur, but it should still occur even if no other changes are registered.
Quick edit: I just tested this. It is true in my testing. Although, it does seem to have waited for the idle time before running. It would be at least an hour before the OP would see the sync occur, but it should still occur even if no other changes are registered.
