cc_staff
290
edits
Data management at Niagara: Difference between revisions
Jump to navigation
Jump to search
m
→/project
No edit summary |
m (→/project) |
||
| Line 17: | Line 17: | ||
=== /project === | === /project === | ||
/project is intended for common group software, large static datasets, or any material very costly to be reacquired or re-generated by the group. <font color=red>Material on /project is expected to | /project is intended for common group software, large static datasets, or any material very costly to be reacquired or re-generated by the group. <font color=red>Material on /project is expected to remain relatively immutable over time.</font> Temporary or transient files should be kept on scratch, not project. High data turnover induces stress and unnecessary consumption tapes on the TSM backup system, long after this material has been deleted, due to backup retention policies and the extra versions kept of the same file. Even renaming top directories is enough to trick the system into assuming a completely new directory tree has been created, and the old one deleted, hence think carefully about your naming convention ahead of time, and stick with it. Users abusing the project file system and using it as scratch will be flagged and contacted. Note that on niagara /project is only available to groups with RAC allocation. | ||
=== /bb (burst buffer) === | === /bb (burst buffer) === | ||