I'm starting to think that the issue of case in directory names is a red herring. I wrote a quick program to verify the names on objects on drive N: compared with drive F: ... zero.
What seems to be happening is that some files are triggering this message, even when there's nothing apparently wrong with the output directory names.
I can speculate... suppose my new drive N: is mis-behaving and that a directory which exists is occasionally reported as NOT present. This would cause SyncBackPro to attempt to create the directory. But then the filesystem objects that a directory with the same name already exists.
Why might I think my new N: drive is mis-behaving? I just got two popups saying that N: needed to be formatted before Windows could use it. But when I checked in Windows Explorer, it all seems OK.
Perhaps it's time to go to the Drobo forum...
What seems to be happening is that some files are triggering this message, even when there's nothing apparently wrong with the output directory names.
I can speculate... suppose my new drive N: is mis-behaving and that a directory which exists is occasionally reported as NOT present. This would cause SyncBackPro to attempt to create the directory. But then the filesystem objects that a directory with the same name already exists.
Why might I think my new N: drive is mis-behaving? I just got two popups saying that N: needed to be formatted before Windows could use it. But when I checked in Windows Explorer, it all seems OK.
Perhaps it's time to go to the Drobo forum...