Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (9)
Similar to Network Attached Storage Initiative
Similar to Network Attached Storage Initiative (20)
More from Gary Wilhelm
More from Gary Wilhelm (8)
Recently uploaded
Recently uploaded (20)
Network Attached Storage Initiative
- 1. Network Attached Storage Brent Caison Charles Hammitt Sean Semone Lewis Binkowski Casey Emerson Georgia Allen David Pcolar Rob Noel James Fox Michael Barker Objective: to provide a cost-effective consolidation point for network attached storage that allows campus units to choose not to duplicate similar or identical solutions locally Team members:
- 2. Solutions: UNC Home space • Personal storage space located on a network accessible resource • Complementary space to AFS • Centrally allocated- opt in service using a web submit, similar to AFS • Initial offering: – 10 GB per user, with no expansion at start – CIFs based – Authentication based on ad.unc.edu – User Managed, supported through ITS Help
- 3. Solutions: UNC Shared Space Shared enterprise level network attached storage space for departments, divisions, and Schools. • Central provisioning and backup paired with distributed localized management • Base allocation established by headcount, and provided at no cost • Additional allocation available at cost, billed annually • Base allocation calculation: 10 GB per employee
- 4. Solutions: UNC Shared Space Initial offering: • CIFs based • Includes disaster recovery protection (backup) • Authentication based on ad.unc.edu • Additional allocation: – $2.50 per GB – Billed yearly – Minimum incremental size of 100GB
- 5. Possible Future Additions Add "Dropbox" style connectivity to allow "cloud like" access. Add sFTP, FTPs and HTTPs (WebDAV) to allow more options in connectivity.
- 6. Currently out of scope • Specialty research storage • Higher level “Sensitive” or “Secure” data
- 7. Proposed Timeline Funding dependent • Phase roll out beginning in January 2011- Offer UNC Home space and UNC Shared Space to campus. • Late Spring 2011- Expand access options – Investigate “Dropbox” or “Cloud like” access to UNC Home – Expand options for UNC Group to include sFTP, FTPs • Fall 2012- Expand access options to include NFS4
- 8. Next Steps • Solution review by Security • Complete hardware evaluation • Operationalize service • Work with campus groups on “Secure” storage needs
- 9. Levels of “Secure” • IRB definitions from UNC VCRED • UNC Information Security Policies • Carnegie Mellon Security Policies • Trend is toward 3 levels of Secure: – Public – Private – Restricted
Editor's Notes
- Thanks to Lew Binkowski for authoring the slides and making the initial presentation to ITEC Overview of NAS committee charter Survey results provided a good starting point for development of services. Size and connectivity We decided to focus on the types of services that could be offered. Looking at hardware separately, since there are only a few vendors, needed to determine requirements for service? Focused on CIFs to start for costs Out of scope: Space for specialty research storage High speed drives
- UNC Home space Personal storage space located on a network accessible resource Complimentary space to AFS Centrally allocated- opt in service using a web submit, similar to AFS Initial offering: 10 GB per user, with no expansion at start CIFs based Authentication based on ad.unc.edu - ad/ONYEN User managed, supported through ITS help Backup and recovery service Guidelines for use: Subject to acceptable use policy Do not recommend storing .pst files since Microsoft does not support network drive access Would prefer that people did not use this for their entertainment collections
- UNC Shared Space Shared enterprise level network attached storage space for departments, divisions, and Schools. Central provisioning and backup paired with distributed localized management Base allocation established by headcount, and provided at no cost may include student employees – under discussion Additional allocation available at cost, billed annually Base allocation calculation: 10 GB per employee Initial offering: CIFs based Includes disaster recovery protection (backup) Authentication based on ad.unc.edu Additional allocation: $2.50 per GB Billed yearly Minimum incremental size of 100GB Potential future options/ Additions Add sFTP and FTPs Add "Dropbox" style connectivity to allow "cloud like" access. Https (Webdav) Guidelines for use: Do not recommend storing .pst files since Microsoft does not support network drive access Would prefer fewer larger expansions over several smaller expansions
- Base allocation calculation: 10 GB per employee Initial offering: CIFs based Includes disaster recovery protection (backup) Authentication based on ad.unc.edu Additional allocation: $2.50 per GB Billed yearly Minimum incremental size of 100GB
- Add sFTP and FTPs Add "Dropbox" style connectivity to allow "cloud like" access. Https (Webdav)
- Research data- Most research data sets require specific levels of security etc., HIPPA, Ferpa. Due to the uniqueness of each of these requirements, Many require “one off” solution. Can not offer a “General” service for these with out significant cost increase Research Computing offers service. Committee recommends creation of taskforce to look at expanding this service. Sensitive or secure? Both offerings are being designed to hit mid-level of security- (Level 2 from UNC IRB) Will be some data sets that should not be stored here. Meeting security requirements for Research data sets requires increased security regulations on both infrastructure and access that increase costs significantly. Not necessarily appropriate for lower levels of data High speed disk Different group addressing that issue Can’t put fast disk on slow network Research is built around placing fast disk next to fast systems
- Phased roll out beginning Estimated cost about- $1.1 million for year one, same for year 2 500 TB of data to start 7000 SPA, 7000 EPA 14K headcount
- Year 3 poses additional costs for replacement/expansion Segway for Stan to talk about storage
- Public – “Could be written on billboard” Private- Breach could cause university minor embarrassment or issue Restricted – Breach could cause university major embarrassment or issue