REDDNET and digital preservation in the open cloud: Research at Texas Tech University libraries on long-term archival storage

James Brewer, Tracy Marie Popp, Joy Perrin

Research output: Contribution to journalArticle

Abstract

In the realm of digital data, vendor-supplied cloud systems will still leave the user with responsibility for curation of digital data. Some of the very tasks users thought they were delegating to the cloud vendor may be a requirement for users after all. For example, cloud vendors most often require that users maintain archival copies. Beyond the better known vendor cloud model, we examine curation in two other models: inhouse clouds, and what we call "open" clouds which are neither inhouse clouds nor vendor supported clouds. In open clouds, users come aboard as participants or partners for example, by being invited to participate in development or in hosting hardware. In open cloud systems users can develop their own software and data management, control access, and purchase their own hardware while running securely in the cloud environment. To do so will still require working within the rules of the cloud system, but in some open cloud systems those restrictions and limitations can be walked around easily with surprisingly little loss of freedom. It is in this context that REDDnet (Research and Education Data Depot network) is presented as the place where the Texas Tech University (TTU)) Libraries have been conducting research on long-term digital archival storage. The REDDnet network by year's end will be at 1.2 petabytes (PB) with an additional 1.4 PB for a related project (Compact Muon Soleniod Heavy Ion [CMS-HI]); additionally there are over 200 TB of tape storage. These numbers exclude any disk space which TTU will be purchasing during the year. National Science Foundation (NSF) funding covering REDDnet and CMS-HI was in excess of $850,000 with $850,000 earmarked toward REDDnet. In the terminology we used above, REDDnet is an open cloud system that invited TTU Libraries to participate. This means that we run software which fits the REDDnet structure. We are beginning the final design of our system, and moving into the first stages of construction. And we have made a decision to move forward to purchase one-half PB of disk storage in the initial phase. The concerns, deliberations and testing are presented here along with our initial approach.

Original languageEnglish (US)
JournalJournal of Digital Information
Volume13
Issue number1
StatePublished - Aug 13 2012
Externally publishedYes

Fingerprint

data network
Education
open system
education
Heavy ions
hardware
purchase
Hardware
Digital storage
Purchasing
Terminology
Access control
deliberation
Information management
technical language
funding
responsibility
Testing
science
management

ASJC Scopus subject areas

  • Information Systems
  • Computer Science Applications
  • Library and Information Sciences

Cite this

@article{e5663960bee04a2a9bd1f1e838717d7b,
title = "REDDNET and digital preservation in the open cloud: Research at Texas Tech University libraries on long-term archival storage",
abstract = "In the realm of digital data, vendor-supplied cloud systems will still leave the user with responsibility for curation of digital data. Some of the very tasks users thought they were delegating to the cloud vendor may be a requirement for users after all. For example, cloud vendors most often require that users maintain archival copies. Beyond the better known vendor cloud model, we examine curation in two other models: inhouse clouds, and what we call {"}open{"} clouds which are neither inhouse clouds nor vendor supported clouds. In open clouds, users come aboard as participants or partners for example, by being invited to participate in development or in hosting hardware. In open cloud systems users can develop their own software and data management, control access, and purchase their own hardware while running securely in the cloud environment. To do so will still require working within the rules of the cloud system, but in some open cloud systems those restrictions and limitations can be walked around easily with surprisingly little loss of freedom. It is in this context that REDDnet (Research and Education Data Depot network) is presented as the place where the Texas Tech University (TTU)) Libraries have been conducting research on long-term digital archival storage. The REDDnet network by year's end will be at 1.2 petabytes (PB) with an additional 1.4 PB for a related project (Compact Muon Soleniod Heavy Ion [CMS-HI]); additionally there are over 200 TB of tape storage. These numbers exclude any disk space which TTU will be purchasing during the year. National Science Foundation (NSF) funding covering REDDnet and CMS-HI was in excess of $850,000 with $850,000 earmarked toward REDDnet. In the terminology we used above, REDDnet is an open cloud system that invited TTU Libraries to participate. This means that we run software which fits the REDDnet structure. We are beginning the final design of our system, and moving into the first stages of construction. And we have made a decision to move forward to purchase one-half PB of disk storage in the initial phase. The concerns, deliberations and testing are presented here along with our initial approach.",
author = "James Brewer and Popp, {Tracy Marie} and Joy Perrin",
year = "2012",
month = "8",
day = "13",
language = "English (US)",
volume = "13",
journal = "Journal of Digital Information",
issn = "1368-7506",
publisher = "British Computer Society",
number = "1",

}

TY - JOUR

T1 - REDDNET and digital preservation in the open cloud

T2 - Research at Texas Tech University libraries on long-term archival storage

AU - Brewer, James

AU - Popp, Tracy Marie

AU - Perrin, Joy

PY - 2012/8/13

Y1 - 2012/8/13

N2 - In the realm of digital data, vendor-supplied cloud systems will still leave the user with responsibility for curation of digital data. Some of the very tasks users thought they were delegating to the cloud vendor may be a requirement for users after all. For example, cloud vendors most often require that users maintain archival copies. Beyond the better known vendor cloud model, we examine curation in two other models: inhouse clouds, and what we call "open" clouds which are neither inhouse clouds nor vendor supported clouds. In open clouds, users come aboard as participants or partners for example, by being invited to participate in development or in hosting hardware. In open cloud systems users can develop their own software and data management, control access, and purchase their own hardware while running securely in the cloud environment. To do so will still require working within the rules of the cloud system, but in some open cloud systems those restrictions and limitations can be walked around easily with surprisingly little loss of freedom. It is in this context that REDDnet (Research and Education Data Depot network) is presented as the place where the Texas Tech University (TTU)) Libraries have been conducting research on long-term digital archival storage. The REDDnet network by year's end will be at 1.2 petabytes (PB) with an additional 1.4 PB for a related project (Compact Muon Soleniod Heavy Ion [CMS-HI]); additionally there are over 200 TB of tape storage. These numbers exclude any disk space which TTU will be purchasing during the year. National Science Foundation (NSF) funding covering REDDnet and CMS-HI was in excess of $850,000 with $850,000 earmarked toward REDDnet. In the terminology we used above, REDDnet is an open cloud system that invited TTU Libraries to participate. This means that we run software which fits the REDDnet structure. We are beginning the final design of our system, and moving into the first stages of construction. And we have made a decision to move forward to purchase one-half PB of disk storage in the initial phase. The concerns, deliberations and testing are presented here along with our initial approach.

AB - In the realm of digital data, vendor-supplied cloud systems will still leave the user with responsibility for curation of digital data. Some of the very tasks users thought they were delegating to the cloud vendor may be a requirement for users after all. For example, cloud vendors most often require that users maintain archival copies. Beyond the better known vendor cloud model, we examine curation in two other models: inhouse clouds, and what we call "open" clouds which are neither inhouse clouds nor vendor supported clouds. In open clouds, users come aboard as participants or partners for example, by being invited to participate in development or in hosting hardware. In open cloud systems users can develop their own software and data management, control access, and purchase their own hardware while running securely in the cloud environment. To do so will still require working within the rules of the cloud system, but in some open cloud systems those restrictions and limitations can be walked around easily with surprisingly little loss of freedom. It is in this context that REDDnet (Research and Education Data Depot network) is presented as the place where the Texas Tech University (TTU)) Libraries have been conducting research on long-term digital archival storage. The REDDnet network by year's end will be at 1.2 petabytes (PB) with an additional 1.4 PB for a related project (Compact Muon Soleniod Heavy Ion [CMS-HI]); additionally there are over 200 TB of tape storage. These numbers exclude any disk space which TTU will be purchasing during the year. National Science Foundation (NSF) funding covering REDDnet and CMS-HI was in excess of $850,000 with $850,000 earmarked toward REDDnet. In the terminology we used above, REDDnet is an open cloud system that invited TTU Libraries to participate. This means that we run software which fits the REDDnet structure. We are beginning the final design of our system, and moving into the first stages of construction. And we have made a decision to move forward to purchase one-half PB of disk storage in the initial phase. The concerns, deliberations and testing are presented here along with our initial approach.

UR - http://www.scopus.com/inward/record.url?scp=84864686051&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84864686051&partnerID=8YFLogxK

M3 - Article

AN - SCOPUS:84864686051

VL - 13

JO - Journal of Digital Information

JF - Journal of Digital Information

SN - 1368-7506

IS - 1

ER -