Group and Project Files

Group and Project Disk

• Files which need to be accessed by members of a group or project should be stored in that project's or group's own filesystems.
• For more information about your project's filesystems, contact your supervisor, project or group leader, or your group's internal documentation. They know where the appropriate space is, which filesystems are backed up, and what other special characteristics they might have. For example, some filesystems can be accessed only if special arrangements have been made or if you're a member of a particular group.
• See also CLASSE Filesystems for a listing of CLASSE file systems accessible over Samba and NFS

Backed-up Project Space

• Files which are difficult to recreate (e.g. program source code) should be kept in your project's backed up filesystem.
• Backed-up project filesystems usually have significantly larger quotas than your personal home directory, but still are limited because of the expense in maintaining its backups.
• For a list of backed-up filesystems, please see BackupSchedule.

Not-Backed-up Project Space

• Files wich are relatively easy to recreate (e.g. by re-running an analysis program) should be kept in your project's non-backed-up filesystem.
• Project data filesystems usually do not have disk space quotas affecting individuals, but may have a limited total capacity.