...
...
Overview
Code-named Beartooth, the ARCC provides several types of storage for researchers. Each is detailed below.
Research Data Storage
ARCC provides two options for research data storage. Alcova, and Pathfinder.
Research Data Storage on Alcova is subject to default quotas as listed on our Pricing Sheet.
Data on HPC
ARCC high-performance storage system (HPS) for Beartooth is a high speed, tiered storage system designed to maximize performance while minimizing cost. Beartooth is intended to be used for storing data that is actively being used.
The following policies discuss the use of this space. In general, the disk space is intended for support of research using the cluster, and as a courtesy to other users of the cluster, you should try to delete any files that are no longer needed or being used. All data on the HPS, are considered to be related to your research and not to be of a personal nature. As such, all data is considered to be owned by the principal investigator for the allocation through which you have access to the cluster.
...
| Note |
|---|
Note: None of the Beartooth file systems are backed up. We do data replication within the file system in order to minimize the loss of data in case of a system fault or failure. |
Storage Allocations on HPC
Each individual researcher is assigned a standard storage allocation or quota on /home, /project, and /gscratch. Researchers who use more than their allocated space will be blocked from creating new files until they reduce their use, or in the case of /project and /gscratch, request a one-time expansion or purchase additional storage. The chart below shows the storage allocations for individual accounts and the cost of additional space.
Directory Descriptions
/home
Private user space for storing small, long term files such as environment settings, scripts, and source code.
...
Node specific space for storing short-term computational data relevant to jobs running on that node. Files are deleted nightly.
HPC Directory Summary Table
Directory | Backed Up? | Default Allocation Storage Quota | Total Size | Media Type | Additional Storage Cost | Supported Protocols |
|---|---|---|---|---|---|---|
/home | No25 GB | 1.2PB | Tier 1 | Please see Cost of Resources | NFS, CIFS, GPFS | |
/project | No | 1 TB1.2PB | Tier 1 & 2 | Please see Cost of Resources | NFS, CIFS, GPFS | |
/gscratch | No5 TB | 1.2PB | Tier 1 & 2 | Please see Cost of Resources | NFS, CIFS, GPFS | |
/lscratch | No | N/A | 200GB or 1TB | N/A | N/A | N/A |
Augmenting Capacity of Disk Allocation
Researchers working with or generating massive data sets that exceed the default 5 TB allocation, or having significant I/O needs should consider the following options:
...
/home: Home directories will only be deleted after the owner has been removed from the university system./project: Project directories will be preserved for up to 6 months after project termination./gscratch: Files may be deleted as needed without warning if required for system productivity./lscratch: Files will be removed after thirty (30) days of not being used or accessed.
Costs Associated with
...
HPC Storage
If users require quota increases on Beartooth file storage, they may apply for a one-time, no-cost capacity increase by providing written justification for the amount of extra storage and it’s benefit to the UW mission of research, education and economic development.
This capacity increase lasts for the life of the storage system (typically 3 years), the increase must be approved by ARCC Leadership, and is subject to a 10TB max limit.
In all other cases, the user will be charged per Cost of Resources as listed here.
Users may request capacity increases on the ARCC Service Portal.
...