Syncronisation Conflict with copied/restored files

HHRodney · Guest

Hi,

I have found that if a file is replaced with an older version from another backup source then VV considers this a conflict instead of synchronising to the restored file.

I would have expected VV to compare both source and target to the database and see that the restored file is a change that would be synchronised to the other side. This is what I would want to happen.

Cheers
Rodney

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Hello, which version / build are you using? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

HHRodney · Guest

Hi,
ViceVersa PRO 2.5 Build 2514 64-bit [Server]
Thanks

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8758

Thanks, I checked and ViceVersa will not sync an older file over a newer one.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

HHRodney · Joined: 29 Apr 2016 Posts: 2

How can we make it so it does do it?

HHRodney · Joined: 29 Apr 2016 Posts: 2

Can you please comment if this will be fixed?
It surely cant be designed that way. If you copy a new file to either side it will sync both ways.
I need it to sync if an older file is restored to either side.

I have also noticed that if there is a true conflict (file changes on both sides) then the email result will be:
Result: Execution completed with conflicts. Some files were in conflict. These files need to be reconciled manually.

If it is a false conflict because a file has changed to an older date then the result will be:
Result: Execution completed with file copy/delete errors.

You need to read further down the log to see that there are files listed as being in conflict.

Can this be fixed and/or an option to ignore this type of conflict added.

Cheers
Rodney