Why task converted from Contribute to Echo does not delete data on destination ?

[Francois Outao]

It is because you are using FastScan.

For example:

1. You are using Contribute mode:
   1. 1st sync is copying 5 files , snapshot1 is validated and is the reference
   2. 2nd sync , you are deleting 1 file from the source, FastScan is doing the diff and snapshot2 is validated as reference .
      It is knowing only 4 files but nothing is deleted at destination because you are in contribute mode.
   3. 3rd sync you are deleting 1 more file from the source, FastScan is doing the diff and snapshot3 is validated as reference and is knowing only 3 files but nothing is deleted at destination because you are in contribute mode.
2. You decide to change to Echo mode:
   1. 4th sync you delete 1 more file  from the source so you will have only 2 files on the source, FastScan is doing the diff  based on the snapshot3 which is knowing 3 files, but in the fastscanlist it will tag only one file deleted.
      So, on the destination we will delete only 1 file instead of 3 because FastScan generated a fastscanlist based on the last snapshot which is the reference.

That’s why, if you want to delete files at destination, you must delete the reference snapshot in Miria/DataFlow and run the task again.

That way, the synchronization task will run with a fresh snapshot and will use a standard scan that will let us know what is really on the source file system, then deleted files at the source will be deleted also from the destination.

[Author]

Posts