Preventing Data Loss

100 views
Skip to first unread message

Alok Parlikar

unread,
May 29, 2016, 9:57:48 AM5/29/16
to Camlistore
I'm now ingesting all my terabytes into camlistore. While that is running, I'm thinking -- to be certain I don't lose data, is it sufficient to back up blobs and the gpg keyring, (S3 and/or locally)?

Any tips on what I could do from the get go to simplify exporting data later?

Alok


Mathieu Lonjaret

unread,
May 30, 2016, 10:04:22 AM5/30/16
to camli...@googlegroups.com
On 29 May 2016 at 15:57, Alok Parlikar <happ...@gmail.com> wrote:
> I'm now ingesting all my terabytes into camlistore. While that is running, I'm thinking -- to be certain I don't lose data, is it sufficient to back up blobs and the gpg keyring, (S3 and/or locally)?

Yes. Everything is blobs, so you just need to backup wherever you
store your blobs (the blobPath directory if on disk, or the relevant
bucket if on the cloud). And yes, your GPG keys (keep them secure
too).
The various indexes and caches can be reconstructed later from the blobs.
You can use standard tools (rsync, scp...), or camtool sync.

> Any tips on what I could do from the get go to simplify exporting data later?

What do you mean by exporting?

> You received this message because you are subscribed to the Google Groups "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to camlistore+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Alok Parlikar

unread,
May 30, 2016, 11:03:23 AM5/30/16
to camli...@googlegroups.com

On Mon, May 30, 2016 at 7:34 PM, Mathieu Lonjaret <mathieu....@gmail.com> wrote:
On 29 May 2016 at 15:57, Alok Parlikar <happ...@gmail.com> wrote:
> I'm now ingesting all my terabytes into camlistore. While that is running, I'm thinking -- to be certain I don't lose data, is it sufficient to back up blobs and the gpg keyring, (S3 and/or locally)?

Yes. Everything is blobs, so you just need to backup wherever you
store your blobs (the blobPath directory if on disk, or the relevant
bucket if on the cloud). And yes, your GPG keys (keep them secure
too).
The various indexes and caches can be reconstructed later from the blobs.
You can use standard tools (rsync, scp...), or camtool sync.

> Any tips on what I could do from the get go to simplify exporting data later?

What do you mean by exporting?

Blobs --> local files.
I guess mount + cp is the way out; but once everything becomes sha1 numbers, I haven't yet understood how I can do the equivalent of "locate -i fname". I guess the more I use this, the more I'll understand.

Somehow I'm finding it hard to think outside of the posix-y tree view on my data :-).
 

> You received this message because you are subscribed to the Google Groups "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to camlistore+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "Camlistore" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/camlistore/Xqo5tb1Bq9A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to camlistore+...@googlegroups.com.

Simon B.

unread,
Jun 1, 2016, 8:31:17 AM6/1/16
to Camlistore
And I think "exporting" may be read with a *wink* after. If camlistore works properly, then you'll ingest data into it, and read stuff out as needed, but never really need to export. Also, a hash-based file storage is less limited than a tree file system, even with links (hard/soft) and macintosh extended attributes.
camlistore has a wider range of use cases. Newbie-friendlyness is an upcoming feature :)
Reply all
Reply to author
Forward
0 new messages