Consider improvements to the backup experience to support long filenames/directory names
-
@girish is there any progress here? Wanted to implement CR for a business client and ran into this problem.
Since the NextCloud Instance already has approx 1 TB and increasing, doing daily (request by client) tarball Backups to an offsite storage produces way too much traffic. rsync would be perfect and the Client already has MINIO services running but they encounter the already discussed key-length-error when syncing.
Any update here? Is there something on the roadmap to solve this?
-
@Jan-Macenka We can look into this for the next release but for the moment the best workaround is to rename the files. Alternately, don't use minio and instead use some sort of filesystem mount (nfs) setup.
-
@Jan-Macenka @Robin Would it be acceptable if filename encryption was optional? That would atleast make it slightly better.
-
@Jan-Macenka ok, that should be easy to do for next release. a checkbox that disables filename encryption.
-
I wonder if filenames/paths could be hashed into a database lookup table?
I've not looked in greater detail, but I suspect this how blockchain file storage systems like IFPS and Storj might handle such things.
-
@marcusquinn yes, that's the long term plan. The implementation is a bit involved though. This "database" has to be stored as a separate file/object on s3, downloaded and then we have to decrypt filenames. And viceversa for the backup process where we have to upload this database after all files are backed up.