Initial tests not working as expected
Posted: Fri May 21, 2021 3:02 pm
Hi,
We are trying Syncovery to see if it would fit our needs. We have many TB of data that we need to synchronize from some server shares to a Synology NAS.
We adjusted the file versioning accordingly and did a first synchronization which took about 30 hours, that was expected since it`s the first sync.
After this was completed we started the sync again, we thought it wouldn't take that long since almost nothing have changed since the first pass but the software started to apply versioning on every file and sync a second copy of them.
As an example we had an acronis image dated from 2019 on the server which synced correctly the first pass. On the second pass Syncovery did rename the file with a timestamp and recopied the same file again which will lead to 2 exact same files on the NAS, one with a timestamp (versioned) and the new copy. This file hasn`t changed since 2 years, so why does Syncovery need to version it ?
Any help will be very appreciated.
Thanks
We are trying Syncovery to see if it would fit our needs. We have many TB of data that we need to synchronize from some server shares to a Synology NAS.
We adjusted the file versioning accordingly and did a first synchronization which took about 30 hours, that was expected since it`s the first sync.
After this was completed we started the sync again, we thought it wouldn't take that long since almost nothing have changed since the first pass but the software started to apply versioning on every file and sync a second copy of them.
As an example we had an acronis image dated from 2019 on the server which synced correctly the first pass. On the second pass Syncovery did rename the file with a timestamp and recopied the same file again which will lead to 2 exact same files on the NAS, one with a timestamp (versioned) and the new copy. This file hasn`t changed since 2 years, so why does Syncovery need to version it ?
Any help will be very appreciated.
Thanks