cc_staff
176
edits
Using nearline storage: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(preliminary mention of hsm tools) |
mNo edit summary |
||
| Line 3: | Line 3: | ||
==Nearline is a filesystem virtualized onto tape== <!--T:1--> | ==Nearline is a filesystem virtualized onto tape== <!--T:1--> | ||
Nearline storage is a disk-tape hybrid filesystem with a layout like [[Project layout|Project]], except that it can virtualize files by moving them to tape-based storage on criteria like age and size, and then back again upon read or recall operations. This is a way to manage less used files. On tape, the files do not consume your disk quota, but they can still be accessed, albeit slower than with the home, scratch and project filesystems. | Nearline storage is a disk-tape hybrid filesystem with a layout like [[Project layout|Project]], except that it can virtualize files by moving them to tape-based storage on criteria like age and size, and then back again upon read or recall operations. This is a way to manage less-used files. On tape, the files do not consume your disk quota, but they can still be accessed, albeit slower than with the home, scratch and project filesystems. | ||
<!--T:2--> | <!--T:2--> | ||
This is useful because the capacity of our tape libraries is both large and expandable. When a file has been moved to tape (or ''virtualized''), it still appears in the directory listing. If the virtual file is read, the reading process will block for some time, probably a few minutes, while the file contents is copied from tape to disk. | This is useful because the capacity of our tape libraries is both large and expandable. When a file has been moved to tape (or ''virtualized''), it still appears in the directory listing. If the virtual file is read, the reading process will block for some time, probably a few minutes, while the file contents is copied from tape to disk. | ||
== Expected use == <!--T:3--> | == Expected use == <!--T:3--> | ||