Child pages
  • Selecting a storage resource that best fits my requirements
Skip to end of metadata
Go to start of metadata

Public cloud resources (AWS, Azure, etc.) are excluded from this document.  They would represent the best option in almost all cases, if you have sufficient budget to pay for the service.

Storage Sizings

The following table shows user "limits" associated with various storage options.  PC values are based on a possible JCU issued machine configuration.


Total StorageDefault Quota(s)Notes

Personal Computer (PC)

varies
NOT a responsible location for research data.
External (e.g., USB)drivesvaries
NOT a responsible location for research data.

CloudStor (AARNet)

10TB (JCU)100GB

Your quota can be increased by HPC staff.  Global visibility.

You may lose access to the data after leaving JCU.

OneDrive (Office365)

Unknown5TB

Full sync to your device(s) may not be possible.  Global visibility.

You may lose access to the data after leaving JCU.

HPC Home Directory512TB

5TB

250K inodes

Temporary quota extensions are possible.  RAID protection + offsite copy.

Data will be archived sometime after you leave JCU.

HPC Scratch Space

80TB


5TB

1M inodes

Temporary quota extensions are possible.  RAID protection only.

Data will be deleted sometime after you leave JCU.

ARDC Allocation (QCIF)

516TBvaries

Merit based approval. 90% usage target for all collections.

Allocation may be reduced/removed if not used.

 Best choice for post-JCU access.


Storage Recommendations (JCU options only)

Research data is not held on JCU infrastructure indefinitely - timeframe for archiving/removal of files varies.

STORAGE LOCATIONPCHPC VMHPC HomesHPC ScratchRDS
Protection against disk failuresNoYesYesYesYes
Protection agains disaster (e.g., fire)NoYesYes*NoYes

Long-term Data Retention (& Access)

NoNoYesNoYes

Intensive IO workloads

?No

No

Yes

No
Sensitive DataNoPossibleNoNoNo

* Due to size, several weeks/months of data could be lost in the event of a disaster.

Sensitive Data Requirements

Physical security is a critical component to the housing of sensitive data.  Generally, a personal computing device will not meet requirements.

Exact requirements vary on a per-case basis.  E.g., PCI DSS compliance is required for credit card information - the JCU network is not compliant and so this sort of information must not be stored on JCU infrastructure.

Researchers are largely responsible for ensuring that they meet requirements associated with storing sensitive data.   Consultation with ICT/HPC staff is highly recommended if you are storing (working on) such data.

Disk level encryption may provide sufficient protection against situation such as stolen device.  File level encryption provides protection while the system is running, but there are some gotchas to be considered.  Consultation with ICT/HPC staff is recommended.

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).

  • No labels