Last update: August 23, 2021
XSEDE offers storage to satisfy most users' practical needs. Several XSEDE service providers host storage platforms providing services such as data management, data collections hosting, and large-scale persistent storage. XSEDE provides storage allocations both in support of compute/visualization usage and storage independent of those compute/visualization allocations. Researchers may request data storage allocations for short- and long-term storage and for staging of data collections on disk.
You may request a storage allocation through the XSEDE Resource Allocation System (XRAS), the same service used to request XSEDE compute, visualization and storage resources.
XSEDE users have access to three types of storage.
Archival Storage: Archival storage on XSEDE systems is typically used for large-scale persistent storage requested in conjunction with compute and visualization resources. Archival storage is usually not backed up. Users will need to explicitly request these resources in their request as has been done for compute and visualization requests through XRAS.
Stand-alone Storage: Stand-alone storage allows storage allocations independent of a compute/visualization allocation. Data hosting and data preservation projects may have stand-alone storage needs. PIs may request stand-alone storage on any of the XSEDE storage systems detailed in Table 1 below.
Resource file system storage: All XSEDE compute/visualization allocations include access to limited disk and scratch space on the compute/visualization resource file systems to accomplish project goals.
The following table lists XSEDE allocatable archival and stand-alone storage systems available to XSEDE users. Storage on these systems must be requested along with compute and visualization requests through XRAS. Currently, the only stand-alone storage resource is the TACC Ranch storage resource.
As with compute and visualization allocations, storage allocation durations will be one year with the option to renew for subsequent one-year periods. Data will be preserved for at least one quarter beyond the expiration of the storage allocation end date.
Storage allocations will be provided on a per-project basis. PIs will manage their storage allocations via the XSEDE User Portal's account management feature. PIs will receive automatic notifications at pre-determined intervals as their storage usage approaches the awarded amount and as their allocation approaches its expiration date. PIs and users are responsible for correctly managing their storage allocations.
|System type||Medium-term disk storage||Persistent disk and tape hybrid storage||Long-term tape archival storage|
|Allows stand-alone storage?||no||no||yes|
|Companion HPC resource(s)||Expanse Storage||Bridges-2 Storage||Stampede2 Storage|
|File system type||Lustre||Lustre||Lustre|
|Default/Max storage space for XRAS request||500GB / 75TB||500 GB/None||none / 1PB|
|Data retention beyond allocation expiration||3 months||3 months||6 months|
Users should be aware that attempting to write to a file system while over their quota may cause jobs to fail. Please check your quotas before submitting a job to ensure that the data generated by the job will fit within the quota, or that all job output is written to a file system without quotas.
You may check your quota simply by issuing the eponymous command:
$HOME file systems on XSEDE resources are backed up on a regular schedule, varying from nightly to weekly. For specifics of backup and restore policies and procedures, please consult each resource's user guide for more information. Regardless of backup policies, users are strongly encouraged to create their own backups of all critical data on their own resources and/or on XSEDE Archive resources.
$SCRATCH and other large file systems on XSEDE resources are purged on a regular basis, meaning that older, unused data will be deleted. Most such file systems are not backed up. Please consult site- or system-specific documentation for details on these policies. Users should be aware that data stored on purged resources could be deleted, and should exercise care to ensure that important data is copied or moved to appropriate long-term storage resources promptly.