Realtimesync is running but doesn't start sync

[aussiefries]

Hi all,

I've configured FreeFileSync to mirror two folders. I've pressed compare and saved a batch file.

I then started RealtimeSync, loaded the batch file and pressed Start. It says "Directory monitoring active".

I have created a text file in the folder on my pc, but it's not synced to the folder on my Time Capsule drive.

What did I forget?

Your help is much appreciated!

[aussiefries]

Solved:

As the Time Capsule acts as a server in a network, it needs to have a proper network name.
I initially named it "Time Capsule". However lower case and spaces are not always supported.
After I changed the name to "TIME-CAPSULE" the syncing process started!

[aussiefries]

[EDIT]

It still doesn't work.

FreeFileSync copies everything from my pc to the Time Capsule. No problems there.

However RealtimeSync is sitting in the taskbar and doing its "compare" which slows down the pc a lot, but it doesn't copy my new files from my pc to the Time Capsule.

Does RealtimeSync work in realtime at all? Or will it just compare both devices a few times per day and then copy the newest files?

Can someone please shed some light on this? If the software is unable to copy a file after it has been created to the backup device, it's useless for me.

Many thanks for your help

[Zenju]

RealtimeSync isn't doing anything relevant of its own, so it should never slow your PC down, nor even show up much processing in task manager. Instead it just registers at the OS to get notifications when files have been changed in the specified directories. All it does is call the command line. This is usually FFS, and this will do, depending on the filter settings, a full scan of the directories in order to determine what to sync.

[aussiefries]

Thank you for the clarification.

Can you please advise why newly created files are not automatically copied to the network drive? It only works if synced manually in FreeFileSync.

Furthermore, sometimes I receive error
"Cannot monitor directory "\\NAS\Data\".
Error Code 56: The network BIOS command limit has been reached. (ReadDirectoryChangesW)"

[Zenju]

The "ReadDirectoryChangesW" call depends on the underlying network drivers. Unfortunately these may have incomplete or broken implementations. RTS does propagate all errors it is informed of. But it's possible for buggy network drivers to fail silently.

[Daniel]

I have the same problem with error code 56. I tried it on three different PCs (Win 8, 7 and XP) with the same result. Is it possible to remove this problem?
Thank you for any answer.