Hi, I am trying to mirror a folder located in a mapped network into a local folder in my PC.
The synchronization works when I press the Start button in RealTimeSync. But it doesn't run again after the Idle time I set up. It will work every time I press the Start button.
I am using the UNC path of the shared folder.
I tested RealTimeSync with the same batch file to mirror a local folder (instead of the mapped folder) and it works correctly.
Any idea?
RealTimeSync I need to press Start button
- Posts: 3
- Joined: 18 Jun 2020
-
- Posts: 4867
- Joined: 11 Jun 2019
Use the drive letter instead of the UNC path
- Posts: 3
- Joined: 18 Jun 2020
Thanks, but I tried the drive letter, same issue.
After some trials, I get some interesting points:
If I add/remove a file to/from the main folder I am mirroring (NAS), this does trigger the Mirroring.
If I add/remove a file to/from a subfolder of the main folder I am mirroring (NAS), this doesn't trigger the Mirroring.
If I add a folder with subfolders and files inside at the same time to the main folder I am mirroring (NAS), this does trigger the Mirroring.
If I add/remove a file to/from the destination folder/any subfolder in my PC, this does trigger the Mirroring.
If I press the Start button, this triggers the Mirroring.
After some trials, I get some interesting points:
If I add/remove a file to/from the main folder I am mirroring (NAS), this does trigger the Mirroring.
If I add/remove a file to/from a subfolder of the main folder I am mirroring (NAS), this doesn't trigger the Mirroring.
If I add a folder with subfolders and files inside at the same time to the main folder I am mirroring (NAS), this does trigger the Mirroring.
If I add/remove a file to/from the destination folder/any subfolder in my PC, this does trigger the Mirroring.
If I press the Start button, this triggers the Mirroring.
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
When pressing "Start" RealTimeSync behaves as if it received a change notification to kick things off, i.e. it waits for uninterrupted "idle time" seconds and runs the command line.
Only from there on RTS starts to monitor for change notifications it receives from the operating system. If there are none, there is nothing RTS can do about it. Usually it's just a badly-written/incomplete network driver implementation. Worse, these buggy drivers often do not even fail (with some error code), but just do nothing.
Only from there on RTS starts to monitor for change notifications it receives from the operating system. If there are none, there is nothing RTS can do about it. Usually it's just a badly-written/incomplete network driver implementation. Worse, these buggy drivers often do not even fail (with some error code), but just do nothing.