Lady Fitzgerald:
Thought I'd ask here about a minor issue with FFS that I've noticed. I'm wondering if you've seen it and if I'm missing something in configuration.
I use it in a "mirror" fashion. No versioning, etc. Just a pure replica, D drive to E drive, which are literally separate hard drives.
Imagine this folder:
D:\downloads\stuff
Let's say stuff contains files A, B, and C.
You run FFS and the folder and files are all replicated to the E drive.
Over a period of time, you eventually delete A, B, C and the stuff folder from the D drive and continue to run FFS normally, probably at least daily. You rarely look at the E drive.
Months later, you discover that the E drive backup contains an empty stuff folder. A, B, and C are gone, but the folder remains. A, B, C, and the stuff folder were deleted from D weeks or months previously. So, drive E is not a replica of drive D.
Oddly, this appears to be an occasional thing. Most folders that were deleted from D are in fact deleted from E when FFS is run, but a few seem to still exist and are empty. Because it doesn't always occur, I doubt this is a config issue. It's never FILES that remain on E, it's just occasional empty FOLDERS.
I'm reasonably sure I've seen this same issue with other file backup programs.
It's not a big deal as the empty folders take up little space and I would never notice them if I didn't open the E drive and look from time to time. It's just a curiosity.
I'm wondering if has to do with the sequence in which I do the deletions from D? All at once (folder and the 3 files simultaneously) or item by item (2 files maybe on Monday, another on Wednesday, the then empty folder on Friday). Maybe the first case would not lead to empty folders on E, but the second case would? I have not experimented.
Comments?