Author |
Message |
achan_cc
Joined: 19 Sep 2016 Posts: 23
|
Posted: Thu Oct 24, 2019 3:32 pm Post subject: File will be skipped message |
|
|
Hello,
Does the following message mean that the next time the file (70001.wav) is changed, ViceVersa will not attempt to sync it? If yes, is there any way around this?
- Conflict File List:
** Conflict - ..\700001.wav (CHANGED) (342.56KB) (2019-10-24 11:26:38 AM) <-> \\..\700001.wav (CHANGED) (342.56KB) (2019-10-24 11:26:38 AM)
File Copy Errors:
Copying file ..\700001.wav <to> \\..\700001.wav (342.56KB) (Overwriting) ... [The size, attributes and/or timestamp of the file "\\..\700001.wav" have changed since the last scanning and comparison. File will be skipped.] [ERROR].
Thanks,
AC |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
|
Back to top |
|
|
achan_cc
Joined: 19 Sep 2016 Posts: 23
|
Posted: Fri Oct 25, 2019 2:49 pm Post subject: |
|
|
Not yet . But if I do enable this, would that mean that files that are actually older (in the source) will copy over the newer files in the target?
NOTE: I think the reason for this is because I have 2 source servers sync'ing to the same target server. The 2 source servers also sync between each other. So when 700001.wav changed on server S1 it was synced to the server S2, and the target server. And so when S2 got the 700001.wav it tried to sync it to the target server as well. Not sure why VVEngine thinks they are different files when the file on S2 has the same size and timestamp as the target?
Not sure how to get around this?
Thanks,
AC |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
Posted: Tue Oct 29, 2019 11:08 pm Post subject: |
|
|
If you set ViceVersa to sync file conflicts it will then keep both files and rename the older file with a _CONFLICT suffix.
Which version/build of ViceVersa are you using?
thank you _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
achan_cc
Joined: 19 Sep 2016 Posts: 23
|
Posted: Wed Oct 30, 2019 3:23 pm Post subject: |
|
|
If the older file (e.g. testfile.txt) is on the source server does that mean that it will be renamed to testfile.txt_CONFLICT suffix, and thus resulting in the source server not have a file called "testfile.txt"?
We are using ViceVersa PRO 2.5 Build 2517.
thanks,
AC |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
Posted: Wed Oct 30, 2019 10:05 pm Post subject: |
|
|
Hi, the newer file will be copied over the older file, but the older file will be renamed with suffix _CONFLICT before that happens, so both file names will be present. _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
achan_cc
Joined: 19 Sep 2016 Posts: 23
|
Posted: Fri Nov 01, 2019 8:58 pm Post subject: |
|
|
Is this true if we have the following settings:
- Execution -> Method = Synchronization,
- Advanced Settings -> Synchronize files even if in conflict (synchronization method) is enabled
- Advanced Settings -> Synchronize files one-way only: source to target (synchronization method) is enabled
With the above settings, if the OLDER file is on the SOURCE server, will VVEngine still copy the NEWER file from the DESTINATION server back to the SOURCE server?
Thanks,
AC |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
|
Back to top |
|
|
achan_cc
Joined: 19 Sep 2016 Posts: 23
|
Posted: Tue Nov 05, 2019 4:02 pm Post subject: |
|
|
I have 2 source servers sync'ing to the same target server. and the 2 source servers also sync between each other.
So on each of the 2 source servers I have 2 profiles each, both essentially set up the same way.
- S1-Profile1 syncs one way to T1
- S1-Profile2 syncs one way to S2
- S2-Profile1 syncs one way to T1
- S2-Profile2 syncs one way to S1 |
|
Back to top |
|
|
|