| Both sides previous revision Previous revision Next revision | Previous revision |
| public:cs1_data_policy [2007-09-21 11:40] – grit | public:cs1_data_policy [2017-03-08 15:27] (current) – external edit 127.0.0.1 |
|---|
| |
| Archived data will be moved to GRID based storage servers. Commissioning data will be owned by the /lofar/ops group and stored under the lfc directory /grid/lofar/ops/cs1_data as a tarball. The current policy for this data is that it will be archived on tape in two copies after an unknown period. Please beware that GRID based storage is experimental. At present, no guarantees can be given about data lifetime and retrieval although these issues are being addressed and data security is likely orders of magnitude better than on the central CS1 storage facilities. | Archived data will be moved to GRID based storage servers. Commissioning data will be owned by the /lofar/ops group and stored under the lfc directory /grid/lofar/ops/cs1_data as a tarball. The current policy for this data is that it will be archived on tape in two copies after an unknown period. Please beware that GRID based storage is experimental. At present, no guarantees can be given about data lifetime and retrieval although these issues are being addressed and data security is likely orders of magnitude better than on the central CS1 storage facilities. |
| | |
| |
| |
| ===== CS1 commissioning data (user data) policy ===== | ===== CS1 commissioning data (user data) policy ===== |
| |
| To allow commissioning analysis of datasets and testing of offline processing software, users may request usage of central strorage capacity. Requests should be directed to the CS1 system administrator (Teun Grit). The request should be accompanied by the capacity needed. Further information may be requested by the CS1 system administrator (such as motivation, expected period for which storage capacity is needed, etc). | To allow commissioning analysis of datasets and testing of offline processing software, users may request usage of central strorage capacity. Requests should be directed to the observer on duty (observer at aston dot nl). The request should be accompanied by the capacity needed. Further information may be requested (such as motivation, expected period for which storage capacity is needed, etc). |
| |
| The CS1 system administrator will confirm the allocated storage capacity and the period for which it can be used. If demanded so for operational or commissioning purposes, the CS1 system administrator can ask users to (re) move their data. An overview of data capacity allocated to users is given in the following table:\\ | Operations personnel will confirm the allocated storage capacity and the period for which it can be used. If demanded so for operational or commissioning purposes, operations personnel can ask users to (re) move their data. An overview of data capacity allocated to users is given in the following table:\\ |
| |
| ^ **Useraccount\\ ** ^ **Storage directory\\ ** ^ **Allocated capacity\\ ** ^ **Used capacity\\ (if more) ** ^ **Allocated until\\ ** ^ | ^ **Useraccount\\ ** ^ **Storage directory\\ ** ^ **Allocated capacity\\ ** ^ **Used capacity\\ (if more) ** ^ **Allocated until\\ ** ^ |
| NB1: The CS1 offline storage servers provide storage on "best effort" basis. Data is stored on disks in a RAID striping configuration (for optimal performance) and is not backupped. Any data that is important enough to keep for any period of time should be copied to other systems that provide better data security. | NB1: The CS1 offline storage servers provide storage on "best effort" basis. Data is stored on disks in a RAID striping configuration (for optimal performance) and is not backupped. Any data that is important enough to keep for any period of time should be copied to other systems that provide better data security. |
| |
| NB2: There is no software used for accounting of storage capacity. Please check the used capacity yourself. Manual checks will be carried out by the CS1 system administrator regularly, in particular in situations where the available storage capacity becomes too small to allow planned operations and commissioning. Offenders will be notified and prompt action is expected in that case. In case there is no response, corrective actions may be taken by the CS1 system administrator including, ultimately, removal of data. Offending users may be "named and shamed". | NB2: There is no software used for accounting of storage capacity. Please check the used capacity yourself. Manual checks will be carried out by operations personnel regularly, in particular in situations where the available storage capacity becomes too small to allow planned operations and commissioning. Offenders will be notified and prompt action is expected in that case. In case there is no response, corrective actions may be taken by operations personnel including, ultimately, removal of data. Offending users may be "named and shamed". |
| |
| |