Re: [Duplicity-talk] Restoring from Glacier to S3

[Benjamin Henrion]

On Wed, Jul 29, 2015 at 12:39 PM, Benjamin Henrion <address@hidden> wrote:
> On Wed, Jul 29, 2015 at 11:01 AM, Andrew Langhorn
> <address@hidden> wrote:
>> Compared to S3, Glacier will take a lot longer to restore. It's primary
>> purpose is archiving whereas S3 is an object store. The trade-off is speed
>> vs price, since you should rarely need to restore from a Glacier vault.
>>
>> Do you have auto-archiving set on your S3 bucket? You can check in the
>> console. If so, turn that off, and your files should then stay in the S3
>
> Yes, to 30 days, and the signature file I mentioned earlier is trapped
> in glacier mode.
>
> I will disable manually the S3 policy of 30 days and use the purge
> --force command to 30 days instead.
>
> It would be nice if both could be in sync because that would make a
> restore quasi impossible, as the restore from Glacier is not that fast
> and the process will timeout at some point.

So other problem: some duplicity files are in glacier, some others are
in standard.

When I try to do a recursive restore with s3cmd:

s3cmd restore --recursive s3://mydatastore/mymachine/

It fails on standard files which of course are not in glacier:

ERROR: S3 error: Restore is not allowed, as object's storage class is
not GLACIER

Any idea how to solve that?

--
Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."