Campuses:
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:department:unix:file_storage [2016/02/02 13:16] – [Backups on Unix] allan | computing:department:unix:file_storage [2016/02/02 13:52] (current) – [sshfs] allan | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| The home directories are backed up nightly, and in addition filesystem " | The home directories are backed up nightly, and in addition filesystem " | ||
| - | ===== Shared | + | ===== Shared |
| - | If you need a shared area for a group or project where multiple people can develop or store code, we can create such an area and back it up for you. These are made available under the ''/ | + | If you need a shared area for a group or project where multiple people can develop or store code, we can create such an area and back it up for you. These are made available under the ''/ |
| - | ===== Research | + | ===== Research |
| - | Other file systems are provided for research or project-specific data, under the **/data** hierarchy. This storage space is **purchased by the research group**. It can take the form of simple single drives in linux workstations, | + | Other file systems are provided for research or project-specific data, under the **/data** hierarchy. This storage space is **purchased by the research group**. It can take the form of simple single drives in linux workstations |
| These file systems are usually named either after the research group group (for a fileserver volume), or with the name of the workstation which hosts it, and contain further directories organized by user or by project. These areas should be used for large data sets and storage for local processes. Note that these areas are provided by the // | These file systems are usually named either after the research group group (for a fileserver volume), or with the name of the workstation which hosts it, and contain further directories organized by user or by project. These areas should be used for large data sets and storage for local processes. Note that these areas are provided by the // | ||
| Line 31: | Line 31: | ||
| * Data areas on our ZFS storage have nightly // | * Data areas on our ZFS storage have nightly // | ||
| * Linux RAID storage does not have snapshots. | * Linux RAID storage does not have snapshots. | ||
| - | * If you have critical research data which requires backup, | + | * If you have critical research data which requires backup, |
| * Local data drives in workstations are **never** backed up. | * Local data drives in workstations are **never** backed up. | ||
| </ | </ | ||
| Line 49: | Line 49: | ||
| - | ===== Remote access to file systems using sshfs ===== | + | ===== Remote access to data ===== |
| - | You can use //fuse// (the userspace filesystem driver) to mount any remote filesystem which you have ssh access to. You can use this to access files from other systems | + | The security model of Unix NFS is too weak to permit exporting it to any systems which are not part of the Physics cluster. Some alternative methods of transferring data include... |
| + | |||
| + | ==== globus ==== | ||
| + | |||
| + | Please see [[: | ||
| + | |||
| + | ==== sshfs ==== | ||
| + | |||
| + | You can use //fuse// (the userspace filesystem driver) to mount any remote filesystem which you have ssh access to. Although this is not a high-performance solution, you can use this to access files from non-Physics linux systems. For example: | ||
| mkdir ~/mnt #create a place to put it, can be called anything you want. | mkdir ~/mnt #create a place to put it, can be called anything you want. | ||