- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
Storage usage policy: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page describe how to handle data within HLRS computing environment. | This page describe how to handle data within HLRS computing environment. | ||
Please be aware, storage ressources are are optimized for bandwidth of large parallel IO operations. This requires lots of components like disks, controllers, network connections, ... and make it expensive. | Please be aware, storage ressources are are optimized for bandwidth of large parallel IO operations. This requires lots of components like disks, controllers, network connections, ... and make it expensive. To get the maximum | ||
benefit for all Users, following extra short guidlines should be read. | |||
No Backup on any filesystem. Please copy important data into the archive. | |||
Storge ressources are overcommitted, this means the disk quota is not equal with a grant of storage space. (This is also true for compute ressources) | |||
Revision as of 10:00, 11 October 2016
This page describe how to handle data within HLRS computing environment.
Please be aware, storage ressources are are optimized for bandwidth of large parallel IO operations. This requires lots of components like disks, controllers, network connections, ... and make it expensive. To get the maximum benefit for all Users, following extra short guidlines should be read.
No Backup on any filesystem. Please copy important data into the archive.
Storge ressources are overcommitted, this means the disk quota is not equal with a grant of storage space. (This is also true for compute ressources)