LCC storage Quotas

This page describes storage locations and quota limits on the Lipscomb Compute Cluster (LCC).
It also explains data retention policies and recommended practices for managing storage usage.

1 Important Notice
2 Scratch Storage Retention Policy
3 Storage Locations and Quotas
4 Requesting Additional Storage
5 Large Data Transfers
6 Additional Resources

Important Notice

LCC systems are designed for high reliability. However, unexpected events such as hardware failures or outages may occur.

Data stored on cluster scratch storage is not backed up.
Users are responsible for maintaining copies of important data.

Scratch Storage Retention Policy

Files stored in scratch and group project scratch locations are subject to a 90-day file retention policy.

Files not accessed within 90 days may be automatically deleted.
Users should move important data to long-term storage before this period expires.

Storage Locations and Quotas

The table below summarizes available storage areas and their quota limits.

Storage Area	Location	Quota/Limit	90-day file deletion policy	Backed Up

Storage Area	Location	Quota/Limit	90-day file deletion policy	Backed Up
User scratch	$SCRATCH	25 TB (per user)	Yes	No
Group project scratch	$PSCRATCH/PI_linkblue_uksr	50 TB(shared among all members in a PI group)	Yes	No
User home	$HOME	10 GB(per user)	No	No
Group Project home	$PROJECT/PI_linkblue_uksr	1 TB(shared among all members in a PI group	No	No

Requesting Additional Storage

Additional storage may be available through Object Storage services.

Object storage is not mounted directly on compute nodes.
Requests for additional capacity can be submitted to CCS Service Desk.

Large Data Transfers

For transferring large datasets:

Use Globus or DTN nodes instead of login nodes.
Transfers using standard tools like scp may be slower or less reliable.