Differences between revisions 4 and 5
Revision 4 as of 2015-09-21 09:02:24
Size: 1689
Editor: mreimers
Comment:
Revision 5 as of 2015-09-21 09:03:19
Size: 1710
Editor: mreimers
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
 * No data appending (data are invariant)  * No data appending after storing on LTS (data are invariant)

LTS Archive

LTS (Long Term Storage) is an Archive Service hosted by ID. More information about ID's LTS service is given here. Basically LTS works like a WORM file system, i.e "Written Once Read Many".

LTS provides NFS and CIFS Storage as well, but both back ends are autonomous devices, i.e. one might use either NFS or CIFS to store data (not concurrently).

Purpose

The LTS archive system is intended as a final storage for thesis, projects and other invariant data. It's is not a backup system.

Access

Although the LTS Archive is hosted by ID access is granted by ISG only! Due to its design as a long term storage access is provided to nonpersonal accounts only. In practice, each institute or group is entitled to request a special LTS account. The account's credentials are hold by the person in charge, e.g. Professor, group leader or local IT-Admin. In some exceptional cases access is also given to a project account.

For any questions concerning LTS Archive write an email to support@ee.ethz.ch.

Usage

The usage of LTS causes some strict requirements and limitations:

  • Access is either NFS or CIFS (no concurrent access)
  • Data must be packed in an archive (e.g. TAR, ZIP etc.)
  • Data must be collected and prepared in a pre-processing task (best on local scratch disk)
  • File size < 2TB (best between 10 and 200 GB)

  • No data appending after storing on LTS (data are invariant)
  • Non security mechanism against data deletion by mistake
  • Full data deletion is not possible (on request only)
  • Meta information can be stored within file name only

Services/LTSArchiving (last edited 2024-01-29 07:10:40 by mreimers)