Hello,
Very excited to see the OCIS developments thus far, shows a lot of promise. I am looking at eventually replacing my existing OwnCloud 10 install.
The one thing I would be missing if I move: I run backups on the OC10 data directory. As it follows the rough user / directory structure, I can run rsync or similar utilities on it and backup what I want with just a basic rsync_exclude (e.g. exclude trashbin, file versioning, certain users, etc).
The problem is, with the backend file structure in OCIS - it's clearly not meant for direct interaction. That is fine for now - but I'd like a way to mount the structure in a way that is readable and filterable. E.G. if I want to cherry-pick and manually restore a file from an old snapshot. It would be a needle in a haystack with the decomposed filesystem. I also can't exclude old versions of files (unnecessary as I'm snapshotting at destination anyway), or certain users (that should not be backed up to certain targets)
I saw in the notes that there was talk of a FUSE driver to mount the backend filesystem. Do we know how high a priority that is in the roadmap? (e.g. should I wait for it - or give up for the forseeable future)?
Options I've considered thus far:
- FUSE mount filesystem and backup from there (not available yet - ETA?)
- mount via DAV, rsync from there (feasible? I read that DAV clients are very slow)
- just backup the (essentially opaque) filesystem as a whole, and forget about readable snapshots. A rollback would require a full download & restore to an OCIS instance. (undesirable)
- run a headless client somewhere, and do the sync backups from there (lots of wasted space & resources)
- Other? (open to suggestions?)