Public cloud resources (AWS, Azure, etc.) are excluded from this document. They may represent the best option in almost all cases, if you have ongoing budget to cover the costs.
Note: Research data may not be held ad-infinitum - timeframe for archiving or removal of files varies.
JCU Storage Recommendations (primary copy of data)
|Resiliency: Disk failure(s)||no||yes||yes||no||yes||yes||yes|
|Resiliency: Disasters (e.g., fire)||no||yes||no||no||possibly+||no||yes|
|Resiliency: Silent data corruption||no||yes||no||no||yes||yes||yes|
|Long-term data retention||no||possibly*||no||no||yes||no||yes|
|Intensive I/O work||no||no||yes||yes||no||no||yes#|
IMPORTANT: Personal computing devices are not considered to be a responsible location for housing the primary copy of your research data.
/gpfs01 filesystem has performance to do intensive I/O work, but it is only a cache to data being house in SE Qld.
* Suitability is dependent on configuration of the environment. Consultation with TS staff required.
+ Due to size, several weeks of data could be lost in the event of a disaster.
|Space Quotas||File quota||Notes|
Your quota can be increased by HPC staff.
Full sync to your device(s) may not be possible.
|HPC Cluster: /home||512|
Temporary quota extensions are possible.
|HPC Cluster: /scratch|
Temporary quota extensions are possible. Old data will be deleted.
|HPC Cluster: /fast/tmp||7||In-server SSDs. Automatic deletion of files >=30 days old|
|HPC Cluster: /tmp||0.3||In-server SSDs. Automatic deletion of files >=14 days old|
ARDC Allocation (QCIF)
Merit based approval. 90% usage target for all collections.
Allocation may be reduced/removed if not used.
Best choice for post-JCU access.
@ JCU is likely to purchase significantly more capacity from AARNet (CloudStor) for the housing of research data that isn't likely to be part of a computational research workflow.
Notes: After leaving JCU, you may lose access to your research data. In time, it will be archived to an offsite location prior to local deletion. Current government guidelines only require research data to be retained for 7 years.
Sensitive Data Requirements
Requirements relating to working with sensitive or classified data can incur an extremely high cost. In 2020, JCU discussions around such requirements resulted in a decision to look at out-sourcing of infrastructure to support research in such areas. Key points to note:
- The JCU HPC cluster has not be architected/configured for work on senstive or classified data.
- The JCU network has not been architected/configured for work on sensitive or classified data.
- If you are working with sensitive of classified data, you should notify HPC/eResearch staff.
- Researchers are responsible for ensuring that appropriate controls are in place for any work on sensitive or classified data.
- If you are working with sensitive data it is important that you keep up to date with changing requirements (e.g., if an encryption algorithm is no longer safe).