FreeFileSync Forum

Thanks for the replies; this is now resolved.

The problem was with TrueNAS (actually Samba) and not FreeFileSync.

Apparently the new version of Samba that TrueNAS 12 ships with doesn't allow unresolvable Windows ACL SIDs. I had some files and directories with SIDs leftover from an old domain trust ...

Yes, it is still enabled. Program settings appear to have carried over to the new version.

After upgrading to 11.17 (from - I think - 11.14), I'm hitting some permissions errors syncing files from Windows (Server 2016) to a TrueNAS (ver 12.0u8 - recently upgraded from 11.3) CIFS/SMB share.

I'm running FFS the same way I was with the old version - in fact using the same config files. I ...

Thanks for posting - glad this helped!

After a lot of digging, this is now solved - and it was a FreeNAS issue, not a FFS issue.

This happened because of a difference in the way BSD (FreeNAS) and Windows handle file user and group ownership.

The short answer: in the FreeNAS Samba service configuration options add this to Auxiliary ...

I'm syncing files and directories to an SMB share on a FreeNAS server, with the "Copy DACL/SACL/owner/group" option enabled, and with full control privilege setting on the FreeNAS side. Both the source and destination (FreeNAS) are joined to the AD domain.

Most files and directories copy just fine ...

Great suggestion to use a mirror initially, I will do that.

Regarding why to 2-way sync with the backup server, the backup is also the failover server (using DFS) - if the primary server fails the backup will take over as the active file server and so could potentially have changes to sync back ...

I have a production file server and a backup server that I 2-way sync files between.

I want to transition from the current backup server to a new one. My initial thought was to set up another FFS batch job to sync with the second server, staggering the runtimes, until the new backup server is in ...

Update: I was focusing on the local lock file because that's what I was seeing FFS refer to (when running manually). Turns out, there was a lock file on the OTHER side of the sync as well. After I killed the background processes and removed BOTH lock files, a manual run then worked.

I'm still not ...

Administrator is the current user; that's the only account used on this server

It's currently running as administrator.

It is repeatable, and happening again. To try to clear it, we kill all running FreeFileSync processes, remove the lock file, and manually start a sync - the lock file is recreated and it hangs.

The manual sync window says "Waiting while directory is in use ...

Hi!

FFS is a great tool!

I have run into a couple situations though where stale lock files (sync.ffs_lock) cause subsequent runs to get stuck - this seemingly happens at random. There are two FFS instances configured on the system, each syncing a different folder (ie d:\datastore\folder1 and d ...

I tested a bit with the "run minimized" and "ignore errors" options unchecked, but unfortunately the process seems to hang in the background (possibly waiting for some sort of input). I had to re-enable these for it to sync normally.

Is there a way to access the program output window/popups while ...

I've been testing FFS for a few months now, and have been so impressed that I paid for several donation copies. Thanks for good, solid software that "just works"!

I'm doing 2-way sync to an offsite backup storage server and plan to leverage DFS for redundancy between the primary and backup pools ...