SNIA Summer Symposium Update


Published on

SNIA-DMF Storage Industry Networking Association - Data Management Forum project. Sustainable Long-term data preservation storage and business architecture.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • SNIA Summer Symposium Update

    1. 1. [LTACSI] Long-Term Storage Reference Guide Committee Webcast-Summer Symposium &quot;Decomposition of Archival System” 2008 <ul><li>Long-Term Storage “Reference Guide Committee” </li></ul><ul><ul><li>Chair Peter Mojica, AXS-One Inc. </li></ul></ul>
    2. 2. Background <ul><li>Long-Term Storage “Reference Guide Committee” </li></ul><ul><ul><li>Chair Peter Mojica, AXS-One Inc. </li></ul></ul><ul><ul><li>LT-SRG Committee Charter Statement </li></ul></ul><ul><ul><li>The LT-SRG charter is to address the more practical implementation and design challenges for long-term archival utilizing both a current state and future state framework. </li></ul></ul><ul><ul><ul><li>What’s here, what’s coming and how to best use it and what to be aware of… </li></ul></ul></ul>
    3. 3. The Case for Decomposing an Archive <ul><li>How do we deliver better and more durable systems and processes (capabilities) for long term archives compliant storage systems? </li></ul><ul><li>#1 Solve big problems </li></ul><ul><ul><li>Industry standards: </li></ul></ul><ul><ul><ul><li>SIRF Storage Information Retention Format (formerly known as SD-SCDF) </li></ul></ul></ul><ul><li>#2 …… </li></ul>
    4. 4. The Case for Decomposing an Archive <ul><li>#2 Education </li></ul><ul><ul><li>100 Year Archive Requirements Survey </li></ul></ul><ul><ul><li>Provided comprehensive data points on long term archival requirements. </li></ul></ul><ul><ul><li>Developed greater awareness and understanding of problem domain. </li></ul></ul>
    5. 5. The Case for Decomposing an Archive <ul><li>Education is the general business case for Case for Decomposition of an Archive </li></ul><ul><li>However, the primary driver is “change” </li></ul><ul><li>“ Change” is inevitable </li></ul><ul><ul><li>LTACSI – Reference Guide Committee work-product provides a method for “continual education” and process improvement across the archival value chain – targeted at all members of the eco-system! </li></ul></ul>
    6. 6. What do we mean, change? <ul><li>How things change quickly, overtime and have significant consequence on design and build considerations for archiving architectures. </li></ul><ul><ul><li>Email archival industry example: </li></ul></ul><ul><li>Day 1 – Archival needed due to 16GB limit on Standard MS Exchange license. Answer upgrade to Enterprise edition or archive. So email archival industry appears. Vendors build software to move bits and insert pointers into mailboxes, tier2 is supported – however no comprehensive search, retrieve, disposition management, etc. </li></ul><ul><li>Day 2 – An industry regulatory requirement “change” </li></ul><ul><ul><li>The specifics: Rule 3010(d)(3) would require each member firm to retain correspondence in accordance with Rule 3110. NASDR proposes amending Rule 3110 to specify that members make and preserve records in the manner prescribed by Rule 17a-3 under the Securities and Exchange Act of 1934 (the &quot;Exchange Act&quot;), and that the format, medium and retention period for such records comply with Rule 17a-4. </li></ul></ul><ul><ul><li>Industry scrambles to consolidate so storage and software vendors can adapt content supervision. </li></ul></ul><ul><li>Day 3 – Legal Discovery is the word of the day, Amended Federal Rules of Civil Procedure make electronic record retention for legal discovery even more pertinent. </li></ul><ul><ul><li>More consolidation </li></ul></ul>
    7. 7. The Case for Decomposing an Archive <ul><li>“ Change” </li></ul><ul><ul><li>Storage Driven </li></ul></ul><ul><ul><li>Compliance Driven </li></ul></ul><ul><ul><li>Legal Driven </li></ul></ul><ul><ul><li>What’s next? </li></ul></ul><ul><li>Each “change” has a significant effect on the technological requirements needed to fulfill the business requirements, what’s important is not knowing that “compliance is a driver” but how compliance requirement maps into privacy and how that effects object level security, single instance storage and search. </li></ul><ul><li>All of this knowledge is distributed and self-contained. </li></ul><ul><li>This is the best practice information that can be extracted from the decomposed view of the archive. </li></ul>
    8. 8. Question? <ul><li>Will the industry benefit from a comprehensive and continual updating of archive component, interdependency and best practice information, for both business and technical, as it pertains to the many moving and evolving components of an archive system? </li></ul><ul><li>Can specific technologies (i.e. de-duplication sector) benefit from a better understanding of all of the interconnected components of an archive architecture? </li></ul><ul><ul><li>Will it lead the technology vendors to build better archival systems that take more into account upfront vs. after-the-fact? </li></ul></ul>What’s on the other side?
    9. 14. Basic Content <ul><li>Every node on the map providing two levels of information </li></ul>Description: Concerns: Interdependencies:
    10. 15. Detailed Content <ul><li>Second level of information provides more detailed data + best practice recommendations </li></ul><ul><ul><li>1) Identification </li></ul></ul><ul><ul><li>2) Description of current and future state </li></ul></ul><ul><ul><li>3) Business Requirement </li></ul></ul><ul><ul><li>4) Conflicting Requirement Identification </li></ul></ul><ul><ul><li>5) Industry Best practice </li></ul></ul><ul><ul><li>6) SNIA Recommendation. </li></ul></ul>
    11. 16. Questions? <ul><li>We are continuing to expand the map into greater detail </li></ul><ul><li>Two levels of review and agreement are needed </li></ul><ul><ul><li>Content </li></ul></ul><ul><ul><ul><li>Best practice recommendations </li></ul></ul></ul><ul><ul><li>Node representations </li></ul></ul><ul><ul><ul><li>Hierarchal structures </li></ul></ul></ul><ul><ul><li>Node owners </li></ul></ul><ul><ul><ul><li>Content contributors </li></ul></ul></ul><ul><li>What is the best venue for the final work-product? </li></ul><ul><ul><li>Paid Subscriber content? </li></ul></ul><ul><ul><li>SNIA </li></ul></ul><ul><ul><li>Wikipedia </li></ul></ul><ul><li>All of the above? </li></ul>
    12. 17. The Tool <ul><li>FreeMind mapping software </li></ul><ul><li>Opensource </li></ul><ul><li>Can be downloaded at </li></ul>
    13. 18. As always we need your help! <ul><li>Long Term Reference Guide, contact us to join. </li></ul><ul><ul><li>LT-SRG Committee Chair </li></ul></ul><ul><ul><li>Peter Mojica </li></ul></ul><ul><ul><li>AXS-One Inc. </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>Chair, SNIA-DMF LTACSI </li></ul></ul><ul><ul><li>Gary Zasman </li></ul></ul><ul><ul><li>NetApps </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>Michael Peterson Chief Strategy Advocate, SNIA Data Management Forum [email_address] </li></ul></ul>