On 23/12/15 19:12, Nikolaus Rath wrote:
And that's not surprising. If you want to store data in S3, you need to
use the S3 backend, not the local backend.
I made the foolish assumption that the stored data format would be the same.
(b) is there any way to recover from it?
Not sure what you mean. Did you delete the local copy? If so, you can
just download the data from S3 using whatever tool you used to upload it
and you should be able to mount it using the local backend.
The source data is no longer accessible; it is on a hard disk in a
disconnected machine in Wales. I am in Spain. Downloading and
re-uploading is not a possibility; the data (5 Terabytes) was uploaded
by sending a USB disk to AWS in Ireland. They insist on wiping the
source disk so I can't even recover from that when it's returned.
If you want to "convert" a local S3QL file system to an S3 one, you can
use the contrib/clone_fs.py script from the S3QL tarball.
I don't suppose there's a way to convert the data in situ? Is it just
the metadata that is different or is it all data? Any suggestions?
Thanks
Cliff.
--
Cliff Stanford
Office: +44 20 0222 1666 UK Mobile: +44 7973 616 666
Spain: +34 952 587 666
http://www.may.be/
--
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.
