Is it right for you?
A good fit
- Raw data and project snapshots kept for funder or university retention rules
- Data you rarely read but cannot lose
- A second copy of data held elsewhere
Not a fit
- Data you read or change often (retrieval from archive classes is slower and can carry charges)
- Data rated P3 or P4 outside an approved environment
- The only plan for data with a retention requirement you have not checked
What it is
Labs with an Ursa Major project can keep long-term data in Google Cloud archive storage classes. These are designed for data you are required to keep but expect to read rarely, such as raw instrument data held to meet a funder's retention rules.
Costs and terms
Under the current Ursa Major terms, archive storage may be available without recharge to the lab, within limits and subject to eligibility. That coverage depends on continued campus funding. Research Computing makes no commitment about how long it will continue or at what scale. Retrieval, early deletion and other operations can carry charges. The Ursa Major guidelines describe the current terms.
Plan for the possibility that terms change during the life of your data. Keep a record of what you archived, where, and why.
How to use it
KB012: Using Ursa Major archive storage shows how to move data into archive classes. Before you start, check how long you are required to keep the data: see records retention.