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 requests could cut into that.
The Glacier location is in the format /<Account ID>/vaults/<Vault Name>/archives/<Archive ID>, so you might want to consider using the whole string. Thanks, Cary > On Apr 8, 2015, at 3:32 PM, Sara Amato <[email protected]> wrote: > > 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 to > deposits, as it looks like that is the only way to retrieve information if > needed (though you can attach a brief description also that appears on the > inventory along with the id.) We’re considering putting the ID in Archivist > Toolkit, where the location of the dissemination copies is noted, but am > wondering if there are other tools out there specific for this scenario that > people are using.
