Using nearline storage: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 20: Line 20:
<FILE>: [...]: released archived, [...]
<FILE>: [...]: released archived, [...]
</source>
</source>
"HSM" stands for "hierarchical storage manager". If you wish to ensure that the file is brought in from tape, you can use
lfs hsm_restore <FILE>
The difference with reading the file is that the restore would be implicitly done.


== Using nearline == <!--T:3-->
== Using nearline == <!--T:3-->
Line 35: Line 39:
* After a further period, the disk copy will be dropped, and the file will only be on tape (our policy is two tape copies: one local and one remote).  At this point, the file will be slow to read, since content must be recalled from tape.
* After a further period, the disk copy will be dropped, and the file will only be on tape (our policy is two tape copies: one local and one remote).  At this point, the file will be slow to read, since content must be recalled from tape.
* When such a file is recalled, it returns to the second state.
* When such a file is recalled, it returns to the second state.
<!--T:23-->
Thus, you may wish to inquire about the status of a nearline file:
lfs hsm_state ~/nearline/def-mine/user/somefile
("HSM" stands for "hierarchical storage manager".)  Normally, if you wish to use a file in Nearline, you can treat it as a normal file (just read/write it).  If you wish to ensure that the file is brought in from tape, you can also use
lfs hsm_restore ~/nearline/def-mine/user/somefile
The only difference is that reading the file does the restore implicitly.


== Access == <!--T:6-->
== Access == <!--T:6-->
cc_staff
127

edits

Navigation menu