Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are there any options for the "Compare" behavior when upload / download / mirror? #10974

Closed
cyberduck opened this issue Feb 20, 2020 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 20, 2020

4d4477b created the issue

Hi,\
\
Currently using Cyberduck to sync my folders (>100GB) with google drive (in encrypted vaults).\
Everytime just a few files in the local folders are modified, but Cyberduck will takes so long to compute the MD5 hash of all contents of in the folders.\
in\
(https://trac.cyberduck.io/wiki/help/en/howto/transfer#Compare)
\says the "Compare" function will compare the checksum if available, then the modification date.\
Are there any possibilities of customizing the options of "Compare" behavior (e.g. filesize or checksum, then the modification date, newer or older)? Or any simple way to update the copy in the cloud without hashing every bytes in the whole folders?\
\
Besides, a bit confused about the "Mirror / Upload / Download" behavior.\
(https://trac.cyberduck.io/wiki/help/en/howto/sync#MirrorFiles)\\
The description says these operations will either create or replace the files. What happens if I rename, move, or delete the files?
Are there any ways that automatically identify the deleted files and remove them in the other copy accordingly? (similar to FreeFileSync).\
\
Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 22, 2020

adc75a0 commented

Hi,

Unfortunately, it isn't possible to customize the "Compare" behavior.

Regarding the "Mirror/Upload/Download" behavior in general:
Cyberduck doesn't have the possibility to perform automated destructive processes which is why the description within the documentation says that these operations will either create or replace the files. If you rename, move or delete a file the old file will remain as before on the server, and in case of a file rename or move, Cyberduck will create a new file within the corresponding location.

– Laura

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant