Re: [CODE4LIB] Amazon Glacier - tracking deposits

2015-04-09 Thread Jason Sherman
Hi Sara, At OU Libraries, we've just started using Glacier in earnest. We're tracking our glacier archives in DynamoDB tables. I've whipped up a little python script to stick LC bags into glacier and make them easier for us to keep track of and retrieve.

Re: [CODE4LIB] Amazon Glacier - tracking deposits

2015-04-09 Thread Scancella, John
for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Cary Gordon Sent: Wednesday, April 08, 2015 7:49 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Amazon Glacier - tracking deposits We have been playing with Glacier, but so far neither us nor our clients have been convinced

Re: [CODE4LIB] Amazon Glacier - tracking deposits

2015-04-09 Thread Kyle Banerjee
Howdy Sara, I've played around a bit with Glacier. It's a bit weird to work with, but tools keep on improving. The real question is what you hope to accomplish with it. As its name implies, it's designed for stuff that is basically frozen. When you take things out, you need to do so very slowly.

Re: [CODE4LIB] Amazon Glacier - tracking deposits

2015-04-09 Thread Han, Yan - (yhan)
@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Amazon Glacier - tracking deposits We have been playing with Glacier, but so far neither us nor our clients have been convinced of its cost-effectiveness. A while back, we were discussing a project with 15 PB of archival assets, and that would certainly have

[CODE4LIB] Amazon Glacier - tracking deposits

2015-04-08 Thread Sara Amato
Has anyone leapt on board with Glacier? We are considering using it for long term storage of high res archival scans. We have derivative copies for dissemination, so don’t intend touching these often, if ever. The question I have is how to best track the Archive ID that glacier attaches

Re: [CODE4LIB] Amazon Glacier - tracking deposits

2015-04-08 Thread Cary Gordon
We have been playing with Glacier, but so far neither us nor our clients have been convinced of its cost-effectiveness. A while back, we were discussing a project with 15 PB of archival assets, and that would certainly have made Glacier cost-effective, saving about $30k/mo. over S3, although