Actions

Difference between revisions of "File and I/O Management"

From ALICE Documentation

(Created page with "== File and I/O Management == The file system is one of the critical components to the service and users should aim to make the best use of the resources. This chapter detail...")
 
(File and I/O Management)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
== File and I/O Management ==  
+
= File and I/O Management =
The file system is one of the critical components to the service and users should aim to make the best use of the resources. This chapter details the differing file systems in use, the best practices for I/O, and basic housekeeping of your files.
+
The file system is one of the critical components to the service and users should aim to make the best use of the resources. This chapter details the different file systems in use, the best practices for reading and writing data (I/O), and basic housekeeping of your files.
 +
 
 +
{{:Data Storage Policy}}

Latest revision as of 13:58, 2 October 2020

File and I/O Management

The file system is one of the critical components to the service and users should aim to make the best use of the resources. This chapter details the different file systems in use, the best practices for reading and writing data (I/O), and basic housekeeping of your files.

Data Storage Policy

ALICE does not provide support for any type of controlled data. No controlled data (GDPR, HIPAA, EAR, FERPA, PII, CUI, ITAR, etc.) can be analysed or stored on any HPC storage. Users must not transfer sensitive data (data related to people) to ALICE. Data must be anonymized before it can be transferred to ALICE. In case you are unsure about the contents/classification of the data, please contact the helpdesk.

ALICE is not a datamanagement system where research data can be stored for longer periods of time. All data that is transferred to ALICE must be copies of data. Users must make sure that data that is transferred to ALICE remains available somewhere else. All data with value that is generated on ALICE must be moved off ALICE as soon as this is possible after the job completed.

Data in the user’s home directory is backed up (see Backup & Restore). The home directory is intended to store scripts, software, executables etc, but is not meant to store large or temporary data sets.