I have got the below known issue in the latest version from one of the links.
•Mirroring a file will fail on the first run if a folder with the same name already exists in the destination (even if the folder is configured to be deleted). This is because SyncBack creates and deletes folders after files have been copied and deleted. New folders are created as needed as files are copied. The folder will be deleted (after the copy has failed) so the second run of the profile will not have a problem (as the folder has already been deleted).
However i dint understand what is actually done.Does it mean that the files will be copied and then the folders of that file will be created? IN our case we are using Mirror profile to copy 1000 + files and folders from Source (which is a network location) to a Cloud base destination (Box).Can you please elaborate what will be the impact in our case of the above known issue.
•Mirroring a file will fail on the first run if a folder with the same name already exists in the destination (even if the folder is configured to be deleted). This is because SyncBack creates and deletes folders after files have been copied and deleted. New folders are created as needed as files are copied. The folder will be deleted (after the copy has failed) so the second run of the profile will not have a problem (as the folder has already been deleted).
However i dint understand what is actually done.Does it mean that the files will be copied and then the folders of that file will be created? IN our case we are using Mirror profile to copy 1000 + files and folders from Source (which is a network location) to a Cloud base destination (Box).Can you please elaborate what will be the impact in our case of the above known issue.
Statistics: Posted by AlpitaR — Wed Dec 27, 2017 5:18 pm