FreeFileSync Forum

RSync does not copy files in readable format from one device to another. I'm using it now to 'backup' one share on my primary NAS, to my backup NAS. The Share appears on the backup NAS, but these are not readable files - the files are broken down into blocks with indicies, across multiple folders ...

Interesting... I don't know what SFTP server is or how to implement it, but I will look into this, thank you.
I would still need FreeFileSync in a docker container, though. Thoughts?

I am very interested in installing FreeFileSync on my NAS in a docker container. I want to be able to 'sync' all my files from the 'hostNAS' to a 'backupNAS' on the same network. How did you solve mounting a UNC path including the credentials? I assume I can install the Linux version on a linux ...

I am very interested in installing FreeFileSync on my NAS in a docker container. I want to be able to 'sync' all my files from the 'hostNAS' to a 'backupNAS' on the same network. How did you solve mounting a UNC path including the credentials? Do you have a link to the Linux virtual machine you used ...

Thanks, I appreciate the update on the threads & delay.

One the Processed... just seems odd to me, that in a file *SYNC* app, we wouldn't care about bytes transferred, but bytes *successfully* transferred. Same with the file count, if I tried to send a file 5 times, do I count it as 5 when it ...

Plus, it also appears that the Processed: (xx.x GB) is the total attempted... NOT the total completed. I am copying 1.5GB files, it has completed 2 of 6 - the other 4 are stuck in thread retires... but the display is showing 16.0 GB Processed... which may well be attempts... but is definitely not ...

So you have no idea what the delay is actually delaying? The retry, or the processing of all the threads? It appears to me, that when an 'Automatic retry' is displayed on the screen, the other threads are stuck - or at least the update to the display of Processed: does not update... idk.

I was ...

When using automatic retries, I had hoped that the delay option would simply delay the retry of the selected thread. It appears that ALL threads suspend (delay) while waiting for this timeout. I especially noticed it when more than one thread had an error/retry. I had set the delay for 20 seconds ...

Sweet! Thank you!

I just purchased a new NAS and I want to eliminate my current cloud storage requirements, so I plan to backup my new NAS to my old NAS using FreeFileSync. I am on MacOS. Can anyone point me to a resource here showing how I can automate this in the Mac environment? I understand I can use batch files ...

Good news. After FFS copied all the files over to gDrive again - subsequent runs of the job only process updates as expected. For some reason, it is erroring on a few files - it says it's trying to write a file but it already exists... it's true the file is there, not sure why it's trying to write ...

I found what I was looking for!! I am able to set the timeout duration AND the retry count. However, this does not work when a file already exists - it could retry all day, it isn't going to help... however, there is an 'ignore errors'... which, works well - you can still see the errors at the end.

Good tip on the 'permanently delete' - thanks!

Thanks! I'll have to look then next time I have to restart the app... also another anomaly I can't pin down... my normal rock-steady iMac (reboot every 6 months), now has to reboot every other day when I run FFS... eventually Finder is unresponsive, then finally BSOD (black for MacOS)... but I can't ...

What sync settings are you using?
If Date & Time, are the dates/times the same, between your source & the original uploaded files?
Are the dates/times the same, between your source & the FFS uploaded files?

Are the relative directory trees the same between your original upload & the what you are ...

I have a local fileshare that I did a 'drag and drop' onto Google Drive (300GB took 3 days)... folder names, file names, everything the same. To not have to keep the two in sync manually, I pointed filesync to the local fileshare and then to the google drive folder. FileSync is reuploading every ...

Can you please either eliminate, allow me to control, or drastically increase the timeout on the:

CURLE_OPERATION_TIMEDOUT: Operation too slow. Less than 1 bytes/sec transferred the last 15 seconds

Best case would be to simply allow for retries, perhaps show a retry counter. But this stops my file ...