"'Shannon Dealy' via s3ql" <[email protected]> writes: > I have been using S3QL 3.7.3 (and earlier versions) with Amazon S3 for many > years. Due to a variety of circumstances I have just setup version 5.2.0 using > the s3c4 backend with Backblaze. Part of my standard incremental backup script > is to use s3qlcp to make a copy of the latest backup into a timestamped > directory. The s3qlcp command has been running for around 2 hours now with a > subset of the same data set in my old backups and it previously never took > even > a quarter of this time to do the copy. > > Is anyone aware of problems like this?
This is the first report that I've seen. > As I understand it, the s3qlcp copy is > strictly a database operation so the backend shouldn't even be relevant to > performance of this command other than the database upload after the copy is > complete. That's right. Best, -Nikolaus -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/878r0b5yt0.fsf%40vostro.rath.org.
