Using nearline storage: Difference between revisions

Using nearline storage (view source)

13 bytes removed , 4 years ago

no edit summary

rsnt_translations

56,420

edits

Revision as of 19:20, 11 March 2020 (view source) Ppomorsk (talk \| contribs) (clarify) ← Older edit		Revision as of 20:20, 12 March 2020 (view source) Diane27 (talk \| contribs) No edit summary 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 ~~project quota (instead~~ nearline ~~has its own 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 any of your quotas other than nearline and they can still be accessed, albeit more slowly than with the home, scratch and project filesystems.