https://wiki.diglib.org/index.php?action=history&feed=atom&title=NDSA%3ANYU_Response 2026-05-10T18:19:15Z Revision history for this page on the wiki MediaWiki 1.44.0 https://wiki.diglib.org/index.php?title=NDSA:NYU_Response&diff=2566&oldid=prev 2016-02-11T19:18:29Z

<p>1 revision imported: Migrate NDSA content from Library of Congress</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 15:18, 11 February 2016</td> </tr><tr><td colspan="4" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div> </td></tr> <!-- diff cache key wiki_production-dlfwiki_:diff:1.41:old-2565:rev-2566 --> </table>

Dlfadm https://wiki.diglib.org/index.php?title=NDSA:NYU_Response&diff=2565&oldid=prev 2011-05-17T15:54:30Z

<p>Created page with &#039;1. What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.) NYU Libraries proces…&#039;</p> <p><b>New page</b></p><div>1. What is the particular preservation goal or challenge you need to accomplish? <br /> (for example, re-use, public access, internal access, legal mandate, etc.)<br /> <br /> NYU Libraries processes, enables access to, and preserves digital materials<br /> that come from both the NYU community and from collaborating partner <br /> organizations. <br /> <br /> <br /> 2. What large scale storage or cloud technologies are you using to meet that <br /> challenge? Further, why did you choose these particular technologies?<br /> <br /> Our current repository asset store runs on SunFire X4500 and X4540 storage <br /> servers. The data servers are mirrored and backed up to tape. We are <br /> building a new repository system using Isilon storage arrays. The Isilon <br /> arrays are mirrored, geographically distributed, and backed up to tape. <br /> <br /> We are not pursuing cloud storage at this time. <br /> <br /> <br /> 3. Specifically, what kind of materials are you preserving (text, data sets, <br /> images, moving images, web pages, etc.)<br /> <br /> Our preservation repository contains:<br /> - texts <br /> - images<br /> - video<br /> - audio<br /> <br /> <br /> 4. How big is your collection? <br /> (In terms of number of objects and storage space required)<br /> <br /> Combined existing and new repository systems:<br /> 22,594 objects<br /> 81 TB (63 TB of video)<br /> <br /> <br /> 5. What are your performance requirements? Further, why are these your <br /> particular requirements?<br /> <br /> The storage solution must be fast enough to support ongoing fixity, <br /> ingest, and access operations.<br /> <br /> <br /> 6. What storage media have you elected to use? (Disk, Tape, etc) <br /> Further, why did you choose these particular media?<br /> <br /> We use both disk and tape (for backup).<br /> The first and second copies are stored on disk.<br /> The third copy is stored on tape.<br /> <br /> We need content on disk because we serve some content directly from<br /> repository storage. We also transcode to create access copies served<br /> through streaming media servers.<br /> <br /> <br /> 7. What do you think the key advantages of the system you use?<br /> <br /> The new system is under construction, but will be able to support various<br /> curation, publication, and preservation workflows. The underlying storage<br /> solution will allow us to easily add capacity to the system as needed.<br /> <br /> <br /> 8. What do you think are the key problems or disadvantages your system present?<br /> <br /> Ingest in our current system can be rather slow due to the ingest <br /> mechanisms in our application. <br /> <br /> <br /> 9. What important principles informed your decision about the particular <br /> tool or service you chose to use?<br /> <br /> We requested that the storage system be scalable, and ideally present a <br /> single filesystem to the applications using the storage. Our systems group<br /> then researched multiple storage solutions.<br /> <br /> <br /> 10. How frequently do you migrate from one system to another? <br /> Further, what is it that prompts you to make these migrations?<br /> <br /> We are coming up on our first major migration in approximately four years.<br /> In addition to content in our preservation repository, we have a legacy <br /> content that is stored across multiple systems. The new repository should<br /> allow us to aggregate and manage all of our content in a single system.<br /> <br /> <br /> 11. What characteristics of the storage system(s) you use do you feel are <br /> particularly well-suited to long-term digital preservation? (High levels <br /> of redundancy/resiliency, internal checksumming capabilities, automated <br /> tape refresh, etc)<br /> <br /> The Isilon storage system is designed to scale and includes configurable<br /> data integrity and data recovery features. <br /> <br /> <br /> 12. What functionality or processes have you developed to augment your storage <br /> systems in order to meet preservation goals? (Periodic checksum validation, <br /> limited human access or novel use of permissions schemes)<br /> <br /> Ongoing fixity checks and &quot;completeness&quot; checks.<br /> <br /> <br /> 13. Are there tough requirements for digital preservation, e.g. TRAC <br /> certification, that you wish were more readily handled by your storage <br /> system?<br /> <br /> Not at this time.</div>

Jgp