rsnt_translations
56,420
edits
No edit summary |
No 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 | Nearline storage is a disk-tape hybrid filesystem with a layout like [[Project layout|Project]], except that it may 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 more slowly. | ||
<!--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 ( | 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 are read from tape to disk. | ||
== Expected use | == Expected use == <!--T:3--> | ||
Because of the delay in reading from tape, Nearline is not intended to be used by jobs | Because of the delay in reading from tape, Nearline is not intended to be used by jobs where allocated time would be wasted. It is only accessible as a directory on certain nodes of the clusters, and in particular, not on the compute nodes. | ||
<!--T:9--> | <!--T:9--> | ||
Nearline is intended for use with relatively large files | Nearline is intended for use with relatively large files and should not be used for large numbers of small files. In fact, files smaller than a certain threshold size may not be moved to tape at all. Files smaller than ~200MB should be combined into archive files (''tarballs'') using [[Archiving and compressing files|tar]] or a similar tool. | ||
<!--T:5--> | <!--T:5--> | ||
Line 28: | Line 28: | ||
<!--T:8--> | <!--T:8--> | ||
If you remove a file | If you remove a file from <tt>~/nearline</tt>, the tape copy will be retained for up to 60 days. To restore such a file, contact [[technical support]] with the full path for the file(s) and desired version (by date), just as you would for [[Storage and file management#Filesystem quotas and policies|backup]] restoration. Note that since you will need the full path for the file, it is important for you to retain a copy of the complete directory structure of your Nearline space. For example, you can run the command <tt>ls -R > ~/nearline_contents.txt</tt> from the <tt>~/nearline/PROJECT</tt> directory so that you have a copy of the location of all the files in your Nearline space. | ||
</tab> | </tab> | ||
<!--T:16--> | <!--T:16--> | ||
<tab name="Cedar"> | <tab name="Cedar"> | ||
Nearline service | Nearline service will be available soon. | ||
</tab> | </tab> | ||
<!--T:17--> | <!--T:17--> | ||
<tab name="Niagara"> | <tab name="Niagara"> | ||
There are three | There are three methods to access Nearline on Niagara: | ||
<!--T:12--> | <!--T:12--> | ||
1. By submitting | 1. By submitting HPSS-specific commands <tt>htar</tt> or <tt>hsi</tt> as an 'archive' job to the Slurm scheduler; see [https://docs.scinet.utoronto.ca/index.php/HPSS the HPSS documentation] for detailed examples. Using job scripts offer the benefit of automating Nearline transfers and is the best method if you use HPSS regularly. | ||
<!--T:13--> | <!--T:13--> | ||
2. For small data management of files in HPSS, you can use the VFS ( | 2. For small data management of files in HPSS, you can use the VFS (''Virtual File System'') node, which is accessed with the command: <tt>salloc --time=1:00:00 -pvfsshort</tt>. | ||
<!--T:14--> | <!--T:14--> | ||
3. | 3. By using [[Globus]] for transfers to and from HPSS using the endpoint <b>computecanada#hpss</b>. This is useful for occasional usage and for transfers from other sites. | ||
<!--T:15--> | <!--T:15--> |