|
Size: 3192
Comment:
|
Size: 3606
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = Data Archiving on Jabba = | = Data archiving on jabba = |
| Line 6: | Line 6: |
| == Overview == All data you put on our data archiving system will we stored on tape drives. Like this the archive system can hold a large amount of data. The downside is that read and write operations are slow since the tape roboter has to physically grab the right tapes to handle your data. Thus, you should not use jabba for data you use daily. But if you have a huge amount of simulation data that you might need in some weeks, jabba would be a good place to take care of them. |
|
| Line 7: | Line 9: |
| == Jabba Usage == For using the system, you must have an account on Jabba. Contact your system manager and ask him for such an account. If you have an account, Jabba can be accessed via NFS: {{{ /usr/jabba/backup/<institute>/<username> |
== Usage == ==== Access rights ==== We will have to give the proper rights to your account before you will be able to use jabba. Please write an email to support@ee.ethz.ch if you need access to our data archiving system (include your Linux workstation's name for NFS access as well). Permission will be granted to D-ITET staff members only, no access for students. ==== How to access jabba ==== As soon as access is granted, you have the following options to get/put data from/to the archiving system: * NFS (preferred on Linux): `/usr/jabba/archive/INSTITUTE/USERNAME` or `/usr/jabba/backup/INSTITUTE/USERNAME` * Samba or MS Windows Network Map: `\\jabba\USERNAME` * OpenSSH: `scp` ==== Important notes ==== Please follow these rules when storing data on jabba: * '''Only write big archive files (`.tar.gz, .zip, ...`) to jabba, not many small files'''. * The ideal size of these archive files is between 5 and 10 Gigabytes. * Don't create archive files bigger than 20 Gigabytes. * Take care when you delete files. You are working on the backup system and there is no further backup of these data. * Only put data into the `archive` or `backup` folder. ==== Differences between storage areas ==== * '''archive''' : Files within the archive directory will be stored on '''one tape and one disk''', five minutes after the last modification. * '''backup''' : Files within the backup directory will be saved to '''one tape''', 30 minutes after their last modification on harddisk. In both cases the cached files on harddisk will be deleted only if the threshold of free disk space on the partition is reached. == Usage examples == * Backup `Pictures` folder via NFS: {{{ tar cfv - Pictures | /usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/backup/tik/USERNAME/Pictures.tar }}} * Archive `Pictures` folder with ssh: {{{ tar cfv - Pictures | ssh jabba "/usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/backup/tik/USERNAME/Pictures.tar }}} '''Note:''' The usage through NFS/Samba is preferred since above command creates excessive CPU load on the archive system. * Assume you had a tar archive split in multiple parts (000 to XXX) and want to get them via NFS and unpack it in scratch: {{{ cd /scratch cat /usr/jabba/backup/tik/USERNAME/Pictures.tar_* | tar xvf - |
| Line 13: | Line 58: |
| Please note the following: * Jabba is a huge file system and should not be used as a one-one copy of your files. Please use tar or zip to store your backups and archives. * Files should not be bigger then 5 to 10 GB. (Under Windows you can use winzip to split the files.) |
== Advanced usage == The data transfer between harddisk and tape storage can be influenced with the commands below. You have to be logged in on jabba through SSH to use these commands. Please consult the man pages for further details. |
| Line 17: | Line 61: |
| To backup/archive your files via NFS, do the following: {{{ tar cfv - <Directory> | /usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/archive/tik/hans/file.tar }}} To archive/backup your files, you can use the following alternatives: * Via Samba ('''\\jabba\[username]''') * By remote-copy ('''scp''') * Via ftp (not recommended) * and via ssh Via ssh, archiving your files can done the following way: <<BR>> '''Note:''' If you have an official account you should prefer the NFS-way. Because the ssh-way causes to much load on 'jabba'! {{{ tar cfv - [Directory] | ssh jabba "/usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/archive/tik/hans/file.tar" }}} == Two different storage areas are provided == * '''archive''' : Every file you put into the archive directory (partition) will be stored twice on two tapes, 5 minutes after the last modification. * '''backup''' : Files write into the backup directory (partition) will only be saved to one tape and 30 minutes after their last modification on harddisk. In both cases the files on harddisk will be deleted (after storage on tape) only if the threshold of free disk space on the partition is reached. The idea of this two methods of storage is, that you can define how much security you need for your data by choosing the name of the directory. There are several methods to transport the files to the jabba. You can use '''ftp''', '''ssh''' (secure shell) or '''scp''' (secure copy) or your system manager can mount the directories on jabba using NFS on your own machine. If you want retrieve your files, its only necessary that you call it in the appropriate directory. If the inode leaves on the harddisk (even when the file is stored on tape and deleted on harddisk), the filename leave in the directory and will recopied automatically from tape to the harddisk when you call it. == User commands == The data transfer between harddisk and tape storage can be influenced with the following commands: '''-sls '''''an extended version of GNU ls for listing directory information'' '''-sdu '''''an extended version of GNU du'' '''-archive '''''set archive attributes and archive files'' '''-release '''''release disk space and set release attributes'' '''-stage '''set staging attributes and copy off-line files to harddisk '''-ssum '''''set file checksum attributes'' Note: You must be logged in on Jabba to use these commands. Certain options are only available to the super user. Please consult the man pages on Jabba for more detailed information. |
|| ''Command'' || ''Description'' || || `sls` || An extended version of GNU ls for listing directory information || || `sdu` || An extended version of GNU du || || `archive` || Set archive attributes and archive files || || `release` || Release disk space and set release attributes || || `stage` || Set staging attributes and copy off-line files to harddisk || || `ssum` || Set file checksum attributes || ---- [[CategoryBKUP]] |
Data archiving on jabba
Overview
All data you put on our data archiving system will we stored on tape drives. Like this the archive system can hold a large amount of data. The downside is that read and write operations are slow since the tape roboter has to physically grab the right tapes to handle your data. Thus, you should not use jabba for data you use daily. But if you have a huge amount of simulation data that you might need in some weeks, jabba would be a good place to take care of them.
Usage
Access rights
We will have to give the proper rights to your account before you will be able to use jabba. Please write an email to support@ee.ethz.ch if you need access to our data archiving system (include your Linux workstation's name for NFS access as well). Permission will be granted to D-ITET staff members only, no access for students.
How to access jabba
As soon as access is granted, you have the following options to get/put data from/to the archiving system:
NFS (preferred on Linux): /usr/jabba/archive/INSTITUTE/USERNAME or /usr/jabba/backup/INSTITUTE/USERNAME
Samba or MS Windows Network Map: \\jabba\USERNAME
OpenSSH: scp
Important notes
Please follow these rules when storing data on jabba:
Only write big archive files (.tar.gz, .zip, ...) to jabba, not many small files.
- The ideal size of these archive files is between 5 and 10 Gigabytes.
- Don't create archive files bigger than 20 Gigabytes.
- Take care when you delete files. You are working on the backup system and there is no further backup of these data.
Only put data into the archive or backup folder.
Differences between storage areas
archive : Files within the archive directory will be stored on one tape and one disk, five minutes after the last modification.
backup : Files within the backup directory will be saved to one tape, 30 minutes after their last modification on harddisk.
In both cases the cached files on harddisk will be deleted only if the threshold of free disk space on the partition is reached.
Usage examples
Backup Pictures folder via NFS:
tar cfv - Pictures | /usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/backup/tik/USERNAME/Pictures.tar
Archive Pictures folder with ssh:
tar cfv - Pictures | ssh jabba "/usr/isgtc/bin/tubasplit --size 5056 /usr/jabba/backup/tik/USERNAME/Pictures.tar
Note: The usage through NFS/Samba is preferred since above command creates excessive CPU load on the archive system.
- Assume you had a tar archive split in multiple parts (000 to XXX) and want to get them via NFS and unpack it in scratch:
cd /scratch cat /usr/jabba/backup/tik/USERNAME/Pictures.tar_* | tar xvf -
Advanced usage
The data transfer between harddisk and tape storage can be influenced with the commands below. You have to be logged in on jabba through SSH to use these commands. Please consult the man pages for further details.
Command |
Description |
sls |
An extended version of GNU ls for listing directory information |
sdu |
An extended version of GNU du |
archive |
Set archive attributes and archive files |
release |
Release disk space and set release attributes |
stage |
Set staging attributes and copy off-line files to harddisk |
ssum |
Set file checksum attributes |