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

Question regarding transfer between Clouds / Sources: through local device or direct? #8239

Closed
cyberduck opened this issue Sep 27, 2014 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 27, 2014

9387989 created the issue

Hello:

Am trying to determine how data is handled between clouds & sources - I tried to find this info already, could not, so apologies if redundant. Q: is the data from one cloud or source moving DIRECTLY to the other location, or is it being handled through my own local device (internet connection)?

That is to say, for example: when I move content from my web host to Amazon to archive that content, is it going directly from point to point, or is it first being moved through Cyberduck pursuant to the limits of my bandwith and connection?

REASON I ask is because I am working for a while in a developing country with limited internet - yet I have big chunks of data already on my host that I would like to move and archive to S3.

If that data would be handled through my local device and connection, it would take forever and I couldn't do it. YET: if it goes directly from point to point, that would be preferable, and if this functionality depends on a certain setting (ie., go through my device or go from point to point directly) , please let me know what that setting is! (*because currently it appears to be slow...)

Thanks

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 30, 2014

@dkocher commented

Documentation forthcoming in Copy files and folders between servers.

@cyberduck cyberduck closed this Sep 30, 2014
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants