When running an update from one source folder to two destinations could the speed be improved by allowing write to both destinations at the same time?
When I have set a backup from one source folder to two removable drives FFS always backs up to one drive, then the second. I have tried setting the source drive to two parallel operations and each of the destination drives to one parallel operation but this doesn't help.
i.e. operation is as below
d:\out ---> f:\in
d:\out ---> g:\in
D sits at about 30% utilisation through the whole process. F goes to 100% for the first half of the synch then G goes to 100% for the second half. I only ever use update synchronisation.
[Feature Request]:Speed up backup from one drive to two simultaneously.
- Posts: 3
- Joined: 27 Jun 2023
- Posts: 4056
- Joined: 11 Jun 2019
Multiple threads (parallel operations) are per folder-pair. Your settings will make D->F use two threads and then D->G use two threads, not make D sync to both locations at the same time. It isn't possible to do what you are asking with flash drivers unfortunately. With storage drives, according to Windows, you could create a mirror RAID, which has its own complications if you plan to separate the individual drivers. You could have a script that calls two individual FFS configs, one that syncs to F and the other that syncs to G, that can run simultaneously. If the source is a mechanical HDD, it may even be slower if you do this, but an SSD should be fine.
https://freefilesync.org/manual.php?topic=command-line
https://freefilesync.org/manual.php?topic=command-line
- Posts: 3
- Joined: 27 Jun 2023
@xCSxXenon
Thank you. I hadn't thought of using scripts with two FFS configs. I will give it a try. Hopefully it will be a bit faster :-).
Thank you. I hadn't thought of using scripts with two FFS configs. I will give it a try. Hopefully it will be a bit faster :-).
- Posts: 2450
- Joined: 22 Aug 2012
> You could have a script that calls two individual FFS configs
Be aware that Bnuff wants to sync D:\out to both the F:\in and G:\in location.
If this is done simultaneously via two separate FFS instances, the *.ffs_lock file in D:\out would still force the two syncs to run in sequence, which will be slower than syncing the two left-right pairs in a single FFS instance.
Only if you set the LockDirectoriesDuringSync flag to False, the two instances can really run simultaneously and could potentially be faster.
Make sure to read the risk of setting that flag to false. For your example there would be no risk, but note that that flag is (presently) a global setting.
Be aware that Bnuff wants to sync D:\out to both the F:\in and G:\in location.
If this is done simultaneously via two separate FFS instances, the *.ffs_lock file in D:\out would still force the two syncs to run in sequence, which will be slower than syncing the two left-right pairs in a single FFS instance.
Only if you set the LockDirectoriesDuringSync flag to False, the two instances can really run simultaneously and could potentially be faster.
Make sure to read the risk of setting that flag to false. For your example there would be no risk, but note that that flag is (presently) a global setting.
- Posts: 4056
- Joined: 11 Jun 2019
Ah yes, an oversight! Good looking out
- Posts: 3
- Joined: 27 Jun 2023
Thanks Guys. I did wonder if the scripting method would bypass the issue with two lock files but clearly not. Thanks Plerry and xCSxXenon. Excellent forum support.
Just to say I love the app and do have a Donation Edition. I always recommend to friends.
Just to say I love the app and do have a Donation Edition. I always recommend to friends.