Re: [Duplicity-talk] HubiC Backend: Multi Threaded uploads

[Tiernan OToole]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Manual RSync might be the way to go... mind you, looking at the
script, i already have the --asynchronous-upload option turned on...
and it makes no difference... Will try the RSync option... Not sure if
Hubic supports RSync, but i do have a server in closer to HubiC that
has a faster connection... maybe uploading to there and from there to
HubiC...

- --Tiernan

On 28/07/2015 13:41, Kenneth Loafman wrote:
> Nice connection.
> 
> At this point duplicity does not have the capability to handle this
> kind of configuration.  You could handle it by backing up locally
> and doing the rsync manually (HubiC supports rsync?).  As a second
> option you could use --asynchronous-upload to get two connections
> going which should alternate between the two if load balanced.
> 
> ...Ken
> 
> 
> On Tue, Jul 28, 2015 at 5:29 AM, Tiernan OToole 
> <address@hidden <mailto:address@hidden>>
> wrote:
> 
> Morning all.
> 
> I am using Duplicity and HubiC to backup some machines and noticed 
> that when uploading, its only using 1 of my internet connections 
> (24mb/s up). I have 2 pipes at the same speed, and was wondering
> how (if possible) i can get Duplicity to upload multiple files to
> the HubiC backend at the same time?
> 
> The connection is load balanced and i ran some tests and can get a 
> full 48mb/s up if i use multiple rsync connections... (rsync with 
> parallel).
> 
> Any ideas?
> 
> Thanks.
> 
> --Tiernan
> 
> _______________________________________________ Duplicity-talk
> mailing list address@hidden
> <mailto:address@hidden> 
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> 
> _______________________________________________ Duplicity-talk
> mailing list address@hidden 
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVt3usAAoJECWDUKjOk5r1MEkQAKm79Qa/u5wAuKi+pkzw18Nd
qaqTwPm6sjVlvrAF/1jhJaTr47PGEZ4FnVLV1G5IudD08QAZ1PV7Gu9Mu9mdjiEa
UcyuSFvaB0Jx9bXBuIA6qIasvYZ5K5fuSCHvj1yT2T0A21TV+fNYMX3mlhNKVQcO
HN1GsiuFVgBGtiqxWf9WnjpBgT70dqEwi63uVtxEz6DL+1QFycBjz7jFbEZCvP+U
ZgrnLvD3ackdEhFKrXUG+aTa5Bj1KkS83s11KyCKP5w9uz0gtLQgBa3VBE24hUdf
CLRzahctUFgPaxRczxIsGSlPO1dyaZJCxQdo2c4P5VEShUZOAv5SyJZ0lizK4Keu
yoyXq/VdpaT7a8dLFYlpRqIY1uJzd6IQ6VFIHaEt2hN0aOSd5GB1eXcA4L4RjqEj
UKYDapHZ12SSwgTWQsQPPCbjmCwhGNxgvoCoW1K7+cPrOvXWg6+Ac+t3Lw2xwG00
W2NkaqXYU92oNVTS7V/R6pUUz7N160RqN1m+wGOnby0Wq290BHNploMekxV3f0Tm
U8frTjLIT6Pys9Fqnags5+qN3H9wQsmo/AbRPMDp4EVVenA+v82CqmJW0iXmE8P/
I1K7V5kd0Y3oVRWIlAa8ssaOXqsd3mQjPAndbFDnDebnjT0nfrWaMIuS7BoU+6Nu
Ym/k41KytZbZdJ2bxFgk
=5tcp
-----END PGP SIGNATURE-----