Using nearline storage: Difference between revisions

Using nearline storage (view source)

40 bytes added , 4 years ago

clarify

cc_staff

229

edits

Revision as of 20:18, 6 February 2020 (view source) Diane27 (talk \| contribs) (Marked this version for translation) ← Older edit		Revision as of 19:20, 11 March 2020 (view source) Ppomorsk (talk \| contribs) (clarify) Newer edit →
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 such as 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 such as 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 project quota (instead nearline has its own quota), but they can still be accessed, albeit slower than with the home, scratch and project filesystems.