Renamed folders in a Mirrored Folder

[Anonymous]

Hello,

I've been using RealTimeSync to mirror a set of folders from my computer to a
network drive to act as a continuous backup, and it's been working very well
-- I'm very happy with FreeFileSync.

I just have one little problem, and I'd like to find out if anyone else has
noticed the same behaviour: When I rename a folder on my computer,
RealFileSync fires up FreeFileSync, and I then see the new folder appear on
the network drive. I assume it must be creating a new folder, copying the
contents from my computer's renamed folder, then deleting the contents of the
old-named folder on the network drive. That all works fine, but it never
deletes the old folder itself, even though the folder is empty by then.

I'm doing a lot of renaming as I reorganize some of my legacy software
development projects, so the mirrored folder on the network drive is
accumulating more and more empty folders as time goes on. Has anyone else seen
this? I could, of course, just delete the entire network folder and let
everything get mirrored from scratch, but this is a many-gigabyte folder, so
I'd rather not solve the problem that way.

Thanks for any help anyone can give.

[Zenju]

This seems to an issue related to FreeFileSync and not RealtimeSync. You can
open a bug tracker item for this and add some detailed information about the
expected and actual behavior.

[Anonymous]

Thanks for the quick reply -- shall do. :)

[Anonymous]

Hmm. It turns out that mirroring renamed folders on my local hard drive works
fine, and simple mirroring to my network drive works OK too. The ffs_batch job
I use to sync my source-code folders to the network drive has a long list of
file and file-type inclusions and exclusions, so I suspect the problem is in
there somewhere. I'll keep experimenting with it to see if there's an actual
bug or if I'm doing something wrong.

Thanks for your help, and for the motivation to finally track this down in
more detail. :-)