Re: [Duplicity-talk] Par2 not fixing | Hubic review?

[edgar . soldin]

On 13.01.2015 00:47, Duplicity Mailing List wrote:
> On 12/01/15 23:21, Duplicity Mailing List wrote:
>> This is a two part message.
>>
>> //FIRST PART//
>>
>> How do I get par2 to repair? Upon hitting a corrupted difftar file,
>> Duplicity throws:-
>>
>>> Backtrace of previous error: Traceback (innermost last):
>>>  File "/usr/local/lib/python2.7/dist-packages/duplicity/backend.py",
>>> line 361, in inner_retry
>>>    return fn(self, *args)
>>>  File "/usr/local/lib/python2.7/dist-packages/duplicity/backend.py",
>>> line 534, in get
>>>    self.backend._get(remote_filename, local_path)
>>>  File
>> "/usr/local/lib/python2.7/dist-packages/duplicity/backends/par2backend.py",
>> line 119, in get
>>>    par2volumes = filter(re.compile((r'%s\.vol[\d+]*\.par2' %
>>> remote_filename).match,
>>> AttributeError: 'str' object has no attribute 'match'
>>
>> This is version 0.7.1 of Duplicity, running on a Debian Wheezy install.
>>
>> //END OF FIRST PART//
>>
>>
>> //SECOND PART - Slightly off topic//
>>
>> Has anyone here used Hubic seriously? I recently gave it a try
>> considering they offer 25GB for free and Duplicity just got support for
>> it, I uploaded 5GB to their service then tried to restore it. Within the
>> hour my files were up on their service my files were already corrupted
>> (Granted, it was one of the last files (But not the very last file), at
>> ~4.9GB through my backup), this is less than impressive. After looking
>> through their forums it seems like they have lots of issues with very
>> few replies from administrators, and when there is a reply, it's nearly
>> always "PM us" with no public discussion. The combination of both the
>> failure to keep my files, even for one hour, secure and the terrible
>> support on their site pushes me away from their services, although, I am
>> interested in what Duplicity users think, being only €1/TB/month, I
>> might be worth going with them even if they do corrupt *some* data.
>>
>> //END OF SECOND PART//
> 
> I'd like to just add to this:-
> 
> 1. I just restored the entire file down from Hubic again, apparently
> this time it worked. Not sure if it was an issue at my end
> (DigitalOcean's hardware, not sure what sort of ECC they're running) or
> Hubic's, I believe OpenStack's Swift goes over TCP[0] so it probably
> wasn't an error in transport.
> 2. If anyone has any personal reviews for OneDrive either (considering
> they're going quote-on-quote 'unlimited' soon), I'd love to hear them.
> 
> [0]https://ask.openstack.org/en/question/6433/openstack-services-and-port/
> - swift TCP port 6000,6001,60002,873.
> 

please keep an eye on this. the par2 backend may have quirks and the "//FIRST 
PART//" may be an actual bug. if it reoccurs please add it to the duplicity bug 
tracker
 https://bugs.launchpad.net/duplicity
or even better try to fix it and contribute a patch, if possible.

thx.. ede/duply.net