Great, thank you for your answers! Am Sonntag, 1. Februar 2015 05:52:30 UTC+1 schrieb Nikolaus Rath: > > "J. E." <[email protected] <javascript:>> writes: > > 1) I read that I should't use s3ql more than once at a time. Does this > > only apply when using the same storage url? > > Yes. > > > May I use it twice on the > > same computer with e.g. to different S3 target buckets? > > Absolutely. > > > Is there any advantage (in speed or size) of using several smaller > > s3ql filesystems than a large one? > > Theoretically yes. Practically probably not. > > > 2) May (should) I directly use an s3ql mount point as data directory > > for my Seafile storage server and git storage, or should I prefer e.g. > > rsync-ing the content into s3ql using a cronjob? > > If you use the mount point directly as a data directory, Seafile and git > will probably become a lot slower. Try it and decide if it's still fast > enough for your purposes :-). > > > 3) What happens with an s3ql filesystem if either the network > > connection or the backend service (s3) is not available? > > You can still access files that happen to be cached locally at the > time, and create new files until the cache is full. Any other request > blocks until the network is up again. If connectivity isn't restored > within a day, S3QL bails out and terminates. > > > Is there a > > full, offline-available copy of the data? > > No. > > > 4) How can I realize an additional backup of (the current state of) an > > s3ql file system e.g. to an external drive? > > Not easily. Instead I'd suggest to run an rsync job from your data > directory to an S3QL mount point, and to your external drive. > > > Is there local (cached) > > content discarded when it gets uploaded, > > No. But there is a limit on the cache size, and you don't have direct > control over what gets evicted if the cache is full. > > > 5) Will interrupted uploads (e.g. network outage or local system > > crash) be automatically resumed after the next mounting? > > If there's a network outage, you should not even need to unmount. > > If the system crashes, you need to run fsck.s3ql and it will upload > everything that is cached but not yet uploaded. > > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« >
-- 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.
