I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)
on
Which general topic do you have
Hey all, one question regarding the new chunk upload that comes with Hub10: does this mean, NC can now sync deltas like Seafile is able? For example that when only a few Bytes differ in an edited 10GB Veracrypt container, not the whole 10GB goes over the wire but only the delta? Would (for me) be the greatest evolution Nextcloud would have made in years!
Thanks for clarification, I would go crazy, if this is the case!
and the chunked upload was already available in the desktop client before (without the delta sync)
Since it is an encrypted container, even a small change might change a lot of bytes here and there. It is not like a encrypted file system where encryption is done file-by-file. In a container, it should not be obvious what the exact content is.
Thanks for your answer. Then my thought that chunk could have meant delta sync was wrong.
Since the requests for delta sync are quite old, it seems a very long if not neverending journey.
It’s clear that after a change of let’s say 1 Byte there will be some more Bytes to sync but Seafile does this (and it works very well). But the Seafile sync algorithm is very different from Nextcloud’s and I assume, Nextloud won’t change it’s algorithm completely.
For other reasons we’re not able to switch to Seafile.
So that’s a pitty…
But thank you for clarification!
I think delta-sync would be a game changer for Nextcloud. Seafile uses a completely different approach to synchronise files. But it is probably also due to the fact that Seafile uses e.g. compiled C code and not PHP. This will probably not change in Nextcloud in the next few years. However, PHP also has many advantages, but unfortunately also a few disadvantages.
What you describe as an advantage of Seafile can also be seen as a disadvantage…
Because in order to achieve delta sync and deduplication, Seafile splits the files into hashed chunks when saving them to disk, and the original file structure, filenames and metadata are stored in the database, so if the database is lost or corrupted for any reason, it will be complicated to recover your files.
Nextcloud, on the other hand, stores the file and folder structure on disk as is. This means that even if Nextcloud and/or the database are completely screwed up, you can still easily access and recover your files.
I agree. There’s pros and cons in everything.
As a workaround one could use fuse (FUSE extension - Seafile Admin Manual) in order to get access to the whole files (but I don’t want to promote seafile here!).
Would just be great to have both…
You can access e.g. /path/to/nextcloud/data/username/files e.g. with rsync and ssh. I think read is no problem. On write you must use sudo -u www-data php /pat/to/nextcloud/occ files:scan --all after write.
With a Nextcloud Backup, you also use procedures such as rsync and ssh for the backup and not the less reliable Nextcloud sync.
Also you can use all kinds of WebDAV. There you don’t have to execute the occ command mentioned above either for write access.