FreeFileSync Forum

I tried your suggestion, but it didn't produce a crash dump.

Although I sorted out my batch file, I'm still getting the error in the task scheduler Last Run Result, even when I don't call anything on completion. I don't know whether this is a recent thing, because I don't look at it normally. I did recently update FFS to 11.2. Any known issues I could look ...

Thanks for the suggestions.

So, only by manual intervention, not by using FFS during backup.

I have other similar files, like .dstore & folder.jpg. I was hoping for a way to say exclude them from source, but if they exist on target, delete them.

I suppose another other way is to use a clean up ...

I have thumbs.db files on my target (NAS) which I don't really want (not sure how they got there). FFS is set to exclude them which it seems, means they are not considered at all. Is there a way to configure FFS so they get deleted?

Maybe, but I thought I would ask how FFS operates in that regard, since I couldn't see anything in the documentation or forum posts.

I may have found a problem though - I have an & (ampersand) in my path which needs special handling in a batch file. I'll find out tonight whether I fixed it.

I have added a .bat file to On Completion which doesn't appear to be working. I have ffs running unattended from a scheduled task and the PostSyncAction is set to sleep. I'm wondering whether ffs puts the computer to sleep before the .bat file completes? The ffs log shows it calls the .bat file ...

Update: in my case, the folder existed in the Version History tree as "IMAGES", that is all uppercase, and the file that FFS was trying to move was in folder "Images", only first letter is a uppercase. When I changed the Version History folder to "Images", FFS completed normally.

Assume this is a ...

I'm experiencing the same problem with versioning. Used to work ok. I moved these files from one folder to another. Those in the target folder were backed up. But FFS can't move the original to the version folder on the nas. Windows 10 machine mirrored to Synolgy nas. FFS 9.5. Error message in the ...

I switched all the references to X:\ drive to use SFTP instead and now it runs fine in batch and interactive. I still kept the target folders using mapped drive W:\ and FFS works with that OK. It's just the X:\ that I used on the version history folders that I switched. So it can't be anything to so ...

Tried upgrading to version 8.0. Still getting same error. Don't know why it's not logged in pml or how to get more error info. I suspect the reason it showed the pdf files were saved is that they were new files, so nothing needed to be moved into version history on the server.

I'm reluctantly going ...

I sent you a pml file yesterday. Hope it helps. I'm using version 7.8. Thanks.

I'm getting the following error:-

Error Cannot create directory "X:\".
Error Code 3: The system cannot find the path specified. (CreateDirectory)

X:\ is a mapped network drive to a NAS share to hold my version history. I can see the drive in Windows Explorer and write to it.

I have specified X ...

I would like to add my vote for a limit on the number of previous versions of files.

Age would be useful where a file changes rapidly. Even if you kept say 30 copies, you might only be able to go back one day.

SpiderOak (spideroak.com) has a useful utility to archive versions so for example you ...

Managed to answer my own question. For anyone else struggling with this, the answer is to specify the full path of where you want the revisions to go to. In my example that would be:-

X:\Revisions\Users\My Name\My Documents

Also note, I had several source/target folders set up to mirror in the ...

I seem to have this problem also.

Say I'm mirroring D:\Users\My Name\My Documents\ to X:\Users\My Name\My Documents\ and I have Versioning set to X:\Revisions with Timestamp.

I have a Folder\File.txt on X:\ in My Documents but not on D:\.

Folder\File.txt gets moved to X:\Revisions\Folder\File ...