You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this great tool! It's really easy and good to use.
My aim is to backup my music, video and photo folders to a webserver and I chose Cyberduck because of it's synchronisation feature.
It would be great though if there is a function that Cyberduck doesn't check all files on the webserver everytime before it starts to do the upload (because this takes a very long time if you uploaded already thousands of files).
Instead if cyberduck would create a simple database file where it saves the information about what it has already uploaded to the server (including the date information of the files). Given that the webserver is used for backups only, no files on the server will ever be altered. Thus cyberduck only has to compare the local harddisk to the database file to determine what has changed and then only upload these files.
By keeping a local database file that reflects the file names (and dates) on the server), the backup would be much much faster as cyberduck doesnt has to browse through the whole server to see what has changed.
Would be great if this could be considered as a 'Backup mode'.
The text was updated successfully, but these errors were encountered:
G'day,
First of all, thanks for this great tool! It's really easy and good to use.
My aim is to backup my music, video and photo folders to a webserver and I chose Cyberduck because of it's synchronisation feature.
It would be great though if there is a function that Cyberduck doesn't check all files on the webserver everytime before it starts to do the upload (because this takes a very long time if you uploaded already thousands of files).
Instead if cyberduck would create a simple database file where it saves the information about what it has already uploaded to the server (including the date information of the files). Given that the webserver is used for backups only, no files on the server will ever be altered. Thus cyberduck only has to compare the local harddisk to the database file to determine what has changed and then only upload these files.
By keeping a local database file that reflects the file names (and dates) on the server), the backup would be much much faster as cyberduck doesnt has to browse through the whole server to see what has changed.
Would be great if this could be considered as a 'Backup mode'.
The text was updated successfully, but these errors were encountered: