Changes lost / overwritten, following realtime sync

[toof4st]

I followed:
http://www.tgrmn.com/web/kb/showall6.htm#85
Best Way to Sync Files Between 3 Computers (PCs or Servers)
Note about Real-Time Synchronization

I have prototyped all 4 profiles on my local machine, with 3 folders:
Computer1
Computer2
NAS

NAS can't handle VV, but Computer1 and Computer2 can sync to it.
So I have 4 profiles
Profile 1A:Computer1 to Computer2
Profile 1B:Computer1 to NAS
Profile 2A:Computer2 to Computer1
Profile 2B:Computer2 to NAS
In each case, the Source is monitored in realtime.
I also have Synchronize even if in conflict checked (to avoid the conflict error as recommended by one of your admins in another post - if you don't do this the sync starts to fail and nothing ever gets synced and I would have to manually resolve. And if I have to manually resolve, there is no point having backup software)

If I create a blank file on Computer1.
I then edit that file, and save some data into it a few seconds later.
I expect that file with data to be replicated to the other computer.

In fact what happens is:
1) I create a blank file on Computer1.
2) A blank file is detected on Computer1.
3) This gets synced to Computer 2 and to NAS. Via Profile 1A and 1B.
4) I save the file with data on Computer1.
5) Profile 2A and 2B, detect that that there is a new file on Computer2 as it is set to monitor the source in real time. These copy the blank file back to Computer1 and NAS. And I have a file with blank data in all locations.
6) Profile 1A and 1B detect a change in the file, from both steps 4 and 5. The blank file is compared to Computer 2 and NAS. And probably not copied because it is the same

This might seem like an edge case, but I know some software operates like this - creates the file first. Then runs some process (eg Database query which takse a second or 2), then saves data into it the file.

One question: Do you replicate the file timestamps of the files you copy so they always match? Because if you don't you should.

I haven't been able to check the timestamps on the file. However I imagine, the timestamp of the blank file copied to Computer2 in step 3, would be before the timestamp of the file containing data saved in step 4. So step 5 shouldn't overwrite the file on Computer 1, as the timestamp is older than the update file on Computer 1. Then step 6 should run, and copy the file with data to Computer 2.

[TGRMN Software]

Hi,

You are correct, in step 5:

>> 5) Profile 2A and 2B, detect that that there is a new file on Computer2 as it is set to monitor the source in real time. These copy the blank file back to Computer1 and NAS. And I have a file with blank data in all locations.

The file should be copied from Computer 1 to Computer 2, because the file is newer on Computer 1....
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[toof4st]

I don't understand your reply.

Step 5 isn't correct. Computer 2 shouldn't copy the blank file back to Computer 1, overwriting my updated file with the blank one.
I am only ever updating the file on Computer 1, but the backup process 2A deletes my changes made on Computer 1.

So is this something you are going to fix?

[TGRMN Software]

Step 5 should copy for Computer 1 to 2, because the file should be newer on Computer 1. Are you suing the synchronization method on all profiles? If you setup a log in profile settings -> execution on each profile, the log should contain more info on what ViceVersa finds. thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[toof4st]

Yes, the profiles settings are identical. I copied / pasted the xml.

I think I have established that it is down to the "no rescan" option, and what I believe is a bug in the "no rescan" option.

Each profile has "no rescan" set to "target". If I switch this off it works correctly and step 5 (as i documented it in my original post) does not trigger an overwrite of the file on Computer 1. Step 6 then runs correctly copying the updated data to Computer 2.

As I understand it, no rescan, means it will not rescan the entire folder structure. Which is a great option.
But before it is about to overwrite an individual file, it should scan that file that it is about overwrite, regardless of the "no rescan" setting, to ensure it hasn't been modified in the meantime.

[TGRMN Software]

Yes, if you use the norescan option with the sync method it can cause that issue, because the target is not rescanned each time.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com