On Thu, Nov 1, 2018 at 5:15 PM David Gasaway <[email protected]> wrote:
> > On Thu, Nov 1, 2018 at 4:03 AM Peter Schüller <[email protected]> > wrote: > >> Hello, >> >> I am not sure I am getting the "SSH Backend" Tips&Tricks here: >> http://www.rath.org/s3ql-docs/tips.html >> >> Currently I am doing the following: >> * mount a S3 storage on a server to /mnt/s3ql >> * use sshfs on several workstations to bind that server's /mnt/s3ql into >> the local filesystem >> * happily use the storage in the cloud (in S3) from multiple workstations >> >> The Tips&Tricks shows what I do somehow in the reverse order (first mount >> sshfs and then mount s3ql on the client (it seems): >> >> > mount.s3ql local:///mnt/sshfs/myfsdata /mnt/s3ql >> >> Why should I care about the local:/// backend? >> >> Is this for cases where I do not care about the S3 storage backend at >> all, but where I care about data de-duplication and other s3ql features and >> the storage is in some (unspecified) file system? >> > > The tip is for cases where the repository is on a server accessible > through SSH (not S3). S3QL is speaking "local", which an sshfs > intermediate translates to SSH to store the data on a remote system. > Nothing uses S3 protocol. The tip doesn't have much to do with S3QL, other > than to point out that other software that causes remote resources to > appear as local filesystems (such as sshfs) can be targeted by the local > backend. Although, I'm not certain if others actually work well with > S3QL. > > Completely difference scenario than yours, where S3QL and the server are > speaking directly over the S3 protocol, then SSH is layered on top to give > additional clients access to the S3QL mount. I can't comment on potential > pitfalls to your setup. > > Thank you very much! Peter -- Dr Peter SCHÜLLER Postdoctoral Researcher at TU Wien http://www.peterschueller.com/ -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
